State of the project

Nukes 2 is a compliant JSR-168 implementation.

• Roadmap

• Architecture

-

How to get Nukes 2 working

Obtain Nukes

Get it from the CVS : cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co nukes-2.0

Environment setup

Set the environment variable JBOSS_HOME to a working JBoss installation. Nukes 2 has less dependencies on JBossAS internal classes, it compiles with JBoss-3.2.3 and JBoss-4.0.0RC1 and it works with Tomcat 4 and Tomcat 5.

Build the server

cd build sh build.sh

That will chain the build of the different modules and produces several jar files. The interesting files are :

• portlet/output/lib/portlet.sar : deploys a working portlet implementation that deploys war files containing portlets. The layout is very basic and it is not intended to be a portal by itself. You can deploy some test portlets from Nukes (portlet/output/lib/test.war). You can try also the examples available from Sun. Just put them in the deploy directory after you have dropped the portlet.sar file. Access is done with that url

• core/output/lib/nukes-core.sar : this is the portal embryon which reuse the portlet implementation and has a better default layout, this is the current Work In Progress. You can deploy it likewise for portlet.sar. If you deploy a .war file containing portlet you must before modify this file to include two files that will tell the portal how to build instances of portlet. In the portlet.sar example this is not required because there is an automatic process that creates for each portlet an instance of it. We plan to make the dynamic configuration as well, so you can deploy a portlet war file and then create instances at runtime. Access is done with that url

• core/output/lib/nukes-samples.war : this is intended to be deployed with nukes-core.sar, it contains the static XML files that dictates the portlet instance creation. In this case, each portlet will be created once and for each instance you will see two windows.