Article:		Nukes: the Open Source Java CMS
Subject:		"there was no open source Java CMS"
Date:		2003-06-04 20:37:48
From:		akuckartz
Marc Fleury writes: "at the end of the day there was no open source Java CMS engine source when we looked." Maybe he closed his eyes when he looked? See: Content Management Frameworks/Systems Overview http://oscom.org/matrix/index.html

Showing messages 1 through 16 of 16.

• Java Open Source CMS
  2004-04-01 10:16:22  fj_rodriguez [View]
  
  
  Java-Source.Net contains a list of Open Source CMS written in Java
• Java Open Source CMS
  2008-11-26 09:11:31  melenti [View]
  
  
  Hello ,
  
  We are working on a Spring, JPA, Hibernate CMS. Identical To joomla in behavior and Look ,
  
  we have already some work and code on sourceforge and soon we will relaease a WAR so you can drop it on any JEE container and use it, it will use postgres or MySQL your flavor
  
  bye
  
  Adrian Cadena
  www.melenti.org

• "there was no open source Java CMS"
  2003-06-09 08:30:14  anonymous2 [View]
  
  
  Common man, that index page clumps PHP, Perl, and other languages together - there's only a minor few listed are in Java, and not to the same level as p*Nuke

• "there was no open source Java CMS"
  2003-06-04 21:59:23  anonymous2 [View]
  
  
  Seriously. The arrogance of this guy is ubelievable. And the idea that this total rewrite somehow says something larger about the performance of PHP and Java is insane.
• "there was no open source Java CMS"
  2003-06-05 16:14:36  anonymous2 [View]
  
  
  Marc Fleury Here,
  
  I knew the "first open source java cms" line was going to come back to haunt us. Frankly we didn't run into the ones you mention and what we were really looking for is the postnuke kind of solution with the CMS AND THE MODULES that go with it. That is what really made us go to postnuke and made us like the PHP solution in the first place.
• "there was no open source Java CMS"
  2003-06-09 08:17:58  anonymous2 [View]
  
  
  Marc,
  
  I whole heartedly agree with you - most Open Source CMS available is not designed to be Community-based portal, but more of a Publisher/Editor portal. Your work is this matter is appreciated!
• "there was no open source Java CMS"
  2003-08-05 07:29:34  anonymous2 [View]
  
  
  JetSpeed is java based framework that will exactly what your looking for. Correct me if I'm wrong...:)
  
• "there was no open source Java CMS"
  2003-06-10 03:24:59  anonymous2 [View]
  
  
  As we have seen in this thread so far, there are plenty of Java-based CMS systems in existence. However, what Java needs is a system like phpnuke that allows a user to have the framework of a site created for them, and select a skin to suit your needs.
  
  IMHO, there are too many small portal frameworks appearing, but no single framework has enough portlets to merit the time spent installing them. Other systems like Liferay are difficult to configure and require dedicated machines, i.e. you need your own server to have the amount of control and resources required. I think phpnuke exceeds in this regard because any man and his dog can download phpnuke, install it on his free/cheap hosting solution and have the capacity to included syndicated content, edit custom content, change skins at the click of a mouse.
  
  Nukes is a positive movement towards a portlet-rich framework which allows a user to put a site together very quickly, with lots of functionality. My two concerns, though, are with the lack of an MVC framework (why didn't they bundle Rikard's webwork?) and the lack of portability.
  
  What I would love to see is a portal system based on Struts/Tiles for the control and rendering, hibernate for persistence (perhaps Castor for XML) which would be installed in a sinle WAR file. I've been keeping an eye on http://jnuke.sourceforge.net/ for some time, but there seems to be very little happening there. Perhaps its a good thing that Marc et al. have started this project, it might spur some of us lazy developers to get up and do something about it, maybe join the jnuke project, just as Linus' move to bitkeeper sparked the bitbucker project!
• "there was no open source Java CMS"
  2003-06-12 05:23:08  anonymous2 [View]
  
  
  I agree with you, a "portal system based on Struts/Tiles for the control and rendering, hibernate for persistence (perhaps Castor for XML) which would be installed in a sinle WAR file" seems to be a good way to do it, I really don't understand why they mix html and java code and Julien nor Marc answered about that.
