No, the property is used to support the backward compatibility of the jar
visibility. Th v3 is enforcing the jar visibility rules defined in the
JavaEE 6 spec. For example, the jars at the ear root level should not be
automatically visible to the sub modules, but as these used to work in v2, we
put in this property to support the product backward compatibility of it.
In any case, in your application, if you have a top level
META-INF/application.xml which clearly defines the two modules in the ear, I
am not sure why you would get that error. Any other exceptions in the
server.log?
--
[Message sent by forum member 'hzhang_jn']
View Post: http://forums.java.net/node/711106