Now we have a project with java 1.4 and ejb 2.1 running on jboss 3.2.1. We are trying to update up to java 6 and ejb3.1, but we are doing it in steps. So my question is simple, can we use ejb2.1 on jboss6?
In theory, yes. EJB 2.x is still part of the current JavaEE spec, and JBoss6 supports it fully.
However, JBossAS 3.x and 6.x are architecturally very different to each other. Do not assume the upgrade will be a smooth one, it may well feel like migrating to a completely new appserver.
Related
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.
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 using Weblogic 10, so maximum Java allowed there is Java 1.5
I inherited the code using EJB3
So, I will have to work on it within a realm of my Java 1.5 limitation.
I think, original designers had in mind to use Hibernate for implementing Data access, and
at some point we will migrate to JBOSS, so would like to keep Hibernate as a choice
There is one sitting in a project - version 3.2.1.ga. Same is a version for hibernate-entitymanager.jar
What is the latest version of Hibernate that I can use for this? I understand there were some changes in it.
Hibernate 3.x workes with JDK 4 and 5,
The 4.x requires 6.
I think you should go with HIbernate 3.6.x. The last version in 3.x was 3.6.10.
You will not find it on hibernate site you will to goto sourcefoge.net to get this version.
here's the link
I am using Jboss 2.4.11, if i upgrade JDK from 1.4 to 6 How is the jboss server going to handle the application?. What are the common things i should start investigating while i am in the process of the upgrade. I am looking at the Oracle's documentation and other posts in stackoverflow related to jdk 6 backwards compatibility with v1.4. My question is more specific towards using Jboss server. Also the application uses ejb 1.1
I'd recomment to move from one consistent system to another one. Even JBoss 4 needs a special version for JDK1.6. Java 5 brought MBeans rigth into the VM and older versions of JBoss used MBeans for configuration. As there must not be to MBean servers within a single VM this was a big issue, when migrated to java5. As EJB 1.1 is still supported I'd recomment to move at least to JBoss 4.2 as this is still kind of similar to older versions, while JBoss 7 is totally different.
The only thing that will really help you to get the migration a little bit smother are tests. At least quite a number of integration tests.
I just need clarifications related to JBoss Application Server. I've developed a project which is compiled in Java 6. And it is deployed in Jboss 5 version. Till now I didn't find any problem with the application. But I want to know will there be any possibility that Jboss will have any backward compatibility problem. Or does Jboss needed upgradation with respect to Java version. Any suggestion would be appreciable.
Thanks,
Marshal.
Even if JBoss 5 is compiled with Java 5 there shouldn't be compatibility problems at a language level.
As for the libraries there might be a problem but those that JBoss requires should have been taken care of. This leaves you with core libraries that JBoss might have replaced in its class loader hiearchy and thus might have an older version. In that case you could put those libraries into your application and effectively override the JBoss versions on a per-application basis. We did that with some XML libs (IIRC JAXB was one of them).
As an alternative - as suggested by #Geziefer - use a JBoss 5 version specifically compiled for Java 6.