So it seems not possible to true application scoped datasources at this time.
I have a few followup questions.
1) How are others working with this issue? Do you trust your developers to not
comb the jndi tree and look for datasources? Or do you just spawn a new jboss
install for each
1) By restricting who has access to the production server (only the sysadmin is
allowed to deploy apps to production) and by using code reviews to make sure
that no developer write a datasource fishing app. For really secure
environments, an app server instance per app is also used.
2) Enter a
Thanks henk53 - this is the sort of idea I was looking for. I'll see what I
can figure out from this.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249926#4249926
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249926
I did what you suggested - and It still added the datasource on the global jndi
tree.
In this case, i put my test datasource in the META-INF directory.
| jboss-app
| module
| serviceMETA-INF/datasource1-ds.xml/service
| /module
| /jboss-app
|
When the
As Peter said, even if you package the datasource within your app, the
datasource will finally be bound to a JNDI tree which can be accessible by
other applications deployed on the same server instance.
View the original post :
matanderson wrote : I am looking for a way to setup application scoped
datasources within JBoss (4.2.3 or 5).[...] Is this possible on JBoss?
|
|
I think so, put your database-ds.xml in your ear at the top level, and define a
reference to it in yourear/META-INF/jboss-app.xml:
|
As far as I know, once the datasource is deployed and its name show up in the
JNDI tree, any app can connect to the database.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4245882#4245882
Reply to the post :
