Castor is based on a SAX parser approach to handling XML which isn't
compatible with the StAX parser basis of Axis2. You can still use it,
but it requires a conversion that adds a heavy performance penalty.
If you're using Castor binding definitions you should be able to convert
them to JiBX (which does work well with Axis2) without restructuring
your code. The same thing might apply for Castor code generated from
schema, but I haven't looked into this lately.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Reneta Säll (HF/EBC) wrote:
Hi all,
Do anybody know why Castor as a data binding framework in Axis2 is not
efficient?
We are updating our application from Axis1.4 to Axis2.
Castor is our primary choice as a data binding. To start using a new
one will cost us a lot of
refactoring.
Best regards,
*Reneta Säll*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
