Zedler, Michel wrote:
Thank you for your answer.
I made my hands dirty and it really seems to be possible,
but I don't know how to register castor's (de)serialisers within wsif.
<>Michel,
i think that what we could do is to try to convert castor generated beans into DOM node and then use it inside WSIF?
So how can I register the Castor (De)Serializers when using WSIF?if possible try to cast WSIFPort to WSIFPort_ApacheAxis and then call getCall() to get org.apache.axis.client.Call - that should give you place to register castor (de)serializers so they are sued by Apache AXIS provide
(Using latest cvs versions of both ws-axis and ws-wsif)
however this is solution for *just* axis provider it would be nice to have Castor XML<->Java conversion working for any provider ...
thanks,
alek
-----Urspr�ngliche Nachricht----- Von: Aleksander Slominski [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 10. August 2004 18:26 An: [EMAIL PROTECTED] Betreff: Re: Experience with Castor and WSIF?
Zedler, Michel wrote:
Hi all,
I successfully integrated the castor data binding framework (www.castor.org)
into axis. Now I don't want wo lose the benefits of WSIF when
calling my service from the client side.
I guess, that WSIF would need to be capable of marshalling and unmarshalling
castor generated objects from and to XML.
Is there any way to make WSIF and Castor play together?
i think that AXIS-SOAP provider may work after you manage to setup required mappings - did you try?
however when thinking about it my opinion is that WSIF should depend more on XML Infoset when passing data to providers and not Java objects - if Java object is passed to provider and provider does not know how to deal with it it should ask WSIF runtime to convert it to preferred XML representation (DOM, SAX events, whatnot) - if we had this then this would be the place where to plug Castor for *all* providers - alas we do not have this capability ...
thanks,
alek
-- The best way to predict the future is to invent it - Alan Kay
