This version 0.6 of volunteerbase contains fixes and minor improvements, the project is now in a stable phase. The Wiki user guide has a comprehensive coverage of all the functions. The package has been upgraded to Tomcat 6.0 and the distribution can use Java 5.0 or 6.0.

With the release 0.5, the project is now covering the initial specifications. The next big steps will be the functional tests, acceptance test and the documentation. The test by the new SPW Australia team should add some new ideas and further evolutions.

After a long iteration, finally the 0.4 is published.

The biggest challenge was to include a reporting capability without using heavy weight framework. After some issues with JPA and iReport, I have decided to choose a simpler and well known solution with Apache Fop. The idea of xsl-format looks good. It uses the css style and is able to generate many output (html, pdf, png, RTF etc...). It's really handful to separate the content of the presentation and it gives the possibility to customize easily the report. However it's not very efficient to create rapid report with complex structure. Associated with a lack of tools and the future css3, I not sure of the future of this product.

The release contains also a bunch of bug fixes.

The new function is the volunteer contribution management. The features are:

• A schedule to define the payment plan for a year, depending of the month of selection
• Book keeping of the volunteer contributions

The next feature in 0.5 will be an individual report to give a situation of the volunteer contributions.

This release is mainly focused on usability improvements. The iterations will deliver alternatively new functions and defect fixes. The goal is to move from a prototype (release 0.1) to a production ready software with all the functions required in version 1.0.

This release includes work from Sean Melody, a new active and motivated contributor.

This blog follow the previous one "Secured EJB 3.0 Web Start Application Client".

Now, we want to access the same EJB without Java Web Start and we want to provide a user/login programmatically. We can use a class provided with GlassFish : ProgrammaticLogin.

I assume you have done and deployed the previous project. The client part of the previous Enterprise Application is not necessary, you can skip it if you have not already done the demo. We will create a totally independent project.

Create the project

Create a new project, select Java, Projects -> Java Application and click Next. Name the project ProgrammaticLogin and click finish.

Add the libraries

We need few libraries from Glassfish in order to run the project. Right click on Libraries -> Add JAR/Folder, and add the following jar files from the <GLASSFISH_INSTALL_DIR>/lib directory of your GlassFish serveur :  appserv-rt.jar, j2ee.jar, appserv-ext.jar, appserv-admin.jar. These jar contain all you need to run the client.

Right click again on Libraries -> Add Project and add the EJB project Login-ejb.

Login code

You can now open the Main class and input the following code inside the main method:

ProgrammaticLogin pm = new ProgrammaticLogin();
pm.login("demo", "demo"); //user and password of a user mapped to admin role

InitialContext ctx;
try {
    ctx = new InitialContext();
    Object ref = ctx.lookup("demo.CalculatorRemote");
    CalculatorRemote calc = (CalculatorRemote) PortableRemoteObject.narrow(ref,CalculatorRemote.class);
    javax.swing.JOptionPane.showMessageDialog(null, "2 + 2 = " + calc.add(2, 2));
    javax.swing.JOptionPane.showMessageDialog(null, calc.hello("Mr Demo"));
} catch (Exception ex) {
    ex.printStackTrace();
}

Resolve the imports (Ctrl+Maj+F with NB 5, Ctrl+Maj+I with NB 6).

Run the demo

Start the application server.

Before running the client, we must set the configuration in order to obtain the correct login module. We must give the JAAS config file.

Right click on the project, select Properties -> Run.

In VM Options, add : -Djava.security.auth.login.config=D:/JavaServers/glassfish-v2-b53/lib/appclient/appclientlogin.conf

Replace D:/JavaServers/glassfish-v2-b53/ by the directory of your GlassFish serveur. Note: don't forget the - at the beginning of -Djava.sec...

Click Run, you will see the 2 messages, including the message from restricted method hello().

Note

The programmatic login can be used with Java Web Start. Just add the 2 lines in bold in the code to the previous demo and add the required libraries.