--- Venkat Reddy <[EMAIL PROTECTED]> wrote:
> As far as I understand, XML-Beans is useful only at
> the code
> generation time, to generate Java code corresponding
> to an input XML
> schema. An xml-beans specific implementation of
> OMXBContext will know
> how to do the conversion between an XML instance
> (OMElement) and the
> corresponding Java object instantiated using the
> xml-bean generated
> java code. Please confirm this understanding.
>
Correct. XMLBeans and JAXB can be integrated with OM
easily through StAX and SAX APIs. However the problem
is to expose the type mappings present in the
generated code to our stub/skeleton generation tool.
XMLBeans exposes these mappings (after code
generation) but in the case of JAXB I couldn�t find
any method to pull them out.
In the case of XMLBeans the XMLBeans jar will be
required at run-time as well. I don�t think XMLBeans
generates POJOs--- none of the generated classes have
fields for representing info-set items for instance.
So my guess is that it works in more or less the same
way like the beast that Alex was arguing for sometime
back on the list.
> Jaya was wondering if this serialization and
> deserialization go into a
> seperate phase?
Are we talking about Axis2 phases? If so the answer is
NO, since that could happen in any phase depending on
when and how the tree is accessed.
thanks
--dasarath
>
> -- venkat
>
>
> On 5/12/05, Davanum Srinivas <[EMAIL PROTECTED]>
> wrote:
> > Dasarath,
> >
> > don't worry about the size right now...get it
> working and then we can
> > ask xmlbeans folks to get us a jar of what we
> want.
> >
> > -- dims
> >
> > On 5/12/05, Dasarath Weeratunge
> <[EMAIL PROTECTED]> wrote:
> > > Two things:
> > > 1. Data binding needs to be layered on top of
> OM
> > > and not incorporated into it.
> > > 2. External data-binding tools should be
> pluggable
> > > into our data binding framework.
> > >
> > > So I propose that we go for the following:
> > >
> > > package org.apache.axis.om.xmlbinding.*
> > >
> > > interface OMXBContext {
> > > Object getObjectValue(OMElement e);
> > > OMElement getOMElement(Object e);
> > > String getTypeMapping(QName qname);
> > > }
> > >
> > > OMXBContextFactory {
> > > OMXBContext createContext(Properties prop);
> > > }
> > >
> > > There will be different implementations of
> OMXBContext
> > > interface for different data-binding tools
> including
> > > our own. The interface encapsulates the
> particular
> > > marshalling/un-marshalling mechanisms specific
> to the
> > > framework. For instance in the case of JAXB, for
> > > converting objects to OM, one needs to use the
> > > SAXOMBuilder. In the case of XMLBeans we have
> the
> > > option of using either StAX builder or the SAX
> > > builder. In our own data-binding tool we can
> optimize
> > > this and create OM directly if need be without
> going
> > > through XML APIs.
> > >
> > > At the moment I'm working on a code generation
> tool.
> > > The tool uses the schema model of XMLBeans.
> However,
> > > the XMLBeans jar is ~1.8MB! So we will either
> have to
> > > separate out the schema model into a smaller jar
> file
> > > or write our own thing.
> > >
> > > So if you guys can shoot questions/proposals we
> can
> > > discuss those and move ahead.
> > >
> > > Thanks
> > > --dasarath
> > >
> > > --- jayachandra <[EMAIL PROTECTED]> wrote:
> > > > Dasarath et al,
> > > > Can you think loud what you are finalizing in
> the
> > > > databinding in
> > > > Axis2.0. May be we can input our views and
> help in
> > > > the implementation
> > > > as well.
> > > >
> > > > Bye
> > > > Jayachandra
> > > > --
> > > > -- Jaya
> > > >
> > >
> > >
> __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > > http://mail.yahoo.com
> > >
> >
> > --
> > Davanum Srinivas -
> http://webservices.apache.org/~dims/
> >
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
