Two things make me think that this error is caused by the ear:
1) I only get the error when I have the loader-repository specified in the ear
2) The error messages show up while deploying the ear


  | 2004.05.18 07:25:07.890 EDT INFO  [org.jboss.deployment.MainDeployer] Deployed 
package: file:/C:/khub/JBossEval/jboss/server/lms1/deploy/deploy.last/
  | 
  | 2004.05.18 07:25:07.890 EDT INFO  [org.jboss.deployment.MainDeployer] Starting 
deployment of package: file:/c:/khub/JBossEval/deploy/lms
  | 
  | 2004.05.18 07:27:37.953 EDT INFO  [org.jboss.deployment.EARDeployer] Init J2EE 
application: file:/c:/khub/JBossEval/deploy/lms/dave.ear/
  | 
  | 2004.05.18 07:27:38.062 EDT INFO  [org.jboss.deployment.EARDeployer] Init J2EE 
application: file:/c:/khub/JBossEval/deploy/lms/dave2.ear/
  | 
  | 2004.05.18 07:27:38.140 EDT INFO  [org.jboss.deployment.EARDeployer] Init J2EE 
application: file:/c:/khub/JBossEval/deploy/lms/kauthor.ear/
  | 
  | 2004.05.18 07:27:38.171 EDT WARN  [org.jboss.deployment.DeploymentInfo] Only the 
root deployment can set the loader repository, ingoring 
config=LoaderRepositoryConfig(repositoryName: lmnk:loader=kauthor.ear, 
repositoryClassName: org.jboss.mx.loading.HeirachicalLoaderRepository3, 
configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, 
repositoryConfig: java2ParentDelegaton=true)
  | 
  | 2004.05.18 07:27:38.687 EDT INFO  [org.jboss.deployment.EARDeployer] Init J2EE 
application: file:/c:/khub/JBossEval/deploy/lms/lms.ear/
  | 
  | 2004.05.18 07:27:38.750 EDT WARN  [org.jboss.deployment.DeploymentInfo] Only the 
root deployment can set the loader repository, ingoring 
config=LoaderRepositoryConfig(repositoryName: lmnk:loader=lms.ear, 
repositoryClassName: org.jboss.mx.loading.HeirachicalLoaderRepository3, 
configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, 
repositoryConfig: java2ParentDelegaton=true)
  | 
  | 2004.05.18 07:27:44.734 EDT INFO  [STDOUT] May 18, 2004 7:27:44 AM 
java.util.jar.Attributes read
  | 
  | 

So, the question remains, what qualifies as a top level deployment?  Is an ear a top 
level deployment?  The documentation clearly states that this is the appropriate 
approach to getting scoped classloading.  

Thanks

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835581#3835581

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835581


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to