okay,
We host four websites in different realms, which all do a DatabaseLoginModule login. I
have configured 4 datasources, which all use a different schema within the same oracle
9.2 instance.
In JBoss 3.07 production, this works perfectly. In the 3.2 version, I do not get any
errors, only the first realm to login 'wins', and the others won't be able to login
anymore.
I was kind of hoping that configuration has changed with the new version. I know
datasource configuration has changed, does it have anything to do with the JNDI
bindings? In the former version, I had to configure in the datasource file the mbean
ManagedConnectionPooleach time a different "name" for it to work.
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
In every datasource-service.xml, i have to change the name=OracleDS to a different
name (DS1, DS2 etc).
In the new oracle-ds.xml, that is not possible anymore, so I figure it is not
necessary either. Or am I wrong, hopefully!!!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837023#3837023
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837023
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
