Hi Thomas,
I'm sorry if I'm a bit confused but is this supported in JbossWS 2.0.X? The
original post is from a week before 2.0.0 GA, which suggest that it is
available but subsequent replies suggest that it will not be available until
JbossWS 2.1.
If it indeed is possible to choose JAX-WS stack
Currently, we are working on CXF integration issues, which unfortunately are
still delaying the release.
Native and Metro integration is completed already. You can try the latest from
trunk.
http://jbws.dyndns.org:8180/hudson/
View the original post :
http://www.jboss.com/index.html?module=b
Hi Thomas,
When is the expected release date of JBossWS-2.1.0?
I am hoping to solve the type substitiution issue in the jbossws 2.0.0 GA by
upgrading to 2.1.0
Thank you!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070141#4070141
Reply to the post :
http
lol, hit the return button by accident:
i meant to say should _not_ depend on the WS stack
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064999#4064999
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064999
__
anonymous wrote :
| In short, deployment archives should depend on the WS stack that is
currently installed.
|
He probably means should depend on the WS stack...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064998#4064998
Reply to the post :
http:/
Common deployment model means that you can use standard EE5 deployments with
all tree stacks. You will not have to provide Metro or CXF proprietary
descriptors. In short, deployment archives should depend on the WS stack that
is currently installed.
Common management interface means that you ca
Hi Thomas,
Could you please elaborate (or direct us to some discussions that elaborate
on) the following comment from your earlier post :
"There will be a common deployment model and management interface to all
deployable stacks. "
Thank you!
jeff
View the original post :
http://www.jboss.
