Hi Yoav,
Good points. I think first you should approach to WSDL2Java generation. You
can see [1] for some information on it. That article was written by our Mr.
ADB and I think he will help you if you have any problem during the process.
I think first you will have to convince the devs here, that J2XB is really
good by some sorta performance or features implemented. Then they will deep
dive in to J2XB.
Please read the above article [1] and let us know when you have problems.
Ajith and Amila (gurus of ADB) will help you for sure. ("A" in ADB can be
any of "Axis2", "Ajith" or "Amila" ;) )
One another point. ADB is not meant to be a complete data binding framework.
We designed it to be a simple framework which is tightly integrated in to
things like AXIOM within Axis2. ADB might serve the purpose most of the
time, I think. I specially like it since it is light weight and tightly
coupled in to the internals of Axiom.
If J2XB is a light weight framework to generate schema from Java classes,
then perhaps we might be able to use that to improve our Java2WSDL as well.
For the time being, IIRC, we use some sorta reflection and annotations
mechanism and definitely we like to get some help for that too.
Thanks,
Eran Chinthaka
[1] : http://wso2.org/library/35
On Sun, Jun 1, 2008 at 1:51 AM, Yoav Abrahami <[EMAIL PROTECTED]> wrote:
> Hi Eran,
>
> J2XB certainly introduces new functionality beyond ADB, XmlBeans or JiBX.
>
> * XMLBeans Supports Java code generation from an XML schema - it requires
> that the generated binding classes be separate then the application classes
> and it does not generate an XML schema from Java code.
>
> * JiBX has good support for binding Java Beans to XML and back. However, it
> is still missing some features such as XML Schema generation (which is
> important for WSDL generation), XML list styles, flexibility in enumeration
> support, etc.
>
> * ADB - well, ADB is a simplistic databinding framework, but still has a
> lot of features missing compared to J2XB.
>
> I think that integrating J2XB into Axis 2 is a good idea (and hence this
> thread). However, I find it difficult to do so myself - I am not a member in
> the Axis 2 dev team. As such, except the technical difficulty, I do not have
> the knowledge now Axis 2 is structured and where the I should integrate J2XB
> (in the code). I am seeking help from you guys here to help in this
> integration.
>
> I can think of 4 possible integration points:
>
> * marshaling and unmarshaling XML to Java classes used as parameters for an
> Axis WS (in an AAR archive).
>
> * marshaling and unmarshaling MXL to Java classes used as parameters for an
> Axis WS client
>
> * automatic WSDL generation for a service in an AAR.
>
> * extending Java2WSDL to support J2XB binding
>
> I am basically looking of developer involvement (from the Axis team) to
> help creating those integrations.
>
> Cheers,
> Yoav
>
>
> On Sat, May 31, 2008 at 5:13 AM, Eran Chinthaka <[EMAIL PROTECTED]>
> wrote:
>
>> Perhaps you can integrate J2XB into Axis2 and prove, using some
>> experimental results, the areas J2XB is better than ADB or XMLBeans or JiBX.
>>
>> And I hope this will motivate our ADB team and Mr. JiBX (Dennis) to
>> compete with J2BX :)
>>
>>
>> On Fri, May 30, 2008 at 4:30 AM, Yoav Abrahami <[EMAIL PROTECTED]> wrote:
>>
>>> Hi Axis dev team.
>>>
>>> (I hope this is the right mailing list. if not, my apologies)
>>>
>>> I have recently released the J2XB (Java 2 XML Binding) project as an open
>>> source project. I believe J2XB can be used as a new binding for Axis 2 and
>>> offer some unique advantages over the existing bindings.
>>> see at http://j2xb.sourceforge.net/index.html
>>>
>>> J2XB is unique in that it allows to annotate Java classes and generate
>>> the XML schema (XSD) from the Java classes, including facets, constraints,
>>> etc. In addition, it allows to map any Java class to XML structure in a vary
>>> flexible way, supporting any Java class (POJO) including classes with
>>> non-trivial constructors and factories. All this is performed without need
>>> to write code or to generate code.
>>>
>>> Connecting J2XB and Axis 2 will result in the ability to white a Web
>>> Service the axis way (POJO in an AAR) with WSDL generated including XSD
>>> generated form the Java classes. The XSD generated can then be controlled
>>> using the J2XB annotations.
>>>
>>> Note that J2XB allows considerably more control over the XML structure
>>> compared to JAXB.
>>>
>>> In hope that there is interest to join forces,
>>>
>>> Cheers,
>>> Yoav
>>>
>>>
>>>
>>
>>
>> --
>> With Mettha,
>> Eran Chinthaka
>>
>> --------------------------------------------------------------------
>> Health is the greatest gift; contentment is the greatest wealth; trusting
>> is the best relationship; nirvana is the highest joy. - Dhammapada
>
>
>
--
With Mettha,
Eran Chinthaka
--------------------------------------------------------------------
Health is the greatest gift; contentment is the greatest wealth; trusting is
the best relationship; nirvana is the highest joy. - Dhammapada
