The SPI actually breaks down into two abstraction layers
#1 container SPI (deployment model, invocation, etc)
#2 stack SPI (request/response processing)
The SPI is not bound to JBossAS, hence it should theoretically be
possible to support other containers (i.e. Tomcat) and other WS stacks
(i.e. Axis)
Currently we have SPI implementations for jboss-4.0, jboss-4.2,
jboss-5.0 on the container side and on the stack side for
JBossWS-Native, Sun-Metro, Apache-CXF.
cheers
-thomas
On Mon, 2007-09-10 at 15:44 +0200, Tom Baeyens wrote:
Hi Thomas, meet Charles and Miguel from Bull. I'm working with
them on the new
Process Virtual Machine implementation.
Charles and Miguel, meet Thomas Diesler, the web services lead at JBoss.
I heard you had injected an abstraction interface for the web service stack to be
pluggable. Bull is interested in this layer. Two questions that I couldn't answer
were the following:
Was that layer designed only for internal usage or is it also consumable from by
external clients ?
Can you use the pluggability layer outside the appserver ? Which WS-stack
implementations can be used in e.g. tomcat ?
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx