More specifically, my JavaBean uses the BeanSerializer.  It is dying on
line 143 of BeanSerializer with a NullPointerException:

143>    String encodingStyle = context.getMessageContext().getEncodingStyle
();

Which would certainly imply that the serialization framework cannot be used
outside of the context of a SOAP message and would concur with your
findings.

So, now I guess I go back to something like JiBX to (un)marshal my
JavaBeans outside the context of a SOAP message, and bring the Axis jars
along for the ride since the WSDL2Java sticks Axis metadata and
serialization code at the bottom of JavaBeans.  I suppose, however, that
I'm going to have to put up with that if I want the deserialized JavaBean
coming in from a SOAP request to be the same JavaBean that is passed as a
parameter to a Local SessionBean interface.

<sigh/>

It just seems like a shame that the web service will use one type mapping
facility, and then a different one has to be used externally.

Cheers
Steve Maring




                                                                                       
                                                
                      "George                                                          
                                                
                      Jagodzinski"             To: <[EMAIL PROTECTED]>                 
                                          
                      <[EMAIL PROTECTED]       cc:                                     
                                                
                      .com>                    Subject:  RE: serializer.serialize() 
and org.xml.sax.Attributes                         
                      07/22/2003 01:59                                                 
                                                
                      PM                                                               
                                                
                                                                                       
                                                
                      Please respond to                                                
                                                
                      axis-user                                                        
                                                
                                                                                       
                                                
                                                                                       
                                                




I had no luck with this and I am using Axis with ColdFusion so I am forced
to use an old version of Axis.

>From what I could see the only way to manually deserialize/serialize is to
use the contextimpl, but the contextimpl requires an envelope. The whole
process seemed to have way too much overhead, and I was just trying to
serialize/deserialize attachments. Since my attachments were xml I just
used
castor to build my beans and then i used the castor serialize/deserialize
functionality. I think in the end it was the best way to do it. The
capabilities of castor are far better. The mapping features are great and i
like the fact that my attachment objects are all independant from my
service
code.

soapxdk also has some nice features for this.

--george

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 1:45 PM
To: [EMAIL PROTECTED]
Subject: serializer.serialize() and org.xml.sax.Attributes


I'm trying to manually serialize a JavaBean with the serialize method in
org.apache.axis.encoding.Serializer.  The does anyone know anything about
the attributes parameter?  It does not like me passing it null.

serialize(QName name, org.xml.sax.Attributes attributes,
java.lang.Object value, SerializationContext context)

Cheers
Steve Maring






_________________________________________________________________
         The information transmitted is intended only for the person or
         entity to which it is addressed and may contain confidential
         and/or privileged material.  Any review, retransmission,
         dissemination or other use of, or taking of any action in reliance
         upon, this information by persons or entities other than the
         intended recipient is prohibited.   If you received this in error,
         please contact the sender and delete the material from any
         computer.

Reply via email to