I'm looking for guides regarding specific details / instructions to migrate our app.
The closest I have found is this.
But that is about AS 4.2 GA to EAP 6.2.
Can anyone guide my poor soul? Please help.
I cant tell if this is an "answer". But just leaving this here in case somebody needs it.
We've now successfully ported our app with no errors. What fixed our problem was just properly adding our machine's hostname in /etc/hosts.
In our case, there were no other "porting-specific" files to change. Its either our app didnt use very complex features, or I think maybe AS 7 -> EAP 7 is just a direct port?
Anyways, cheers :D
Related
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.
We are starting to migrate our CMS to liferay.Could anybody please help me understand which version of liferay we should be going with?
Liferay 6.2 looks to be having great support for mobile devices but some posts on internet say about having bugs in 6.2 and patches being available only for EE version of 6.2?
Any quick suggestions would really help! thanks.
Well when you go with CE and you are just starting with liferay than it is always preferable to start with the latest version.
Reasons:
Here is a one from Liferay Staff
Bugs are always there, but 6.2 GA2 solves most of them and there would be other versions coming out for 6.2 which would solve more bugs.
If you find any bugs in 6.1, there would be no newer version for this. So it is better to go with 6.2.
Hope this helps.
I now it's a pretty peculiar, uninteresting and old combination of application server and JVM version but that is what's being used in my company nowadays. I would need to be able to test EJB3 components with JTA(TransactionManagementType.BEAN) and access to database through JPA 1.0/Hibernate
I've been struggling with this one and a half day by now, with very little luck so far. I found some answers here in Stackoverflow and in JBoss Community forums but all of them involve using Java 6. I've already got tests of this kind running using OpenEJB (written without Arquillian) but -hopefully- this year we will be migrating to a new application server and it would very useful to have the same set of tests in Arquillian to be able to check that EJBs that are working now on JBoss 4.2 will work too in another newer application server (likely to be JBoss 7)
Would anyone know a working Arquillian example with these requirements?
Finally, after fighting a little bit more with this, I put together a solution combining Arquillian, JAVA 5, JBoss4.2 y JPA. Anyone interested can found it in this GitHub miniproject
Regards
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.