jaxws ejb integration

[Jarek Gawor <jg...@gmail.com>]

Hi,

I think I have most of the jaxws ejb integration working now in
Geronimo. However, I've run into one problem that I need your help
with. It has to do with service endpoint interfaces (SEI). For JAX-WS
based web services the SEI is not required. For example, the following
web service is totally valid:

@WebService
@Stateless
public class Foo {

  public void sayHi() {
  }

}

And it has no DDs. The problem is that the current OpenEJB code
determines if it is a web service call by checking if there is a SEI
and if the method called is part of that interface. Obviously, in the
case where there is no SEI this check will fail (see
StatelessContainer.java:266).

I'm not sure what's the right solution for this problem so I would
appreciate any help I can get on this.

Thanks,
Jarek

Re: jaxws ejb integration

[David Blevins <da...@visi.com>]

On May 3, 2007, at 10:25 PM, Jarek Gawor wrote:

> Hi,
>
> I think I have most of the jaxws ejb integration working now in
> Geronimo. However, I've run into one problem that I need your help
> with. It has to do with service endpoint interfaces (SEI). For JAX-WS
> based web services the SEI is not required. For example, the following
> web service is totally valid:
>
> @WebService
> @Stateless
> public class Foo {
>
>  public void sayHi() {
>  }
>
> }
>
> And it has no DDs. The problem is that the current OpenEJB code
> determines if it is a web service call by checking if there is a SEI
> and if the method called is part of that interface. Obviously, in the
> case where there is no SEI this check will fail (see
> StatelessContainer.java:266).
>
> I'm not sure what's the right solution for this problem so I would
> appreciate any help I can get on this.

We'd likely do like we did for business interfaces which have no home  
interface and add a DeploymentInfo.ServiceEndpoint interface we can  
use when there is none.  This probably won't work with just that,  
we'll probably have to add some special handling for it when we map  
interfaces to methods on the bean as there won't be any methods in  
the "stand-in" interface.

Will give it a poke tomorrow and see what I can come up with.

-David