The structure of the ear looks like this:
meta-inf/application.xml
module1.jar
module2.jar
...
module14.jar
lib1.jar
lib2.jar
...
lib20.jar
The application.xml contains a list of all the modules. Nothing special there.
The only thing interesting for each module is in the manifest there is a
Class-Path entry that contains the list of libraries.
What appears to be happening is:
foreach module do
classpath = get module classpath
for each item in classpath do
deploy classpath item (includes scan of jar)
end
end
If the above was switched do this it would be MUCH faster:
foreach module do
classpath = get module classpath
for each item in classpath do
if classpath item hasn't been deployed
deploy classpath item (includes scan of jar)
end
end
end
It appears the libraries are getting scanned once per module that has a
classpath entry that references it.
The scanning of the jars appears to take about 22 seconds. The problem is 22
seconds * 14 modules is more than 5 minutes.
I have no problem with jboss scanning the jars. I just would like jboss changed
so it only scans them once per ear, instead of once per module in the ear.
Jeff Brooks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932289#3932289
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932289
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
