Hi Jacob, Thanks for the reply. The following bullet item is listed on http://wiki.apache.org/xmlbeans/V2Features:
SAAJ 1.2 Support - SAAJ defines a SOAP Envelope Document structure and in the latest spec release SAAJ 1.2 it is defined to be tightly integreated with DOM. In V2 it should be possible to create a SAAJ Envelope structure such that the SAAJ Nodes are the same objects as the underlying DOM Nodes. This would save a SAAJ implementation on top of DOM not to have a parrallel Node tree and should improve performance substantially. Note the goal is not to develop a SAAJ implementation within XMLBeans but to allow for a SAAJ 1.2 implementation to be effectively implemented on XMLBeans. SAAJ is a web services related technology and could have web services container specific functionality (logging, error handling, etc.) in it's implementation. XMLBeans V2 will have a SAAJ interface and the underlying XML Store tree nodes will implement the appropriate SAAJ interfaces and call back through the XMLBeans defined SAAJ interface. The goal is that any web services container could implement SAAJ 1.2 efficiently over XMLBeans. While trying to figure out how to use this new feature, I noticed the interface org.apache.xmlbeans.impl.newstore2.Saaj in the v2 source code, which I assume is related to the above feature. It appears one can enable proxied SAAJ support in the live DOM store by setting the Saaj.SAAJ_IMPL XmlOption to an object that implements the Saaj interface when creating an XmlObject. The part that confused me is that there are no classes in the v2 source base that implement the Saaj interface. Thanks, Ian > Hey Ian, > I'm a little confused as to what you are trying to do. > If you want to use a SOAPEnvelope type from an xsd you can always scomp > the soap xsd and go from there. > > If you would like to specify to SAAJ implementation you can add > something like this when running a class: > -Djavax.xml.soap.SOAPFactory=com.foo.baz.SOAPFactoryImpl > -Djavax.xml.soap.MessageFactory=com.foo.baz.MessageFactoryImpl > > If this doesn't answer your questions, can you give us more information. > > I'm lost as far as the Saaj class you are referring to since its not in > the API. > -Jacobd > > -----Original Message----- > From: Springer, Ian P. [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 24, 2005 5:50 PM > To: Ali, Haneef > Cc: dev@xmlbeans.apache.org > Subject: RE: XMLBeans and SAAJ > > I never got a reply from my post to the users list. I'll try reposting it to dev. From looking at their source, I think you would do something > like: > > XmlOptions xmlOpts = new XmlOptions(); > Saaj saaj = new ?????(); > xmlOpts.put( Saaj.SAAJ_IMPL, saaj ); > XmlObject xBean = XmlObject.Factory.parse( new File( > "SoapEnvelopeInstance.xml" ), xmlOpts ); > System.out.println( xBean instanceof SOAPEnvelope ); > // the returned XMLBean magically implements SOAPEnvelope, proxying its > methods to the Saaj impl under the covers > > The only problem is I don't see any implementations of the Saaj > interface in the XMLBeans code base. I'm not sure if users are expected > to write their own impl of Saaj. If this is the case, it would be helpful if an example/default impl was provided. > > Would someone from the XMLBeans dev team please shed some light on how to use this feature? > > Thanks in advance, > Ian > > | -----Original Message----- > | From: Ali, Haneef > | Sent: Tuesday, May 24, 2005 6:30 PM > | To: Springer, Ian P. > | Subject: XMLBeans and SAAJ > | > | Hi, > | > | Did you get any examples on how to use the SAAJ support available in xmlbeans? > | > | Haneef > | > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
