The latest jbpm 5.3.0 version (jbpm-5.3.0.Final-installer-full.zip) which bundles jboss 7.0.2 by default . But I want to ask will it work or how can make it work with the latest jboss 7.1.X?
18:10:09,783 ERROR [org.reflections.Reflections] (MSC service thread 1-7) could not create Vfs.Dir from url. ignoring the exception and continuing: org.reflections.ReflectionsException
at org.reflections.vfs.Vfs.fromURL(Vfs.java:99) [reflections-0.9.5-RC2_jboss-SP1.jar:]
at org.reflections.vfs.Vfs.fromURL(Vfs.java:89) [reflections-0.9.5-RC2_jboss-SP1.jar:]
It is sad that though many users reports that they have this problem , there still no workarounds or solutions that I can found out
When deploying to jboss 7.0.2 , I simply use the standalone.xml provided by jbpm-5.3.0.Final-installer-full.zip .
When deploying to jboss 7.1.1 , I do the following changes based on the default standalone.xml provided by the jboss 7.1.1:
- Configure the datasource for the DB (I am sure the datasource is setup properly)
- Change the <deployment-scanner> ‘s deployment-timeout attribute to some larger values to avoid timeout before the web apps are successfully deployed.
- Add <security-domain> for the web apps drools-guvnor , jbpm-console ,jbpm-form-builder (I copied the corresponding section from the standalone.xml in jbpm-5.3.0.Final-installer-full.zip )
- Disable the JPA extension because jbpm is developing using JPA1 but jboss 7 is JPA2
Is it simply due to configuration problems of my standalone.xml in jboss 7.1.1 ?
If yes , what is the problem of my standalone.xml in jboss 7.1.1?
If my standalone.xml in jboss 7.1.1 is correct ,please confirm if it is a bug .If yes,I suggest jbpm team to warn user that jBPM 5.3 final release version cannot work with jboss 7.1.X in order to prevent new users from wasting their time and have bad experience when trying jbpm5.3 with the jboss 7.1.X . Especailly , they should delete this remark " if you move to 7.1, don't forget to change the following line (7.0 -> 7.1) " from build.properties as this remark causes user think that it will work with jboss 7.1.X but actually it does not.
Thanks for any idea or insight .