EJB 3.0 Web Service

Question

Hi!
I tried to create a Web Service (through wizard) from existing EJB 3.0 Session Bean. Basicly, the wizard just added @WebService annotation to my existing code...
Now, the problem is that simple methods like:
@WebMethod
public String helloWorld() {
  return "Hello World!";
}works fine. Expect that if I use Local Interface for this Session Bean, the WSDL shows two helloWorld methods (and one is with exclamation icon showing some kind of problem with multiple methods with same name - but it is not true, I have one and the other one is just interface).
But, when I want to expose my real business service methods like:
@WebMethod
public List<Employee> getEmployees() {
  return (List<Employee>)q.getResultList();
}it doesn't work (the Web Service create wizard finishes ok but service doesn't work)! When I try "Test Web Service" (from Session Bean context-menu) or "Show WSDL for Web Service annotations" the error is thrown (Null pointer exception in WSDL).
Basically, it looks to me that Web Service cannot use EJB Entities as parameters or results. Is this correct? I saw some examples on EJB 3.0 web services and there are entities routinely used as both input and output parameters.
Can someone, please, explain me what I'm doing wrong here.
Thanks in advance,
Pedja
P.S. In Web Service wizard, only SOAP 1.1 is enabled. How can I choose SOAP 1.2? And what EJB 3.0 bindings are in same context (SOAP 1.2 or EJB 3.0 bindings?)?

Answer 1

Hi Frank,
Most of those problems are resolved (NPE was due to Timestamp field, and two methods with the same name in WSDL because of not choosing to generate SEI in wizard, so the generated WSDL had one method from the Session bean and the other from it's Local interface). But, the errors should DEFINITELY be more descriptive.
Does the wizard work correctly? I noticed plenty of "bug like" details. For example, if I choose to create asynchronous web service, later when I go to Properties the "Asynchronous Web Service" checkbox isn't checked. Also, the @WebMethod annotations are sometimes generated and sometimes not (even if the method is checked to be exposed).
I am also getting these exceptions when I create a proxy for the asynchronous web service (I selected "Generate asynchronous methods for all operations"), could be I'm doing something wrong:
WARNING: The parameter/return type "java.util.concurrent.Future" in the method
"public abstract java.util.concurrent.Future<?>
view.proxy.MyAsyncWebService1.queryDepartmentFindAllAsync(javax.xml.ws.AsyncHandler<view.proxy.types.QueryDepartmentFindAllResponse>)"
is not supported. This method will not be exposed.
WARNING: The parameter/return type "java.util.concurrent.Future" in the method
"public abstract java.util.concurrent.Future<?>
view.proxy.MyAsyncWebService1.returnEmployeeAsync(javax.xml.ws.AsyncHandler<view.proxy.types.ReturnEmployeeResponse>)"
is not supported. This method will not be exposed.
Exception in thread "main" java.lang.NullPointerException
     at com.sun.xml.bind.v2.runtime.Coordinator.popCoordinator(Coordinator.java:122)
     at com.sun.xml.bind.v2.runtime.XMLSerializer.close(XMLSerializer.java:823)
     at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:310)
     at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:230)
     at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:87)
     at oracle.j2ee.ws.common.databinding.runtime.jaxb20.Jaxb20Serializer.serialize(Jaxb20Serializer.java:218)
     at oracle.j2ee.ws.common.databinding.runtime.SerializerBase.serializeSequenceWrapper(SerializerBase.java:80)
     at oracle.j2ee.ws.client.jaxws.SoapRequestorSerializer.populateSoapMessage(SoapRequestorSerializer.java:89)
     at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:184)
     at $Proxy11.returnEmployee(Unknown Source)
     at MyAsyncWebService1SoapHttpPortClient.main(MyAsyncWebService1SoapHttpPortClient.java:22)
Process exited with exit code 1.Can anyone throw some light on this?
Thanks,
Pedja