Grzegorz Kossakowski wrote:
Hi
Following Giacomo's comment that Forms samples are broken I tried to run this
sample:
http://localhost:8888/cocoon-forms-sample/form1.flow (first one in Forms
samples)
I got following exception:
Caused by: java.lang.NullPointerException
at
org.apache.cocoon.template.JXTemplateGenerator.setup(JXTemplateGenerator.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:72)
[...]
After taking quick look on this problem I saw that JXTemplateGenerator is
broken by the fact that it
implements (indirectly, by extending AbstractXMLProducer) Recycable interface.
Implementing this
interface makes JXTemplateGenerator handled by our Avalon-Spring bridge instead
of pure Spring and
treated as an Avalon component.
Why bridge code is invoked at all for components from spring's context.xml?
Sounds counter intuitive. I would expect only components from
cocoon.xconf/sitemap.xmap would be handled by the bridge code.
Comments?
Vadim
