Re: own defined step and xml:base "inheritance"

Thank you Florent.

Actually my first attempt was to use "java -cp", but as it didn't worked, I
switch to java -jar.

This is my batch script (made as simple as possible, no catalog, no
calabash.logging.properties file) :

runCalabash-1.0.16-95.bat
--------------------------------------------
@ECHO OFF

SET currentpath=%~dp0
SET _CALABASH_PATH=%currentpath%calabash-1.0.16-95\

SET _CLASSPATH=%_CALABASH_PATH%calabash.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\commons-codec-1.6.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\commons-io-1.3.1.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\commons-logging-1.1.1.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\httpclient-4.2.5.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\httpcore-4.2.4.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\httpmime-4.2.5.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\saxon9he.jar
SET _CLASSPATH=%_CLASSPATH%;%_CALABASH_PATH%lib\xmlresolver.jar


SET JAVAOPT=-Xms512m -Xmx1024m -Dcom.xmlcalabash.phonehome="false"
-classpath "%_CLASSPATH%"
SET CALABASHOPT=--debug -b igs=http://www.igs-cp.fr

SET RUN_CALABASH=java %JAVAOPT% com.xmlcalabash.drivers.Main %CALABASHOPT%

REM Slurp the command line arguments.
SET CMD_LINE_ARGS=%*

@ECHO ON
%RUN_CALABASH% %CMD_LINE_ARGS%
@ECHO OFF

Which I call like this from the command line :
CALL runCalabash-1.0.16-95.bat test_static-uri.xpl

Always the same problem : the pipeline is processed without ending (more
than 10min before I kill it)

which I also have when loading something like :
CALL runCalabash-1.0.16-95.bat  -o result=out.xml -i source=in.xml -l
profile.xpl -s igs:xml2ecf

I also tries with no specific "CALABASHOPT", same result.

When running the "Hello World" pipe.xpl given with Calabash distrib
everything works quite well :
CALL runCalabash-1.0.16-95.bat calabash-1.0.16-95\xpl\pipe.xpl
<doc>Congratulations! You've run your first pipeline!</doc>

That's really strange, am I the only one to have such a problem ?

I have to switch to something else, will give a try at the end of the week.

Cheers,
Matthieu


2013/12/17 Florent Georges <fgeorges@fgeorges.org>

>   Well, the first step is probably to fix your installation.  Try to
> have a complete repro, you already have the pipeline, you only have to
> install all JAR files in a directory, and use a Java command line not
> using "-jar" but with an explicit "-cp" and class name (just to be
> sure there is no hidden Java black magic happening here).
>
>   Regards,
>
> --
> Florent Georges
> http://fgeorges.org/
> http://h2oconsulting.be/
>
>
> On 17 December 2013 09:58, RICAUD-DUSSARGET Matthieu wrote:
> > Hi,
> >
> > Well it seems I have some problem with my Calabash installations.
> >
> > As I'm testing things with xproc i have 3 differents calabash launcher.
> >
> > These are the result of running your simple pipeline :
> >
> > 1) launcher "Calabash1.0.16" : the pipeline never ends up ??
> > command line > java -Xms512m -Xmx1024m
> -Dcom.xmlcalabash.phonehome="false"
> > -jar
> J:\info_editoriale\XML_EDITORIAL\Recherche_et_Developpement\xproc\_de
> > v\calabash-1.0.16-95\calabash.jar  _test\test_static-uri.xpl
> >
> > I have to look what's happen here, this is really strange ! see my other
> > post at http://markmail.org/thread/ih72ahgckiuejb4o
> >
> > 2) launcher "Calabash version 1.0.3 (for Saxon 9.4.x)" : it works fine :)
> >
> > 3) launcher "calabash_0.9.15" :
> > => error parsing xproc : Attribute not allowed: version => ok I delete it
> > => Unexpected step name: p:template => just like what my oXygen 12.2 says
> >
> > Well it seems xproc syntax (DTD?) has changed with the time, I have to
> make
> > my tools ready for 1.0.
> >
> > I find it hard dealing with xproc sometimes, but keep the faith !
> >
> > Cheers
> > Matthieu
> >
> >
> >
> > 2013/12/16 Florent Georges <fgeorges@fgeorges.org>
> >>
> >> On 16 December 2013 17:29, RICAUD-DUSSARGET Matthieu wrote:
> >>
> >> > Seems like static-base-uri() is always empty, equal where I call it
> >> > from.
> >>
> >>   Weird.  The following pipeline outputs correctly a <uri> element
> >> with the URI of the pipeline document.  How do you run your pipeline?
> >>
> >>     <p:pipeline xmlns:p="http://www.w3.org/ns/xproc" version="1.0">
> >>        <p:template>
> >>           <p:with-param name="uri" select="static-base-uri()"/>
> >>           <p:input port="template">
> >>              <p:inline>
> >>                 <uri>{ $uri }</uri>
> >>              </p:inline>
> >>           </p:input>
> >>        </p:template>
> >>     </p:pipeline>
> >>
> >>   Regards,
> >>
> >> --
> >> Florent Georges
> >> http://fgeorges.org/
> >> http://h2oconsulting.be/
> >
> >
> >
> >
> > --
> > Matthieu Ricaud-Dussarget
> > IGS-CP - Développeur XML
> > 05 45 37 09 49
>



-- 
Matthieu Ricaud-Dussarget
IGS-CP - Développeur XML
05 45 37 09 49