My current application is running with JBPM 4 on JBoss 4.0.3 application server. We are planning to upgrade Jboss AS to 7.2 in the near future and we want to know the compatibility of JBPM4 with Jboss 7.2. We are unable to find useful documentation on compatibility between JBPM 4 and Jboss AS 7.2. Please help.
I wud suggest to migrate jBPM 4 also to latest version (6.X) as i have also worked on 4.x and moved back our application to 3.2.X becuase there was no product support aprat from community(https://developer.jboss.org/thread/150947).
Regarding the documentation and compatibility i think it shud work but again you need to test at your end only.
Post results here so it will be helpfull for other also.
Related
In the project, we are looking to migrate the application from Jboss EAP 6.4 to Wildfly 21?
Can anyone suggest:
what are the factors we need to take into consideration?
How I can do that?
what changes I required to do that?
You should take a look at https://github.com/windup as it will analyse all the required changes
I am looking for the reasoning which version of JBOSS or WILDFLY I should choose for migration. Can somebody tell I should go for JBOSS AS5 but not JBOSS AS7 or even WILDFLY 8. My application is using EJB 3 and struts 1.2.8 with EAR packaging.
You should ask yourself which are the reasons why you want to migrate.
Did you hit a critical bug?
Do you need new features?
Do you need support?
JBoss 4 and 5 rather similar, but both outdated. Support for EAP5 ended 2013. You won't get much community-support either. If I decide I had to migrate, i would migrate to the latest EAP or stable WildFly version depending on the needs for support.
I am working on building a workflow application and I'm planning to use JBPM as my BPM framework. Can anyone suggest me which is the stable version to use in producation environment?
You can try with enterprise release of jBPM which is Red Hat JBoss BPMS. Red Hat will provide hot-fix patches to known issues. Also rollup patches are provided on certain interval, which includes fix for multiple issues. Along with all this you will get 24x7 support for issue.
Just let you know, I have been using jbpm 6.5 with docker in production for 2 months. All work smoothly
Recently i read this documenentation and also this announcement, basically targetting the weld-osgi releases.
I am really interested in how to get this to work in JBoss AS 7.1.x. Can someone please point me to a solution that works?
Thanks
The Weld-OSGI release introduced Weld SPI changes. There is currently no stable JBoss AS release supporting the new SPI.
An option is to build the current JBoss AS 7 master from source. Then you should be able to upgrade to 1.2.0.Beta1 simply by replacing weld jars.
Sure thing: Helloworld OSGi quickstart
Liferay 6.0.6, by default doesnt bundle with JBoss 7. Did anyone successfully get liferay to work with JBoss 7. I'm a noob and would prefer if any of you can provide the instructions.
I talked with some of the Liferay staff and they said JBoss AS 7 is still not supported or usable with Liferay. I tried to use it and it failed completely. However, the Liferay staff is working on it AFAIK. So my answer is: wait, because the Liferay team will solve this problem.
Liferay 6.0.6 Is not compatible by default with JBoss 7 I was trying to doing it, but it's incompatible due ClassLoading issues to locate files by the portal.