It's difficult to diagnose without full details, but this is most likely
due to having two versions of the data classes, with the non-bound
version loaded rather than the bound one. I've seen this before when
bundling Axis (using the bound data classes) as part of an .ear file
that has the non-bound data classes for the actual EJB code.
- Dennis
babloosony wrote:
Hi All,
I am very fond of JiBX and I am trying to use it for implementing my
own (De)Serializers replacing AXIS default (De)Serializers. However
when I register my (De)Serializers with AXIS's server-config.wsdd file
and start my web service deployed on WebSphere 5.0, I am getting an
exception which in simple terms translates to
"com.tri.TriJibxDeserFactory Unable to create Tri JiBX deserializer
instance".
Basically what I feel is that even though I distribute my
(de)serializer classes in a jar and keep them in WEB-INF\lib
directory, websphere/jboss somehow does not recognize these classes
and eventually they are not loaded and instantiated. To be more
specific I get JBoss exception like "No classfounder found to load my
<custom class>"
Can anyone tell how do I go ahead and debug this problem and find a
solution. Please suggest ?
Thanks & Regards,
Kumar.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
