Carlo,
This approach is probably not the right way to go.
How about:
WebServiceContextCallback callback = new WebServiceContextCallback()
{
public MessageContext getMessageContext()
{
...
}
public WebServiceContext getWebServiceContext()
{
...
}
};
sessionContext.registerWebServiceContextCallback(callback);
The WebServiceContextCallback interface would live in the ejb3 code base.
The dependency would be unidirectional, as it is now already.
cheers
-thomas
Carlo de Wolf wrote:
Hi Thomas,
I've made an implementation which passes the test:
http://jira.jboss.com/jira/browse/EJBTHREE-757?page=com.cenqua.fisheye.ji...
I turned the tables by pulling in the message context via
MessageContextAssociation. Do you see any problems with this?
The one thing I don't like is the circular dependencies between ejb3 and
ws.
Carlo
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx