Hi,
I'm new to Axis2 and I've been given the task to migrate the Xfire web
service code that one of my colleagues have written to Axis2. From all the
binding mechanisms that Axis2 supports, Jibx appealed to me the most. I can
use jibx2wsdl to generate the WSDL from the POJOs I have.
Relying on just plain jibx2wsdl method will not work for my case because a
couple of the methods provided by the web service returns and accepts as
parameters org.w3c.Document objects. org.w3c.Document as you know is an
interface and there is no way for me to know at build time the subclasses
going to be used by the client at runtime so I can't include the possible
subclasses for that interface in the binding process. Can you suggest how I
should handle this case?
Another problem I have is that there are two methods, upload and download
which accepts and returns javax.activation.DataSource object, which again is
an interface. I'm planning to use MTOM for this but I'm just not sure how
hard it will be to get jibx and axiom data binding working together. Has
anyone on this list already tried this before?
Thanks,
Gerson
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
