You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Sanjiva Weerawarana <sa...@opensource.lk> on 2006/02/13 15:56:11 UTC

timing on need for JAX-WS and JAX-B support

Hi Guys,

Can you give an indication of when you expect to go for J2EE 1.5
certification and hence require JAX-WS and JAX-B support from Axis2?
Getting some indication of the timing will help us prioritize and target
it to a specific version of Axis2. (We're not putting it into 1.0; hence
the question!)

Sanjiva.


Re: timing on need for JAX-WS and JAX-B support

Posted by Dain Sundstrom <da...@iq80.com>.
On Feb 14, 2006, at 12:43 AM, Sanjiva Weerawarana wrote:

> We haven't committed to doing JAX-B yet but there's been some  
> interest.

I'd love to work on JAX-B but there are only so many hours in the day :(

> One concern with JAX-B is that its J2SE 1.5 specific and we want to
> continue to run under 1.4. I'd be interested in understanding the
> Geronimo 1.4/1.5 strategy.

I see two possible strategies here:

1) retrotranslator.sourceforge.net - build time or runtime  
translation from Java 5 byte code to Java 1.4 byte code.  Strangely  
enough, it seems to work perfectly (including debugging).  FWIU, the  
conversion from 5 to 1.4 is a fairly trivial 1-to-1 translation.   
Baisically, it removes the new extra op code in Java 5 and remaps new  
apis in the java.* packages to apis in net.sf.retrotranslator.runtime.*.

2) abstraction layer - the main code is written in Java 1.4 and there  
is an abstraction layer that deals with the Java 5 spcific bits like  
looking up annotations.

James Strachan has done some extensive testing with retrotranslator  
(including the JAX-B ri) and really wants to use it.  I think option  
2 will work but will require a ton of work, so I'm leaning towards  
option 1.  My gut says that option 1 will make people nervous at  
first, but once they see it working, I think they will learn to love  
the bomb ;)

-dain

Re: timing on need for JAX-WS and JAX-B support

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Mon, 2006-02-13 at 11:16 -0800, David Blevins wrote:
> I could use jaxb support now.  I'd like to use it instead of castor  
> or xmlbeans for marshalling deployment descriptors -- or rather with  
> castor or xmlbeans if either of them implement jaxb.

We've done our own partial schema to Java mapping thing (called ADB ..
Axis Data Binding) that covers maybe 80% of schema. 

> I didn't know Axis2 was going to implement jaxb.  Are the xmlbeans  
> guys going to implement it too?

We haven't committed to doing JAX-B yet but there's been some interest.
We've started on SAAJ and JAX-WS but not specific timeline yet.

One concern with JAX-B is that its J2SE 1.5 specific and we want to
continue to run under 1.4. I'd be interested in understanding the
Geronimo 1.4/1.5 strategy.

Sanjiva.


Re: timing on need for JAX-WS and JAX-B support

Posted by Bruce Snyder <br...@gmail.com>.
On 2/13/06, David Blevins <da...@visi.com> wrote:
> On Feb 13, 2006, at 11:45 AM, Bruce Snyder wrote:
>
> > On 2/13/06, David Blevins <da...@visi.com> wrote:
> >> I could use jaxb support now.  I'd like to use it instead of castor
> >> or xmlbeans for marshalling deployment descriptors -- or rather with
> >> castor or xmlbeans if either of them implement jaxb.
> >>
> >> I didn't know Axis2 was going to implement jaxb.  Are the xmlbeans
> >> guys going to implement it too?
> >
> > A couple of weeks ago I began investigating what it will take for
> > Castor support the JAXB 2 API on top of the existing engine. It's
> > certainly doable with one issue being the ability to cover the entire
> > spec in a timely manner if I'm the only one working on it. There are
> > certainly other concerns, but that's the biggest one at the moment.
> >
>
> You guys already support fancy-pants mapping.  How soon do you think
> you could get that part into the 80% compliant range?

That's a good question. Having just started looking into this
recently, I don't have a handle on that yet. Part of the work involved
is getting through the 375 page spec ;-).

