[
http://jira.jboss.com/jira/browse/JBAS-4283?page=comments#action_12358215 ]
Andrew P commented on JBAS-4283:
--------------------------------
Adrian,
I wouldn't be that quick on shutting people's mouth, sorry for a bit harsh
statement, but:
* ra.xml *is* in the correct location, as mandated by the spec. JBoss deployer should
check for this file and if found, use it, and not bail out on the first mismatch.
* Websphere AS, Oracle IAS, Weblogic don't have any conflict with vendor-specific
descriptors, they are simply not processed
* Your reference to the JCA spec is wrong, there's nothing stating ONLY ra.xml file is
allowed, the only requirement is it must be there (17.5.4 section is the XSD schema for
ra.xml)
JBoss application server appears to be matching on *ra.xml inside the
.rar file when deploying
----------------------------------------------------------------------------------------------
Key: JBAS-4283
URL:
http://jira.jboss.com/jira/browse/JBAS-4283
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows XP, JDK 5, Mule 1.3.3/ 1.4 SNAPSHOT
Reporter: Marie Rizzo
In attempting to deploy Mule on JBoss using the rar deployment, I noticed that although a
proper ra-xml file exists for JBoss deployment inside the rar file, JBoss rejects anything
that contains any other file which matches the pattern but does not pertain to JBoss
deployment. In my case this occurs in the resource adapter jar file which has a file
called oc4j-ra.xml file inside it. It seems to me that JBoss is matching on *ra.xml which
may be the cause of the problem. Below is the relevant extract from the log file.
2007-03-30 16:16:48,734 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment
(init step) of package at:
file:/C:/Downloads/jboss-4.0.5.GAR/server/default/tmp/deploy/tmp37913mule-jca-1.4-SNAPSHOT.rar-contents/mule-module-jca-1.4-SNAPSHOT.jar
2007-03-30 16:16:48,734 DEBUG [org.jboss.deployment.JARDeployer] Found entry:
'META-INF/oc4j-ra.xml', matching: 'ra.xml', rejecting jar
2007-03-30 16:16:48,734 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for
url:
file:/C:/Downloads/jboss-4.0.5.GAR/server/default/tmp/deploy/tmp37913mule-jca-1.4-SNAPSHOT.rar-contents/mule-module-jca-1.4-SNAPSHOT.jar
2007-03-30 16:16:48,734 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for
deployer:
file:/C:/Downloads/jboss-4.0.5.GAR/server/default/tmp/deploy/tmp37913mule-jca-1.4-SNAPSHOT.rar-contents/mule-module-jca-1.4-SNAPSHOT.jar
Consequently, a ClassLoaderNotFound exception is thrown because the resource adapter was
never deployed.
11:57:17,203 WARN [ServiceController] Problem starting service
jboss.jca:service=RARDeployment,name='mule-jca-1.3.3.rar'
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.mule.ra.MuleResourceAdapter
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.jboss.resource.deployment.ResourceAdapterFactory.createResourceAdapter(ResourceAdapterFactory.java:66)
at
org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:108)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
Please could you check up on this? If JBoss is indeed matching on the *ra.xml, it would
be very restrictive with regards to naming conventions.
--
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