Recently i read this documenentation and also this announcement, basically targetting the weld-osgi releases.
I am really interested in how to get this to work in JBoss AS 7.1.x. Can someone please point me to a solution that works?
Thanks
The Weld-OSGI release introduced Weld SPI changes. There is currently no stable JBoss AS release supporting the new SPI.
An option is to build the current JBoss AS 7 master from source. Then you should be able to upgrade to 1.2.0.Beta1 simply by replacing weld jars.
Sure thing: Helloworld OSGi quickstart
Related
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.
I am trying to port a web-application to Tomee (Apache TomEE 1.5.2) but I have hit a major hurdle.
The version of quartz our application uses clashes with the bundled version of quartz.
Tomee comes with quartz-2.1.6.jar which is loaded as part of the container set-up as far as I can tell, But our application relies on a very old version of Quartz and we are unable to update at this point in time.
From research I had assumed it would be enough to place the older quarts jar in the WEB-INF/lib of my web-app and as per the Tomcat class loading information here it would be looked up before the quartz-2.1.6.jar in the ${catalina.home}/lib directory, this doesn't seem to be the case.
Is it possible for Tomee to use the bundled version of Quartz and my web-app to use a different version of Quartz?
Thanks to Romain Manni-Bucau.
The solution was to add
openejb.classloader.forced-load=org.quartz
please see Tomee Users Mailing List
I need to set up blitz JavaSpaces (here). On Blitz installation guide one of the requiered packages is the starter kit for JINI 2.1, but the link offered is broken and I can't seem to find it anywhere else. I've been looking at Apache River Project, ¿should I install this instead of the missing JINI 2.1? There's really little or no documentation at all and it really bugs me that blitz is mantaining a broken link to one of its prerequisites. That gave me the idea for this other question ¿is the blitz implementation reliable?
thanks a lot
I'm supporting a legacy application and needed this as well. You can find the starterkit here: maven repository.
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.
We are planning to upgrade our Tomcat from 4.1.31.
Our's is an Axis 1.4 application where we have our web services.
Request you to suggest the latest stable version of Tomcat 5 or Tomcat 6 suitable for our application. And the things to consider while upgrading.
Will the existing 1.4 Java code base works smoothly on Tomcat 5 or 6?
And going further we may write the code in JDK 1.5 as well. So, having Java 1.4 code and Java 1.5 code together, will create any problems?
Kindly suggest.
Please share your upgradation experiences.
Thank You :)
Tomcat 6.0.26 is the latest stable release.
It requires JRE 5.0 or later, so if you are truly stuck on 1.4, you'll need to download the latest 5.5 release, which requires a compatability package to run on 1.4.
My advice: bite the bullet and make the necessary changes for your application to function on 1.6. It is only going to get more and more painful to upgrade (and to continue to code in 1.4) as time goes on.
Go to Java (1.)6; it really makes doing web services like yours easier and it's really widely available now.
If you are going to upgrade I would recommend first doing some tests with java 6 + the existing codebases. If that seems to work, go to Tomcat 6.
Perhaps also upgrade some Axis libraries while you're at it, or leave it as is if it still works.
In my experience you can get to trouble by migrating to Java 5 (and thus 6), especially with XML. My memory has something like a class name clash between Java 5 and an old version of Xerces, but I could be mistaken.