Exception when my login method is a SLSB

[ericjava.eric.chiralsoftware.net]

Here's something I don't understand.

In my components.xml I have:

<security:identity authenticate-method="#{loginAction.authenticate}"/>

Quite typical.

When the component that is loginAction is a POJO, just with a @Name annotation, it works as expected.  However, when I make it into a stateless session bean, something bad happens:

org.jboss.seam.InstantiationException: Could not instantiate Seam component: loginAction
        at org.jboss.seam.Component.newInstance(Component.java:1970)
 Caused by: javax.naming.NameNotFoundException: myproj not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)

        at org.jboss.seam.Component.newInstance(Component.java:1966)

(I've trimmed the exceptions; if you need it in full I'll post it.)

Any ideas?  This is most strange.  My other project does have its login action as a SLSB and it works, but I can't figure out what's different.

I have it working so I'm happy about that, just confused.

Thanks

[ericjava.eric.chiralsoftware.net]

More testing: the problem happens with all SLSBs.  Here's an example:

The interface:

@javax.ejb.Local public interface Test {

    public void yo();
    
}

The bean:

@Name("testBean")
@Stateless
public class TestBean implements Test {
    private static final Logger logger = Logger.getLogger("TESTING");
    
    public void yo() {
        logger.warning("HEY THIS IS A SLSB HERE!");
    }
}

And I get the same Could not instantiate Seam component: testBean type of thing.

This is really strange that somehow SLSBs are no longer working.  Any ideas?

[ericjava.eric.chiralsoftware.net]

I found the bug, and explained it here: Seam instantiation exception.

I would recommend to the Seam team to put a little more info in that exception message.  This one is not at all obvious until you figure it out.

[pmuir]

File an issue in JIRA asking for a better exception