Precompilation of XSP-files via CLI - flag precompile-only broken

[Jo...@o2.com]

Hi all,

has anybody managed to precompile XSP-files during the ANT build-process?
I'm able to execute a pipeline using cocoon 2.1.1 command line interface:
If I set precompile-only="false" in my custom cli.xconf, cocoon then 
generates *_xsp.java and *_xsp.class files into its work directory. Fine, 
but my pipeline is also executed, which I DO NOT want!

If I specify precompile-only="true", no xsp file gets precompiled, instead 
cocoon produces the following error:

java.lang.NullPointerException
    at 
org.apache.cocoon.environment.AbstractEnvironment.initComponents(AbstractEnvironment.java:532)
    at 
org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:511)
    at 
org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:500)
    at org.apache.cocoon.Cocoon.precompile(Cocoon.java:735)
    at org.apache.cocoon.bean.CocoonBean.processXSP(CocoonBean.java:930)
    at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:636)
    at org.apache.cocoon.Main.main(Main.java:375)

This happens, because no CocoonComponentManager is instantiated, the call

this.manager = CocoonComponentManager.getSitemapComponentManager();

in line 531 obviously returns null, which leads to the above NPE when 
looking up the component org.apache.excalibur.source.SourceResolver.

Seems like a bug to me, can anyone provide further details?

Thanks a lot,
Jonas


----------------------------------------------------------------------------------------------------
This electronic message contains information from the mmo2 plc Group which 
may be
privileged or confidential. The information is intended to be for the use 
of the
individual(s) or entity named above. If you are not the intended recipient 
be aware
that any disclosure, copying, distribution or use of the contents of this 
information
is prohibited. If you have received this electronic message in error, 
please notify
us by telephone or email (to the numbers or address above) immediately.



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

Re: Precompilation of XSP-files via CLI - flag precompile-only broken

[Upayavira <uv...@upaya.co.uk>]

Precompilation of XSPs was fixed by Carsten shortly before 2.1.3 was 
released. I'd therefore suggest you consider upgrading.

If you're running from an Ant build process, you'll find a new, as yet 
largely untested Ant task in 2.1.3 too at org.apache.cocoon.CocoonTask. 
It'll do everything the CLI can do, except that you can embed the 
configuration (cli.xconf) into your Ant script rather than having to 
refer to another file. If you want to try it, let me know and I'll send 
you a sample build file. I'd be very pleased if you tried it, as I'm 
curious to see if other people can get it to work.

With best wishes,

Upayavira


Jonas.Kilian@o2.com wrote:

>Hi all,
>
>has anybody managed to precompile XSP-files during the ANT build-process?
>I'm able to execute a pipeline using cocoon 2.1.1 command line interface:
>If I set precompile-only="false" in my custom cli.xconf, cocoon then 
>generates *_xsp.java and *_xsp.class files into its work directory. Fine, 
>but my pipeline is also executed, which I DO NOT want!
>
>If I specify precompile-only="true", no xsp file gets precompiled, instead 
>cocoon produces the following error:
>
>java.lang.NullPointerException
>    at 
>org.apache.cocoon.environment.AbstractEnvironment.initComponents(AbstractEnvironment.java:532)
>    at 
>org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:511)
>    at 
>org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:500)
>    at org.apache.cocoon.Cocoon.precompile(Cocoon.java:735)
>    at org.apache.cocoon.bean.CocoonBean.processXSP(CocoonBean.java:930)
>    at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:636)
>    at org.apache.cocoon.Main.main(Main.java:375)
>
>This happens, because no CocoonComponentManager is instantiated, the call
>
>this.manager = CocoonComponentManager.getSitemapComponentManager();
>
>in line 531 obviously returns null, which leads to the above NPE when 
>looking up the component org.apache.excalibur.source.SourceResolver.
>
>Seems like a bug to me, can anyone provide further details?
>
>Thanks a lot,
>Jonas
>
>
>----------------------------------------------------------------------------------------------------
>This electronic message contains information from the mmo2 plc Group which 
>may be
>privileged or confidential. The information is intended to be for the use 
>of the
>individual(s) or entity named above. If you are not the intended recipient 
>be aware
>that any disclosure, copying, distribution or use of the contents of this 
>information
>is prohibited. If you have received this electronic message in error, 
>please notify
>us by telephone or email (to the numbers or address above) immediately.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>  
>



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