Article:		Nukes: the Open Source Java CMS
Subject:		JLCP!!!
Date:		2003-06-09 03:53:24
From:		anonymous2
Please check out Java Lobby's work at http://www.jlcp.org/ Its not tied any app server. Why is it we accept proprietary lock in when the company calls itself an "Open Source" company? Especially odd when this is supposed to be a Java "Write Once, Run Anywhere" product. Go see jlcp please. dan

Showing messages 1 through 3 of 3.

• JLCP!!!
  2003-06-09 07:19:12  anonymous2 [View]
  
  
  why is that bad to be tied to JBoss ?
  
  if I can save thousand of lines of codes because the code is already written in there, is that a bad thing to do it ?
  
  if JBoss offers features others don't have is that bad to use them for the sake of simplicity ?
  
  we are able to add features others cannot do thanks to JBoss :
  
  For instance we can hotdeploy remote additional modules in a Nukes instance without to have to reset anything. Can you do that ?
  
  JBoss enables us to a provide packaged distribution, you unzip and run and you have a Nukes running without doing more.
  
  Franckly I don't see the BIG problem. If we want to use EJB there is a need for an opensource appserver, do you see any other credible opensource server ? because at the end of the day, a lot of OS java CMS will run on JBoss. Don't take it bad but from your installation file :
  
  # App server to use
  *** appserver=jboss ***
  
  julien
  
• JLCP!!!
  2003-08-19 13:31:22  anonymous2 [View]
  
  
  --- why is that bad to be tied to JBoss?
  
  Being tied to a single app server is always a bad idea. The biggest reason is that by tying the implementation to a single app server, in this case JBoss, you are greatly limiting the potential audiences. The majority of java sites being run are NOT running JBoss, and thus they are prevented from using the dependent applications also. And, the answer is not as simple as saying "well JBoss is free, so anyone can use it". Despite it being free, most corporations and large java web hosters shy away from JBoss.
  
  
  Not being tied to a single application server is a HUGE advantage for the JLCP effort.
• JLCP!!!
  2003-06-09 10:24:01  anonymous2 [View]
  
  
  For the record, I am not affiliated with jlcp. Just an interested 3rd party.
  
  >if JBoss offers features others don't have is
  > that bad to use them for the sake of
  >simplicity ?
  
  Its called embrace and extend when Microsoft does it. Why is JBoss any better?
  
  >For instance we can hotdeploy remote additional
  > modules in a Nukes instance without to have to
  > reset anything. Can you do that ?
  
  Your confusing the app with the app server. I have no problem with JBoss' feature set. Compete away! I *DO* have a problem when we start writing appserver specific _apps_.
  
  You want hotdeploy, fine. But why write Nukes to use JBoss-specific JMX functions?