This content has been marked as final. Show 1 reply
- Does Nukes require the use of a full J2EE server like JBoss? Or can it be used with just Tomcat? (Perhaps a dumb question since it was developed by JBoss. But it never hurts to ask. :-) )
Nukes requires JBoss3.2.3, period. Dont think about trying w another version of JBoss, or another J2EE app server, or just Tomcat alone.
- Is it necessary to understand J2EE/EJB programming in order to use Nukes
- Is it necessary to understand J2EE/EJB programming in order to use Nukes effectively?
Or can I get by with just knowledge of JSP/Servlets?
JSP/Servlet knowledge is largely irrelevant, unless and until you develop your own module(s) and choose JSP for front end (or become a hardcore contributor and get deep into the Nukes servlet)
- Can Nukes be used with Apache Struts? Would using them together require rewriting / modifying Nukes code?
Well, yes, kindof, if you study Sherman's wikis and forum posts about using JSPs with Nukes, and then do more integ/coding work... but planning on jumping from static web pages to Struts probably indicates that you are confused on your strategy. You should get really familiar with the existing Nukes modules at a user and admin level, before you even think about developing custom code. Do as much as you can just by configuring Nukes modules while logged-in as admin. Only after that, consider what modules should be modified to accomplish what else you want to do.
- How difficult / easy is JBoss administration? Does using Nukes require a knowledgable JBoss administrator? Or is it pretty much maintenance free after installation? (We are administering our own web server.)
Just using nukes requires no programming at all; it's developing modules & blocks & themes (and soon, portlets) that requires programming.
Administering nukes requires no programming... and vanilla usage doesn't require knowing much about JBoss even... but the more you know about the world of development and deployment, the better off you are.
Any portal or CMS requires much more admin maint work than a simple static webserver does, for the simple reason that users not only can receive content, but also can contribute content. You have to manage at least who is allowed to do what, and what to do with growing databases of contributed content.
In short, Nukes looks attractive but I am a little leery of having to jump straight into administering (and possibly programming) a full blown J2EE server.
Nolan Bushnell, the founder of Atari and father of videogaming famously replied to the question "What are the characteristics of a good game?" with these words: "Easy to learn, difficult to master." JBoss is the best game in town, for exactly this reason. JBoss is much easier to setup than Nukes... grab the binary, unpack, cd to the bin directory and type run. But it's impossible to master, and getting harder; not even the core developers can know every nook and cranny anymore. To be very effective in developing for Nukes at the module (application) level, you only have to understand ~ 5-10% of JBoss; to just administer Nukes and customize some modules, probably only 1% of JBoss.
Is it worth it?
- Can anyone offer a comparison with OpenCMS or any other open source Java-based CMS?
But nobody who can has yet gotten around to spending the time to do it.
So now it's your job. :-)
Sharing answers to at least as many questions as you ask is good karma. ;-)
Do some research, get a live Nukes up and runnking, work with it, and contribute back your comparison (via Forum or Wiki).
Next step: go to
and do what it says there; then play and get familiar; then share what you learn.