cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <>
Subject Re: JXTemplate initialization in non-flowscript scenarios
Date Fri, 20 May 2005 12:55:43 GMT
Reinhard Poetz wrote:

> Daniel Fagerstrom wrote:
>> Need more info to be able to help. Somwhere in your script 
> I don't use a custom macro, only jx-macro.xml


> you access a
>> value in a jx:set that cannot be evaluated by jxpath, maybe you are 
>> calling an extension function, not sure though. Can you isolate the 
>> expression it happens for.
>> It seem like commons-beanutils not is found, maybe you could add a 
>> <library name="commons-beanutils"/> to the cocoon-block-template 
>> definition in gump.xml. But if that is the case I don't know why it 
>> work without it if you use flow.
> for me it looks like some fallback mechanism because if <map:flow/> 
> has been declared, the problem disappears and *no* commons-beanutils 
> are required.

Ok, but I still need to know the content of the value attribute to the 
jx:set that creates the problem to be able to help. From the stacktrace 
it seem like something goes wrong when JXPath uses reflection on the value.


View raw message