[jboss-jira] [JBoss JIRA] Closed: (JBAS-3854) Oracle datasource deployment error inside a scoped ear.

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3854?page=all ]

Adrian Brock closed JBAS-3854.
------------------------------

    Resolution: Duplicate Issue

This has been reported before, so this is a duplicate,
as always you can use the search function to find the duplicate just as well as I could,
I'd rather just delete these redundant posts.

It is also a relatively frequent question in the JCA forums (cropping up every couple of months).
it is now in the FAQ:
http://wiki.jboss.org/wiki/Wiki.jsp?page=IWantToDeployMyOwnJdbcDriverInAScopedClassloader

> Oracle datasource deployment error inside a scoped ear.
> -------------------------------------------------------
>
>                 Key: JBAS-3854
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3854
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.0.5.GA
>         Environment: Windows XP SP2
>            Reporter: Alexandre Bitencourt
>         Attachments: cadastro-non_scoped.ear, cadastro-scoped.ear
>
>
> In our enviroment we create a common classloader to scope applications and common libraries. All ears deployed in application server uses this classloader. When we upgrade the version of application server from 4.0.4.GA to 4.0.5.GA the datasource descriptors that are inside the scoped ears fails to came up. Removing the scope declaration from jboss-app.xml the datasources works fine, but applications needs some classes that are shared in scoped classloader and we cannot put them on default classloader to avoid version conflicts.  On Jboss 4.0.4 the datasources works fine even if jboss-app.xml declares a scoped classloader for ear. The error showed when the deployment of datasource fail is: "java.lang.IllegalArgumentException: interface javax.sql.DataSource is not visible from class loader".
> Doing some tests I discover that the problem is specific with Oracle 8i database drivers. When i try to simulate the error with Derby or HSQLDB it not ocurs. 
> The problem is when the database drivers are in a scoped classloader. The datasources inside ears that use the same scoped classloader fails to came up. I will atach two ears with only the database driver and datasource descriptors inside. One of them is scoped and the other not. The connection mannager related with datasource came up ok on non scoped jar and fails on scoped.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira