Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
Java Programming

Open Source CMS Solutions Based on Java? 153

Posted by Cliff from the coffee-blogs dept.
namityadav asks: "I've been looking for an open source Content Management System (CMS) which is widely used / supported, and has features like web-logging, online communities, RSS feeds, forums, polls, calendars, website searching, and so on. The most obvious choices are Drupal (I've played with it in the past) and Joomla, however both of them are PHP based. Since I am a Java developer, I wanted to find something based on Java. To my surprise, I could find some very weak Java based alternatives to Drupal, like MMBase, OpenCMS and Magnolia. Why is it that there are so many PHP based open source CMS which are hugely successful (Drupal is used by The Onion, Spread Firefox, and more), but there is not even one comparable solution based on Java?"
This discussion has been archived. No new comments can be posted.

Open Source CMS Solutions Based on Java? More

Open Source CMS Solutions Based on Java?

Comments Filter:
  • ... Make something from scratch? I can understand the usefulness of something done for you with documentation (though the poster said open source so we can somewhat scratch the documentation part out). But with CMS, I would think it'd be much more efficient to build the system to your needs, as opposed to tweaking something already out there.

    • Re: (Score:3, Insightful)

      by FreeKill ( 1020271 )
      Of course you're right, but creating a system like Drupal or Joomla yourself is not exactly a small undertaking. These systems have huge user bases and hundreds of tools built to make it easy to setup a site thats perfect for your needs. To write it yourself, you would have to implement a lost of features and security just as a start, and that's not even mentioning the robust search engine optimization, templating engines and page caching.

    • The Java Trap (Score:3, Insightful)

      by byolinux ( 535260 ) *
      I'll bet the fact that Java has only just become free software, is the reason there are not many Java based free software CMS's

      • Re:The Java Trap (Score:4, Insightful)

        by GuyWithLag ( 621929 ) on Sunday December 10, 2006 @02:57AM (#17182204)
        No. For better or worse, PHP is easier to administer from an ISPs perspective - it integrates directly in the web server, you just deal with files and possibly their permisssions. With java you have to have a separate server (that is relatively heavyweight) for the various components, you need to map URLs to that server, and the users can't update their apps by themselves, the ISP has to do it.

        Java servlets have been designed for the enterprise, and it shows....
        • I could argue this, heavily.
          Installing JBoss involves unzipping a file, and the URL mapping is taken care of in your web.xml file. All you really need to do is upload a war (or ear) file into a directory, and you've just deployed a web application.
          Yes, there is a touch of configuration to get a web server, like apache, to connect to JBoss, but its about as difficult as getting something like mod_perl running...
  • It's not that hard. Your problem is the limited parameters you've set.
    • You're suggesting PHP over Java? Good lord.
      • Yes. If something works, then use it. Complaining its not using your favourite language/platform/OS is useless.

        PHP, Perl, Java - who cares what it's made of if it gets the job done past a minimum standard.

        • Re:learn PHP (Score:4, Insightful)

          by Schraegstrichpunkt ( 931443 ) on Saturday December 09, 2006 @08:05PM (#17179332) Homepage

          Yes. If something works, then use it.

          I write PHP code for a living, and that's exactly my problem with PHP: It doesn't work. At least, not very well.

          • you know the proverb about bad workmen and their tools, don't you? :-)

            Far be it for me (a C++ dev) to praise a scripting language, but a lot of PHP is out there, and a lot of it achieves its tasks well. As for the rest, perhaps you're asking too much of what of it, trying to make it do something its not really designed for, or perhaps the comment above is more insightful than funny.
            • That proverb is completely bullshit. I'm sorry, but there is such a thing as "the right tool for the job", and using the wrong tool makes the job harder or the result worse. I know you had a smiley after your statement, so were probably not totally serious, but I agree with the GP that some tools are just wrong for the job, and specifically PHP is wrong for the job. Having coded in PHP and Java, I would never recommend PHP. I'd basically recommend almost anything else. PHP is designed for quick and dir

              • I agree with everything except your mysql_real_escape example, and that's only because mysql_real_escape comes from the MySQL client library. Of course, other languages actually bother to abstract their database libraries in some sort of standard database API, instead of just providing thin wrappers around the individual C libraries.

                "It's too much work to get things right" is exactly right. Need evidence? Look at the PHP.net "User Contributed Notes", and you'll find dozens of errors.

        • But things written in PHP, Perl, and Java tend to only get the job done to a minimum standard.
      • Do not make the error of comparing languages instead of solutions. For example if you deploy (even as backup) to a virtual server leased somewhere, ram usage is a problem. So ruby/python/perl/php/lua solutions beat java ones.

        On the other hand a java solution might be better than a ruby/python.... ones even if most scripting languages (except php) are more elegant because java frameworks addressed some issues that others still lack.

  • Poor Java Support with Webhosts (Score:4, Insightful)

    by FreeKill ( 1020271 ) on Saturday December 09, 2006 @06:50PM (#17178590) Homepage
    I think the reason you don't see many Open Source Java CMS tools is due to fairly weak Java support with most Web hosting providers. Take a look at the available webhosts, and very few over support for Servlets/JSP. I would think, on average, the most common user of a CMS system would be someone wanting to setup a small to medium website that won't require too much customization outside of the standard package. Of course, the systems available are powerful (Drupal, Plone, Joomla, Nuke), but for the most part the people using them don't need the majority of the powerful customization tools. These are also the same people who would be using Web hosting packages, and not setting up their own servers. Therefore, you have to write it in a language that is almost universally supported by web hosting providers, like PHP.

    • Re: (Score:3, Interesting)

      by Shados ( 741919 )
      I doubt thats the issue, since there are quite a bunch of .NET CMS solutions, which have the same issue (free providers never support it, you need to shell out, like for J2EE)

      • Re: (Score:2, Insightful)

        by FreeKill ( 1020271 )
        Most web hosts offer 2 packages. A windows server with .NET support and a Linux server with Apache and PHP/CGI support. Since Java support generally requires customization of Apache at the least, but most likely an alternative web server like Tomcat, the hosting providers don't even bother.

    • Re:Poor Java Support with Webhosts (Score:5, Insightful)

      by phoenix.bam! ( 642635 ) on Saturday December 09, 2006 @07:32PM (#17179068)
      I don't think that's it at all. I think it's that it takes less than 10 minutes to have a presentable PHP based website. Just talking hello world here.

      Trying to do the same thing with JSP? The overhead for configuration and security layers is just awful. Not to mention the documentation is atrocious. To find a step by step guide for getting tomcat set up as you need is painful at best and impossible at worst. Deploying webapps is a huge pain and the amount of xml you have to right to configure your webapp is daunting.

      That is why php is chosen. Someone could start small site, displaying "Hello World!" from a database for instance, and then the CMS can grow and mature. Java on the other hand takes a huge commitment to just get the program to displaying "Hello World"! from a database.

      • Re: (Score:3, Informative)

        by doktorjayd ( 469473 )
        web hosts may provide poor support, but claiming its hard to get tomcat and apache to work together is BS.

        setting up tomcat and apache is dead simple.

        $> sudo yum install tomcat5 tomcat5-webapps tomcat5-admin-webapps httpd

        add proxy mapping for httpd -> tomcat on the ajp protocol in httpd.conf:

        [ ProxyPass / ajp://localhost:8009 with httpd 2.2,
        mod_jk for earlier httpd ]

        add a html file to $TOMCAT_HOME/webapps/ROOT/, name it blah.jsp

        browse to your http://webserver/blah.jsp [webserver]

        the

      • Re: (Score:3, Informative)

        by Cyberax ( 705495 )
        Here's my guide:
        1) Go to http://tomcat.apache.org/download-55.cgi [apache.org] and select your distribution. I assume you are running Windows, so download binary installer.
        2) Run installer and click 'Next' until finished.
        3) There's no step 3).

        You can get Tomcat up and running in minutes and writing JSP pages is very similar to PHP.
        • Yeah, that's the easy part. The hard part is connecting to a database and writing queries (combining strings with variables in java is a pain compared to php).

          I'm not saying PHP is better than JSP for the purpose of CMS. I was answer why there are almost exclusively CMSs written in PHP. Ease of setup and connection to a backend is the reason.

          And I'm talking about connecting to an external database (The entire point of writing the CMS in the first place)
          Taking your example would be a great way of getting

          • Re: (Score:2)

            by lewp ( 95638 )

            Yeah, that's the easy part. The hard part is connecting to a database

            No, that's pretty easy too.

            and writing queries (combining strings with variables in java is a pain compared to php).

            If you're using PreparedStatements in Java, or one of the many PHP database abstractions (PDO, ADODB, PEAR::DB) instead of interpolating variables directly into query strings (tsk, tsk) then it's about the same. Likewise if you just use a higher level ORM library.

            As a person who makes a living writing PHP, getting sta

      • Shut your fud spreading mouth. A JSP to do hello world on tomcat is easy as pie. You don't need to modify any xml, you just drop an html file that says hello world into the right directory.

        The step by step guide for setting up tomcat IS ON THE FRONT FREAKING PAGE.

        I swear to god if I see another CMS that has "grown and matured" from a hello world app I'll shit in my hat and wear it. I am sick of unplanned, barely good enough, ad hoc crap.

        I don't know who I'm more pissed at regarding this post. You for sp

        • Re: (Score:2)

          by XO ( 250276 )
          All CMSs are infinitely more complex than they should be.

          Every one that I've had the utter misfortune of using, was incredibly difficult to learn how to either use or modify or both, and it would've taken less time to just build the whole damn thing statically than to actually figure out how to get the CMS to do what the people paying me to make it do wanted. The only time it's EVER been easier for me to use a CMS, was when someone paid me to setup a particular CMS (e107) and wanted to use exactly one of t
      • It's been said elsewhere, but bears repeating since the parent post has been moderated 'insightful' (snerk)

        The problem isn't "hello, world!", it's maintaining the site after it's been live for awhile. JSP can use embedded scriptlets just like PHP, but unlike the latter we learned years ago how painful that is during later development and maintainance. So now it's standard practice to use MVC. It's a modest amount of extra work on the front end, but that's more than offset when (not if) we need to make su

    • Re: (Score:3, Insightful)

      by DragonWriter ( 970822 )
      I think the reason you don't see many Open Source Java CMS tools is due to fairly weak Java support with most Web hosting providers.
      Is it really true that there aren't many Open Source Java CMS tools? I mean the list here [java-source.net] suggest otherwise, though I'm not familiar enough with the tools to know if they are any good...

  • That's an easy one (Score:3, Insightful)

    by Bluesman ( 104513 ) on Saturday December 09, 2006 @06:58PM (#17178686) Homepage
    >Why is it that there are so many PHP based open source CMS which are hugely successful
    >(Drupal is used by The Onion, Spread Firefox, and more), but there is
    >not even one comparable solution based on Java?"

    Maybe because Java offers no advantage over writing a system in PHP, which obviously is up to the task based on the successful projects you mention?

    Seriously, why would you want to use Java when you don't have to? It's like asking why there is no web browser written in assembly language. Higher level languages get the job done with minimal aggravation and perform well enough that they're not the bottleneck.

    PHP was tailor-made for this sort of thing, Java...wasn't.

    • Re: (Score:2)

      by Shados ( 741919 )

      Maybe because Java offers no advantage over writing a system in PHP, which obviously is up to the task based on the successful projects you mention?

      Oh boy...I died a little inside reading that...

      PHP was tailor-made for this sort of thing, Java...wasn't. Actualy, J2EE has already half the job done built in... There just doesn't have all that much done around it in the open source world (in the commercial world its another story). Why? Probably only because the open source community around PHP is bigger

    • Re: (Score:3, Insightful)

      by M. Baranczak ( 726671 )
      Funny you should mention that... My job involves writing code for Java-based content management systems. It's proprietary, so it doesn't meet the stated requirements, but it works just fine. I can think of quite a few things that work better in Java than in PHP, but I'm not interested in starting another boring flamewar. And besides, you're right about one thing: the language should be one of the less important considerations here. If there are PHP systems that do what you need, go ahead and use them. If th

    • Re:That's an easy one (Score:4, Interesting)

      by imroy ( 755 ) <imroykun@gmail.com> on Sunday December 10, 2006 @02:17AM (#17181986) Homepage Journal
      PHP was tailor-made for this sort of thing

      No, it wasn't. PHP was made for writing quick little bits of code in Personal Home Pages. And for that it was perfectly reasonable. Unfortunately it became very popular (probably because it was easy to install on Windows) and since then it has been extended and had all sorts of modules added with little or no change to the core language. Many people are now discovering just how bad it is to use PHP on large projects [ukuug.org]. It's just a mess.

      • there are zillions of apps written in php for ecommerce, security, collaboration, publishing, gaming, parsing, collecting data, database management, and innumerable stuff, crap, sh*t that if i wanted to name fields and examples, 6 months of my life would only be enough to complete them.

        not nifty arguments, deductions, logicalisations, semantics or can define something is good or not, nor your or some other people's views as 'expert programmers'. nor what something was made for at the start does.

        what d
        • How *dare* you compare PHP with a C-47/DC3?

          If the DC3 was anything like PHP, it would be permanently grounded.

          There's no programming language worthy of comparison with the DC3. Not even LISP.

          -Lasse

          • Re: (Score:2, Flamebait)

            by unity100 ( 970058 )
            it is easily comparable. c47s themselves were also grounded when they were external disturbances - flak fire, lack of fuel and so on - where they did service in the war and after the war. and due to their widespread use in high numbers, they have faced these issues more than other airplane types, just like php does in programming languages.

    • Hang on there a sec, bub. (Score:4, Insightful)

      by RedDirt ( 3122 ) * on Sunday December 10, 2006 @03:54AM (#17182476) Homepage
      (This is gonna hose my karma, but it's something I feel strongly about so damn the torpedoes, full speed ahead! [nps.gov])

      There is a major benefit that Java brings to the table versus PHP and that is security. My inside voice says that the only way to secure a PHP webapp is to delete it. My outside voice says that if you've just got to have a particular PHP package, then fine - that particular PHP package you can have, along with an SSL cert, a site-wide ACL and off-machine logging so that *WHEN* the app gets hacked, you know who to go after. :P

      Some folks don't think that PHP has anything intrinsically wrong with it, that PHP is just trying hard to be an incredibly helpful language, that it's not a bad language - it's just drawn that way. I don't think so. It's got a history of stuff like: "Oh, you provided some URL parameters? Allow me to convert those into variables automagically!" (Yes, yes - this has since been changed but it was around for a long, long time and is still available if you set the proper config variable) "You want to talk to a database? Please, feed me a string and I'll do whatever you want me to do. In fact, if you give me several things to do, I'll do them all!" (Hooray for SQL injection) And on it goes.

      I'm sure a case could be made that schlock code written in any language can be abused - but in the typical Java (or Perl, or Ruby, or Python, or some other non-PHP language of your choice) framework you've got to work a lot harder to create exploitable things. PHP is entirely too damn easy to be bitten by unforeseen circumstances - witness the same vulnerabilities being lovingly replicated over and over and over in lots of different projects [google.com].

      In closing, yes it takes more up-front effort to bang out a simple CRUD [wikipedia.org] app in Java versus what the average tutorial or manual would tell you to do in PHP. But the Java version isn't vulnerable while the PHP version is and will require a net greater expenditure of effort to understand and fix the problem. And that's not talking about the energy burned up by the poor shmucks running the code and having to clean up and rebuild after the app gets owned. (No, I'm not still bitter phpBB, Gallery, Wordpress and PHP-Nuke. Not at all. I don't even miss my data anymore. Nor do I regret having to deal with my account being used to attack other machines. Not one bit.)

      • Re: (Score:2)

        by Tinfoil ( 109794 ) *
        First, I am not a programmer but I do play one on TV. Second, as someone who just had his PHPNuke site (running since sometime in late 2000) attacked, crippled and corupted data, I can certainly understand the bitterness. It was a good motivation to finally move away from phpnuke.

        I do, however, believe that some quality applications can, and are, done up in PHP. The problem with PHP is that it is such an easy and (too) flexible language that those who don't necessarily understand the finer concepts & pr

        • Re: (Score:2)

          by RedDirt ( 3122 ) *
          > as someone who just had his PHPNuke site (running since sometime in late 2000) attacked, crippled and corupted data, I can certainly understand the bitterness.

          My condolences. Nobody should have to suffer that sort of thing. :(

          > I do, however, believe that some quality applications can, and are, done up in PHP.

          Oh yes, I totally agree. That's what gives me the love-hate relationship I have with the language. Recent releases of Wordpress are so darn compelling because of the oodles of themes and plu
    • I have trouble defending Java here, but I think PHP is actually worse. I don't know how, but it is.

      The only reason for writing anything in PHP is because "worse is better". You write in PHP because everyone thinks (server side software == PHP), and every hosting provider has it... Everyone seems to think PHP is the P in LAMP...

      But really, everything "good" that PHP has promotes bad design. Embedding in HTML: Bad design, please separate code from content. Variables don't have to be declared? Great, now you c
  • Never used it personally but saw references multiple times. You might want to read more about it HERE [java.net].

  • They do exist (Score:3, Informative)

    by Jagungal ( 36053 ) on Saturday December 09, 2006 @07:17PM (#17178928)
    There are a few out there. Alfresco http://www.alfresco.com/ [alfresco.com] looks the most interesting.

    I agree though, doing a CMS in PHP is such a kludge, it would be good if there were some good solid java alternatives that could match the ease of use of something like Joomla or Drupal. Something using of the of popular frameworks such as Tapestry would be good as well.

    As for hosting, there are plenty of VPS services out there that are quite cheap and host server based java applications just fine.

  • Few ideas... (Score:3, Informative)

    by toxygen01 ( 901511 ) on Saturday December 09, 2006 @07:19PM (#17178970) Journal
    Obviously one would check http://www.opencms.org/ [opencms.org]

    OpenCms is based on Java and XML technology. Therefore it fits perfectly into almost any existing modern IT infrastructure. OpenCms runs in a "full open source" environment (e.g. Linux, Apache, Tomcat, MySQL) as well as on commercial components (e.g. Windows NT, IIS, BEA Weblogic, Oracle DB).

    or you can check other Open Source CMS on wikipedia. Comparison of content management system [wikipedia.org]
  • What made you decide those alternatives were weak? We've used Magnolia to deliver a site that got 4 hits a second on average, it certainly wasn't weak. Did you actually look at the product, or just look at the website and not find something shiny?

    • Re: (Score:1)

      by ximenes ( 10 )
      Perhaps the submitter saw that Magnolia has a .info domain and immediately presumed it was worthless. I know that I instantly disregard anything from a company with .info/.biz.

      For instance I never would have bought from Papercut (papercut.biz), it took one of my co-workers to find out that it was actually a sweet product.
  • From their site:
    Daisy is a comprehensive content management application framework, consisting of a standalone repository server accessible through HTTP/XML (using the ReST style of WebServices) and/or a high-level (remote) Java API, and an extensive browsing and editing DaisyWiki application running inside Apache Cocoon. Daisy is licensed under the commercially-friendly Apache License 2.0. Outerthought provides commercial services around Daisy. More marketing talk can be obtained from their website. This

  • Magnolia (Score:3, Interesting)

    by paugq ( 443696 ) <pgquiles&elpauer,org> on Saturday December 09, 2006 @07:46PM (#17179186) Homepage

    Magnolia [magnolia.info] is a really nice and powerful CMS in Java, with a BSD license. I have been involved in several serious projects (>300 hits/second) using Magnolia and it has always performed very well. Of course, we tuned the JVM, Tomcat, the Linux kernel and almost everything you could ever imagine.

    After evaluation, if you decide Magnolia is the CMS you are going to use, I advise to take the official training. It's worth the price.

  • SAKAI [sakaiproject.org] is a CMS for classrooms and academic workgroups. It's Java. If that's what you need, take a look.

    Having said that, I agree with the posters who say that it's easier to program web apps in PHP (or any scripting language), and that Java isn't well-supported by webhosts.
  • This is a shameless plug, but take a look at dotCMS http://www.dotcms.org/ [dotcms.org]. dotCMS is a Java based CMS that is feature rich and easy to pick up. It is entirely web based - you can create templates, dynamic content and custom content structures within its administrative portal. It is database agnostic, offers in line editing, clustering, easy to use macros, AJAX based file browser, fine-grained permissioning and privileges, content versioning, completely separates content from site structure and on and on

  • Dear slashdot, (Score:5, Funny)

    by Klowner ( 145731 ) on Saturday December 09, 2006 @08:51PM (#17179698) Homepage
    I'm a construction worker and the other day I was thinking about baking a cake. As it turns out, I'm having a heck of a time finding a cake-batter mixing machine that runs on diesel.
    • see subject

    • Re: (Score:2)

      by LWATCDR ( 28044 )
      Actually java isn't a bad solution for a CMS. The big performance issues with java applications are load time and the speed of Swing. Most problems with Swing are just bad programming. For a server you don't need to worry about load time since it is always running.
      The real issue comes down to hosting. Every nickel and dime web hosting service has PHP and MySql so the most popular CMSs will tend to use PHP and MySQL. It is just a case of the lowest common denominator not the best technical solution.
      You will

  • Apache Lenya (Score:2, Informative)

    by dos ( 415274 )

    I have not had a chance to use it past the online demo*, but you might want to check out Apache Lenya [apache.org]

    * A contract webmonkey proposed switching to Lenya halfway through a project. As much as I like F/OSS, I decided I'd rather have his existing VB/ASP mess working "on time" (only months late) rather than a nifty Lenya setup ready sometime after I would be fired for still not having delivered the new website...

  • Isn't JBoss-Nukes based on, um, JBoss?
  • Not only is it not open source, it's unbelievably expensive...40k per processor for the required database backend, plus $40k for Oracle's application server (oc4j) and then if I remember correctly Portal (the actual CMS product) is multiple thousands (and always per processor, and dual cores count as 1.5 processors).

    That said, Portal is a really really nice product and probably the best example of a Java-based CMS that I've seen. I've compared it to a souped up Plone or Mambo. I set up a demo site for my co

  • Comment removed (Score:3, Informative)

    by account_deleted ( 4530225 ) on Sunday December 10, 2006 @12:02AM (#17181158)
    Comment removed based on user account deletion
  • You might want to check out Lenya [apache.org], which is based on the Apache Cocoon project. I don't know mature and full-featured it is though. More generally speaking, Apache has a lot of Java-based projects that can be used toward building a CMS, so if you did want to write your own, you could do worse than start on top of some Apache framework.

  • good question (Score:5, Insightful)

    by jilles ( 20976 ) on Sunday December 10, 2006 @03:20AM (#17182304) Homepage
    I am a Java developer and I have worked for a commercial CMS vendor. Essentially, the low end of the market is dominated by php for obvious reasons: it's easy to get started and basically any hosting will do since it will run php out of the box. Also that stuff is pretty good: I'm perfectly happy with wordpress for my low end needs.

    On the other hand with Java there are no cheap hosting solutions. Basically it requires a a dedicated server solution which will set you back 50-100 $ per month minimum. There are shared hosting facilities but they are still more expensive and don't really give you enough control. People with low end needs won't even consider that as an option, and they shouldn't.

    However, there's also such a thing as the high end of the market. Basically php is just one of the many options there and as far as I can see it far from dominates that market. A lot of interesting things are happening in the Java enterprise scene: there is standardization of content repositories (JSR 170) with several commercial and OSS implementations available; there is the portlet standard, which is basically the backbone of many commercial portal servers; there are lots of options for implementing web UI stuff; there is adoption of the cool rails stuff with both groovy and jruby on rails being worked on; etc. Essentially Java is one gigantic toolkit for building web applications now.

    Bottom line is that if you are expecting to spend a few thousand dollars on hosting (yearly) and have a budget of say 20K+ for building the web site, you are in the high end of the market. You will want some guarantees about your site not collapsing when a few million people decide to drop by; you'll probably have some old content to migrate and some non trivial functionality that you'd like to have. Chances are that you'll end up using Java. Or rather, chances are that you decide not to reinvent the wheel and use the services of some professional CMS companies.

  • Sorry, but your out of luck. If there is anything where PHP has outrun Java by nearly a decade, then it's the CMS game. PHP CMSes are so mature you don't even need to do any programming anymore to have a reasonably configurable setup. You might just join a project and work on the Java Clients they are starting to build. Joomla and Typo3 both using Java for exactly that. THe last thing I remember that was up to date with PHP was the Cocoon framework and that was like 7 years ago or so. Time has passed since

  • What are you talking about? (Score:4, Informative)

    by bigHairyDog ( 686475 ) on Sunday December 10, 2006 @09:47AM (#17183774)
    There are plenty of good open source CMS systems in Java.

    At the bank I work at we use OpenCMS [opencms.org].

    Magnolia Community Edition [magnolia.info] is probably better.

    Apache Lenya [apache.org] is another CMS written by a well known group but I can't vouch for it

    JBoss Nukes [onjava.com] is poorly documented but written by JBoss so should be good.
  • The Java CMSes you named are fine. The problem is that you aren't looking for a CMS. A CMS is just a platform for publishing static articles. What you want is an interactive community site. Things like Roller are more along the lines of what you're asking for.

  • Java's focus has always been on enterprise software development. Consider this quote from the Java EE 5 Tutorial [sun.com] on “Development Roles”:

    After software is purchased and installed, Java EE components can be developed by application component providers, assembled by application assemblers, and deployed by application deployers.

    Also consider the Java EE Architecture Overview diagram [sun.com] from the same document.

    This “tutorial” is aimed at enterprise people with time and money to spend

  • I see a lot of people who feel compelled to praise java, put it over other stuff for such or such reasons.

    what i see is that some of this inclination stems from the fact that all people have the need to be 'different' in them, and all of us manifest this in this way or another. some choose 'breaking off from the crowd in programming languages', and pick a language to be enthusiast of and praise it. some choose java, some asp some another.

    this is just an unfruitful thing to do. differentiation of self
  • I manage a Stellent Content Server where I work, and it's a pretty decent app. Not cheap from what I hear though.

    It's the only Java application I've tried that hasn't been problematic.

    Like everything else, it has some of what you want, some you don't.

    Con:
    1) It's not open source
    2) It's not cheap

    Pro:
    1) The training courses are good
    2) It's fairly well documented, once you get the basic concepts of the design understood, which are not as well documented.
    3) It's very modular, while it's not open source, you can

Slashdot Top Deals

It is easier to write an incorrect program than understand a correct one.

Close