Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
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.
The debugger showed
Daniel Fagerstrom wrote:
Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
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.
Need more info to be able to help. Somwhere in your script 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
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
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
Ok.
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
Daniel Fagerstrom wrote:
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.
The debugger showed that it's this line:
