[jboss-dev-forums] [Design of JBoss jBPM] - SEAM / Java 5

[tom.baeyens@jboss.com]

I want to reopen the discussion on SEAM and Java 5.  Afaik, the only reason, we didn't opt for SEAM was Java 5.  But i can't seem to find that discussion thread any more :-(  

Now we have a company that is considering collaboration with significant contributions.  But they have seam as a prerequisite.  If not SEAM, they are going to build /are already building their own web console with SEAM.

Since this is a matter of time, I think we might reconsider.

>From a general jbpm-adoption standpoint i don't think that dropping support for java 1.4 is a problem.   BUT the problem is that big coorporations tend to be slow on adopting new versions...  These might not be big in numbers, but they are important for JBoss.    BUT Fadar also made the remark: 'if they are slow to adopt java versions, they will probably also be slow to adopt new jBPM versions...'

Note that this is only a compatibility issue for the web console.  The runtime engine for 3.x versions of jBPM will surely remain 1.4 compliant.  But this will of course also impact the java 5 compatibility requirement of the simple-to-install suite package and might give the wrong impression.

Anyways, these are all the pro and con arguments that i could think of from the top of my head. 

Do you see other arguments ?

Would you think it is a good overall idea to move to SEAM ?

I know that Gavin is going to be happy if we would make the change... well... let's say he's going to declare us "less nuts" :-)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991044#3991044

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991044