This XML file should allow us to reproduce the element creation sequence causing your error. For now, we do not have many hints about what is going on.
If it is source code that matters, you may remove all the <note> markers from the file, they contain all operation content and documentation from your sources.
pcouas wrote:
I'll describe what to do if you want to try finding the cause of the error by yourself:
- Download JavaDesigner sources from the community forge
- Set up an eclipse debug environment as described in the module developer's guide .
- Add a breakpoint on ClassCastException and launch your reverse again.
=> the execution should stop when the error occurs, and you should be able to identify which element is causing it.
If it is source code that matters, you may remove all the <note> markers from the file, they contain all operation content and documentation from your sources.
pcouas wrote:
which xml sequence search in this file ?
As I said, it is the creation sequence that matters rather than the file itself.I'll describe what to do if you want to try finding the cause of the error by yourself:
- Download JavaDesigner sources from the community forge
- Set up an eclipse debug environment as described in the module developer's guide .
- Add a breakpoint on ClassCastException and launch your reverse again.
=> the execution should stop when the error occurs, and you should be able to identify which element is causing it.