Has anybody successfully implemented Weld with a JBoss AS 5.1 project? I'm using EJB3.1, and I'm disappointed with the injection limitations (can't call from POJO, lookups from JNDI)
BUT on their site, JBoss 5.x isn't listed as a tested platform.
http://seamframework.org/Weld
Supported platforms
Weld has been tested on the following platforms:
JBoss Application Server 7
JBoss Application Server 6
GlassFish V3.x
Apache Tomcat 6 & 7
Jetty 6.1 & 7.x
Java SE 5.0+
Anyone have success with this?
CDI support is only available OOTB in AS6 and above. If you want, you can embed Weld in your ear or war file. but it won't have EJB integration
Related
Every tutorial for the upgrade to Spring 5 has tomcat 8.5+ as a requirement but no detailed explanation. The application that I want to upgrade should not run as a standalone application with an embedded webserver, but beeing deployed on a tomcat 6, which we cannot upgrade for several reasons.
As #procrastinate_later points out, Spring 5 actually requires Servlet 3.1 (and Tomcat 8.5.x).
Spring 5 has initially was expected to have Servlet 3.0+ minimum requirement which supported only from tomcat 7
We’ll definitely raise to Servlet 3.0+ (from our present Servlet 2.5 runtime compatibility)
So you need to upgrade to at least Tomcat 7.
Looking at the What's New in Spring Framework 5.x documentation:
Java EE 7 API level required in Spring's corresponding features now.
Servlet 3.1, Bean Validation 1.1, JPA 2.1, JMS 2.0
Recent servers: e.g. Tomcat 8.5+, Jetty 9.4+, WildFly 10+
Cross-referencing this with the Apache Tomcat Which Version documentation, Tomcat 8.0 would be sufficient for the Servlet 3.1 requirement, but Tomcat 8.0 has been superseded by Tomcat 8.5+, as stated in the Which Version (Tomcat 8.x) documentation:
Tomcat 8.5 is thought as a replacement for Tomcat 8.0. Please refer to Migration guide for guidance on migrating to Tomcat 8.5....Users of Tomcat 8.0 should be aware that Tomcat 8.0 has now reached end of life. Users of Tomcat 8.0.x should upgrade to Tomcat 8.5.x or later.
Anybody facing the same problem? When I try to change the Dynamic Web Module version, eclipse does not allows me to.
Check this Link:
Quoting the same:
The error message is quite understandable - you are attempting to execute an application that requires the server to support Servlet Spec 3.0 when it doesn't. You must therefore, run the application on a server that complies with that version of the Servlet Specification.
As far as I know you have the following options at your disposal, at the time of writing this:
Apache Tomcat 7.0
Glassfish 3.1
IBM WebSphere 8
JBoss 6 and 7
Any one done migration from JBoss AS 4.2 GA to JBoss EAP 6.2?
Does JBoss EAP 6.2 has web and app server..? In JBoss AS 4.2 GA has the folder structure /server/app and /server/web where as in JBoss EAP 6.2 no server folder at all.
How to deploy the services in web and app in JBoss EAP 6.2?
Gone through the system migration guide, have to change the packaging structure of EAR or WAR due to change of modular class loading.
Where/how to find the system dependencies, user dependencies, local resources and inter-deployment dependencies in JBoss AS 4.2.
Thanks in advance.
Basically, JBoss 7 / EAP 6 is nearly 100% different, so there is no speaking of "migration". You will have to start from scratch; learning how the AS works, how to configure stuff (which is much easier to be honest and very well documented on the JBoss site) and to get the deployment of your application working. Which might be a very hairy thing to do if you have legacy tech such as Seam 2.
Luckily JBoss 7 is also quite nicely documented so guess what? There is actually some form of a guide. For JBoss 5 and up though, but it should still be helpful.
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7
Have a look at the Windup project.
It is the official JBoss project to support (semi)automated migration. There are no rules for 4.2 yet, the current set of rules covers a subset of migration knowledge.
i am a newbie,today i am tring to use jboss and deploy my application with jboss,i did't use
jboss before ,when i try to download ,i log into the official website,click download Jboss Application Software 7,but it jump to JBOSS eap6.1.final download place,so i download the EAP6.1 instead. after sometinme of probing,i start the server with standalone mode and upload my app war file with Management Console,but i cann't access my app,my application name is MedicineManage
i try with: http://localhost:8080/medicineManage/login.jsp
here is the result
JBWEB000065: HTTP Status 404 - /medicineManage/login.jsp
what's the difference between AS7 and EAP6.1.0
somebody can explain for me ! thanks a lot
AS is the application server and it is an open source.
EAP is the enterprise application platform supported by red hat and red hat is often releasing the patches for this version.
For more detail just go through the web page it has clear difference between application server AS and Enterprise application platform.
http://planet.jboss.org/post/security_community_jboss_as_versus_jboss_eap
Boot time of Jboss as 7 is less than Jboss EAP 6.1 and also memory consumption is less in Jboss as 7.
Find more about Jboss EAP 6.1 from here and Jboss as 7 from here. Follow these links for documentation about Jboss EAP 6.1 and Jboss as 7.
How ever JBoss EAP is a product that is officially supported by Red Hat. You get patches, updates, security fixes etc. It is shipped secure.
I was able to deploy a WAR file with AOP enabled in JBoss Application Server 5. I passed the spring-agent jar as the javaagent parameter.
But I am not able to deploy the war file in JBoss AS 7. Is AOP enabled in AS 7?
EDIT:
AOP Support in JBOSS 4
So, AOP Support is present in JBoss AS 4, and I was able to make it work in AS 5.
Application Server 7 is the latest version and one would expect to find some word about it in the AS 7 documentation. I am not able to find anything.
Am I missing something?
Read the JBoss Community forum thread on this topic: JBoss AOP is not part of AS 7
You're not missing anything, but JBoss 7 is. There is (currently) no explicit JBoss AOP support in 7.