Re: XSLT import/include errors

[Jos Snellings]

OK, having a short look for:


later today



On Mon, Jun 24, 2013 at 10:05 AM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:

>  On 24/06/2013 09:57, Jos Snellings wrote:
>
>Hi Francesco et al,
>
>  Good idea. Where would you put the lever to switch LRU cache on/off?
>  - sitemap?
>  - cocoon spring configuration files?
>
>
> +1 for settings - as currently done for sitemap reload, for example.
>
> Regards.
>
>
>   So, the context is limited to developers who want to keep seeing
> instant results ...
>
> Cheers,
>  Jos
>
>  On Mon, Jun 24, 2013 at 9:43 AM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>> On 22/06/2013 11:25, gelo1234 wrote:
>>
>>>  And of course I'm using noncaching pipeline :)
>>>
>>> When I make a change in the main XSL file (that from sitemap), the
>>> change is visible.
>>> When I make a change in any of the imported/included (from main XSL) XSL
>>> file, the change is not visible. Cocoon serves
>>>  the Content from cache.-- Francesco Chicchiriccò ASF Member, Apache
>>> Syncope PMC chair, Apache Cocoon PMC Member
>>> http://people.apache.org/~ilgrosso/
>>>
>>
>> Hi,
>> this has nothing to do with pipeline caching: with pipeline caching, the
>> whole pipeline execution is cached (in memory, by default) and thus
>> subsequent calls to the same pipeline won't trigger any pipeline component
>> execution.
>>
>> What is causing you headaches (same did to me) is a local LRU cache
>> managed by some SAX components, including the XSLTTransformer [1]; as you
>> can see from the load() method, in fact, only the last modified timestamp
>> of the main XSLT file is taken into account for deciding whether the cached
>> template should be read.
>>
>> The local LRU cache is very useful in production but very annoying during
>> development: I guess it should stay enabled by default - as currently - but
>> also given the possibility to switch it off via some configuration
>> parameter: who wants to file an issue on JIRA and provide a patch? ;-)
>>
>> Regards.
>>
>> [1]
>> http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/component/XSLTTransformer.java
>>
>--
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC 
> Memberhttp://people.apache.org/~ilgrosso/
>
>


-- 
We should be careful to get out of an experience only the wisdom that is
in it - and stay there, lest we be like the cat that sits down on a hot
stove-lid.  She will never sit down on a hot stove-lid again - and that
is well; but also she will never sit down on a cold one any more.
-- Mark Twain
 

Re: XSLT import/include errors

[Francesco Chicchiriccò]

On 24/06/2013 09:57, Jos Snellings wrote:

Hi Francesco et al,

Good idea. Where would you put the lever to switch LRU cache on/off?
- sitemap?
- cocoon spring configuration files?


+1 for settings - as currently done for sitemap reload, for example.

Regards.

So, the context is limited to developers who want to keep seeing 
instant results ...


Cheers,
Jos

On Mon, Jun 24, 2013 at 9:43 AM, Francesco Chicchiriccò 
mailto:ilgro...@apache.org>> wrote:


On 22/06/2013 11:25, gelo1234 wrote:

And of course I'm using noncaching pipeline :)

When I make a change in the main XSL file (that from sitemap),
the change is visible.
When I make a change in any of the imported/included (from
main XSL) XSL file, the change is not visible. Cocoon serves
the Content from cache.-- Francesco Chicchiriccò ASF Member,
Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



Hi,
this has nothing to do with pipeline caching: with pipeline
caching, the whole pipeline execution is cached (in memory, by
default) and thus subsequent calls to the same pipeline won't
trigger any pipeline component execution.

What is causing you headaches (same did to me) is a local LRU
cache managed by some SAX components, including the
XSLTTransformer [1]; as you can see from the load() method, in
fact, only the last modified timestamp of the main XSLT file is
taken into account for deciding whether the cached template should
be read.

The local LRU cache is very useful in production but very annoying
during development: I guess it should stay enabled by default - as
currently - but also given the possibility to switch it off via
some configuration parameter: who wants to file an issue on JIRA
and provide a patch? ;-)

Regards.

[1]

http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/component/XSLTTransformer.java


--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

Re: XSLT import/include errors

[Jos Snellings]

Hi Francesco et al,

Good idea. Where would you put the lever to switch LRU cache on/off?
- sitemap?
- cocoon spring configuration files?

So, the context is limited to developers who want to keep seeing instant
results ...

Cheers,
Jos




On Mon, Jun 24, 2013 at 9:43 AM, Francesco Chicchiriccò  wrote:

