[jboss-dev-forums] [Design of EJB 3.0] - Re: webservices ejb3 api usage

[heiko.braun@jboss.com]

anonymous wrote : 
  | Deployment handling should be done by an intermediate deployer. How 
  | does the webservice meta data merge with the ejb3 meta data?
  | 

IMO there is no such thing as dedicated WS metadata. It's all part of the Ejb3 meta data. So this will be handled by whatever component parses the Ejb3 meta data. The WebServiceDeclaration interface addresses this.
You can move it around, deprecate your sources or implement a new metadata representation. Just make sure the interface is offered to WS deployers.

anonymous wrote : 
  | As for injection. That should have happened before method invocation. I was thinking about a ThreadLocalStack construction which is injected during construction and set during invocation.
  | 

Right, that makes sense. Let's regard two pieces:

1) a web service invocation (SOAP, hit's jbossws)
2) an endpoint (i.e. EJB3) invocation that derives from 1

Currently the ws invocation model offers a callback (InvocationContexCallback) to access WS injection properties. This is passed on to the StatelessContainer (implements ServiceEndpointContainer). To me the order of injection vs. method invocation is an implementation detail of the EJB3 domain. 

If I understand you correctly we speak about dependency injection before the bean becomes method-ready, right? 
So I'd say leave ServiceEndpointContainer interface in place and get Ejb3 problems sorted internally. Up to now I don't see why this should affect the WS-EJB3 API in place.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144179#4144179

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144179