dev@jax-ws.java.net

Re: Just a heads up that I started tweaking the JMS transport...

From: Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_Sun.COM>
Date: Thu, 04 Jan 2007 15:55:23 -0800

Kohsuke Kawaguchi wrote:
> 1. Adding Maven POM for the build
> 2. Converting to Tube

Done.

> 3. Adding spring support as the deployment mechanism

I have a question/brainstorming with respect to the deployment mechanism
of the JMS transport.

While looking at the JMS transport (and thinking about other transports,
like SMTP), it became clear to me that we can't afford to have different
  deployment mechanisms for each one of them.

So I'd like to rework the deployment of the JMS transport around our
Spring support [1]. This would enable the consistent configuration
mechanism across all transports. For example, you can configure
handlers, bindingID, pipeline assembler, etc, all in the same way.

Would that be OK to you, Oleksiy? Does that make sense? This makes it
possible to deploy JMS transport into AppServer without writing
boiler-plate ejb-jar.xml (and similarly we won't need a separate
"stand-alone launcher" for each transport.)

We can talk over the phone if it helps.


[1] https://jax-ws-commons.dev.java.net/nonav/spring/
-- 
Kohsuke Kawaguchi
Sun Microsystems                   kohsuke.kawaguchi_at_sun.com