title: How to get control over JAXBContext in JAX-WS?
body: <p>I need to deploy the same web service for each customer. This <code>@javax.jws.WebService</code> uses <code>Object</code> as method arguments and return types (resulting in <code>&lt;xs:anyType/&gt;</code> in wsdl). Each instance of web service is deployed along with customer's jar on the classpath. This jar has known structure and contains JAXB-annotated classes which client wants to handle via my service. </p>
  
  <p>The problem is that when customer passes an instance of his class as method agrument, server-side JAXB context unmarshals it into some strange xerces dom node because (as I understand it) during the deployment time only <code>@WebMethod</code> and <code>@WebService</code> annotations were scanned which, as was already said, are all dealing with <code>Object</code> only.</p>
  
  <p>Simply speaking, I need to hint JAXB at <code>WEB-INF/lib/customer_classes_14586.jar</code> which means taking some control over <code>JAXBContext</code> creation during JAX-WS deployment. </p>
  
  <p>Is it possible at all? </p>
  
  <p>Server-specific solutions are fine (glassfish 3.1 with metro ws stack)</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>I've missed one thing that might be important: I deploy these web services as OSGI bundles at runtime via web admin console. When I press deploy button new jar is programmatically built up from customer library, webservice class, <strong>wsdl</strong> and manifests. So I could interfere in build process and provide hinting information at this point of time if this helps.</p>