Good question. I know that the JAX-RPC spec defines how the WSDL <-> Java
mapping should take place. However, I can't really tell if the WSDL2Java
process in Axis uses the serialization framework and could be configured to
use a different set of factories. My guess would be no. Source code
generation based on a binding is a different animal from runtime mapping of
data types. If you are going to use an external serialization framework, I
believe the expectation is that that framework should then be responsible
for source generation. Maybe the handling of the <types> section of the
WSDL could be redesigned to have configurable handlers or something.
Davanum?
Steve Maring
"Mark D. Hansen"
<[EMAIL PROTECTED] To: <[EMAIL PROTECTED]>
m> cc:
07/25/2003 09:58 Subject: RE: WSDL2Java with JAXB ??
AM
Please respond to
axis-user
JAXB support in Axis would be great - but how could you use JAXB to
generate WSDL from Java classes? Doesn't JAXB only generate one direction:
XML Schema --> Java classes?
-- Mark
> -----Original Message-----
> From: Robert Lowe [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 25, 2003 2:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: WSDL2Java with JAXB ??
>
>
> The latest version of the JAXB-RI is free for commercial use,
> and is about
> to become open source. It was only the beta that wasn't licensed for
> commercial use. Also, you don't need to modify your XSD at
> all, you can use
> an external binding schema.
>
> My limited of JAXB has been that it's pretty solid--I would
> love to see JAXB
> support in Axis.
>
> - Rob
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, July 24, 2003 8:45 PM
> Subject: Re: WSDL2Java with JAXB ??
>
>
> > Yes, you could write a JAXBSerializer, JAXBDeserializer,
> > JAXBSerializerFactory, and JAXBDeserializerFactory. Then,
> map your QNAME
> > to your Java class, specifying these factories, in the
> typemapping section
> > of your WSDD.
> >
> > However, you might want to consider using Castor or JiBX
> instead, and
> write
> > serializers for those. I don't believe the JAXB-RI is licensed for
> > commercial use, and to my knowledge (I could be wrong, and
> usually am),
> > there are no implementations of the latest spec besides the
> RI. Also, you
> > will have to muddy up your XSD to get your classes to implement
> > serializable, and anything that uses thoses classes will
> have to have all
> > of the JAXB and JAXB related jars in it's classpath,
> regardless of whether
> > or not it intends to do (un)marshalling. Also, the
> abstraction of the
> > generated classes in JAXB is a bit annoying. I just want
> stupid data
> types
> > with direct instantiation that are not coupled with the
> binding framework.
> > Castor and JiBX will let you map any standard XML Schema
> (i.e. no other
> > namespaces) to plain-old JavaBeans. JiBX performance
> rocks, but many more
> > developers are familiar with Castor.
> >
> > The current Castor serializer in the Axis code assumes a
> default mapping.
> > I've seldom gotten away with not having to write a mapping file with
> Castor
> > so you may have to write your own serializer. I'm writing
> one right now
> > that just looks for a file named "mapping.xml" in the classpath.
> >
> > Cheers
> > Steve Maring
> >
> >
> >
> >
> >
> > "Mark D. Hansen"
> > <[EMAIL PROTECTED] To: "AXIS
> Users (E-mail)"
> <[EMAIL PROTECTED]>
> > m> cc:
> > 07/23/2003 05:53 Subject:
> WSDL2Java with
> JAXB ??
> > PM
> >
> > Please respond to
> > axis-user
> >
> >
> >
> >
> >
> >
> > Is is possible to replace the XML Schema --> Java mapping
> mechanism in
> > WSDL2Java with JAXB? Alternatively, is there another way
> to use JAXB as
> > the binding mechanism within the Axis framework?
> >
> > Thanks,
> >
> > Mark
> >
> >
> >
> >
> > _________________________________________________________________
> > 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.
> >
>
_________________________________________________________________
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.
