Web Service @EJB injection isn't working

Question

I'm running WebLogic Server 10.0 MP1
I have a local interface:
@Local
public interface Login {
     boolean loginUser( String username, String password );
}And an implementation:
@Stateless
@Local
public class LoginBean implements Login {
     public boolean loginUser(String username, String password) {
          if (username != null && password != null && username.equals("test")
                    && password.equals("password")) {
               return true;
          return false;
}Those are bundled up in service.jar
I also have a Web Service:
@Stateless
@WebService(name = "LoginService", targetNamespace = "http://my.namespace/here")
@WLHttpTransport(contextPath = "services", serviceUri = "LoginService")
public class LoginService {
     @EJB(name="bLogin")
     private Login login;
     @WebMethod
     public boolean login(String username, String password) {
          return login.loginUser(username, password);
}The webservice is bundled into LoginService.war by the jswc ant task.
LoginService.war and services.jar are together bundled into my .ear file with an appropriate application.xml, and the web console shows both the web service and EJB as being deployed with the EAR.
When I access the LoginService, I always get a NullPointerException on the return login.loginUser() line (and a println indicates that in fact login is null).
So WebLogic isn't injecting my bean into the login variable, however there are no warnings or errors on the console.
I have seen http://forums.bea.com/thread.jspa?threadID=300003881 but that doesn't help, as my web.xml is generated by jswc and I verified that it always sets the version to 2.5 and namespace properly.
One other interesting tidbit: If I set beanName to something crazy (like "foo") on the @EJB annotation in LoginService, I DO get an error (at deployment time) in the server log saying that the ejb-link for 'foo' wasn't found. So the lookup appears to be happening (though there is nothing about an ejb-link in the web.xml, I expect that it is implicitly happening at deploy time from the @EJB annotation) just not the actual injection.
Thoughts?

Answer 1

Since it looks like no one from BEA actually monitors these forums, I'll answer my own question.
I no longer use the jswc ant task to generate LoginService.war. Now, I just drop my Login web service into its own jar file (apparently it doesn't work if it's in a JAR with other EJBs), say, ws.jar and put that into the EAR with everything else, and it works. Here is my web service now (called LoginImpl)
@WebService(name = "Login", targetNamespace = MY_NAMESPACE)
@SOAPBinding(style = Style.DOCUMENT, use = Use.LITERAL, parameterStyle = ParameterStyle.WRAPPED)
@WLHttpTransport(contextPath = "services", serviceUri = "LoginService")
@Stateless
public class LoginImpl {
     @EJB(name = "Login")
     private Login login;
     @WebMethod(operationName="LoginRequest")
     @WebResult(name = "LoginResponse")
     public boolean login(
          @WebParam(name = "Username", targetNamespace = MY_NAMESPACE) String username,
          @WebParam(name = "Password", targetNamespace = MY_NAMESPACE) String password
          return login.loginUser( username, password );
     @WebMethod(operationName="LogoutRequest")
     @WebResult(name="LogoutResponse")
     public void logout( @WebParam(name = "SessionToken", targetNamespace = MY_NAMESPACE) String sessionToken ) {
          login.logoutUser( sessionToken );
}So in summary:
* Put @WebService files in their own JAR
* Don't use jswc
I also used Sun's JAX-WS reference implementation to generate the *.jaxwx.* files, otherwise WebLogic complains