[jbossws-dev] Moving to SPI 3 M1

[Richard Opalka]

Hi Heiko,

  I finally found some time to study the SPI 3.0 M1 first cut.
I identified the following basic building blocks of the new SPI:

* InvocationHandler
* RequestHandler
* EndpointRegistry
* TransportManager
* WSFRuntime
* DeploymentAspect
* DeploymentModel

Comments:

* I don't like WSFRuntime interface name.
  WebServiceRuntime would be a better term.
* I don't like there are DeploymentAspects involed.
  I guess your next step is to remove dependency on them?
* The DeploymentModel is going to be part of the SPI 3.0
  or it's just part of this first prototype?

Questions:

* What is going to change in SPI 3.0 M2?
* When do you plan to provide SPI 3.0 M2 for preview?
* Don't you need help with some parts of SPI 3.0?

Richard

Heiko Braun wrote:
> Yesterday I commited the first cut of SPI 3 migration to
>
> - Container 4.2.2, 4.2.3 and 5.0.1
> - Native and CXF
>
> Tonight Hudson runs seem to be OK, except for some JAX-RPC regression in
> Native. I am going to look at it today.
>
> One that is done, I am planning to continue with Metro and then finally
> take a look at the remaining containers 4.2.1 and 5.0.0.
>
> One of the things you already look at is the new Transport API, which
> allows us to use JBossWS embedded. Currently this features resides with
> native. Samples can be found under 'tests/embedded'.
>
> Rock on'
>
>
>
> _______________________________________________
> jbossws-dev mailing list
> jbossws-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-dev
>