Ales Justin wrote:
You could change the deployment's classloading metadata's parent domain to point to your WS domain,
if you recognize that deployment as WS depolyment and no explicit classloading metadata is given.
Yes... the problem is that currently the deployment is recognized as a WS one after the classloading phase (in real phase) as in most cases the only way of doing that is finding jaxws annotations on the endpoint. Is the shared annotation repository (which we don't use yet, we have a jira for that) also populated after the classloader for the deployment unit is setup, isn't it?