These changes to support forking under JBoss EAP 6.x and JBoss 7.x. Not sure about Wildfly, but they should work for that version of JBoss as well. There are no dependencies on JBoss API's, because the code uses Java reflection to access the JBoss VSF VirtualFile object.
I tested with an Arquillian container JUnit test that I have locally, but I did not want to introduce all of that to the project. I also tested the snapshot jar with my application under JBoss EAP 6.x.
The code will behave as before if Ghost4J is not running under JBoss.
zippy1978
commented
8 years ago
These changes to support forking under JBoss EAP 6.x and JBoss 7.x. Not sure about Wildfly, but they should work for that version of JBoss as well. There are no dependencies on JBoss API's, because the code uses Java reflection to access the JBoss VSF VirtualFile object.
I tested with an Arquillian container JUnit test that I have locally, but I did not want to introduce all of that to the project. I also tested the snapshot jar with my application under JBoss EAP 6.x.
The code will behave as before if Ghost4J is not running under JBoss.