JAX-WS 2.1

[Jarek Gawor <jg...@gmail.com>]

Hi,

I'm working on JAX-WS 2.1 upgrade in Geronimo and right now I'm
looking into any issues with JAX-WS 2.1 and OpenEJB that I discovered
through my work in Geronimo. So far I've found one issue:
https://issues.apache.org/jira/browse/OPENEJB-917. I would appreciate
if somebody could take a look at the patch attached to the bug and
comment or suggest better ways of doing things or apply it.

Also, where does org.apache.openejb:javaee-api come from? I can't find
source for this package. Can it be updated to have JAX-WS 2.1 API in
it? Or maybe we could just add a dependency on Geronimo JAX-WS 2.1
spec jar to the appropriate modules. That way you could remove the
javax/xml/ws packages from openejb-core or openejb-client modules.

Thanks,
Jarek

Re: JAX-WS 2.1

[David Blevins <da...@visi.com>]

Committed in trunk, publishing new snapshots.

On Sep 18, 2008, at 9:58 AM, Jarek Gawor wrote:

> On Wed, Sep 17, 2008 at 9:34 PM, David Blevins  
> <da...@visi.com> wrote:
>> Hi Jarek,
>>
>>
>> Looks pretty good to me.  I'd also be fine with moving the  
>> EjbWsContext
>> copies into the core.webservices package.  I'll hold off for  
>> another package
>> if you wanted to do that or else I'll just apply this tomorrow.
>
> Great. core.webservices package sounds good to me.
>
>> We used the maven shade plugin to repackage all the spec jars into  
>> one uber
>> jar.  We could roll another jar that has the jax-ws 2.1 apis in  
>> there.
>> Would there be any issues with that other than jar size?
>
> I don't think so. I updated the javaee-api-5.0-1.jar file (locally)
> with the extra JAX-WS 2.1 classes, removed the
> container/openejb-core/src/main/java/javax/ and
> server/openejb-client/src/main/java/javax/ directories and built the
> code with tests and everything went fine.
>
> Jarek
>

Re: JAX-WS 2.1

[Jarek Gawor <jg...@gmail.com>]

On Wed, Sep 17, 2008 at 9:34 PM, David Blevins <da...@visi.com> wrote:
> Hi Jarek,
>
>
> Looks pretty good to me.  I'd also be fine with moving the EjbWsContext
> copies into the core.webservices package.  I'll hold off for another package
> if you wanted to do that or else I'll just apply this tomorrow.

Great. core.webservices package sounds good to me.

> We used the maven shade plugin to repackage all the spec jars into one uber
> jar.  We could roll another jar that has the jax-ws 2.1 apis in there.
>  Would there be any issues with that other than jar size?

I don't think so. I updated the javaee-api-5.0-1.jar file (locally)
with the extra JAX-WS 2.1 classes, removed the
container/openejb-core/src/main/java/javax/ and
server/openejb-client/src/main/java/javax/ directories and built the
code with tests and everything went fine.

Jarek

Re: JAX-WS 2.1

[David Blevins <da...@visi.com>]

Hi Jarek,

On Sep 16, 2008, at 10:41 AM, Jarek Gawor wrote:

> I'm working on JAX-WS 2.1 upgrade in Geronimo and right now I'm
> looking into any issues with JAX-WS 2.1 and OpenEJB that I discovered
> through my work in Geronimo. So far I've found one issue:
> https://issues.apache.org/jira/browse/OPENEJB-917. I would appreciate
> if somebody could take a look at the patch attached to the bug and
> comment or suggest better ways of doing things or apply it.

Looks pretty good to me.  I'd also be fine with moving the  
EjbWsContext copies into the core.webservices package.  I'll hold off  
for another package if you wanted to do that or else I'll just apply  
this tomorrow.

> Also, where does org.apache.openejb:javaee-api come from? I can't find
> source for this package. Can it be updated to have JAX-WS 2.1 API in
> it? Or maybe we could just add a dependency on Geronimo JAX-WS 2.1
> spec jar to the appropriate modules. That way you could remove the
> javax/xml/ws packages from openejb-core or openejb-client modules.

We used the maven shade plugin to repackage all the spec jars into one  
uber jar.  We could roll another jar that has the jax-ws 2.1 apis in  
there.  Would there be any issues with that other than jar size?

-David