[jboss-user] [Microcontainer] - Re: ClassNotFound on deployment of a SchemaResolverDeployer

[david.lloyd@jboss.com]

"adrian at jboss.org" wrote : I've uploaded a 2.0.2-SNAPSHOT of jboss-cl with a fix for this bug if you want to try it.

It seems to work.  In JBossAS minimal configuration, it prints the warning several times:


  | 08:37:13,719 WARN  [ClassLoadingSpace] VFSDeploymentClassLoaderPolicyModule jboss-threads-deployer-classloader:1.0.0.Alpha resolved PackageRequirement{org.jboss.deployers.vfs.deployer.kernel [0.0.0,?)} to VFSClassLoaderPolicyModule deployers-classloader:0.0.0 which has import-all=true. Cannot check its consistency.
  | 08:37:13,719 WARN  [ClassLoadingSpace] VFSDeploymentClassLoaderPolicyModule jboss-threads-deployer-classloader:1.0.0.Alpha resolved PackageRequirement{org.jboss.deployers.vfs.spi.deployer [0.0.0,?)} to VFSClassLoaderPolicyModule deployers-classloader:0.0.0 which has import-all=true. Cannot check its consistency.
  | 08:37:13,720 WARN  [ClassLoadingSpace] VFSDeploymentClassLoaderPolicyModule jboss-threads-deployer-classloader:1.0.0.Alpha resolved PackageRequirement{org.jboss.deployers.vfs.deployer.kernel [0.0.0,?)} to VFSClassLoaderPolicyModule deployers-classloader:0.0.0 which has import-all=true. Cannot check its consistency.
  | 08:37:13,720 WARN  [ClassLoadingSpace] VFSDeploymentClassLoaderPolicyModule jboss-threads-deployer-classloader:1.0.0.Alpha resolved PackageRequirement{org.jboss.deployers.vfs.spi.deployer [0.0.0,?)} to VFSClassLoaderPolicyModule deployers-classloader:0.0.0 which has import-all=true. Cannot check its consistency.
  | 08:37:13,720 WARN  [ClassLoadingSpace] VFSDeploymentClassLoaderPolicyModule jboss-threads-deployer-classloader:1.0.0.Alpha resolved PackageRequirement{org.jboss.deployers.vfs.spi.deployer [0.0.0,?)} to VFSClassLoaderPolicyModule deployers-classloader:0.0.0 which has import-all=true. Cannot check its consistency.
  | 

...if that matters to you.

"adrian at jboss.org" wrote : Most people (except the eclipse developers :-) think that importing modules is lazy - it makes things prone to problems when modules are refactored i.e. you move packages to other modules.

Hm, okay, that seems reasonable.

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

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