Following problem: We have a Swing based fat client application with a JBoss7 as backend. I need to do a lookup for a JMS ConnectionFactory from our client-application to a JBoss7 instance after a JAAS login process via a custom login module.
This works perfekt for the login procedure and the lookup for stateless EJB's.
I get the same Exception (doesn't matter, if it is a user which is defined in the ApplicationRealm property file or which is a valid user in our JAAS realm, the user has always the role "messaging").
TRACE [org.jboss.remoting.remote.server] (Remoting "myserver" read-1) Server received capability: remote endpoint name "config-based-naming-client-endpoint"
I don't know if this has something to do with the EJBClientContext mechanism.
Does anybody has any ideas ?
Using "EJBClientContext.setSelector(contextSelector)" is dangerous. Hopefully it only affects your ear, and not any other ears. Since you know at runtime how you want the properties to be, you should probably just include the properties file in your classpath.
Wolf-Dieter Fink and Jaikiran Pai show you how to lookup an EJB without using the properties file.
I'm also using the JBoss 7.1.1.
remote secured EJB calls are working unless i want to get the JMS connection factory using a JNDI lookup. Specifing the InitialContextFactory and the security realms the access to the secured EJBs fails and the creation of the context throws an exception.
Do you have any solution for the problem so far?