I don't think I am going to dive too deep into the operation of the SerializationContext. Only when and why serialize and startElement get called. I'll probably have a draft late next week some time. I'll announce it here.
Cheers
Steve MaringArijith Roy <[EMAIL PROTECTED]> wrote:
Hi Steve,
Hi Steve,
Looks like you have done a lot of work with those debug statements. Could you help me a bit by publishig your findings. I am going through that pain right now and woud appreciate a few pointers in placing the debug statements in the right order .
Thanks.Steve Maring <[EMAIL PROTECTED]>
Hi Cory,
"yes you can" I have a DOCUMENT/LITERAL service whereby the top level element of the soap body represents either a request or response to my method and my parameters are based on external XSD and JavaBeans that I want Castor to marshal. You could easily plug in any marshaller as a cus
th it until I see something better!
Naresh
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 9:42 PM
To: [EMAIL PROTECTED]
Subject: Re: castor & axis & marshalling
Hi Naresh,
Considering you're using an XMLPull parser for des
Title: RE: castor & axis & marshalling
Yes, Dennis is correct.
From reading the JSRs it appears
that JAX-RPC and JAXB will be unified
with respect to data binding and both will
use the new pull parser JSR.
All in all a step in the right direction.
Greg
-Original Message--
Hi Naresh,
Considering you're using an XMLPull parser for deserializing objects,
you might want to look at using JiBX (http://www.jibx.org) in
combination with your framework. JiBX provides high-performance data
binding using an XMLPull parser for unmarshalling. This should eliminate
the need
Cory,
Theoretically, the answer to your question is yes. But practically when
I tried this in the past, Castor mapping approach could not handle the
complexities of my data structures. So I use an XML Pull parser to
serialize / deserialize my business objects. You can look at my detailed
implement
