Frustrating! What IS JBoss/Nukes?

[gary_kephart]

{vent}
You know, as astounding as it may seem, there are people out there who've never used PHP, much less Nukes. And barely know about CMS. I'm a Java programmer, and could take the time to research all of that stuff and I would understand it, but that would take a LOT of time, which I don't have.
There's not a damned thing on the web site that actually explains what JBoss Nukes really does! All it does is reference other projects. What IS the actually functionality? Maybe there's some links hidden around somewhere, but I didn't find them. And those links should NOT be hidden! Those should be the first thing the user sees when they come to the site. Big friggin neon blinking links!
Here's my problem. I've got a couple of thousand HTML files that I'm translating to XML files. I want to keep the XML files so that I can create a downloadable version of the site by zipping up the files. So, a database is right out. When I get the site running, I want a web interface so that my content writers can log in and change the files directly. And I want the Wiki type of linking inside of the XML files so that the content writers don't have to remember the URLs of the files they're referencing. Can JBoss Nukes do this?
I don't f'ing know! There's nothing that I can find on this site that can help me find out! How does it compare to Apache Cocoon, or perhaps JSPWiki? Again, I don't know!
ARRRRRGGGGH!
{/vent}

[sgwood]

JBoss Nukes is a Java implementation of PHP Nukes. It provides a framework to host multiple applications/modules, with a common login, security, look and feel, deployment and other services. There are a number of standard JBoss Nukes modules - forums, news, wiki (based on JSPWiki) etc - that are available, or you can roll your own.

The next full version of this idea is a full portal implementtion (JSR168), with a beta Real Soon Now. The Nukes framework will be left behind, but the transition for Nukes themes and modules is hopefully going to be relatively easy.


Sherman

[gary_kephart]

-sigh- Point proven. You just defined JBoss Nukes in terms of PHP Nukes, which I just got through telling you I don't know anything about. Then, you add in other terms without explaining them: "applications" and "modules". Or explaining the differences between them. As far as I'm concerned, an application is a J2EE EAR file or JAR file than has a main() in it.

Here's your homework: create a JBoss Nukes page without referring to/hinting at/mentioning PHP Nukes. Tell us the feature list from a user's point of view, not a developer's point of view. Explain your special terms.

[theute]

Before yelling, did you even look at the project page or datasheet ?

http://www.jboss.com/products/nukesjboss

If you don't know anything about Nukes, you should consider looking at JBoss Portal as it is a step further. (And Nukes development is stopped in favor of JBoss Portal).

http://www.jboss.com/products/jbossportal

[gary_kephart]

Before yelling, did you even look at the project page or datasheet ?

http://www.jboss.com/products/nukesjboss

Yes, I did. They seem to have minimal information.

If you don't know anything about Nukes, you should consider looking at JBoss Portal as it is a step further. (And Nukes development is stopped in favor of JBoss Portal).

http://www.jboss.com/products/jbossportal

Yeah, I saw that, too, but didn't delve into it that much. I was thinking that Nukes would be smaller scope and therefore easier to grok.

Like I said, I was venting (and feel much better now!) so don't take what I said too literally or seriously. It's just that I didn't find anything to answer the question from my first post. Does JBoss Nukes solve my problem? I'm not sure.