[
http://jira.jboss.com/jira/browse/JBAS-4242?page=all ]
Shelly McGowan reopened JBAS-4242:
----------------------------------
These tests are failing again with latest trunk - well, probably since beta4, as the URLs
are not able to be retrieved from the classloader as the classloader is the
BaseClassLoader. scanforMappings() does not check for that, should it?
URL[] urls;
ClassLoader cl = Thread.currentThread().getContextClassLoader();
if ( cl instanceof RepositoryClassLoader )
{
urls = ( ( RepositoryClassLoader ) cl ).getClasspath();
}
else if ( cl instanceof URLClassLoader )
{
urls = ( ( URLClassLoader ) cl ).getURLs();
}
else
{
throw new DeploymentException( "Unable to determine urls from classloader
[" + cl + "]" );
}
ERROR [AbstractKernelController] Error installing to Real:
name=vfsfile:/NotBackedUp/smcgowan/TRUNK/trunk/testsuite/output/lib/hib-test.ear
state=PostClassLoader mode=Manual requiredState=Real
org.jboss.deployment.DeploymentException: Unable to determine urls from classloader
[BaseClassLoader@1f6fa3f{vfsfile:/NotBackedUp/smcgowan/TRUNK/trunk/testsuite/output/lib/hib-test.ear}]
at org.jboss.hibernate.jmx.Hibernate.scanForMappings(Hibernate.java:272)
at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:114)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
Port Hibernate deployer to VDF
------------------------------
Key: JBAS-4242
URL:
http://jira.jboss.com/jira/browse/JBAS-4242
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Deployment services, Hibernate service
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Fix For: JBossAS-5.0.0.Beta3
The current hibernate integration tests are broken in jboss5 trunk, and the deployer
needs to be ported to the VDF
(
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework). This really should
be done in concert with the ejb3 deployer refactoring as there should be minimal
duplication of the various deployment aspects related to persistence.
--
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