Can anybody please tell me, which version of EJB is supported on JBoss EAP 6.3 ?
My current application is running on JBoss AS 4.0.3 and EJB 1.1 . I want to upgrade it to JBoss EAP 6.3. Does EJB 1.1 is supported on JBoss EAP 6.3?
[Not suitable for comment, little lengthier. These are only pointers, may not directly answer the question, but indirectly can help]
Try to go through JBoss documentation first for the specific version, which you are intended to use.
Look into the changes made in the version, there is reasonable amount of documentation provided about the features supported/added in that particular release.
Go to specific version download page.
Frequently asked questions
Refer here [JBoss Enterprise Application Platform Supported Standards] for the release version you are looking to utilize.
There you can find details; Enterprise JavaBeans with Interceptors 1.1 (EJB) [JSR-153, 220, 318] 3.1, 3.0, 2.1, 2.0 for JBoss EAP 6.
For the record
Meh, to many turns to say:
Support JDK 6, 7 and 8 (8 only for EAP 6.3.3 and higher)
Or, to be specific - No, JBoss EAP 6.3 does not support the EJB 1.1 specification.
Related
I will try to keep this general, as I am seeking a general answer.
When I open the properties window of one of the references in my project in Visual Studio I see this runtime version: v4.0.30319
This reference is used in a project where the target framework is .NET Framework 4.7.1. And it works fine.
My project is communicating with a database, and I want to make sure that this communication will be utilizing the TLS version 1.2 protocol. As I understand it, this can be insured by having the project targeted against .NET 4.7 or above.
Here is my question: if I have a project with a reference, which have a target framework that is lower than .NET 4.7, will this ruin my goal of using a TLS protocol of version 1.2?
How can I make sure that my reference is up to snuff? The runtime version written above, is not suggesting that this reference has a .NET Framework of 4.7 or above, or does it?
We have a legacy app which uses seam 1.1. Its deployed on websphere 7 which has JSF 1.2. So will it cause any problems? Are seam 1.1 and JSF 1.2 compatible?
Or do i need to upgrade the version of jboss seam which is compatible with jsf 1.2?
EDIT 1:-
The reason I am asking this question is that suddenly we are getting following erros
application E JSF1007: Duplicate component ID listForm:j_id_jsp_768167483_47:templateItems:j_id_jsp_768167483_77 found in view.
Another team has said that its because of the version mismatch of JSF being used in app and the JSf version supported by websphere 7 which is 1.2.
Yes, They both are compatible and will cause no problems.
Current environment: WebSphere 6.1 with IBM java jdk 1.5 with Struts 1.3 and some version of Tiles.
I would like to replace Structs 1.3 with Spring MVC. What is the maximum Spring Framework version can I use? Fortunately, JPA 2.0 compatibility is not required because the current system uses REST calls for all database access instead of using Hibernate. We will eventually move WebSphere to 8.5, but not anytime time soon.
Again, upto which version of Spring framework can I use with Websphere 6.1 (with IBM jdk 1.5)? Thanks in advance.
You can use spring with the latest 3.2 version.
We're using Spring 3.0 today with WebSphere 6.1, and I'm pretty sure there's no reason we can't use 3.1.
Is there any way to use servlet 2.5 specification on WAS 8.0, by default he try to use 3.0 but the portal which I'm using doesn't support new servlet specification and I've to run it on lower version.
No, the only servlet container included in WebSphere Application Server 8.0 is the one that supports the Servlet 3.0 specification.
(If you have a specific backwards compatibility problem, you could post that, and someone might know how to workaround the issue.)
is jbos5.1.0 compatible with jdk6 and spring2.5.X.
I am also integraion acegi security and not spring security 3.0 as i am using spring 2.5.0?
IS jboss 5.1.0 comaptible with spribng3.0 andjdk6 ?
A few months ago, I've tried JBoss 5 with Spring 2.5.6 and couldn't deploy my application, because of this bug. The comments on the issue, mention the problem only happens with EJB, but my application didn't make use of EJB and it was packed as a war.
According to the JIRA, this was fixed in spring 3.0RC1, but I haven't tried it (for now, I gave up updating to a new version of JBoss).