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.
Related
I am planning to migrate a webapp from java 8/tomee 7.0.4 to java 11/tomee 7.1.0, but still unsuccessful. So I write a barebone webapp with only one facelet page and one managed bean. This works on java 10/tomee 7.1.0 but not java 11. The errors are:
java.lang.IllegalStateException: Cannot get Unsafe.defineClass
....
java.lang.NoSuchMethodException: sun.misc.Unsafe.defineClass(java.lang.String, [B, int, int, java.lang.ClassLoader, java.security.ProtectionDomain)
After some Googling, from http://tomee-openejb.979440.n4.nabble.com/Some-jars-in-TomEE-8-SNAPSHOT-are-not-Java-11-compatible-td4685162.html it seems that the problem originates from jaxb-impl. So I tried adding to pom.xml according to https://winterbe.com/posts/2018/08/29/migrate-maven-projects-to-java-11-jigsaw/ which failed. I restored pom.xml and modified according to Java 11 package javax.xml.bind does not exist which also failed.
This is for tomee server which is less popular. But tomee 7.1.0 is based on tomcat 8.5 which should be much more popular. I think the problem will still be the same.
Advice is appreciated and I think many people should have the same problem.
Try upgrading your tomcat/tomee to the latest version, or downgrading your Java version as incompatible versions tend to fire these NoSuchMethod/NoSuchFile exceptions.
Could be that one technology is reliant on a certain other technology, and is aware of a certain API version, but you are trying to use a higher API version, which could be entirely different.
Another possibility is that tomee is not yet ready to work with java 11 at all (but this seems rather unlikely).
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'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
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.