afaik:
console: next release will be seam based (and thus require 1.5)
engine: 3.x branche will stay 1.4, 4.0 will be 1.5
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052877#4052877
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
afaik:
console: next release will be seam based (and thus require 1.5)
engine: 3.x branche will stay 1.4, 4.0 will be 1.5
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052876#4052876
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
Has anything changed regarding the requirement for JVM 1.4 compatibility in the
6 months since this thread was last active?
We are considering contributing back some engine code (not console code) with
JVM 1.5 dependencies.
Thanks,
-Ed Staub
View the original post :
http://www.jboss.com/index
Integration with Java 5 is of utmost importance IMO. We need to get tighter
integration with SEAM! SEAM is getting a lot of attention right now and so now
is the time to either branch JBPM to port 1.5 or just declare the change as
part of the roadmap. With all of the attention, people are sur
Again a new refactoring of the web console, after the struts version, the jsf
version, and the current developped version ?
Four times in three or four years, it becomes too difficult to follow in a
production environment, I will become to consider jbpm as a non-stable
product...
View the or
Many companies I've seen in Mexico are very reluctant to migrate their stable
applications to a new app server or a new JVM. I know a bank that was using WAS
3.5 two years ago, just to make my point.
So, I think that jBPM having a dependency on J2SE 5.0 would not be such a good
idea. So far, I
"[EMAIL PROTECTED]" wrote : Hi,
|
| We are considering moving to SEAM as the web technology for our jBPM web
console. The main concern is that this introduces a dependency on a Java 5
JVM. Note that this dependency will only be there for the web console. NOT
FOR THE RUNTIME ENGINE. In c
This is partly true for the company I work for as well, There it is not so much
that we do not want to run 1.5, but that the appserver we use (wls 8.1) does
not support using newer jvm's (it doesn't even start trying without anything
deployed in it with 1.5). So that would mean migrating to wls
Hi Tom,
I don't know any big company (or app server other than JBoss maybe?) that isn't
behind the newest JVM by at least 2-3 years. The company I'm working for right
now is DICUSSING moving TO JVM 1.4.2 (jBPM being one of the reasons to do so).
I'm not sure if we will need the WebConsole in th
