[
http://jira.jboss.com/jira/browse/JBAS-4242?page=all ]
Ales Justin resolved JBAS-4242.
-------------------------------
Resolution: Done
The tests now pass.
I introduced a VFS visitor patter for searching .hbm.xml files from URLs given by the
Classloader.
private void scanForMappings() throws DeploymentException
{
// Won't this cause problems if start() is called from say the console?
// a way around is to locate our DeploymentInfo and grab its ucl attribute
// for use here.
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 + "]" );
}
// Search the urls for each of the classpath entries for any containing
// hibernate mapping files
VirtualFileVisitor visitor = new HibernateMappingVisitor(classpathUrls);
// visit har url if set
if (harUrl != null)
visitURL(harUrl, visitor);
// visit CL urls
for ( int i = 0; i < urls.length; i++ )
{
final URL entry = urls[i];
visitURL(entry, visitor);
}
log.trace("Found mappings: " + classpathUrls);
}
Current implementation of handling MBeans has no notion of holding har's URL, the same
way previous SARDeployer did.
So that feature can now only be achieved by explicitly setting har URL.
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