[Design of POJO Server] - EARDeploymentUnitTestCase failure
by alesj
OK, I know we said these tests are bogus, obsolete ...
"adrian(a)jboss.org" wrote :
| I'll repeat, these tests are bogus they need replacing with something that
| tests the new relaxed rules. There's no point trying to fix them
| since they are testing obsolete rules.
|
But I was already in the middle of fixing them, so this is done ... almost.
The last test that is failing is this one - EARDeploymentUnitTestCase:
Just trying to identify the failure cause, if it might help with our future developement.
| org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear/testdeployers-mcf1-ds.xml
|
| Caused by: java.lang.IllegalStateException: No ConnectorMetaData found for mdf rarName: testdeployers-ear1.ear#testdeployers-mcf1.rar
| at org.jboss.resource.deployers.builder.ManagedConnectionFactoryBuilder.buildConstructor(ManagedConnectionFactoryBuilder.java:83)
| at org.jboss.resource.deployers.builder.AbstractBuilder.buildService(AbstractBuilder.java:56)
| at org.jboss.resource.deployers.builder.AbstractBuilder.build(AbstractBuilder.java:65)
| at org.jboss.resource.deployers.ManagedConnectionFactoryDeployer.deploy(ManagedConnectionFactoryDeployer.java:177)
| at org.jboss.resource.deployers.ManagedConnectionFactoryDeployer.deploy(ManagedConnectionFactoryDeployer.java:52)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
| ... 59 more
| 21:48:12,890 WARN [MainDeployer] Failed to deploy: file:/C:/projects/jboss5/trunk/testsuite/output/lib/testdeployers-ear1.ear
|
This is the xml:
| <connection-factories>
|
| <tx-connection-factory>
| <jndi-name>testdeployers/DS1</jndi-name>
| <rar-name>testdeployers-ear1.ear#testdeployers-mcf1.rar</rar-name>
| <connection-definition>org.jboss.test.deployers.rar.mcf1.MCF1ConnectionFactory</connection-definition>
| </tx-connection-factory>
|
| </connection-factories>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110663#4110663
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110663
18 years, 4 months
[Design of JCA on JBoss] - Re: JBAS-5023
by adrian@jboss.org
I don't see why it is critical?
jboss-ra.xml is a new feature in JBoss5 that Weston did only in the old deployer
(which isn't used). So nobody is using this feature except the testsuite.
With the profile service its main use case (being able to override ra.xml properties)
is pretty much redundant.
It was really redundant anyway because you could always just modify the ra.xml
Its only other use would be allow classloader config but in the new deployers you will be able
to add a META-INF/jboss-classloader.xml to achieve the same purpose.
184 is a feature we can do in RC1 since it only affects how deployers are implemented
when they need to parse more than one file, in this case ra.xml and jboss-ra.xml
Currently you write two parsing deployers which is messy.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110647#4110647
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110647
18 years, 4 months