Moderated: HIJACK - start a new thread. My answer solves the stated problem.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3841955#3841955
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3841955
I need javax.sql.DataSource in my deployment in order to assembly a list of Value
Objects
via JDBC instead of query the database through EJB-QL.
I also need certain degree of isolation because our deployment lives with legacy
releases
of our application in the same container.
We never had
We use jboss-app.xml in META-INF folder of EAR file to
restrict classes to be loaded only by the application's
ClassLoader.
Like this:
jboss-app
| loader-repositorymypackage:loader=myapp.ear/loader-repository
| /jboss-app
It works fine in Jboss 3.0.x. But we had a ClassCastException
It is expected, why do you need javax.sql in your deployment?
If you really do want isolation, you would have to copy the entire infrastructure
(jboss rar, jdbc driver) into the ear, otherwise you will get all sorts of class
confusion.
View the original post :
Run this small program
| System.out.println(DataSource from + DataSource.class.getClassLoader());
|
| Class[] interfaces = WrapperDataSource.class.getInterfaces();
| for (int i = 0; i interfaces.length; ++i)
|System.out.println(interfaces + from + interfaces.getClassLoader();
OK. I only had it in 2 other places..:)
Thanks,
Nate
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3832170#3832170
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3832170
