If this still takes too long, look at breaking up the components in the .ear. Either into smaller .ears, or into individual components (.war, ejbs jars, etc) and move those to deploy/. Then you only need to re-deploy the components that have changed.
From experience, breaking an application up into multiple smaller deployablecomponents can be error-prone in terms of the JBoss classloader. Especially true if one component relies on another component that isn't bundled in the same archive (ear, jar, etc).
This was exactly what happened to us here :)
The solution we used was to share the interface files through a single .ear file.
Thanks for feedback, Barlow
-- Regards,
Francisco Figueiredo Jr. Membro Fundador do Projeto MonoBrasil - MonoBrasil Project Founding Member
------------- "Science without religion is lame; religion without science is blind."
~ Albert Einstein
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