The other concern I have is how changes to support the JAXB spec will
affect the database side of Castor. I've been thinking that starting a
Castor 2 branch would be a good idea and do all of the work in there -
kinda like what David did with OpenEJB 2. It would also make it easier
to know that Castor 2 supports JAXB 2.

> That'd at least be enough to get started.

I agree - it's a good starting point.

Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache Geronimo (http://geronimo.apache.org/)

Castor (http://castor.org/)

Re: timing on need for JAX-WS and JAX-B support

Posted by David Blevins <da...@visi.com>.
On Feb 13, 2006, at 11:45 AM, Bruce Snyder wrote:

> On 2/13/06, David Blevins <da...@visi.com> wrote:
>> I could use jaxb support now.  I'd like to use it instead of castor
>> or xmlbeans for marshalling deployment descriptors -- or rather with
>> castor or xmlbeans if either of them implement jaxb.
>>
>> I didn't know Axis2 was going to implement jaxb.  Are the xmlbeans
>> guys going to implement it too?
>
> A couple of weeks ago I began investigating what it will take for
> Castor support the JAXB 2 API on top of the existing engine. It's
> certainly doable with one issue being the ability to cover the entire
> spec in a timely manner if I'm the only one working on it. There are
> certainly other concerns, but that's the biggest one at the moment.
>

You guys already support fancy-pants mapping.  How soon do you think  
you could get that part into the 80% compliant range?

That'd at least be enough to get started.

-David



Re: timing on need for JAX-WS and JAX-B support

Posted by Bruce Snyder <br...@gmail.com>.
On 2/13/06, David Blevins <da...@visi.com> wrote:
> I could use jaxb support now.  I'd like to use it instead of castor
> or xmlbeans for marshalling deployment descriptors -- or rather with
> castor or xmlbeans if either of them implement jaxb.
>
> I didn't know Axis2 was going to implement jaxb.  Are the xmlbeans
> guys going to implement it too?

A couple of weeks ago I began investigating what it will take for
Castor support the JAXB 2 API on top of the existing engine. It's
certainly doable with one issue being the ability to cover the entire
spec in a timely manner if I'm the only one working on it. There are
certainly other concerns, but that's the biggest one at the moment.

Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache Geronimo (http://geronimo.apache.org/)

Castor (http://castor.org/)

Re: timing on need for JAX-WS and JAX-B support

Posted by David Blevins <da...@visi.com>.
I could use jaxb support now.  I'd like to use it instead of castor  
or xmlbeans for marshalling deployment descriptors -- or rather with  
castor or xmlbeans if either of them implement jaxb.

I didn't know Axis2 was going to implement jaxb.  Are the xmlbeans  
guys going to implement it too?

-David


On Feb 13, 2006, at 6:56 AM, Sanjiva Weerawarana wrote:

> Hi Guys,
>
> Can you give an indication of when you expect to go for J2EE 1.5
> certification and hence require JAX-WS and JAX-B support from Axis2?
> Getting some indication of the timing will help us prioritize and  
> target
> it to a specific version of Axis2. (We're not putting it into 1.0;  
> hence
> the question!)
>
> Sanjiva.
>


Re: timing on need for JAX-WS and JAX-B support

Posted by Jacek Laskowski <el...@gmail.com>.
2006/2/13, Sanjiva Weerawarana <sa...@opensource.lk>:
> Hi Guys,
>
> Can you give an indication of when you expect to go for J2EE 1.5
> certification and hence require JAX-WS and JAX-B support from Axis2?

Hi Sanijva,

I alone wish to know when we're going to support Java EE 1.5. I don't
remember any discussion about an exact timeframe or anything alike,
but I wouldn't be mistaken saying all of us would be interested in
doing it as soon as possible. I think we need to read the spec from
cover to cover, divide it on short and simple tasks, create them in
JIRA and move on (how simple it was to write it ;)).

As Dave B. already said, there's some interest in using JAX-B in
OpenEJB 3 to handle xml files. I don't know it at all, and am going to
read over the JAX-B spec soon. I think that the sooner the spec will
be available in Axis2, the better.

> Sanjiva.

--
Jacek Laskowski
http://www.laskowski.org.pl