In jboss eap 7, I want a non-ejb jar access war file. How to do it?

[wuweibear]

The file structure is the following:

test.ear has one jar file testjar.jar and one war file testwar.war

testjar.jar

     L  test1.java

     L  test2.java

testwar.war

     L   testwar1.java

     L   testwar2.java

testwar.war was treated as subdeployment,

Now, testwar1.java can access test1.java in testjar.jar  but test2.java cannot access testwar2.java in war file.

Now my question is how the class in jar file can access the class in war file.

Thanks

[wuweibear]

I add jboss-deployment-structure.xml testjar.jar META-INF, but this file not was called. (I made some mistake inside, but no exception)

[lafr]

Have a look at Class Loading in WildFly - WildFly 10 - Project Documentation Editor e.g., especially the statement in the yellow box.

war files within an ear deployment are always isolated as requested by the Java EE specifications.

And on the same you can read, that the jboss-deployment-structure.xml file has to be placed into the top level deployment, to be placed into /META-INF of the ear file.

[wuweibear]

If the ear-subdeployments-isolated is set to false, then the classes in web.war can access classes belonging to ejb1.jar and ejb2.jar. Similarly, classes from ejb1.jar can access classes from ejb2.jar (and vice-versa).

The ear-subdeployments-isolated element value has no effect on the isolated classloader of the .war file(s). i.e. irrespective of whether this flag is set to true or false, the .war within a .ear will have a isolated classloader and other sub-deployments within that .ear will not be able to access classes from that .war. This is as per spec.

I read the above, thanks a lot