User development,

A new message was posted in the thread "LoginModule dependence on Datasource":

http://community.jboss.org/message/525966#525966

Author  : Geoffrey Ulman
Profile : http://community.jboss.org/people/ulmangt

Message:
--------------------------------------------------------------
My test application simply makes a JMS connection and sends a message every 5 
seconds. The problem is that HornetQ's automatic reconnection appears to try to 
reconnect immediately when it sees the server come back up. But at that point 
the server has not yet bound the DefaultDS to a JNDI name (which my custom 
LoginModule requires). This definitely seems like something that should be 
enforced on the server side, since it deals with the order that various 
services/components on the server are inititalized.
 
 
I know that mbeans can have an explicit dependencies, including on particular 
datasources. Here's an example snippit:
 
<mbean code="org.jboss.messaging.core.jmx.JDBCPersistenceManagerService"
      name="jboss.messaging:service=PersistenceManager"
      xmbean-dd="xmdesc/JDBCPersistenceManager-xmbean.xml">

      <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
            ...
</mbean>
 
 
I was hoping that there would be something similar for LoginModules.
 
For example, does the <login-module> tag in login-config.xml provide some 
similar syntax? Or is there some other way to ensure that the Datasource is 
bound to a JNDI name that the LoginModule can lookup before its initialize() 
method is called?

--------------------------------------------------------------

To reply to this message visit the message page: 
http://community.jboss.org/message/525966#525966


_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to