• "there was no open source Java CMS"
  2003-06-11 15:14:00  anonymous2 [View]
  
  
  about portal framework:
  What di you think about jetspeed?
  
  The project did gain speed the last year and has developed very well. Seeing the JPC 168, which will push jetspeed to the standards, it will be a good start.
• the real question behind the article?!
  2003-06-11 15:11:38  anonymous2 [View]
  
  
  I agree with the opinion, that there were/are some Java based Open Source CMS projects out there (openCMS, Wyona (now Apache), Redhat (former Ars Digita) and others). When talking about PHPNuke and talking about "non-Java-based" projects for JBoss, the guys had have to look on Zope also. There were/are better Open Source CMS projects than PHPNuke.
  
  But isn't there another intention behind this article than just talking how sey Java based applications are? Besides appservers and database servers there is just one application, which is on the brink to a commercial hurdle: CMS! (Onlineshops like Intershop, Broadvision and others are almost out of busines).
  
  IMHO the JBoss group is trying to settle new grounds for their business. Next to the Apache project, the Jboss group is perhaps the only one who is able to push an Open Source project into the community. At the end of the day this "company" is selling services and makes it living out of this services. So from their perspective, why pushing another Open Source project when they can push their own?
  
  "Is it just a new business for the Jboss group?"
• the real question behind the article?!
  2003-06-13 08:35:56  anonymous2 [View]
  
  
  When we evaluated our options we really felt that there was a gaping hole in the java CMS OSS space. Nothing the size of Postnuke, which is widly succesful as a project and community and we felt it was worth doing. The business angle is definitely there, in the sense that first mover advantage is real and creates communities (JBoss ;).
  
  I do believe there is a small business potential though, maybe training on nukes module development/usage in the near future.
  
  marcf
• the real question behind the article?!
  2003-06-20 04:33:32  anonymous2 [View]
  
  
  But the most dangerous thread to Open Source is to have too many projects dealing with the same issue. Adding a new OOS CMS is not bringing anyone forward. Think about having 10 operating systems instead of one Linux? Then Linux or any other wouldn't have the success it has today.
  
  If someone wants to push OOS projects then concentrate on one project, in terms of CMS choose one PHP and one Java based. Then you will have the same success or eaven greater which the Phyton project had. The nightmare of OOS is in this days that the projects will fight each other instead of beeing an alternative to commercial products. This fight is based on emotions and personal feelings and not on business values.
  
  At the end of the day just one thing has gained success: "beeing focused!"
• the real question behind the article?!
  2003-06-23 06:53:27  anonymous2 [View]
  
  
  if we are talking about business, the basis of OSS sales is brand and URL. By pushing our own branded solution to the CMS mess we hope to drive some business as well. Building brand is business 101, redhat tries this as well, only they just "rebrand" at least we try to build and brand.
  marcf
• the real question behind the article?!
  2003-06-20 19:37:50  anonymous2 [View]
  
  
  The bulk of OSS projects aren't concerned with 'business values' in the first place - it's primarily ego.
• the real question behind the article?!
  2003-06-24 14:11:58  anonymous2 [View]
  
  
  So the next question will be: "Do we want a successfull OOS project?" or are we satisfied with our ego in the first place?
  
  Myself is focused on an enterprise application, build in a OSS model. At the moment there are two application categories that could reach a state of maturity: content management and databases.
  
  Databases are taking care by SAP and the MySQL group by giving the SAPDB source code and a $29 Mio founding by a VC.
  
  CMS are likely unclear. The community can wait to the next white knight, like SAP or IBM/Oracle for Linux etc., or the community can decide by their own.
  
  If Jboss group will take over this position, then we have to wait for the future. If this OOS thing is realy driven by ego - then there will be no success.
  
  At the end of the day money will be in services and enhancement products on a "kernel". But no CIO will invest on a 1 to 250 chance (if there are about250 OOS CMS projects). CIOs did bet on a 1 to 3 chance when it came to Appservers and invested in JBoss instead of BEA, IBM or Oracle. If this is about making money, then everybody has to change the chances for the guys with the money. This means: "Reduce the choice"
  
  thomas