thanks for answer. I noticed this morning you used up-to-date jars for running your samples , jars that you retrieved from web sites (force.thirdparty.get property in your build.xml), so concerning Jaxws version -with @resource WebServiceContext- I just copied the jars jaxb-api and jaxb-impl instead of the previous older jars of Jboss AS 4.2.0.CR2 and it is ok, injection of WebServiceContext is working. I mentioned there are lots of jars retrieved that way. From now I don't know exactly how to constitute a clean environment for our deployment. I think it is better to use last version Jboss-1.2.0.SP1 (or may be next Jboss-1.2.1.GA) than version Jboss-1.0.3 I was previously working with. So I'm using Jboss 4.0.2.CR2 with Jboss-1.2.0.SP1. I'm using WSAddressing for session management, if possible HTTPS and basic authentication (which is easy through context if I remember well), MTOM to get/post binary content. To avoid interoperability problems in the previous version we delivered, we specified our API only through the description of the SOAP messages exchanged; I don't know from the moment how to constitude a SOAP message with a binary part (i.e. to be sent through MTOM instead of SOAP with attachments). Do you thing it is possible without risks to propose our API as a web service instead of specifying the soap messages? I will write a source code then generate the wsdl so I ask you if the generated wsdl will be compatible with any clients based on any web services stack? Our deployment must be done soon so I'm asking you the versions appropriate of JbossAS and JbossWS. Thanks a lot CPires View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041387#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...