I have this question as well. Since the (upcoming) 4.0.3 will have strong EJB3 support already, and people would like to start working with Webservices (preferably with the annotation support), when JbossWS1.0 release does come out it does make sense to be able to 'add' JbossWS to an existing 4.0.3 AS install (for EJB3 + Webservices).
Is this in the gameplan?
Support in 4.0.3 cannot be guarenteed at the point. Support in some future 4.0.x baseline will be possible as ejb3 and related containers mature.
Scott, thanks for the feedback. I feel more comfortable starting to develop in EJB3 + webservices knowing one of the 4.0.X AS production trees will be supporting these requirements and not have to wait for a production/stable/supported jboss5 in the ever-changing future.
JSR-181 annotations will drive the EJB3 world wrt Web Services.
Someday in the near future, you will have the following to be used with JBoss v4.0.x:
a) JBossWS new stack that is J2EE 1.4 tck compliant.
b) JSR 181 annotation support (drives EJB3 web services).
So be assured that your step is in the right direction.
update: I grabbed Jboss 403RC2 (the integrated SEAM build since I'm playing with that anyway) and tried to deploy the jbossws.sar from JBOSS-HEAD.
It seams the new JAXB support (that jbossWS is expecting) is integrated into the jboss-j2ee.jar from Jboss5. Hopefully this small piece of information will help move things forward :-)
The backport will be done with the jbossws-1.0 final release. You can monitor the jira roadmap for details.