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

[heiko.braun@jboss.com]

anonymous wrote : 
  | Define an interface for the SessionContainer.localInvoke. 
  | 

Right, I already did that. Currently I am playing with two integration interfaces. One for deployment and another one for invocation. Both need to be implemented by the Ejb3Deployment and SessionContainer respectively. A generic way to access injectable properties (2.2) is covered by the later as well:

Deployment handling:


  | 
  | /**
  | * Access web service decl. within an EJB3 deployment.
  | */
  | public interface WebServiceDeployment  {
  |    
  |    java.util.List<spi.integration.WebServiceDeclaration> getServiceEndpoints();
  | }
  | 
  | public interface WebServiceDeclaration
  | {
  |    /* aka bean name */ 
  |    String getComponentName();
  | 
  |    /* aka bean impl */
  |    String getComponentClassName();
  |    
  |    /* generic meta data retrieval  */
  |    <T extends java.lang.annotation.Annotation> T getAnnotation(Class<T> t);   
  | }
  | 

Invocation handling:

  | 
  | /**
  | * Invoke a web service implementation hosted by a StatelessSession container.
  | */
  | public interface ServiceEndpointContainer  {
  |    
  |    java.lang.Class getServiceImplementationClass();
  |    
  |    java.lang.Object invokeEndpoint(Method method, Object[] objects, 
  |         spi.InvocationContextCallback invocationContextCallback) 
  |           throws java.lang.Throwable;
  | }
  | 
  | /**
  |  * Callback for invocation context properties that may be injected
  |  * in the service endpoint prior to actual method invocation.
  |  */
  | public interface InvocationContextCallback
  | {
  |    <T> T get(Class<T> propertyType);
  | }
  | 
  | 

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

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