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.
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.
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.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How to EJB 3.1 Deployment in Tomcat 5.5.x
Blockquote
Any buddy please help me i have an web space with apache tomcat 5.0 jsp 2.0 and jvm 1.6
and i want to use ejb in my project so please tell me what should i do that i can use ejb 3.1 in my web space which have these resources listed below
i) Tomcat - 5.5.xSupport
ii)JDK - 1.6.x Support
iii)JSP/servlet - 2.0 Support
so how can i use EJB with web application with this available resources i mean what should i do to these things
Please Help me...!!!
It's not possible, go download JBoss AS or GlassFish.
Tomcat implements just the web container part of Java EE
It's definitely possible and in some cases I prefer the option of using a lightweight container instead of a more heavy weight application server. Having said this though the version of Tomcat your using is too old and won't work anyway without some serious messing about with the container (changing some JARs that come preinstalled with Tomcat), even with that I'm not sure it will work.
As Bozho says, try OpnEJB, but go for JBoss or Glassfish if you can. Tomcat is a JSP container and therefore not meant to this kind of use. EJB run on Application servers.
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
I'm making a little project with Seam, Hibernate and JSF. This project run on JBoss 5.1.
My boss wants to deploy this project on WebLogic. I read on the seam documentation that seam and WebLogic don't work fine together.
I would like to know if I can use Hibernate (with JPA) and JSF on WebLogic and what framework (struts, spring?) I can use to replace Seam.
Edit: I read in the seam documentation (chapter 39, weblogic integration) and I find that:
For several releases of Weblogic there has been an issue with how Weblogic generates stubs and compiles EJB's that use variable arguments in their methods. This is confirmed in the Weblogic 9.X and 10.0.MP1 versions. Unfortunately the 10.3 version only partially addresses the issue as detailed below. So, I want to know if other problems like this exist.
Edit 2: I use Weblogic 10.3
What do you mean by "don't work fine together"? I've already seen Seam applications on WebLogic and the Seam documentation provides detailed instruction to run Seam on WebLogic without mentioning any blocking issue.
If you have something specific in mind, please clarify. But in the current state of the question, my advice would be to stick to Seam and to deploy your application on WLS.