> On 22/06/2013 11:25, gelo1234 wrote:
>
>> And of course I'm using noncaching pipeline :)
>>
>> When I make a change in the main XSL file (that from sitemap), the change
>> is visible.
>> When I make a change in any of the imported/included (from main XSL) XSL
>> file, the change is not visible. Cocoon serves
>> the Content from cache.-- Francesco Chicchiriccò ASF Member, Apache
>> Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~**
>> ilgrosso/ 
>>
>
> Hi,
> this has nothing to do with pipeline caching: with pipeline caching, the
> whole pipeline execution is cached (in memory, by default) and thus
> subsequent calls to the same pipeline won't trigger any pipeline component
> execution.
>
> What is causing you headaches (same did to me) is a local LRU cache
> managed by some SAX components, including the XSLTTransformer [1]; as you
> can see from the load() method, in fact, only the last modified timestamp
> of the main XSLT file is taken into account for deciding whether the cached
> template should be read.
>
> The local LRU cache is very useful in production but very annoying during
> development: I guess it should stay enabled by default - as currently - but
> also given the possibility to switch it off via some configuration
> parameter: who wants to file an issue on JIRA and provide a patch? ;-)
>
> Regards.
>
> [1] http://svn.apache.org/repos/**asf/cocoon/cocoon3/trunk/**
> cocoon-sax/src/main/java/org/**apache/cocoon/sax/component/**
> XSLTTransformer.java
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/
>
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@cocoon.**apache.org
> For additional commands, e-mail: users-h...@cocoon.apache.org
>
>


-- 
We should be careful to get out of an experience only the wisdom that is
in it - and stay there, lest we be like the cat that sits down on a hot
stove-lid.  She will never sit down on a hot stove-lid again - and that
is well; but also she will never sit down on a cold one any more.
-- Mark Twain
 

Re: XSLT import/include errors

[Francesco Chicchiriccò]

On 22/06/2013 11:25, gelo1234 wrote:

And of course I'm using noncaching pipeline :)

When I make a change in the main XSL file (that from sitemap), the 
change is visible.
When I make a change in any of the imported/included (from main XSL) 
XSL file, the change is not visible. Cocoon serves
the Content from cache.-- Francesco Chicchiriccò ASF Member, Apache 
Syncope PMC chair, Apache Cocoon PMC Member 
http://people.apache.org/~ilgrosso/


Hi,
this has nothing to do with pipeline caching: with pipeline caching, the 
whole pipeline execution is cached (in memory, by default) and thus 
subsequent calls to the same pipeline won't trigger any pipeline 
component execution.


What is causing you headaches (same did to me) is a local LRU cache 
managed by some SAX components, including the XSLTTransformer [1]; as 
you can see from the load() method, in fact, only the last modified 
timestamp of the main XSLT file is taken into account for deciding 
whether the cached template should be read.


The local LRU cache is very useful in production but very annoying 
during development: I guess it should stay enabled by default - as 
currently - but also given the possibility to switch it off via some 
configuration parameter: who wants to file an issue on JIRA and provide 
a patch? ;-)


Regards.

[1] 
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/component/XSLTTransformer.java


--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/


-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail: users-h...@cocoon.apache.org

Re: XSLT import/include errors

[gelo1234]

And of course I'm using noncaching pipeline :)

When I make a change in the main XSL file (that from sitemap), the change
is visible.
When I make a change in any of the imported/included (from main XSL) XSL
file, the change is not visible. Cocoon serves
the Content from cache.

Greetings,
Greg


2013/6/22 gelo1234 

> The same problem appears with Saxon (any version).
>
> I think its rather C3 issue not XSLT engine.
>
> Greetings,
> Greg
>
>
>
> 2013/6/22 Javier Puerto 
>
>> Hi Greg,
>>
>> Did you tried yourself with Saxon? I had caching issues with Xalan but
>> never tried with Saxon before.
>>
>> Salu2.
>> El 22/06/2013 10:34, "gelo1234"  escribió:
>>
>> Now when everything is up and working fine, the really ennoying part of
>>> C3 is caching imported/included XSL files.
>>>
>>> Is there any way to invalidate that cache ? Or to turn if off ?
>>>
>>> I wouldn't like to restart the application server every time I make a
>>> small change inside imported/included XSL file :(
>>>
>>> Greetings,
>>> Greg
>>>
>>>
>>> 2013/6/21 gelo1234 
>>>
>>>> Solution: If you want to call Java functions freely from C3 XSLT, use
>>>> older Saxon implementation.
>>>> Version 9.1 works perfectly!
>>>>
>>>> Greetings,
>>>> Greg
>>>>
>>>>
>>>> 2013/6/21 gelo1234 
>>>>
>>>>> Looks like Saxon-HE doesn't support anymore calling Java functions
>>>>> that way:
>>>>>
>>>>>
>>>>> http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html
>>>>>
>>>>> But there are available in PE and EE versions, huh
>>>>>
>>>>> Greetings,
>>>>> Greg
>>>>>
>>>>>
>>>>>
>>>>> 2013/6/21 gelo1234 
>>>>>
>>>>>> Thanks for the tip. Unfortunately it doesn't work with:
>>>>>> Saxon-HE-9.5.0.2.jar :(
>>>>>>
>>>>>> Greetings,
>>>>>> Greg
>>>>>>
>>>>>>
>>>>>> 2013/6/21 Robby Pelssers 
>>>>>>
>>>>>>>  That is possible but the how-to part depends on the Saxon version
>>>>>>> you are using.  You will need to dive into how to write extension 
>>>>>>> functions
>>>>>>> for that particular implementation.
>>>>>>>
>>>>>>>  I used it a number of times with Saxon 8.7
>>>>>>>
>>>>>>>
>>>>>>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>>>>>>
>>>>>>>
>>>>>>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>>>>>>
>>>>>>>  But i never tried with the latest version of Saxon which works
>>>>>>> differently.
>>>>>>>
>>>>>>>  Robby
>>>>>>>  --
>>>>>>> *Van:* gelo1234 [gelo1...@gmail.com]
>>>>>>> *Verzonden:* vrijdag 21 juni 2013 15:23
>>>>>>> *To:* Cocoon Users
>>>>>>> *Onderwerp:* Re: XSLT import/include errors
>>>>>>>
>>>>>>>  OK, one more question. Is it possible with Saxon/Xalan in C3
>>>>>>> to invoke external Java function ?
>>>>>>> I can't get it working:
>>>>>>>
>>>>>>> http://www.w3.org/1999/XSL/Transform";
>>>>>>> version="1.0"
>>>>>>> xmlns:utils="java:org.example.Utils"
>>>>>>> exclude-result-prefixes="utils">
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>   
>>>>>>>
>>>>>>>   
>>>>>>> >>>>>> select="utils:exists($fileName)"/>
>>>>>>>   
>>>>>>>  
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>  Tried Xalan,

Re: XSLT import/include errors

[gelo1234]

The same problem appears with Saxon (any version).

I think its rather C3 issue not XSLT engine.

Greetings,
Greg



2013/6/22 Javier Puerto 

> Hi Greg,
>
> Did you tried yourself with Saxon? I had caching issues with Xalan but
> never tried with Saxon before.
>
> Salu2.
> El 22/06/2013 10:34, "gelo1234"  escribió:
>
> Now when everything is up and working fine, the really ennoying part of C3
>> is caching imported/included XSL files.
>>
>> Is there any way to invalidate that cache ? Or to turn if off ?
>>
>> I wouldn't like to restart the application server every time I make a
>> small change inside imported/included XSL file :(
>>
>> Greetings,
>> Greg
>>
>>
>> 2013/6/21 gelo1234 
>>
>>> Solution: If you want to call Java functions freely from C3 XSLT, use
>>> older Saxon implementation.
>>> Version 9.1 works perfectly!
>>>
>>> Greetings,
>>> Greg
>>>
>>>
>>> 2013/6/21 gelo1234 
>>>
>>>> Looks like Saxon-HE doesn't support anymore calling Java functions that
>>>> way:
>>>>
>>>>
>>>> http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html
>>>>
>>>> But there are available in PE and EE versions, huh
>>>>
>>>> Greetings,
>>>> Greg
>>>>
>>>>
>>>>
>>>> 2013/6/21 gelo1234 
>>>>
>>>>> Thanks for the tip. Unfortunately it doesn't work with:
>>>>> Saxon-HE-9.5.0.2.jar :(
>>>>>
>>>>> Greetings,
>>>>> Greg
>>>>>
>>>>>
>>>>> 2013/6/21 Robby Pelssers 
>>>>>
>>>>>>  That is possible but the how-to part depends on the Saxon version
>>>>>> you are using.  You will need to dive into how to write extension 
>>>>>> functions
>>>>>> for that particular implementation.
>>>>>>
>>>>>>  I used it a number of times with Saxon 8.7
>>>>>>
>>>>>>
>>>>>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>>>>>
>>>>>>
>>>>>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>>>>>
>>>>>>  But i never tried with the latest version of Saxon which works
>>>>>> differently.
>>>>>>
>>>>>>  Robby
>>>>>>  --
>>>>>> *Van:* gelo1234 [gelo1...@gmail.com]
>>>>>> *Verzonden:* vrijdag 21 juni 2013 15:23
>>>>>> *To:* Cocoon Users
>>>>>> *Onderwerp:* Re: XSLT import/include errors
>>>>>>
>>>>>>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
>>>>>> invoke external Java function ?
>>>>>> I can't get it working:
>>>>>>
>>>>>> http://www.w3.org/1999/XSL/Transform";
>>>>>> version="1.0"
>>>>>> xmlns:utils="java:org.example.Utils"
>>>>>> exclude-result-prefixes="utils">
>>>>>>
>>>>>>  
>>>>>>
>>>>>>   
>>>>>>
>>>>>>   
>>>>>> >>>>> select="utils:exists($fileName)"/>
>>>>>>   
>>>>>>  
>>>>>>
>>>>>>  
>>>>>>
>>>>>>  Tried Xalan, tried Saxon. Both generates some strange errors with
>>>>>> XML Document.
>>>>>>
>>>>>>  Greetings,
>>>>>> Greg
>>>>>>
>>>>>>
>>>>>> 2013/6/20 gelo1234 
>>>>>>
>>>>>>>  The latest Saxon got the same _global_ variable context scope and
>>>>>>> doesn't allow overriding xsl:variables.
>>>>>>>  OK, I will fix that :)
>>>>>>>
>>>>>>>  Greetings,
>>>>>>> Greg
>>>>>>>
>>>>>>>
>>>>>>> 2013/6/20 gelo1234 
>>>>>>>
>>>>>>>>
>>>>>>>> Thank you! I will try to bring back Saxon :)
>>>>>>>>
>>>>>>>>  Greetings,
>>>>>>>> Greg
>>>>>>>>
>>>>>>>>
>>>>>>>>This was discused before in the mailing list [1], it's a two
>>>>>>>>> step process
>>>>>>>>>
>>>>>>>>> * Add saxon dependency to pom file. [2]
>>>>>>>>>
>>>>>>>>>  I think it's better to try Saxon directly if you used to work
>>>>>>>>> with it. Xalan is usually faster but as you have to migrate already 
>>>>>>>>> made
>>>>>>>>> templates from Saxon IMO it's better to switch the engine.
>>>>>>>>>
>>>>>>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>>>>>>> [2]
>>>>>>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>  *The Future Group, dé maat in ondernemen*
>>>>>>
>>>>>>
>>>>>>   [image: The Future Group] <http://www.the-future-group.com> [image:
>>>>>> The Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
>>>>>> Mobiel nummer] 06 15879926  [image: Web-site]
>>>>>> http://www.the-future-group.com [image: E-mail adres]
>>>>>> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31
>>>>>> (0)79 - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
>>>>>>   http://twitter.com/futuregroup
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>

Re: XSLT import/include errors

[Javier Puerto]

Hi Greg,

Did you tried yourself with Saxon? I had caching issues with Xalan but
never tried with Saxon before.

Salu2.
El 22/06/2013 10:34, "gelo1234"  escribió:

> Now when everything is up and working fine, the really ennoying part of C3
> is caching imported/included XSL files.
>
> Is there any way to invalidate that cache ? Or to turn if off ?
>
> I wouldn't like to restart the application server every time I make a
> small change inside imported/included XSL file :(
>
> Greetings,
> Greg
>
>
> 2013/6/21 gelo1234 
>
>> Solution: If you want to call Java functions freely from C3 XSLT, use
>> older Saxon implementation.
>> Version 9.1 works perfectly!
>>
>> Greetings,
>> Greg
>>
>>
>> 2013/6/21 gelo1234 
>>
>>> Looks like Saxon-HE doesn't support anymore calling Java functions that
>>> way:
>>>
>>>
>>> http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html
>>>
>>> But there are available in PE and EE versions, huh
>>>
>>> Greetings,
>>> Greg
>>>
>>>
>>>
>>> 2013/6/21 gelo1234 
>>>
>>>> Thanks for the tip. Unfortunately it doesn't work with:
>>>> Saxon-HE-9.5.0.2.jar :(
>>>>
>>>> Greetings,
>>>> Greg
>>>>
>>>>
>>>> 2013/6/21 Robby Pelssers 
>>>>
>>>>>  That is possible but the how-to part depends on the Saxon version
>>>>> you are using.  You will need to dive into how to write extension 
>>>>> functions
>>>>> for that particular implementation.
>>>>>
>>>>>  I used it a number of times with Saxon 8.7
>>>>>
>>>>>
>>>>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>>>>
>>>>>
>>>>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>>>>
>>>>>  But i never tried with the latest version of Saxon which works
>>>>> differently.
>>>>>
>>>>>  Robby
>>>>>  --
>>>>> *Van:* gelo1234 [gelo1...@gmail.com]
>>>>> *Verzonden:* vrijdag 21 juni 2013 15:23
>>>>> *To:* Cocoon Users
>>>>> *Onderwerp:* Re: XSLT import/include errors
>>>>>
>>>>>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
>>>>> invoke external Java function ?
>>>>> I can't get it working:
>>>>>
>>>>> http://www.w3.org/1999/XSL/Transform";
>>>>> version="1.0"
>>>>> xmlns:utils="java:org.example.Utils"
>>>>> exclude-result-prefixes="utils">
>>>>>
>>>>>  
>>>>>
>>>>>   
>>>>>
>>>>>   
>>>>> >>>> select="utils:exists($fileName)"/>
>>>>>   
>>>>>  
>>>>>
>>>>>  
>>>>>
>>>>>  Tried Xalan, tried Saxon. Both generates some strange errors with XML
>>>>> Document.
>>>>>
>>>>>  Greetings,
>>>>> Greg
>>>>>
>>>>>
>>>>> 2013/6/20 gelo1234 
>>>>>
>>>>>>  The latest Saxon got the same _global_ variable context scope and
>>>>>> doesn't allow overriding xsl:variables.
>>>>>>  OK, I will fix that :)
>>>>>>
>>>>>>  Greetings,
>>>>>> Greg
>>>>>>
>>>>>>
>>>>>> 2013/6/20 gelo1234 
>>>>>>
>>>>>>>
>>>>>>> Thank you! I will try to bring back Saxon :)
>>>>>>>
>>>>>>>  Greetings,
>>>>>>> Greg
>>>>>>>
>>>>>>>
>>>>>>>This was discused before in the mailing list [1], it's a two
>>>>>>>> step process
>>>>>>>>
>>>>>>>> * Add saxon dependency to pom file. [2]
>>>>>>>>
>>>>>>>>  I think it's better to try Saxon directly if you used to work
>>>>>>>> with it. Xalan is usually faster but as you have to migrate already 
>>>>>>>> made
>>>>>>>> templates from Saxon IMO it's better to switch the engine.
>>>>>>>>
>>>>>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>>>>>> [2]
>>>>>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>  *The Future Group, dé maat in ondernemen*
>>>>>
>>>>>
>>>>>   [image: The Future Group] <http://www.the-future-group.com> [image:
>>>>> The Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
>>>>> Mobiel nummer] 06 15879926  [image: Web-site]
>>>>> http://www.the-future-group.com [image: E-mail adres]
>>>>> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31
>>>>> (0)79 - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
>>>>> http://twitter.com/futuregroup
>>>>>
>>>>
>>>>
>>>
>>
>

Re: XSLT import/include errors

[gelo1234]

Now when everything is up and working fine, the really ennoying part of C3
is caching imported/included XSL files.

Is there any way to invalidate that cache ? Or to turn if off ?

I wouldn't like to restart the application server every time I make a small
change inside imported/included XSL file :(

Greetings,
Greg


2013/6/21 gelo1234 

> Solution: If you want to call Java functions freely from C3 XSLT, use
> older Saxon implementation.
> Version 9.1 works perfectly!
>
> Greetings,
> Greg
>
>
> 2013/6/21 gelo1234 
>
>> Looks like Saxon-HE doesn't support anymore calling Java functions that
>> way:
>>
>>
>> http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html
>>
>> But there are available in PE and EE versions, huh
>>
>> Greetings,
>> Greg
>>
>>
>>
>> 2013/6/21 gelo1234 
>>
>>> Thanks for the tip. Unfortunately it doesn't work with:
>>> Saxon-HE-9.5.0.2.jar :(
>>>
>>> Greetings,
>>> Greg
>>>
>>>
>>> 2013/6/21 Robby Pelssers 
>>>
>>>>  That is possible but the how-to part depends on the Saxon version you
>>>> are using.  You will need to dive into how to write extension functions for
>>>> that particular implementation.
>>>>
>>>>  I used it a number of times with Saxon 8.7
>>>>
>>>>
>>>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>>>
>>>>
>>>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>>>
>>>>  But i never tried with the latest version of Saxon which works
>>>> differently.
>>>>
>>>>  Robby
>>>>  --
>>>> *Van:* gelo1234 [gelo1...@gmail.com]
>>>> *Verzonden:* vrijdag 21 juni 2013 15:23
>>>> *To:* Cocoon Users
>>>> *Onderwerp:* Re: XSLT import/include errors
>>>>
>>>>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
>>>> invoke external Java function ?
>>>> I can't get it working:
>>>>
>>>> http://www.w3.org/1999/XSL/Transform";
>>>> version="1.0"
>>>> xmlns:utils="java:org.example.Utils"
>>>> exclude-result-prefixes="utils">
>>>>
>>>>  
>>>>
>>>>   
>>>>
>>>>   
>>>> >>> select="utils:exists($fileName)"/>
>>>>   
>>>>  
>>>>
>>>>  
>>>>
>>>>  Tried Xalan, tried Saxon. Both generates some strange errors with XML
>>>> Document.
>>>>
>>>>  Greetings,
>>>> Greg
>>>>
>>>>
>>>> 2013/6/20 gelo1234 
>>>>
>>>>>  The latest Saxon got the same _global_ variable context scope and
>>>>> doesn't allow overriding xsl:variables.
>>>>>  OK, I will fix that :)
>>>>>
>>>>>  Greetings,
>>>>> Greg
>>>>>
>>>>>
>>>>> 2013/6/20 gelo1234 
>>>>>
>>>>>>
>>>>>> Thank you! I will try to bring back Saxon :)
>>>>>>
>>>>>>  Greetings,
>>>>>> Greg
>>>>>>
>>>>>>
>>>>>>This was discused before in the mailing list [1], it's a two step
>>>>>>> process
>>>>>>>
>>>>>>> * Add saxon dependency to pom file. [2]
>>>>>>>
>>>>>>>  I think it's better to try Saxon directly if you used to work with
>>>>>>> it. Xalan is usually faster but as you have to migrate already made
>>>>>>> templates from Saxon IMO it's better to switch the engine.
>>>>>>>
>>>>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>>>>> [2]
>>>>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>  *The Future Group, dé maat in ondernemen*
>>>>
>>>>
>>>>   [image: The Future Group] <http://www.the-future-group.com> [image:
>>>> The Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
>>>> Mobiel nummer] 06 15879926  [image: Web-site]
>>>> http://www.the-future-group.com [image: E-mail adres]
>>>> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31
>>>> (0)79 - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
>>>> http://twitter.com/futuregroup
>>>>
>>>
>>>
>>
>

Re: XSLT import/include errors

[gelo1234]

Solution: If you want to call Java functions freely from C3 XSLT, use older
Saxon implementation.
Version 9.1 works perfectly!

Greetings,
Greg


2013/6/21 gelo1234 

> Looks like Saxon-HE doesn't support anymore calling Java functions that
> way:
>
>
> http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html
>
> But there are available in PE and EE versions, huh
>
> Greetings,
> Greg
>
>
>
> 2013/6/21 gelo1234 
>
>> Thanks for the tip. Unfortunately it doesn't work with:
>> Saxon-HE-9.5.0.2.jar :(
>>
>> Greetings,
>> Greg
>>
>>
>> 2013/6/21 Robby Pelssers 
>>
>>>  That is possible but the how-to part depends on the Saxon version you
>>> are using.  You will need to dive into how to write extension functions for
>>> that particular implementation.
>>>
>>>  I used it a number of times with Saxon 8.7
>>>
>>>
>>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>>
>>>
>>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>>
>>>  But i never tried with the latest version of Saxon which works
>>> differently.
>>>
>>>  Robby
>>>  --
>>> *Van:* gelo1234 [gelo1...@gmail.com]
>>> *Verzonden:* vrijdag 21 juni 2013 15:23
>>> *To:* Cocoon Users
>>> *Onderwerp:* Re: XSLT import/include errors
>>>
>>>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
>>> invoke external Java function ?
>>> I can't get it working:
>>>
>>> http://www.w3.org/1999/XSL/Transform";
>>> version="1.0"
>>> xmlns:utils="java:org.example.Utils"
>>> exclude-result-prefixes="utils">
>>>
>>>  
>>>
>>>   
>>>
>>>   
>>> >> select="utils:exists($fileName)"/>
>>>   
>>>  
>>>
>>>  
>>>
>>>  Tried Xalan, tried Saxon. Both generates some strange errors with XML
>>> Document.
>>>
>>>  Greetings,
>>> Greg
>>>
>>>
>>> 2013/6/20 gelo1234 
>>>
>>>>  The latest Saxon got the same _global_ variable context scope and
>>>> doesn't allow overriding xsl:variables.
>>>>  OK, I will fix that :)
>>>>
>>>>  Greetings,
>>>> Greg
>>>>
>>>>
>>>> 2013/6/20 gelo1234 
>>>>
>>>>>
>>>>> Thank you! I will try to bring back Saxon :)
>>>>>
>>>>>  Greetings,
>>>>> Greg
>>>>>
>>>>>
>>>>>This was discused before in the mailing list [1], it's a two step
>>>>>> process
>>>>>>
>>>>>> * Add saxon dependency to pom file. [2]
>>>>>>
>>>>>>  I think it's better to try Saxon directly if you used to work with
>>>>>> it. Xalan is usually faster but as you have to migrate already made
>>>>>> templates from Saxon IMO it's better to switch the engine.
>>>>>>
>>>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>>>> [2]
>>>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>  *The Future Group, dé maat in ondernemen*
>>>
>>>
>>>   [image: The Future Group] <http://www.the-future-group.com> [image:
>>> The Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
>>> Mobiel nummer] 06 15879926  [image: Web-site]
>>> http://www.the-future-group.com [image: E-mail adres]
>>> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31
>>> (0)79 - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
>>> http://twitter.com/futuregroup
>>>
>>
>>
>

Re: XSLT import/include errors

[gelo1234]

Looks like Saxon-HE doesn't support anymore calling Java functions that way:

http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/XSLT-2-0-Saxon-9-HE-and-call-java-functions-td4347.html

But there are available in PE and EE versions, huh

Greetings,
Greg



2013/6/21 gelo1234 

> Thanks for the tip. Unfortunately it doesn't work with:
> Saxon-HE-9.5.0.2.jar :(
>
> Greetings,
> Greg
>
>
> 2013/6/21 Robby Pelssers 
>
>>  That is possible but the how-to part depends on the Saxon version you
>> are using.  You will need to dive into how to write extension functions for
>> that particular implementation.
>>
>>  I used it a number of times with Saxon 8.7
>>
>>
>> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>>
>>
>> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>>
>>  But i never tried with the latest version of Saxon which works
>> differently.
>>
>>  Robby
>>  ------
>> *Van:* gelo1234 [gelo1...@gmail.com]
>> *Verzonden:* vrijdag 21 juni 2013 15:23
>> *To:* Cocoon Users
>> *Onderwerp:* Re: XSLT import/include errors
>>
>>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
>> invoke external Java function ?
>> I can't get it working:
>>
>> http://www.w3.org/1999/XSL/Transform";
>> version="1.0"
>> xmlns:utils="java:org.example.Utils"
>> exclude-result-prefixes="utils">
>>
>>  
>>
>>   
>>
>>   
>> > select="utils:exists($fileName)"/>
>>   
>>  
>>
>>  
>>
>>  Tried Xalan, tried Saxon. Both generates some strange errors with XML
>> Document.
>>
>>  Greetings,
>> Greg
>>
>>
>> 2013/6/20 gelo1234 
>>
>>>  The latest Saxon got the same _global_ variable context scope and
>>> doesn't allow overriding xsl:variables.
>>>  OK, I will fix that :)
>>>
>>>  Greetings,
>>> Greg
>>>
>>>
>>> 2013/6/20 gelo1234 
>>>
>>>>
>>>> Thank you! I will try to bring back Saxon :)
>>>>
>>>>  Greetings,
>>>> Greg
>>>>
>>>>
>>>>This was discused before in the mailing list [1], it's a two step
>>>>> process
>>>>>
>>>>> * Add saxon dependency to pom file. [2]
>>>>>
>>>>>  I think it's better to try Saxon directly if you used to work with
>>>>> it. Xalan is usually faster but as you have to migrate already made
>>>>> templates from Saxon IMO it's better to switch the engine.
>>>>>
>>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>>> [2]
>>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>  *The Future Group, dé maat in ondernemen*
>>
>>
>>   [image: The Future Group] <http://www.the-future-group.com> [image:
>> The Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
>> Mobiel nummer] 06 15879926  [image: Web-site]
>> http://www.the-future-group.com [image: E-mail adres]
>> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31 (0)79
>> - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
>> http://twitter.com/futuregroup
>>
>
>

Re: XSLT import/include errors

[gelo1234]

Thanks for the tip. Unfortunately it doesn't work with:
Saxon-HE-9.5.0.2.jar :(

Greetings,
Greg


2013/6/21 Robby Pelssers 

>  That is possible but the how-to part depends on the Saxon version you
> are using.  You will need to dive into how to write extension functions for
> that particular implementation.
>
>  I used it a number of times with Saxon 8.7
>
>
> http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html
>
>
> http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html
>
>  But i never tried with the latest version of Saxon which works
> differently.
>
>  Robby
>  --
> *Van:* gelo1234 [gelo1...@gmail.com]
> *Verzonden:* vrijdag 21 juni 2013 15:23
> *To:* Cocoon Users
> *Onderwerp:* Re: XSLT import/include errors
>
>  OK, one more question. Is it possible with Saxon/Xalan in C3 to
> invoke external Java function ?
> I can't get it working:
>
> http://www.w3.org/1999/XSL/Transform";
> version="1.0"
> xmlns:utils="java:org.example.Utils"
> exclude-result-prefixes="utils">
>
>  
>
>   
>
>   
>  select="utils:exists($fileName)"/>
>   
>  
>
>  
>
>  Tried Xalan, tried Saxon. Both generates some strange errors with XML
> Document.
>
>  Greetings,
> Greg
>
>
> 2013/6/20 gelo1234 
>
>>  The latest Saxon got the same _global_ variable context scope and
>> doesn't allow overriding xsl:variables.
>>  OK, I will fix that :)
>>
>>  Greetings,
>> Greg
>>
>>
>> 2013/6/20 gelo1234 
>>
>>>
>>> Thank you! I will try to bring back Saxon :)
>>>
>>>  Greetings,
>>> Greg
>>>
>>>
>>>This was discused before in the mailing list [1], it's a two step
>>>> process
>>>>
>>>> * Add saxon dependency to pom file. [2]
>>>>
>>>>  I think it's better to try Saxon directly if you used to work with
>>>> it. Xalan is usually faster but as you have to migrate already made
>>>> templates from Saxon IMO it's better to switch the engine.
>>>>
>>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>>> [2]
>>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>>
>>>>
>>>>
>>>
>>
>  *The Future Group, dé maat in ondernemen*
>
>
>   [image: The Future Group] <http://www.the-future-group.com> [image: The
> Future Group kantoor]   Röntgenlaan 27 | 2719 DX Zoetermeer [image:
> Mobiel nummer] 06 15879926  [image: Web-site]
> http://www.the-future-group.com [image: E-mail adres]
> robby.pelss...@the-future-group.com  [image: Telefoonnummer]   +31 (0)79
> - 363 2905 [image: LinkedIn account]   [image: Twitteraccount]
> http://twitter.com/futuregroup
>

RE: XSLT import/include errors

[Robby Pelssers]

That is possible but the how-to part depends on the Saxon version you are 
using.  You will need to dive into how to write extension functions for that 
particular implementation.

I used it a number of times with Saxon 8.7

http://robbypelssers.blogspot.nl/2012/10/creating-unix-timestamp-with-xslt20.html

http://robbypelssers.blogspot.nl/2011/09/power-of-apache-cocoon-xquery-and-xslt.html

But i never tried with the latest version of Saxon which works differently.

Robby

Van: gelo1234 [gelo1...@gmail.com]
Verzonden: vrijdag 21 juni 2013 15:23
To: Cocoon Users
Onderwerp: Re: XSLT import/include errors

OK, one more question. Is it possible with Saxon/Xalan in C3 to invoke external 
Java function ?
I can't get it working:

http://www.w3.org/1999/XSL/Transform"; version="1.0"
xmlns:utils="java:org.example.Utils"
exclude-result-prefixes="utils">



 

 
   
 




Tried Xalan, tried Saxon. Both generates some strange errors with XML Document.

Greetings,
Greg


2013/6/20 gelo1234 mailto:gelo1...@gmail.com>>
The latest Saxon got the same _global_ variable context scope and doesn't allow 
overriding xsl:variables.
OK, I will fix that :)

Greetings,
Greg


2013/6/20 gelo1234 mailto:gelo1...@gmail.com>>

Thank you! I will try to bring back Saxon :)

Greetings,
Greg


This was discused before in the mailing list [1], it's a two step process

* Add saxon dependency to pom file. [2]

I think it's better to try Saxon directly if you used to work with it. Xalan is 
usually faster but as you have to migrate already made templates from Saxon IMO 
it's better to switch the engine.

[1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
[2] 
http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results






The Future Group, dé maat in ondernemen



[The Future Group][The Future Group kantoor]  
Röntgenlaan 27 | 2719 DX Zoetermeer [Mobiel nummer] 
06 15879926
[Web-site]  http://www.the-future-group.com [E-mail adres]  
robby.pelss...@the-future-group.com
[Telefoonnummer]+31 (0)79 - 363 2905[LinkedIn account]
[Twitteraccount]http://twitter.com/futuregroup

Re: XSLT import/include errors

[gelo1234]

OK, one more question. Is it possible with Saxon/Xalan in C3 to invoke
external Java function ?
I can't get it working:

http://www.w3.org/1999/XSL/Transform";
version="1.0"
xmlns:utils="java:org.example.Utils"
exclude-result-prefixes="utils">



 

 
   
 




Tried Xalan, tried Saxon. Both generates some strange errors with XML
Document.

Greetings,
Greg


2013/6/20 gelo1234 

> The latest Saxon got the same _global_ variable context scope and doesn't
> allow overriding xsl:variables.
> OK, I will fix that :)
>
> Greetings,
> Greg
>
>
> 2013/6/20 gelo1234 
>
>>
>> Thank you! I will try to bring back Saxon :)
>>
>> Greetings,
>> Greg
>>
>>
>> This was discused before in the mailing list [1], it's a two step process
>>>
>>> * Add saxon dependency to pom file. [2]
>>>
>>> I think it's better to try Saxon directly if you used to work with it.
>>> Xalan is usually faster but as you have to migrate already made templates
>>> from Saxon IMO it's better to switch the engine.
>>>
>>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>>> [2]
>>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>>
>>>
>>>
>>
>

Re: XSLT import/include errors

[gelo1234]

The latest Saxon got the same _global_ variable context scope and doesn't
allow overriding xsl:variables.
OK, I will fix that :)

Greetings,
Greg


2013/6/20 gelo1234 

>
> Thank you! I will try to bring back Saxon :)
>
> Greetings,
> Greg
>
>
> This was discused before in the mailing list [1], it's a two step process
>>
>> * Add saxon dependency to pom file. [2]
>>
>> I think it's better to try Saxon directly if you used to work with it.
>> Xalan is usually faster but as you have to migrate already made templates
>> from Saxon IMO it's better to switch the engine.
>>
>> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
>> [2]
>> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>>
>>
>>
>

Re: XSLT import/include errors

[gelo1234]

Thank you! I will try to bring back Saxon :)

Greetings,
Greg


This was discused before in the mailing list [1], it's a two step process
>
> * Add saxon dependency to pom file. [2]
>
> I think it's better to try Saxon directly if you used to work with it.
> Xalan is usually faster but as you have to migrate already made templates
> from Saxon IMO it's better to switch the engine.
>
> [1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
> [2]
> http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results
>
>
>

Re: XSLT import/include errors

[Javier Puerto]

2013/6/20 gelo1234 

> Right, it was NOT Xalan, I used Saxon in my old config. Where could we
> change Xalan to Saxon in C3 ?
>

This was discused before in the mailing list [1], it's a two step process

* Add saxon dependency to pom file. [2]
* Create file META-INF/services/javax.xml.transform.TransformerFactory with
content:

net.sf.saxon.TransformerFactoryImpl

But you can't use both engines at the same time.


>
> Now I've got another "strange" XSL error:
> XML document structures must start and end within the same entity.
>
> What could that mean??? :)
>
> That Xalan is making me scratching my head against the wall :)
>

I think it's better to try Saxon directly if you used to work with it.
Xalan is usually faster but as you have to migrate already made templates
from Saxon IMO it's better to switch the engine.

[1] http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE
[2]
http://cocoon.markmail.org/message/mjuftsfwdxmnc5fn?q=saxon#query:saxon+page:1+mid:fe2faygf7jdfrzb3+state:results


> Greetings,
> Greg
>
>
> 2013/6/20 Javier Puerto 
>
>>
>>
>>
>> 2013/6/20 gelo1234 
>>
>>> OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
>>> STRANGE!!
>>>
>>
>> Yeah, computer's stuff. :)
>>
>>
>>>
>>> And also found that more detailed error info about not being able to
>>> compile XSLT stylesheet was in Tomcat log.
>>>
>>> It seems that with C3  cannot be inherited. The error
>>> said about the same  being defined in 2 different places
>>> :/
>>> One place - in main XSL file and other one - in imported XSL file.
>>>
>>> While it worked fine in C2.1. I use extensively  and
>>>  inheritance, now in C3 it makes XSLT not being compiled
>>> :/
>>>
>>
>> What version of C2.1 did you use? Maybe old Xalan? I've found the
>> following note in the Xalan documentation [1]:
>>
>> "Note that all top-level parameters and variables from all imported and
>> included stylesheets will be placed as direct children of the top-level
>> stylesheet in the AST. This done to make global variables truly global and
>> not just global in the stylesheet where it was declared."
>>
>> You should avoid duplicate variable declarations, at the end of the page
>> it's explained how the forward references works. You could extract some
>> common variables to a XSLT template so you can use several templates
>> without collision.
>>
>>  [1]: http://xml.apache.org/xalan-j/xsltc/xsl_variable_design.html
>>
>>
>>> Greetings,
>>> Greg
>>>
>>>
>>>
>>> 2013/6/20 gelo1234 
>>>

 Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
 doesn't help. I tried to clean work directory, and still
 NullPointerException.

 Any idea what might be wrong ?
 And how to switch off imported xslt caching ?

 INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
 cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
 deployDirectory
 INFO: Deploying web application directory
 /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
 cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
 addChildInternal
 SEVERE: ContainerBase.addChild: start:
 org.apache.catalina.LifecycleException: Failed to start component
 [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
 at
 org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
 at
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
 at
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
 at
 org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
 at
 org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
 at
 org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
 Source)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
 Source)
 at java.lang.Thread.run(Unknown Source)
 Caused by: java.lang.NullPointerException
 at
 org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
 at
 org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
 at
 org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
 at
 org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
 at
 org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
 at
 org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
 at
 org.apache.cat

Re: XSLT import/include errors

[gelo1234]

Yes, it must be that "problem" with current Xalan.

Strange thing is that some XSLT variables are predefined like: requestURI
(?!).

So I cannot use:
 in stylesheet file.xsl even though Ive got:


 


in sitemap.xmap. So requestURI is some GLOBAL variable ?

Greetings,
Greg

2013/6/20 Javier Puerto 

>
>
>
> 2013/6/20 gelo1234 
>
> What version of C2.1 did you use? Maybe old Xalan? I've found the
> following note in the Xalan documentation [1]:
>
> "Note that all top-level parameters and variables from all imported and
> included stylesheets will be placed as direct children of the top-level
> stylesheet in the AST. This done to make global variables truly global and
> not just global in the stylesheet where it was declared."
>
> You should avoid duplicate variable declarations, at the end of the page
> it's explained how the forward references works. You could extract some
> common variables to a XSLT template so you can use several templates
> without collision.
>
>  [1]: http://xml.apache.org/xalan-j/xsltc/xsl_variable_design.html
>
>

Re: XSLT import/include errors

[gelo1234]

Right, it was NOT Xalan, I used Saxon in my old config. Where could we
change Xalan to Saxon in C3 ?

Now I've got another "strange" XSL error:
XML document structures must start and end within the same entity.

What could that mean??? :)

That Xalan is making me scratching my head against the wall :)

Greetings,
Greg


2013/6/20 Javier Puerto 

>
>
>
> 2013/6/20 gelo1234 
>
>> OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
>> STRANGE!!
>>
>
> Yeah, computer's stuff. :)
>
>
>>
>> And also found that more detailed error info about not being able to
>> compile XSLT stylesheet was in Tomcat log.
>>
>> It seems that with C3  cannot be inherited. The error
>> said about the same  being defined in 2 different places
>> :/
>> One place - in main XSL file and other one - in imported XSL file.
>>
>> While it worked fine in C2.1. I use extensively  and
>>  inheritance, now in C3 it makes XSLT not being compiled
>> :/
>>
>
> What version of C2.1 did you use? Maybe old Xalan? I've found the
> following note in the Xalan documentation [1]:
>
> "Note that all top-level parameters and variables from all imported and
> included stylesheets will be placed as direct children of the top-level
> stylesheet in the AST. This done to make global variables truly global and
> not just global in the stylesheet where it was declared."
>
> You should avoid duplicate variable declarations, at the end of the page
> it's explained how the forward references works. You could extract some
> common variables to a XSLT template so you can use several templates
> without collision.
>
>  [1]: http://xml.apache.org/xalan-j/xsltc/xsl_variable_design.html
>
>
>> Greetings,
>> Greg
>>
>>
>>
>> 2013/6/20 gelo1234 
>>
>>>
>>> Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
>>> doesn't help. I tried to clean work directory, and still
>>> NullPointerException.
>>>
>>> Any idea what might be wrong ?
>>> And how to switch off imported xslt caching ?
>>>
>>> INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
>>> cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> INFO: Deploying web application directory
>>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>>> cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
>>> addChildInternal
>>> SEVERE: ContainerBase.addChild: start:
>>> org.apache.catalina.LifecycleException: Failed to start component
>>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>>> at
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>> at
>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>>> at
>>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
>>> at
>>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
>>> Source)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>> at java.lang.Thread.run(Unknown Source)
>>> Caused by: java.lang.NullPointerException
>>> at
>>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
>>> at
>>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>>> at
>>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>>> at
>>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>>> at
>>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>>> at
>>> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
>>> at
>>> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
>>> at
>>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
>>> at
>>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>>> at
>>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>>> at
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269)
>>> at
>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>> ... 11 more
>>>
>>> cze 20, 2013 8:43:29 PM org.apache.catalina.startup.HostConfig
>>> deployDirectory
>>> SEVERE: Error deploying web application directory
>>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>>> java.lang.IllegalStateException: ContainerBase.addChild: s

Re: XSLT import/include errors

[Javier Puerto]

2013/6/20 gelo1234 

> OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
> STRANGE!!
>

Yeah, computer's stuff. :)


>
> And also found that more detailed error info about not being able to
> compile XSLT stylesheet was in Tomcat log.
>
> It seems that with C3  cannot be inherited. The error
> said about the same  being defined in 2 different places
> :/
> One place - in main XSL file and other one - in imported XSL file.
>
> While it worked fine in C2.1. I use extensively  and
>  inheritance, now in C3 it makes XSLT not being compiled
> :/
>

What version of C2.1 did you use? Maybe old Xalan? I've found the following
note in the Xalan documentation [1]:

"Note that all top-level parameters and variables from all imported and
included stylesheets will be placed as direct children of the top-level
stylesheet in the AST. This done to make global variables truly global and
not just global in the stylesheet where it was declared."

You should avoid duplicate variable declarations, at the end of the page
it's explained how the forward references works. You could extract some
common variables to a XSLT template so you can use several templates
without collision.

 [1]: http://xml.apache.org/xalan-j/xsltc/xsl_variable_design.html


> Greetings,
> Greg
>
>
>
> 2013/6/20 gelo1234 
>
>>
>> Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
>> doesn't help. I tried to clean work directory, and still
>> NullPointerException.
>>
>> Any idea what might be wrong ?
>> And how to switch off imported xslt caching ?
>>
>> INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
>> cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
>> deployDirectory
>> INFO: Deploying web application directory
>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>> cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
>> addChildInternal
>> SEVERE: ContainerBase.addChild: start:
>> org.apache.catalina.LifecycleException: Failed to start component
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
>> at
>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
>> at
>> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
>> at
>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>> at
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> ... 11 more
>>
>> cze 20, 2013 8:43:29 PM org.apache.catalina.startup.HostConfig
>> deployDirectory
>> SEVERE: Error deploying web application directory
>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>> java.lang.IllegalStateException: ContainerBase.addChild: start:
>> org.apache.catalina.LifecycleException: Failed to start component
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> at
>> org.apache.catalina.startup.HostConfig.dep

Re: XSLT import/include errors

[gelo1234]

Resolved the issue with NullPointerException during Tomcat deploy process.
It seems like putting too many files/directories in WEB-INF/classes/COB-INF
makes Tomcat fail to deploy C3 app.

I moved block root context from: context-path="classpath:/classes/COB-INF/
to some other place:
context-path="file:/anythingNotWithingCLASSPATH/COB-INF/"

And now Tomcat deploys C3 app without problems.

Greetings,
Greg




2013/6/20 gelo1234 

> OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
> STRANGE!!
>
> And also found that more detailed error info about not being able to
> compile XSLT stylesheet was in Tomcat log.
>
> It seems that with C3  cannot be inherited. The error
> said about the same  being defined in 2 different places
> :/
> One place - in main XSL file and other one - in imported XSL file.
>
> While it worked fine in C2.1. I use extensively  and
>  inheritance, now in C3 it makes XSLT not being compiled
> :/
>
> Greetings,
> Greg
>
>
>
> 2013/6/20 gelo1234 
>
>>
>> Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
>> doesn't help. I tried to clean work directory, and still
>> NullPointerException.
>>
>> Any idea what might be wrong ?
>> And how to switch off imported xslt caching ?
>>
>> INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
>> cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
>> deployDirectory
>> INFO: Deploying web application directory
>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>> cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
>> addChildInternal
>> SEVERE: ContainerBase.addChild: start:
>> org.apache.catalina.LifecycleException: Failed to start component
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
>> at
>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
>> at
>> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
>> at
>> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
>> at
>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>> at
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> ... 11 more
>>
>> cze 20, 2013 8:43:29 PM org.apache.catalina.startup.HostConfig
>> deployDirectory
>> SEVERE: Error deploying web application directory
>> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
>> java.lang.IllegalStateException: ContainerBase.addChild: start:
>> org.apache.catalina.LifecycleException: Failed to start component
>> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
>> at
>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>> at java.util.concurrent.Future

Re: XSLT import/include errors

[gelo1234]

OK, resolved the issue. Deleted xslt/ directory :/ and now its starting.
STRANGE!!

And also found that more detailed error info about not being able to
compile XSLT stylesheet was in Tomcat log.

It seems that with C3  cannot be inherited. The error
said about the same  being defined in 2 different places
:/
One place - in main XSL file and other one - in imported XSL file.

While it worked fine in C2.1. I use extensively  and
 inheritance, now in C3 it makes XSLT not being compiled
:/

Greetings,
Greg



2013/6/20 gelo1234 

>
> Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
> doesn't help. I tried to clean work directory, and still
> NullPointerException.
>
> Any idea what might be wrong ?
> And how to switch off imported xslt caching ?
>
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
> cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory
> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
> cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
> addChildInternal
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
> at
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at
> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
> at
> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
> at
> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
> at
> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
> at
> org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
> at
> org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
> at
> org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
> cze 20, 2013 8:43:29 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> SEVERE: Error deploying web application directory
> /var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
> java.lang.IllegalStateException: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
> at
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
> Greetings,
> Greg
>
>
>
> 2013/6/20 Javier Puerto 
>
>> Hi Greg,
>>
>> El 20/06/2013 20:00, "gelo1234"  escribió:
>>
>> >
>> >
>> > It looks like XSLT also got cut in functionality in C3. I tried to
>> rerun old XSL stylesheets with new C3 and gave up.
>> >
>> > The error says nothing meaningful:
>> >
>> > > timestamp="Thu, 20 J

Re: XSLT import/include errors

[gelo1234]

Now Im lost. The Cocoon context doesn't work anymore. Restarting Tomcat
doesn't help. I tried to clean work directory, and still
NullPointerException.

Any idea what might be wrong ?
And how to switch off imported xslt caching ?

INFO: Starting Servlet Engine: Apache Tomcat/7.0.40
cze 20, 2013 8:43:28 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
cze 20, 2013 8:43:29 PM org.apache.catalina.core.ContainerBase
addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
at
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at
org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2092)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
at
org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2093)
at
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1300)
at
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5269)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more

cze 20, 2013 8:43:29 PM org.apache.catalina.startup.HostConfig
deployDirectory
SEVERE: Error deploying web application directory
/var/lib/tomcat/webapps/mywebapp-1.0-SNAPSHOT
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/mywebapp-1.0-SNAPSHOT]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
at
org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1672)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Greetings,
Greg



2013/6/20 Javier Puerto 

> Hi Greg,
>
> El 20/06/2013 20:00, "gelo1234"  escribió:
>
> >
> >
> > It looks like XSLT also got cut in functionality in C3. I tried to rerun
> old XSL stylesheets with new C3 and gave up.
> >
> > The error says nothing meaningful:
> >
> >  timestamp="Thu, 20 Jun 2013 19:58:23 +0200">Impossible to read
> XSLT from 'javax.xml.transform.stream.StreamSource@cba24d', see nested
> exceptionCould not compile
> stylesheetjavax.xml.transform.TransformerConfigurationException:
> Could not compile stylesheet
> > at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(Unknown
> Source)
> > at
> org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:216)
> > at
> org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:165)
> > at
> org.apache.cocoon.sax.component.XSLTTransformer.setConfiguration(XSLTTransformer.java:264)
> > at
> org.apache.cocoon.sitemap.InvocationImpl.installComponent(Invocati

Re: XSLT import/include errors

[Javier Puerto]

Hi Greg,

El 20/06/2013 20:00, "gelo1234"  escribió:
>
>
> It looks like XSLT also got cut in functionality in C3. I tried to rerun
old XSL stylesheets with new C3 and gave up.
>
> The error says nothing meaningful:
>
> Impossible to read
XSLT from 'javax.xml.transform.stream.StreamSource@cba24d', see nested
exceptionCould not compile
stylesheetjavax.xml.transform.TransformerConfigurationException:
Could not compile stylesheet
> at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(Unknown
Source)
> at
org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:216)
> at
org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:165)
> at
org.apache.cocoon.sax.component.XSLTTransformer.setConfiguration(XSLTTransformer.java:264)
> at
org.apache.cocoon.sitemap.InvocationImpl.installComponent(InvocationImpl.java:257)
> at
>
> It looks like there is a problem with xsl:import/xsl:include from the
main xsl stylesheet.

You are right, seems to be a problem with the imports. I've used Imports
and includes with cocoo3 without problems, except that imported files are
cached and doesn't update running in RCL. The xslt engine is still xalan so
the templates should work like before except for the sources with cocoon:/
protocol that aren't supported.

> Moreover I found that when 
> Can we switch on more debugging info what is wrong ?

You can edit the logback.xml file and set level to debug but the exception
comes from xalan. I suggest to look for sources loaded with cocoon:/ in
your code and substitute by servlet:/.

>
> Greetings,
> Greg

Salu2.

XSLT import/include errors

[gelo1234]

It looks like XSLT also got cut in functionality in C3. I tried to rerun
old XSL stylesheets with new C3 and gave up.

The error says nothing meaningful:

Impossible to read
XSLT from 'javax.xml.transform.stream.StreamSource@cba24d', see nested
exceptionCould not compile
stylesheetjavax.xml.transform.TransformerConfigurationException:
Could not compile stylesheet
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(Unknown
Source)
at
org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:216)
at
org.apache.cocoon.sax.component.XSLTTransformer.load(XSLTTransformer.java:165)
at
org.apache.cocoon.sax.component.XSLTTransformer.setConfiguration(XSLTTransformer.java:264)
at
org.apache.cocoon.sitemap.InvocationImpl.installComponent(InvocationImpl.java:257)
at

It looks like there is a problem with xsl:import/xsl:include from the main
xsl stylesheet.
Moreover I found that when