Arun Gupta, Miles to go ...

Java EE 6 & GlassFish - Spark IT 2010, Ruby Conf India 2010, Tech Days 2010

2010-03-01T10:40:03-08:00

Java EE 6 & GlassFish are swimming across the globe to participate in three different conferences in March 2010.

Spark IT 2010 is an inaugural conference and a joint initiative of CIOL, India's largest IT portal and PCQuest, India's leading magazine for IT professionals. You'll hear about:

Java EE 6 & GlassFish (12:05 - 12:50pm, Mar 18)
Improving engineering process through Hudson (3:30 - 4:15pm, Mar 18)
GlassFish Toolapalooza (2:40 - 3:25pm, Mar 19)
Rails on GlassFish workshop (Mar 19)

Check Spark IT 2010 website for the latest updates. See the Agenda, Speakers, Venue Layout, follow the updates on @sparkit2010 and register now!

Ruby Conf India 2010 is India's first RubyConf and is presented by Ruby community in India (which seems to be growing) and supported by RubyCentral. There are lots of great speakers Matz, Chad, Obie, Nick, and Ola. And of course, you'll hear about:

GlassFish supports multiple Ruby frameworks ... really ? (2:00 - 2:45pm, Mar 21)

Check Ruby Conf 2010 website for the latest updates. See the Agenda, Venue (Royal Orchid Hotel), follow the updates on @rubyconfindia and register now!

Don't miss out on Sambar/Dosa and Mavalli Tiffin Room while in Bangalore :-)

Tech Days 2010 at Hyderabad is biggest of all the Tech Days events. Other than Dum Biryani, Minarets, and Pearls, you'll hear about Java EE 6 platform and toolshow, OSGi, and Java Persistence API 2. The Agenda (to be updated) has all the details and James Gosling is going to be there as well!

Check Tech Days 2010 website for the latest updates. The venue (Hyderabad International Convention Center) is indeed very impressive so don't miss out and register now!

Check out reports from Tech Days 2009 (1, 2) and Tech Days 2008 (1, 2, 3, 4, 5, 6, 7).

Here is the current speaking schedule:

Mar 7-8: DevNexus, Atlanta
Mar 18-19: Spark IT 2010, Bangalore
Mar 20-21: Ruby Conf India 2010, Bangalore
Mar 24-25: Tech Days 2010, Hyderabad
Apr 5: Java EE 6 & GlassFish workshop, Dallas

And as always, feel free to join me for a run :-)

Technorati: conf glassfish javaee bangalore hyderabad sparkit2010 rubyconfindia techdays hudson

Oracle at EclipseCon 2010 - Java EE 6, OSGi, GlassFish, EclipseLink, JPA 2.0/Dali, ...

2010-02-26T17:02:11-08:00

Oracle is a strategic developer & board member of the Eclipse Foundation and is a gold sponsor of Eclipse Con 2010. See the complete list of Eclipse projects at Oracle.

When ? Mar 22^nd - 25^th, 2010
Where ? Santa Clara, California
How to register ? Register Now - Use the coupon code ORACLE10 (before Mar 2) for 10% off registration.
What ? Program Schedule

Oracle certainly has a lot to talk about Java EE 6, OSGi/GlassFish, JPA 2.0 and Dali, Future of App Servers, Future of Enterprise Java, Eclipse RT and WTP Reloaded tutorials and many other sessions. See the complete details about Oracle's participation here.

Also don't miss the keynote by Steve Harris and Jeet Kaul on Community and Adaptation. Hear these two industry leaders and prolific speakers talk about how Java has empowered community, engendered new forms of adaptation and will continue to blaze the trails.

And then there is Members and Committers reception on Monday evening sponsored by Oracle. Visit us at booth #8 to speak with technical experts, see demos and get information about Oracle's Eclipse technology and Project participation.

OSGi DevCon 2010 is happening on the same dates/venue and is covered with Eclipse Con registration.

And last, but not the least, let that runner in you have some fun and run with fellow attendees. Yep, there are even prizes!

Keep checking eclipsecon.org for the latest updates.

Unfortunately, I'll be speaking elsewhere in a different part of the world during exact same dates and so will miss all the fun. More on that later but here are some key members of the Eclipse Foundation:

Feel free to greet and thank them for running the show :-)

Read about 2009 participation here.

Technorati: conf oracle glassfish javaee oepe eclipsecon santaclara

Oracle GlassFish Server 3 - New Datasheet available

2010-02-24T12:03:52-08:00

Oracle announced a new datasheet for "Oracle GlassFish Server 3", yep no "v"!

Here are some key points from the datasheet:

BENEFITS

Light weight and flexibility, with fast startup of only those services required by deployed applications
Support available from Oracle’s world-class services organization
Easy-to-use administration console and command-line tool
Microsoft .NET interoperability
Compatibility with the Java EE 6 and Java EE 6 Web Profile, improving application portability and developer productivity
Tomcat developers’ ability to begin with the more capable Java EE 6 Web Profile and then grow to a more feature-rich, standardized platform as needed, using only the resources necessary

. . .

Oracle GlassFish Server is the world’s first implementation of the Java Platform, Enterprise Edition (Java EE) 6 specification. Built with the open source GlassFish Project reference implementation, Oracle GlassFish Server is a flexible, lightweight, and extensible Java EE 6–compatible server. Completely supported for commercial deployment and available standalone or packaged with other Oracle Fusion Middleware offerings, Oracle GlassFish Server delivers a small-footprint, fully featured Java EE application server.

. . .

Oracle GlassFish Server is part of the Oracle Fusion Middleware application grid portfolio and is ideally suited for applications requiring lightweight infrastructure with the most up-to-date implementation of enterprise Java, Java EE 6, and Java Web services. Oracle GlassFish Server complements Oracle WebLogic Server, which is designed to run the broader portfolio of Oracle Fusion Middleware and large-scale enterprise applications.

. . .

Please visit oracle.com/sun or call +1.800.786.0404 to speak to an Oracle representative.

Lot more details in the datasheet, download now! More details about Oracle GlassFish Server are on oracle.com. A Java EE 6 whitepaper is also available on oracle.com.

Additionally, you can watch the webcast on GlassFish Strategy by Oracle or attend a Oracle+Sun welcome event in a city near you.

Technorati: oracle glassfish javaee datasheet

Java EE 6 & GlassFish swimming to DevNexus/Atlanta - Mar 8/9 & Dallas - Apr 5

2010-02-23T11:28:37-08:00

Here is an opportunity to hear the latest & greatest about Java EE 6 & GlassFish in Atlanta and Dallas.

Where ?	When ?	Participate ?
Atlanta	Mar 8/9, 2010	DevNexus
Dallas	Apr 5, 2010	FREE Invite

The Atlanta event is happening at DevNexus, a developer conference organized by the Atlanta Java Users Group. The topics in this year's conference range from Java EE 6, Spring 3.0, Grails, Google App Engine, Google Wave, Context & Dependency Injection, Hudson and many others.

See the complete list of speakers and schedule. Seats are limited and pre-registration is required, so register now! Follow @devnexus for more details.

The Dallas event is organized by Oracle University in association with GCA.net Technology Services and is dedicated to Java EE 6 & GlassFish.

In both the events, you'll learn how Java EE 6 provides a flexible technology stack, takes ease-of-development to a new level by following convention-over-configuration and using defaults, improves developer productivity by intuitive tooling, new/updated specifications in the platform and many other features.

The talk will be accompanied by numerous live code samples showing the benefits of Java EE 6 platform and GlassFish.

More details about both the events are available here.

Technorati: javaee glassfish atlanta dallas conf

TOTD #124: Using CDI + JPA with JAX-RS and JAX-WS

2010-02-18T10:36:00-08:00

This is a follow up blog to TOTD #120 and TOTD #123. These two blogs together have created a simple Java EE 6 application and showed the following features so far:

No-interface view for EJB
EJBs packaged in a WAR file
Optional "faces-config.xml" for Java Server Faces
FacesServlet registered using Servlet 3.0 programmatic registration APIs
Java Server Faces navigation rules using convention-over-configuration
Optional "web.xml" for Servlets 3.0
Add database access using Java Persistence API 2.0
Show type-safe Criteria API from JPA 2.0
Use Context & Dependency Injection for JSF managed beans
Add Ajax effects from Java Server Faces 2.0
Add Bean Validation to the JSF managed bean

GlassFish v3 is the Java EE 6 Reference Implementation and comes bundled with a complete SOAP Web services stack (Metro/JAX-WS) and a RESTful stack (JAX-RS/Jersey). This blog will update the previously created Maven project with:

A SOAP Web service using JAX-WS
A RESTful Web service using JAX-RS
Use Context & Dependency Injection with JAX-WS and JAX-RS
Query the database using JPA 2 based upon criteria from the Web service invocation

Lets get started!

Use the Maven project from TOTD #123 and update the directory structure as follows:

src
src/main
src/main/java
src/main/java/org
src/main/java/org/glassfish
src/main/java/org/glassfish/samples
src/main/java/org/glassfish/samples/ActorResource.java
src/main/java/org/glassfish/samples/RESTApplication.java
src/main/java/org/glassfish/samples/SakilaBean.java
src/main/java/org/glassfish/samples/SimpleBean.java
src/main/java/org/glassfish/samples/SimpleEJB.java
src/main/java/org/glassfish/samples/SimpleServlet.java
src/main/java/org/glassfish/samples/SOAPService.java
src/main/resources
src/main/webapp
src/main/webapp/index.jsp
src/main/webapp/index.xhtml
src/main/webapp/sakila.xhtml
src/main/webapp/show.xhtml
src/main/webapp/WEB-INF
src/main/webapp/WEB-INF/beans.xml
src/main/webapp/WEB-INF/web.xml

The changes are:

"ActorResource.java" is added for the RESTful representation of Actor table.
"SOAPSevice.java" is added to invoke the SOAP-based Web service.
"SakilaBean.java" is updated to query the database for an Actor identified by "id".

The updated files are explained below.
- A new method is added to SakilaBean.java as shown below:
```
 public Actor findActorById(int id) {
    EntityManager em = emf.createEntityManager();

    CriteriaBuilder cb = emf.getCriteriaBuilder();
    CriteriaQuery<Actor> criteria = cb.createQuery(Actor.class);

    // FROM clause
    Root<Actor> actor = criteria.from(Actor.class);

    // SELECT clause
    criteria.multiselect(actor.<Short>get("actorId"),
                         actor.<String>get("firstName"),
                         actor.<String>get("lastName"));

    // WHERE clause
     criteria.where(cb.equal(actor.<Short>get("actorId"), id));

    Query q = em.createQuery(criteria);
    ((org.eclipse.persistence.jpa.JpaQuery)q).getDatabaseQuery().dontMaintainCache();

    return (Actor)q.getResultList().get(0);
}
```
  This method queries the database for an actor by his id and uses the typesafe Criteria API to achieve the purpose. The FROM, SELECT, and WHERE clause are highlighted in the code. A cast to EclipseLink specific class is required because of the bug #303205.
- SOAPService.java
```
package org.glassfish.samples;

import javax.inject.Inject;
import javax.jws.WebService;
import sakila.Actor;

@WebService
public class SOAPService {
    @Inject SakilaBean bean;

    public String sayHello(int id) {
        Actor a = bean.findActorById(id);
        return "Hello " + a.getFirstName();
    }
}
```
  The key points in the code are:
  - Standard JAX-WS annotations from "javax.jws.*" package are used to represent the Web service.
  - The Web service has only one method "sayHello" that concatenates the string "Hello" with the first name of "Actor" identified by "id".
  - No deployment descriptor modifications are required to publish this Web service.
  - "SakilaBean" is injected using @Inject annotation and used to query the database. This allows to encapsulate all the database details in one class and injected in a typesafe manner.
- RESTApplication.java
```
package org.glassfish.samples;

import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;

@ApplicationPath("/sakila")
public class RESTApplication extends Application {
}
```
  This is a marker class to inform Jersey of the root resource to be registered. By default, all classes with @Path and @Provider annotations are included. It also specifies the base path at which all resources are accessible.
  
  An alternative to this class is to specify the required information in "web.xml" as:
```
<servlet>
     <servlet-name>Jersey Web Application</servlet-name>
     <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class>
 </servlet>

 <servlet-mapping>
     <servlet-name>Jersey Web Application</servlet-name>
     <url-pattern>/sakila/*</url-pattern>
 </servlet-mapping>
```
  So only one of RESTApplication.java or changes in "web.xml" are required.
- ActorResource.java
```
package org.glassfish.samples;

import javax.enterprise.context.RequestScoped;
import javax.inject.Inject;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.PathParam;
import sakila.Actor;

@Path("/actor/{id}")
@RequestScoped
public class ActorResource {
    @Inject SakilaBean sakila;

    @GET
    @Produces("application/json")
    public Actor getActor(@PathParam("id") int id) {
        return sakila.findActorById(id);
    }
}
```
  The key points in the code are:
  - Standard JAX-RS annotations from "javax.ws.rs" package are used to represent the RESTful resource.
  - "getActor" method is invoked when the resource is accessed using HTTP GET.
  - The resource is accessible at "/actor/{id}" URL where "{id}" is mapped to the "id" parameter of "getActor" method.
  - SakilaBean is injected in a typesafe manner using @Inject annotation. This bean is then used to query the database using the "id" parameter.
  - "getActor" method produces JSON representation, as defined by the "@Produces" annotation. This is easily achieved by updating our Persistence Unit (PU) created in TOTD #122 and adding "@javax.xml.bind.annotation.XmlRootElement" as the class level annotation on "sakila.Actor" class. Make sure to install the updated PU to your local Maven repository.

Package and deploy the application as:

mvn clean package
./bin/asadmin deploy --force=true ~/samples/javaee6/simplewebapp/target/simplewebapp-1.0-SNAPSHOT.war

Now the SOAP web service is accessible at "http://localhost:8080/simplwebapp-1.0-SNAPSHOT/SOAPServiceService" and looks like:

Notice, the URL in your case may be different if the Web service class name was different. The default URL is "http://<HOST>:<PORT>/<CONTEXT ROOT><WEB SERVICE CLASS NAME>Service".

This Web service can be easily tested by using the in-built tester accessible at "http://localhost:8080/simplwebapp-1.0-SNAPSHOT/SOAPServiceService?tester" and looks like:

The WSDL describing the Web service can be seen by clicking on the "WSDL File" link. The Web service method can be invoked by entering a value ("id" of the Actor) in the text box and clicking on "sayHello" button. Here is a sample run:

Clicking on "Submit" invokes the Web service which then uses the injected "SakilaBean" to query the database using the parameter specified. The first name from the response from the database is then extracted, concatenated with the string "Hello" and returned as Web service response.

The RESTful resource is accessible at "http://localhost:8080/simplwebapp-1.0-SNAPSHOT/sakila/actor/5" and looks like:

As in the SOAP-based Web service, the "5" in the URL is mapped to a parameter in the "ActorResource.java", the injected "SakilaBean" is then used to query the database and returns the JSON representation. Specifying a different number in the URL will show the RESTful JSON representation for that particular actor.

More Java EE 6 features will be covered in subsequent blogs. Are you interested in any particular ones ?

Technorati: jaxws metro webservices jaxrs rest jersey glassfish v3 cdi jsr299 weld

Latest features of Java Persistence 2.0 with MySQL - FREE webinar, Feb 23, 2010

2010-02-15T10:12:04-08:00

Want to learn the latest features of Java Persistence 2.0 (JSR 317) with MySQL ?

JPA 2 provides an object/relational mapping facility for the Java application developer using a Java domain model to manage a relational database. JPA got a major facelift as part of Java EE 6 specification and has been expanded to include several key new features - improved object/relational mapping and modeling additions, the query language facilities, the new criteria API, pessimistic locking, and support for validation.

Learn what these features mean in context of MySQL in an upcoming webinar on Feb 23, 2010.

Linda DeMichiel (specification lead of JPA2) and I will be talking about them and showing live code samples to get you started.

Technorati: jpa mysql webinar glassfish netbeans

TOTD #123: f:ajax, Bean Validation for JSF, CDI for JSF and JPA 2.0 Criteria API - all in one Java EE 6 sample application

2010-02-11T23:23:15-08:00

Taking TOTD #120 forward, we'll add the following features to our application:

Add database access using Java Persistence API 2.0
Show type-safe Criteria API from JPA 2.0
Use Context & Dependency Injection for JSF managed beans
Add Ajax effects from Java Server Faces 2.0
Add Bean Validation to the JSF managed bean

Lets get started!

Use the Maven project created in TOTD #120 and update the directory such that it looks like:
```
src
src/main
src/main/java
src/main/java/org
src/main/java/org/glassfish
src/main/java/org/glassfish/samples
src/main/java/org/glassfish/samples/SakilaBean.java
src/main/java/org/glassfish/samples/SimpleBean.java
src/main/java/org/glassfish/samples/SimpleEJB.java
src/main/java/org/glassfish/samples/SimpleServlet.java
src/main/webapp
src/main/webapp/index.jsp
src/main/webapp/index.xhtml
src/main/webapp/sakila.xhtml
src/main/webapp/show.xhtml
src/main/webapp/WEB-INF
src/main/webapp/WEB-INF/beans.xml
src/main/webapp/WEB-INF/web.xml
```
The key differences are:
1. "beans.xml" is an empty file to enable Context & Dependency Injection bean discovery.
2. The JPA Persistence Unit is copied and installed in local Maven repository as explained in TOTD #122.
3. "web.xml" is added to bootstrap the Java Server Faces runtime. This is required because "@ManagedBean" annotation on "SimpleBean" class is now changed to "@javax.inject.Named". The JSF runtime is automatically registered and booted if any bean in the webapp is annotated with "@ManagedBean" or one of the JSF common classes (such as Converter, Validator, or Renderer) is implemented or extended. If none of these "hints" are available in the application, and it's required, then it needs to enabled explicitly.

Here are the updated files, changes are highlighted in bold and explained after each fragment:

index.xhtml

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtm
l1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
 xmlns:ui="http://java.sun.com/jsf/facelets"
 xmlns:h="http://java.sun.com/jsf/html">
 <h:head>
 <title>Enter Name &amp; Age</title>
 </h:head>
 <h:body>
 <h1>Enter Name &amp; Age</h1>
<h:form>
 <h:panelGrid columns="3">
 <h:outputText value="Name:"/>
 <h:inputText value="#{simplebean.name}" title="name" id="name" required="true"/>
 <h:message for="name" style="color: red"/>
 <h:outputText value="Age:"/>
 <h:inputText value="#{simplebean.age}" title="age" id="age" required="true"/>
 <h:message for="age" style="color: red"/>
 </h:panelGrid>
 <h:commandButton action="show" value="submit"/>
 </h:form>
 </h:body>
</html>

Changed the panelGrid from "2" columns to "3". This allows for any validation messages to be displayed right next to the source. Also added "<h:message .../>" to display the validation messages.

SimpleBean.java

package org.glassfish.samples;

import javax.inject.Named;
import javax.enterprise.context.RequestScoped;
import javax.validation.constraints.NotNull;
import javax.validation.constraints.Size;
import javax.validation.constraints.Min;

@Named("simplebean")
@RequestScoped
public class SimpleBean {
 @NotNull
 @Size(min=2, message="Name must be at least 2 characters")
 private String name;

 @NotNull
 @Min(5)
 private int age;

 public String getName() { return name; }
 public void setName(String name) { this.name = name; }

 public int getAge() { return age; }
 public void setAge(int age) { this.age = age; }
}

The changes to the above code are listed below:

Replaced "@ManagedBean" with "@Named" annotation defined in JSR 330 and used by CDI.
Using constraints defined by Bean Validation APIs (JSR 303) to check for
- Both bean properties to be non-null
- Name to be at least 2 characters
- A minimum age of 5
- There are several other pre-defined constraints in "javax.validation.constraints" package and new constraints can be easily defined as well.

SakilaBean.java

package org.glassfish.samples;

import java.util.List;
import javax.enterprise.context.RequestScoped;
import javax.faces.event.ActionEvent;
import javax.inject.Named;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceUnit;
import javax.persistence.EntityManagerFactory;
import javax.persistence.criteria.CriteriaBuilder;
import javax.persistence.criteria.CriteriaQuery;
import javax.persistence.criteria.Root;
import sakila.Actor;

@Named("sakilabean")
@RequestScoped
public class SakilaBean {
 @PersistenceUnit(unitName="SakilaPU")
 EntityManagerFactory emf;

 private List<Actor> actors;
 private int length;
 private int totalActors;

 // getters & setters
 public List<Actor> getActors() { return actors; }
 public void setActors(List<Actor> actors) { this.actors = actors; }
 public int getLength() { return length; }
 public void setLength(int length) { this.length = length; }
 public int getTotalActors() { return totalActors; }
 public void setTotalActors(int totalActors) { this.totalActors = totalActors; }

 public void findActors(ActionEvent evt) {
   EntityManager em = emf.createEntityManager();

   CriteriaBuilder cb = emf.getCriteriaBuilder();
   CriteriaQuery<Actor> criteria = cb.createQuery(Actor.class);

   // FROM clause
   Root<Actor> actor = criteria.from(Actor.class);

   // SELECT clause
   criteria.select(actor);

   // WHERE clause
   criteria.where(cb.greaterThan(
     cb.length(actor.get("firstName").as(String.class)), length));

   // FIRE
   actors = em.createQuery(criteria).getResultList();
   totalActors = actors.size();
 }
}

The key points:

This is a CDI bean marked by @Named and used in the JSF view (shown next), with the name "sakilabean"
EntityManagerFactory is injected using @PersistenceUnit
"findActors" method builds the query using Criteria API. Returns actors' names limited by the number of characters in their first name.
Queries "Actor" table from the database and set bean properties "actors" and "totalActors".
Uses "length" bean property (set from the JSF view) to restrict the number of characters in the name.

sakila.xhtml

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtm
l1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:h="http://java.sun.com/jsf/html">
  <h:head>
    <title>Sakila - Actors Listing</title>
  </h:head>
  <h:body>
    <h1>Sakila - Actors Listing</h1>
    <h:form>
    <h:outputText value="Show actors with first name's length &lt;"/>
    <h:inputText value="#{sakilabean.length}" id="length" required="true" size="5"/>
    <h:commandButton actionListener="#{sakilabean.findActors}" value="submit">
      <f:ajax execute="length" render="actorTable totalActors"/>
    </h:commandButton><br/>
     Total actors found: <h:outputText value="#{sakilabean.totalActors}" id="totalActors"/><p/>
     <h:dataTable var="actor" value="#{sakilabean.actors}" border="1" id="actorTable">
       <h:column><h:outputText value="#{actor.firstName}"/>, <h:outputText value="#{actor.lastName}"/></h:column>
     </h:dataTable>
   </h:form>
 </h:body>
</html>

Key points:

This JSF view shows a form that accepts a number used for restricting the length of actors' first name. The value of this attribute is bound to "length" property of the underlying bean.
Command Button is tied to a JSF Action Listener which is then bound to "findActors" method in the bean. This method executes the JPA query explained above.
"f:ajax" is a newly introduced tag in JSF 2.0 and means an Ajax request is performed on the "onClick" event of the rendered button, "findActors" method in the bean in this case. The tag also specifies other tags in the page, "actorTable" and "totalActors" in this case, that needs to be rendered after the request is completed. The input parameter to the Ajax request is specified using "execute" attribute. Read more about this tag here or section 10.4.1.1 of the JSF 2 specification.

Package and deploy the application as:

mvn clean package
./bin/asadmin deploy --force=true ~/samples/javaee6/simplewebapp/target/simplewebapp-1.0-SNAPSHOT.war

The application is now accessible at "http://localhost:8080/simplewebapp-1.0-SNAPSHOT/sakila.jsf" and looks like:

Enter a value of "4" in the text box and hit "Submit":

Only the HTML table of names and the total count of actors is refreshed showcasing partial page refresh.

Now enter a value of "8" and hit "Submit":

Enjoy!

More Java EE 6 features to be shown in subsequent blogs.

Technorati: totd javaee glassfish v3 javaserverfaces ajax jpa cdi beanvalidation

Oracle+Sun Welcome Events

2010-02-10T10:00:41-08:00

Want to learn how Oracle+Sun are transforming the industry ? What the combination means to you ?

Hear from Oracle and Sun executives in multiple cities all around the world and learn the strategy.

Here is an email flier from my inbox showing some of the North America cities, more cities are being added every day.

In the meanwhile, check out:

Larry Ellison and other execs on Oracle + Sun strategy
Oracle + Sun Product Strategy Webcast Series (Detailed notes on GlassFish & Developer Tools)
Developer Community FAQ

Technorati: oracle sun welcome

TOTD #122: Creating a JPA Persistence Unit using NetBeans 6.8

2010-02-09T23:08:43-08:00

Taking TOTD #121 forward, this blog explains how to create a JPA Persistence Unit for a MySQL sample database and package it as a library. This JAR file can then be easily included in other web applications.

Lets get started!

Configure GlassFish for using the MySQL sample database (sakila) as described in TOTD #121.
Add the GlassFish instance in NetBeans IDE using "Services" panel.

Create JPA entities using NetBeans IDE.

Create a Java class library:

Our ultimate goal is to create a reusable JAR file and that's why this project type is chosen.
Specify the name of project as "SakilaPU":
Right-click on the project and select "New", "Entity Classes from Database ..." to initiate the process of entity generation:
Choose the database connection as:

If not configured, then can be easily done by clicking on "New Database Connection ..." in the list box.
1. Click on "Add All >>" to generate the mapped JPA entities for all tables and views.
2. The views do not have primary keys and will need to be appropriately annotated (described later).
3. Click on "Next >".
Give the package name as:

and specify the package name as "sakila". Click on "Create Persistence Unit ...".
Change the default PU name from "SakilaPUPU" to "SakilaPU":

and click on "Finish". Notice that "EclipseLink", the Reference Implementation of JPA 2.0, is used as the persistence library.

Add "@javax.persistence.Id" annotation to the following class/field combination:

Class	Field
sakila.SalesByFilmCategory	category
sakila.ActorInfo	actorId
sakila.FilmList	fid
sakila.CustomerList	id
sakila.NicerButSlowerFilmList	fid
sakila.StaffList	id
sakila.SalesByStore	store

This is required because none of the "views" are defined with a primary key.

Right-click on the project and select "Clean & Build". This generates "dist/SakilaPU.jar" and the structure looks like:

This JAR file can now be included in any web application. The pre-built JAR file can also be downloaded here.

In order for this PU to be used in an application server (such as GlassFish) that is pre-configured with a JDBC resource, the "persistence.xml" needs to be changed to:

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
 <persistence-unit name="SakilaPU" transaction-type="JTA">
 <jta-data-source>jdbc/sakila</jta-data-source>
 <properties/>
 </persistence-unit>
</persistence>

The JDBC resource name is specified using <jta-data-source>.

The key items to note about this pre-built JAR:

Persistence Unit Name: "SakilaPU"
All classes are in "sakila.*" package.
Each class has a pre-defined "<CLASS-NAME>.findAll" named query that returns all elements from the underlying view/table.

This JAR can be installed to your local Maven repository as:

mvn install:install-file -Dfile=SakilaPU.jar -DgroupId=org.glassfish.samples -DartifactId=sakilapu -Dversion=1.0 -Dpackaging=jar -DgeneratePom=true

and then included in your "pom.xml" as:

 <dependency>
   <groupId>org.glassfish.samples</groupId>
   <artifactId>sakilapu</artifactId>
   <version>1.0</version>
   <scope>compile</scope>
 </dependency>

Even though this blog uses a MySQL sample database, these steps can be easily followed for any other database such as Oracle or JavaDB.

Technorati: totd javaee glassfish v3 jpa eclipselink persistenceunit mysql sakila netbeans

TOTD #121: JDBC resource for MySQL and Oracle sample database in GlassFish v3

2010-02-08T23:00:17-08:00

This blog clearly explains how to configure the MySQL sample database (sakila) with GlassFish. Even though the instructions use a specific database but should work for other databases (such as Oracle, JavaDB, PostgreSQL, and others) as well. The second half of the blog provide specific syntax for the Oracle sample database.

Download sakila sample database and unzip the archive.
Install the database as described here - basically load and run "sakila-schema.sql" and "sakila-data.sql" extracted from the archive.

Create a new MySQL user account using MySQL CLI Admin and assign the privileges

Using "root" user (sudo mysql --user root)

CREATE USER glassfish IDENTIFIED BY 'glassfish';
GRANT ALL PRIVILEGES ON *.* TO 'glassfish'@'localhost' IDENTIFIED BY 'glassfish';
FLUSH PRIVILEGES;

Using "glassfish" user (sudo mysql --user glassfish)
```
source sakila-schema.sql;
source sakila-data.sql;
```

Download Connector/J, unzip and copy "mysql-connector-java-5.x.x-bin.jar" to "glassfish/domains/domain1/lib/ext" directory.
Start GlassFish server as:
```
asadmin start-domain
```

Create a JDBC resource

Create JDBC connection pool as:

asadmin create-jdbc-connection-pool --datasourceclassname com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource --restype javax.sql.DataSource --property "User=glassfish:Password=glassfish:URL=jdbc\:mysql\://localhost/sakila" jdbc/sakilaPool

Test the JDBC connection pool as:

asadmin ping-connection-pool jdbc/sakilaPool

Create the JDBC resource as:

asadmin create-jdbc-resource --connectionpoolid jdbc/sakilaPool jdbc/sakila

That's it!

Creating a JDBC resource for any other database requires the following updates to the steps mentioned above. Lets consider modifying these steps for the Oracle sample database.

Use the client interface SQL*PLus and connect as:

sqlplus "/ as sysdba"

create user and grant the privileges as:

CREATE USER glassfish IDENTIFIED BY glassfish DEFAULT tablespace users TEMPORARY tablespace temp;
GRANT CONNECT TO glassfish IDENTIFIED BY glassfish;
GRANT UNLIMITED TABLESPACE TO glassfish;
GRANT CREATE TABLE TO glassfish;
GRANT CREATE SEQUENCE TO glassfish;

Copy the appropriate JDBC driver (ojdbc6.jar).

Create the JDBC resource as:

asadmin create-jdbc-connection-pool --datasourceclassname oracle.jdbc.pool.OracleDataSource --restype javax.sql.DataSource --property "User=hr:Password=hr:URL=jdbc\:oracle\:thin\:@localhost\:1521\:orcl" jdbc/hr
asadmin ping-connection-pool jdbc/hr
asadmin create-jdbc-resource --connectionpoolid jdbc/hr jdbc/hr

as explained in TOTD #108.

Here are a few other related entries:

Technorati: totd javaee glassfish v3 jpa mysql sakila oracle

TOTD #120: Deployment Descriptor-free Java EE 6 application using JSF 2.0 + EJB 3.1 + Servlets 3.0

2010-02-05T14:00:54-08:00

Here is trivial Java EE 6 application that is keeping you away from any deployment descriptors. It uses Java Server Faces 2.0, Enterprise Java Beans 3.1, and Servlet 3.0. This application shows the following Java EE 6 features:

No-interface view for EJB
EJBs packaged in a WAR file
Optional "faces-config.xml" for Java Server Faces
FacesServlet registered using Servlet 3.0 programmatic registration APIs
Java Server Faces navigation rules using convention-over-configuration
Optional "web.xml" for Servlets 3.0

The WAR file structure is:

./index.jsp
./index.xhtml
./META-INF
./show.xhtml
./WEB-INF
./WEB-INF/classes
./WEB-INF/classes/org
./WEB-INF/classes/org/glassfish
./WEB-INF/classes/org/glassfish/samples
./WEB-INF/classes/org/glassfish/samples/SimpleBean.class
./WEB-INF/classes/org/glassfish/samples/SimpleEJB.class
./WEB-INF/classes/org/glassfish/samples/SimpleServlet.class

Look ma, no deployment descriptors!

So how do you create this application:

mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=org.glassfish.samples -DartifactId=simplewebapp

This application is purposely not generated as a web application (missing "-DarchetypeArtifactId=maven-archetype-webapp"). If you specify this property then it will generate "WEB-INF/web.xml" which we don't intend to use.

Change "pom.xml" to:

<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>org.glassfish.samples</groupId>
   <artifactId>simplewebapp</artifactId>
   <packaging>war</packaging>
   <version>1.0-SNAPSHOT</version>
   <name>simplewebapp</name>
   <url>http://maven.apache.org</url>
   <repositories>
     <repository>
       <id>glassfish-repository</id>
       <name>Java.net Repository for Glassfish</name>
       <url>http://download.java.net/maven/glassfish</url>
     </repository>
   </repositories>
   <build>
     <plugins>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-compiler-plugin</artifactId>
         <version>2.0.2</version>
         <configuration>
           <source>1.5</source>
           <target>1.5</target>
         </configuration>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-war-plugin</artifactId>
         <version>2.1-beta-1</version>
         <configuration>
           <failOnMissingWebXml>false</failOnMissingWebXml>
         </configuration>
       </plugin>
     </plugins>
   </build>
   <dependencies>
     <dependency>
       <groupId>junit</groupId>
       <artifactId>junit</artifactId>
       <version>3.8.1</version>
       <scope>test</scope>
     </dependency>
    <dependency>
       <groupId>javax</groupId>
       <artifactId>javaee-api</artifactId>
       <version>6.0</version>
       <scope>provided</scope>
    </dependency>
   </dependencies>
</project>

In the above code:

"maven-compiler-plugin" needs to be specified as the default source level for Maven compile plugin is JDK 1.3. It's been over 9 years JDK 1.3 was released, not even listed on Java SE standard downloads page, EOLed many years ago. Vote/Comment for the issue MCOMPILER-80 if you'd like this bug to be fixed.
Adding "failOnMissingWebXml" ensures that Maven packages the WAR file even though no "web.xml" is present.
The complete list of Maven coordinates for GlassFish are available here.

Create the directory structure as:

./src/main
./src/main/java
./src/main/java/org
./src/main/java/org/glassfish
./src/main/java/org/glassfish/samples
./src/main/java/org/glassfish/samples/SimpleBean.java
./src/main/java/org/glassfish/samples/SimpleEJB.java
./src/main/java/org/glassfish/samples/SimpleServlet.java
./src/main/webapp
./src/main/webapp/index.jsp
./src/main/webapp/index.xhtml
./src/main/webapp/show.xhtml

Once again, there are no deployment descriptors, just plain Java files and XHTML/JSP pages.

Here are the different source files with explanation after each one of them:

SimpleBean.java

package org.glassfish.samples;

import javax.faces.bean.ManagedBean;

@ManagedBean(name="simplebean")
public class SimpleBean {
    private String name;
    private int age;

    public String getName() { return name; }
    public void setName(String name) { this.name = name; }

    public int getAge() { return age; }
    public void setAge(int age) { this.age = age; }
}

This is currently a simple JSF managed bean. TOTD #109 explains how to convert a JSF managed bean to use CDI. A future blog will show how to convert this sample to use CDI.

SimpleEJB.java

package org.glassfish.samples;

import javax.ejb.Stateless;

@Stateless
public class SimpleEJB {
    public String sayHello(String name) {
        return "Hello " + name + "!!!";
    }
}

The session bean has no interface, just the @Stateless annotation.

SimpleServlet.java

package org.glassfish.samples;

import javax.ejb.EJB;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.annotation.WebServlet;
import java.io.PrintWriter;
import java.io.IOException;

/**
 * Hello world!
 */
@WebServlet(urlPatterns={"/SimpleServlet"})
public class SimpleServlet extends HttpServlet {
    @EJB SimpleEJB bean;

    @Override
    public void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException {
        PrintWriter out = response.getWriter();
        out.println("<html><body>");
        out.println("<h2>Serving at: " + request.getContextPath() + "</h2>");
        out.println("<h2>Invoking EJB: " + bean.sayHello("Duke") + "</h2>");
        out.println("</body></html>");
    }
}

The servlet injects the EJB in the application, display the servlet context and the result of invoking the business operation of the EJB.

index.jsp

<html>
<body>
<h2>Hello World!</h2>
Invoke the Servlet by clicking <a href="SimpleServlet">here</a>.
</body>
</html>

This is just a placeholder for invoking the servlet.

index.xhtml

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtm
l1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
 xmlns:ui="http://java.sun.com/jsf/facelets"
 xmlns:h="http://java.sun.com/jsf/html">
 <h:head>
 <title>Enter Name &amp; Age</title>
 </h:head>
 <h:body>
 <h1>Enter Name &amp; Age</h1>
<h:form>
 <h:panelGrid columns="2">
 <h:outputText value="Name:"/>
 <h:inputText value="#{simplebean.name}" title="name" id="name" required="true"/>
 <h:outputText value="Age:"/>
 <h:inputText value="#{simplebean.age}" title="age" id="age" required="true"/>
 </h:panelGrid>
 <h:commandButton action="show" value="submit"/>
 </h:form>
 </h:body>
</html>

JSF 2 uses Facelets as viewing technology and so an ".xhtml" file is used for all the JSF tags. This page is intentionally kept simple and not using any templating, composition, or any other features of Facelets. This page renders an HTML form with two text boxes and a command button, binds the value of text box to the managed bean, and displays the page "show.xhtml" when the command button is clicked. The default JSF 2 navigation handler try to match a view on the disk ("show.xhtml" in this case) based upon the "action" attribute.

show.xhtml

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtm
l1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
 xmlns:h="http://java.sun.com/jsf/html">
 <h:head>
 <title>Show Name &amp; Age</title>
 </h:head>
 <h:body>
 <h1>Show Name &amp; Age</h1>
<h:form action="show">
 <h:panelGrid columns="2">
 <h:outputText value="Name:"/>
 <h:outputText value="#{simplebean.name}" />
 <h:outputText value="Age:"/>
 <h:outputText value="#{simplebean.age}" />
 </h:panelGrid>
 </h:form>
 </h:body>
</html>

This page reads the bean properties (stored from previous page) and displays them on the page.

How do you build this entire application ?

mvn clean package

Lets deploy the application on a Java EE 6 compliant application server, GlassFish v3 (download here):

./bin/asadmin deploy --force=true ~/samples/javaee6/simplewebapp/target/simplewebapp-1.0-SNAPSHOT.war

And now your application is accessible at "http://localhost:8080/simplewebapp-1.0-SNAPSHOT/index.jsp" and looks like:

Clicking on "here" looks like:

The JSF page is accessible at "http://localhost:8080/simplewebapp-1.0-SNAPSHOT/index.jsf" and looks like (after entering the values):

Notice that even though the page is named "index.xhtml", it's accessed as "index.jsf". This is because the JSF specification provides recommended mapping for FacesServlet to "*.faces" and "/faces/*". In addition, Mojarra (Reference Implementation of JSF2 in GlassFish) also adds a mapping to "*.jsf". Any views using these URL pattersn are routed through FacesServlet. So alternative URLs for our page are "http://localhost:8080/simplewebapp-1.0-SNAPSHOT/index.faces" and "http://localhost:8080/simplewebapp-1.0-SNAPSHOT/faces/index.xhtml".

Clicking on "Submit" shows the following page:

That's it!

Here are several other useful entries:

TOTD #109 : How to convert a JSF managed bean to JSR 299 bean (Web Beans) ?
TOTD #108 : Java EE 6 web application (JSF 2.0 + JPA 2.0 + EJB 3.1) using Oracle, NetBeans, and GlassFish
TOTD #102 : Java EE 6 (Servlet 3.0 and EJB 3.1) wizards in Eclipse
TOTD #99 : Creating a Java EE 6 application using MySQL, JPA 2.0 and Servlet 3.0 with GlassFish Tools Bundle for Eclipse
TOTD #98 : Create a Metro JAX-WS Web service using GlassFish Tools Bundle for Eclipse
TOTD #95 : EJB 3.1 + Java Server Faces 2.0 + JPA 2.0 web application - Getting Started with Java EE 6 using NetBeans 6.8 M1 & GlassFish v3
TOTD #94 : A simple Java Server Faces 2.0 + JPA 2.0 application - Getting Started with Java EE 6 using NetBeans 6.8 M1 & GlassFish v3
TOTD #93 : Getting Started with Java EE 6 using NetBeans 6.8 M1 & GlassFish v3 - A simple Servlet 3.0 + JPA 2.0 app

The next follow up blog will show "Hello World"s of Context & Dependency Injection, Bean Validation, Java API for Restful Web services, Java Persistence API, Interceptors, and other Java EE 6 specifications in this application.

Technorati: totd javaee glassfish v3 javaserverfaces servlet3 ejb maven

Screencast #29: Web service using NetBeans 6.8 and GlassFish v3 (Accessing database in business method)

2010-02-01T23:14:46-08:00

GlassFish v3 comes bundled with Metro - a secure, reliable, transactional, and .NET interoperable Web services stack. Metro is compliant with JAX-WS and provides additional quality of service attributes that can be easily enabled using NetBeans IDE.

This blog contains a screencast that shows how to create a simple Web service using NetBeans 6.8, implement the business logic by accessing a database table using Java Persistence API, and deploy on GlassFish v3.

Please post your questions to users@glassfish.dev.java.net.

Several other screencasts on GlassFish v3and related topics are available here.

Technorati: netbeans jax-ws metro webservice glassfish jpa database

Developer Tools Strategy by Oracle+Sun: NetBeans & Hudson to stay!

2010-01-29T04:43:05-08:00

Hear Ted Farrell, Chief Architect and Senior Vice President talk about Oracle and Sun Java Developer Tools Strategy.

Here is a summary for those who want a quick juice:

Productivity With Choice
- Choose the right tool set for your needs
- Shared infrastructure across tools with Hudson, Oracle TPC, Subversion. Bugzilla, Maven, etc.
- NetBeans continues with strong Java focus
- Combine and integrate the best features across tools
More resources for Developers
- Netbeans.org, java.net, otn.oracle.com
- More courses/training on Java technologies
- More conferences around the world
- Better products from expanded R&D and partner ecosystem
- Larger combined developer community

Here is a lovely snapshot from the webcast ...

Some more detailed points captured from the webcast ...

If you are a NetBeans user today, you'll continue to be a NetBeans user after acquisition.
Increase the investment in Hudson, lots of synergy with Team Productivity Center.
Discontinue the public interface for kenai.com for now, fits very well with some internal projects. Read more about the future of kenai.com.
Want to make the best Java IDE for the Java platform. NetBeans platform is very important to lot of customers.
For NetBeans, turn to community for external non-Java like Dynamic Languages. Invest more in the infrastructure and community.
netbeans.org unchanged
Community participation is key for:
- NetBeans plug-ins
- Building apps on NetBeans Platform
- Emerging, Dynamic Languages
- Dialog, interaction, lists, docs, events, JUGS, etc
No licensing changes
- Versions of NetBeans <= 6.7 follow Sun policy
- Versions of NetBeans >= 6.8 follow the Oracle policy (complete details)

The webcast also talks about JavaOne being co-located with Oracle Open World (Se 19-23, 2010) and also expanding to Brazil, Russia, India, and China.

oracle.com/tools for more details. The complete list of webcasts + slides from yesterday's event are now available.

There are several other articles (in no particular order):

Also check out the FAQ for Developer Community.

Technorati: sun oracle netbeans kenai hudson strategy

GlassFish strategy by Oracle+Sun

2010-01-28T12:24:31-08:00

Hear Hasan Rizvi, Senior Vice President, Oracle Fusion Middleware, talk about GlassFish in Oracle and Sun Application Server Strategy webcast. The first part of the webcast is about the overall strategy and then the GlassFish part starts around 5:23 in the video.

Here is a summary for those who want a quick juice:

GlassFish joins WebLogic Server in the best java EE application server offering in the industry
GlassFish continues as the Java EE reference implementation
HotSpot and Java System Web Server augment Oracle's application grid portfolio to provide the most comprehensive, integrated, and open middleware foundation
All existing customers current on support will be fully supported according to their existing agreements

Some more detailed points captured from the webcast ...

GlassFish continues as the Java EE reference implementation and as an open source project.
Oracle's strategic application server, Oracle WebLogic Server, together with GlassFish, provide world class Java EE infrastructure.
GlassFish Enterprise Server and WebLogic Server expected to share core components.
Oracle plans to add GlassFish Enterprise Server all WebLogic offerings.
Hotspot and JRockit become Oracle's strategic JVMs.
Java System Web Server part of new Oracle Web Tier offering.
GlassFish Web Stack maintained for existing customers.
GlassFish Message Queue remains as the GlassFish messaging infrastructure.
Oracle plans to license GlassFish Enterprise Server and Java System Web Server with all WebLogic Server offerings.
GlassFish also available as standalone offering.
GlassFish will continue to be supported and maintained for an extended time period for customers current on support.
- GlassFish v2.1 supported until Jan 2013 (Premium) / Jan 2015 (Extended) / Indefinite (Sustaining)
- GlassFish v3 supported until Dec 2014 (Premium) / Dec 2017 (Extended) / Indefinite (Sustaining)
- Full details at http://www.oracle.com/support/lifetime-support-policy.htm
GlassFish open source projects thrive
On-going commitment by Oracle to java.net and other open source projects that make up GlassFish
- Continue collaboration
- Blogs - TheAquarium
- Enhancements - java.net
- GlassFish wiki

oracle.com/AppServer for more details. The complete list of webcasts on Oracle Fusion Middleware Strategy shares the overall strategy (still evolving).

Also checkout the slides presented by Thomas Kurian on Software Strategy at the webcast yesterday. The complete list of webcasts + slides from yesterday's event are now available.

There are several other articles (in no particular order):

Also check out the FAQ for Developer Community.

Technorati: sun oracle glassfish strategy

TOTD #119: Telnet to GlassFish v3 with NetBeans 6.8 - "Could not open connection to the host"

2010-01-22T02:00:48-08:00

As explained in TOTD #118, one of the ways to manage OSGi bundles in GlassFish is by giving the command "telnet localhost 6666".

This straight forward command works fine if you installed either the Sun GlassFish Enterprise Server or the GlassFish community bits. The "domain.xml" in both of them is pre-configured for the telnet port to 6666 using the "jvm-options" as shown below:

<jvm-options>-Dosgi.shell.telnet.port=6666</jvm-options>

However if you installed GlassFish as part of NetBeans 6.8, then you might see an error message as shown below:

C:\Users\Arun>telnet localhost 6666
Connecting To localhost...Could not open connection to the host, on
port 6666: Connect failed

This error is more prominent in Windows Vista / 7 because of the Windows User Account Control (UAC). Or anywhere where GlassFish is installed in a directory that require root/administrator/sudo access to read/write. This Tip Of The Day will explain how to workaround this issue.

The default NetBeans installation directory is "C:\Program Files\NetBeans 6.8" and GlassFish goes in "C:\Program Files\sges-v3". At first start of NetBeans (typically as a non-Administrator), it tries to register the pre-configured domain in GlassFish installed in "C:\Program Files". But the non-Adminstrator user do not have read/write access to "C:\Program Files" and any sub-directories. So NetBeans create a new "personal" domain and assign a random port available at that moment for telnet. It shows all the ports assigned during the domain creation as shown below:

The image shows the port number "22007" for OSGI_SHELL.

How do you find that port later ? - Go to "Services" tab, expand "Servers", right-click on "Personal GlassFish v3 Domain", select "Properties" from the popup menu to see the following window:

The "Domains folder" shows the directory location of newly created domain and "Domain Name" has the domain name. The exact assigned port can be found by looking at "Domains folder"\"Domain Name"\config\domain.xml. On my Windows7, it showed the following line:

<jvm-options>-Dosgi.shell.telnet.port=22007</jvm-options>

So I tried "telnet localhost 22007" and voila, it worked!

Some other possible solutions that will work:

Delete ".netbeans" directory and restart NetBeans by right-clicking on selecting "Run as administrator". This will provide the required rights for NetBeans to read/write "C:\Program Files\sges-v3\glassfish\domains\domain1" directory. And so instead of creating a new "personal" domain, it'll register the existing domain in "\Program Files\sges-v3\glassfish". Then "telnet localhost 6666" will work as expected.
During NetBeans installation, specify GlassFish installation directory in a user directory such as:

This will ensure that NetBeans will have required privileges to read/write the "domains\domain1" directory.
Delete the "Personal GlassFish v3 Domain" and register a new instance that is already installed in a user directory.
Disable UAC.

A complete archive of all the TOTDs is available here.

Technorati: totd netbeans glassfish v3 felix osgi telnet

"Sun Microsystems, 1982 - 2010" - Farewell by James Gosling

2010-01-21T14:46:59-08:00

James Gosling is bidding farewell to Sun Microsystems because of the unconditional approval of Oracle's acquisition by European Commission. Here is fitting artwork from his blog:

After spending close to 11 years at Sun, it's pretty emotional to read through the entire set of comments on his blog. Consider buying a mug, tee-shirt, cap, tile coaster or mousepad.

But there are many more miles to go ...

Technorati: sun oracle rip

TOTD #118: Managing OSGi bundles in GlassFish v3 - asadmin, filesystem, telnet console, web browser, REST, osgish

2010-01-21T04:00:35-08:00

GlassFish v3 and OSGi integration is now known for almost two years. Several blogs have been published on this topic and googling on "glassfish osgi" shows 817,000 results. This blog has published four entries on the topic so far.

This Tip Of The Day (TOTD) will show the different ways you can manage OSGi bundles in GlassFish v3.

The first part is to create a trivial OSGi bundle as explained in TOTD #36.

Create a simple Maven project using the command as shown below:

~/samples/v3/osgi >mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=org.glassfish.samples.osgi.helloworld -DartifactId=helloworld
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [archetype:create] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [archetype:create]
[WARNING] This goal is deprecated. Please use mvn archetype:generate instead
[INFO] Defaulting package to group ID: org.glassfish.samples.osgi.helloworld
[INFO] artifact org.apache.maven.archetypes:maven-archetype-quickstart: checking for updates from central
[INFO] ----------------------------------------------------------------------------
[INFO] Using following parameters for creating OldArchetype: maven-archetype-quickstart:RELEASE
[INFO] ----------------------------------------------------------------------------
[INFO] Parameter: groupId, Value: org.glassfish.samples.osgi.helloworld
[INFO] Parameter: packageName, Value: org.glassfish.samples.osgi.helloworld
[INFO] Parameter: package, Value: org.glassfish.samples.osgi.helloworld
[INFO] Parameter: artifactId, Value: helloworld
[INFO] Parameter: basedir, Value: /Users/arungupta/samples/v3/osgi
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] ********************* End of debug info from resources from generated POM ***********************
[INFO] OldArchetype created in dir: /Users/arungupta/samples/v3/osgi/helloworld
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11 seconds
[INFO] Finished at: Wed Jan 20 14:12:41 PST 2010
[INFO] Final Memory: 12M/80M
[INFO] ------------------------------------------------------------------------

Change the generated App class in "src/main/java/org/glassfish/samples/osgi/helloworld" folder so that it looks like:

package org.glassfish.samples.osgi.helloworld;

import org.osgi.framework.BundleActivator;
import org.osgi.framework.BundleContext;

/**
 * Hello world!
 *
 */
public class App implements BundleActivator {
    public void start(BundleContext context) throws Exception {
        System.out.println("Hey!");
    }
    public void stop(BundleContext context) throws Exception {
        System.out.println("Bye!");
    }
}

This is a trivial Activator class but sitll shows the key methods. The changes are highlighted in bold.

Update "pom.xml" with the following changes:

Change <packaging> to "bundle" from the default value of "jar".
Add <dependency> on "org.osgi.core".

Add the <plugin> maven-bundle-plugin and provide <instructions> to generate the appropriate MANIFEST.MF.

<project xmlns="http://maven.apache.org/POM/4.0.0" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
                  http://maven.apache.org/maven-v4_0_0.xsd">
 <modelVersion>4.0.0</modelVersion>
 <groupId>org.glassfish.samples.osgi.helloworld</groupId>
 <artifactId>helloworld</artifactId>
 <packaging>bundle</packaging>
 <version>1.0-SNAPSHOT</version>
 <name>helloworld</name>
 <url>http://maven.apache.org</url>
 <dependencies>
   <dependency>
     <groupId>junit</groupId>
     <artifactId>junit</artifactId>
     <version>3.8.1</version>
     <scope>test</scope>
   </dependency>
   <dependency>
     <groupId>org.apache.felix</groupId>
     <artifactId>org.osgi.core</artifactId>
     <version>1.0.0</version>
   </dependency>
 </dependencies>
 <build>
   <plugins>
     <plugin>
       <groupId>org.apache.felix</groupId>
       <artifactId>maven-bundle-plugin</artifactId>
       <extensions>true</extensions>
       <configuration>
         <instructions>
           <Export-Package>${pom.groupId}</Export-Package>
           <Bundle-SymbolicName>${pom.artifactId}</Bundle-SymbolicName>
           <Bundle-Activator>${pom.groupId}.App</Bundle-Activator>
         </instructions>
       </configuration>
     </plugin>
   </plugins>
 </build>
</project>

Generate the OSGi bundle as shown below:

~/samples/v3/osgi/helloworld >mvn install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building helloworld
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 1 source file to /Users/arungupta/samples/v3/osgi/helloworld/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to /Users/arungupta/samples/v3/osgi/helloworld/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: /Users/arungupta/samples/v3/osgi/helloworld/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.glassfish.samples.osgi.helloworld.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec

Results :

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

[INFO] [bundle:bundle]
[INFO] [install:install]
[INFO] Installing /Users/arungupta/samples/v3/osgi/helloworld/target/helloworld-1.0-SNAPSHOT.jar to /Users/arungupta/.m2/repository/org/glassfish/samples/osgi/helloworld/helloworld/1.0-SNAPSHOT/helloworld-1.0-SNAPSHOT.jar
[INFO] [bundle:install]
[INFO] Parsing file:/Users/arungupta/.m2/repository/repository.xml
[INFO] Installing org/glassfish/samples/osgi/helloworld/helloworld/1.0-SNAPSHOT/helloworld-1.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Wed Jan 20 14:18:31 PST 2010
[INFO] Final Memory: 20M/80M
[INFO] ------------------------------------------------------------------------

The generated "target/helloworld-1.0-SNAPSHOT.jar" has the following contents:

 META-INF/MANIFEST.MF
 META-INF/
 META-INF/maven/
 META-INF/maven/org.glassfish.samples.osgi.helloworld/
 META-INF/maven/org.glassfish.samples.osgi.helloworld/helloworld/
 META-INF/maven/org.glassfish.samples.osgi.helloworld/helloworld/pom.properties
 META-INF/maven/org.glassfish.samples.osgi.helloworld/helloworld/pom.xml
 org/
 org/glassfish/
 org/glassfish/samples/
 org/glassfish/samples/osgi/
 org/glassfish/samples/osgi/helloworld/
 org/glassfish/samples/osgi/helloworld/App.class

And the generated "MANIFEST.MF" looks like:

Manifest-Version: 1.0
Export-Package: org.glassfish.samples.osgi.helloworld;uses:="org.osgi.
 framework"
Built-By: arungupta
Tool: Bnd-0.0.357
Bundle-Name: helloworld
Created-By: Apache Maven Bundle Plugin
Bundle-Version: 1.0.0.SNAPSHOT
Build-Jdk: 1.6.0_17
Bnd-LastModified: 1264025910352
Bundle-ManifestVersion: 2
Bundle-Activator: org.glassfish.samples.osgi.helloworld.App
Import-Package: org.glassfish.samples.osgi.helloworld,org.osgi.framewo
 rk;version="1.3"
Bundle-SymbolicName: helloworld

Lets install this newly created OSGi bundle in GlassFish v3. First, fire up GlassFish as:

~/tools/glassfish/v3/74b/glassfishv3/glassfish >./bin/asadmin start-domain -v
Jan 20, 2010 2:30:39 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java
-cp
/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/glassfish.jar
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-XX:NewRatio=2
-XX:+LogVMOutput

. . .

Jan 20, 2010 2:30:40 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 52 msec.
Jan 20, 2010 2:30:40 PM com.sun.enterprise.glassfish.bootstrap.ASMain main
INFO: Launching GlassFish on Felix platform

Welcome to Felix
================

[#|2010-01-20T14:30:49.437-0800|INFO|glassfishv3.0|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=11;_ThreadName=FelixStartLevel;|Perform lazy SSL initialization for the listener 'http-listener-2'|#]

[#|2010-01-20T14:30:49.527-0800|INFO|glassfishv3.0|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-11;|Starting Grizzly Framework 1.9.18-k - Wed Jan 20 14:30:49 PST 2010|#]

. . .

[#|2010-01-20T14:30:58.668-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/, felix.fileinstall.debug=1};|Started bundle: file:/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/org.apache.felix.scr.jar|#]

[#|2010-01-20T14:30:58.786-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/, felix.fileinstall.debug=1};|Started bundle: file:/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/osgi-web-container.jar|#]

[#|2010-01-20T14:31:00.436-0800|INFO|glassfishv3.0|null|_ThreadID=23;_ThreadName=ping;|Total number of available updates : 0|#]

There are several ways to manage the OSGi bundles in GlassFish v3:

The "asadmin" command (explained here)
Filesystem operations using the pre-installed Apache Felix File Install bundle (explained here)
A Telnet shell using pre-installed Apache Felix Remote Shell (explained here and TOTD #103)
A Web browser using the Apache Felix Web Console (needs to be installed separately and more details below)
A RESTful client by installing the REST console (need to be installed separately and more details below)

Lets explore each option in detail now.

Option 1: Manage the OSGi bundle using the "asadmin" command

Deploy the generated OSGi bundle using asadmin command:

~/samples/v3/osgi/helloworld/target >~/tools/glassfish/v3/74b/glassfishv3/glassfish/bin/asadmin deploy --type osgi helloworld-1.0-SNAPSHOT.jar 
Application deployed successfully with name helloworld-1.0-SNAPSHOT.


Command deploy executed successfully.

The server log shows the following output:

[#|2010-01-20T16:15:10.553-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=36;_ThreadName=http-thread-pool-4848-(2);
|Hey!|#]

Notice "Hey!" message in the server log as the bundle gets started.

Verify the installed bundle as:

~/samples/v3/osgi/helloworld/target >~/tools/glassfish/v3/74b/glassfishv3/glassfish/bin/asadmin list-applications
helloworld-1.0-SNAPSHOT 

Command list-applications executed successfully.

Or if there are multiple applications deployed then only the OSGi bundles can be queried as:

~/samples/v3/osgi/helloworld/target >~/tools/glassfish/v3/74b/glassfishv3/glassfish/bin/asadmin list-applications --type osgi
helloworld-1.0-SNAPSHOT 

Command list-applications executed successfully.

The bundle can be undeployed as:

~/samples/v3/osgi/helloworld/target >~/tools/glassfish/v3/74b/glassfishv3/glassfish/bin/asadmin undeploy helloworld-1.0-SNAPSHOT 

Command undeploy executed successfully.

And then the following message is shown on the console:

[#|2010-01-20T16:22:19.554-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=37;_ThreadName=http-thread-pool-4848-(1);
|Bye!|#]

Notice "Bye!" message in second line of the log output indicating the bundle is stopped.

Option 2: Manage the OSGi bundle using file system operations

Copy the generated jar (target/helloworld-1.0-SNAPSHOT.jar) in "modules/autostart" directory as:

~/tools/glassfish/v3/74b/glassfishv3/glassfish >cp ~/samples/v3/osgi/helloworld/target/helloworld-1.0-SNAPSHOT.jar modules/autostart/

and that shows the log output as:

[#|2010-01-20T16:29:04.625-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Installed /Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/
helloworld-1.0-SNAPSHOT.jar|#]

[#|2010-01-20T16:29:04.635-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Hey!|#]

[#|2010-01-20T16:29:04.636-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Started bundle: file:/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart
/helloworld-1.0-SNAPSHOT.jar|#]

Notice "Hey!" message in the second line of log output as the bundle gets started.

The bundle can be undeployed by removing the JAR file from "modules/autostart" directory as:

~/tools/glassfish/v3/74b/glassfishv3/glassfish >rm modules/autostart/helloworld-1.0-SNAPSHOT.jar

that shows the following output:

~/tools/glassfish/v3/74b/glassfishv3/glassfish >[#|2010-01-20T16:32:04.677-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Uninstalling bundle 224 (helloworld)|#]

[#|2010-01-20T16:32:04.679-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Bye!|#]

[#|2010-01-20T16:32:04.682-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName={felix.fileinstall.poll=5000, felix.fileinstall.bundles.new.start=true, felix.fileinstall.dir=/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish
/modules/autostart/, felix.fileinstall.debug=1};|Uninstalled /Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart
/helloworld-1.0-SNAPSHOT.jar|#]

Notice "Bye!" message in second line of the log output indicating the bundle is stopped.

Option 3: Manage the OSGi bundle using a remote Telnet Shell

Connecting to the Felix Remote Shell as:

~/tools/glassfish/v3/74b/glassfishv3/glassfish >telnet localhost 6666
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying fe80::1...
telnet: connect to address fe80::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Felix Remote Shell Console:
============================

->

Install the bundle as:
```
-> install file:///Users/arungupta/samples/v3/osgi/helloworld/target/helloworld-1.0-SNAPSHOT.jar
Bundle ID: 225
```
The command output shows "225" as the bundle id. This id is used to start / stop / uninstall the bundle.

Check the bundle status as:

-> find hello
START LEVEL 1
   ID   State         Level  Name
[ 225] [Installed  ] [    1] helloworld (1.0.0.SNAPSHOT)

and then start, stop, and uninstall the bundle as:

-> start 225
-> stop 225
-> uninstall 225
-> find hello
No matching bundles found

which shows following output in the logs:

[#|2010-01-20T16:43:45.399-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=38;_ThreadName=telnetconsole.shell remote=/127.0.0.1:4894;|Hey!|#]

[#|2010-01-20T16:43:58.516-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=38;_ThreadName=telnetconsole.shell remote=/127.0.0.1:4894;|Bye!|#]

Notice "Hey!" and "Bye!" messages in the log output as the bundle is started and stopped.

Option 4 - Manage the OSGi bundle using a Web browser

Lets see how the OSGi bundles in GlassFish can be managed using Apache Felix Web Console. This is originally explained in Sahoo's blog.

Copy GlassFish OSGi HTTP Service bundle from here (latest) and save it in the "modules/autostart" directory.
Copy Apache Felix Web Console bundle from here (latest) and save it in the "modules/autostart" directory.

Ignore the "NoClassDefFoundError" in the server log. The key is to look for the following message in server log:

Started bundle: file:/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole-2.0.4.jar|#]

Open the URL "http://localhost:8080/osgi/system/console/bundles" in a browser and use "admin" as the username and "admin" as the password as shown below:

I had to enter the credentials couple of times for the login to work but finally the following window showed up:

It shows a complete summary of all the OSGi bundles available/installed/active etc in GlassFish v3. A new OSGi bundle can be installed by clicking on "Choose File" button. Several administration commands such as Start/Stop, Update, Uninstall, Refresh Import Packages can be issued for each bundle by clicking on associated buttons.
Install the OSGi bundle by clicking on "Choose File" and selecting "helloworld-1.0.-SNAPSHOT.jar" and then click on "Install or Update" button. The following message is shown in the server log:
```
[#|2010-01-20T17:04:46.654-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.
sun.enterprise.v3.services.impl|_ThreadID=39;_ThreadName=Background Install /var/folders/+E/+E6YtSvGGEKNwOA77I-9Fk+++TI/-Tmp-/install1657418488877506078.tmp;
|Hey!|#]
```
The bundle gets installed and started as identified by "Hey!" message.
The recently installed "HelloWorld" bundle looks like:

Clicking on "helloworld" shows the complete status about the bundle as shown below:
The bundle can be stopped by clicking on the Stopped, Refreshed Package Imports, Updated, and Uninstalled by clicking on the respective buttons in the "Actions" column. Clicking on the Stop button shows the following message:
```
[#|2010-01-20T17:10:56.359-0800|INFO|glassfishv3.0|javax.enterprise.system.std.com
.sun.enterprise.v3.services.impl|_ThreadID=25;_ThreadName=http-thread-pool-8080-(2);
|Bye!|#]
```
Notice "Bye!" message indicating the bundle has stopped.

Option 5: Manage the OSGi bundle using a REST console

If not done already, copy GlassFish OSGi HTTP Service bundle from here (latest) and save it in the "modules/autostart" directory.
Download the REST console bundle (latest) in "modules/autostart" directory.

The complete list of bundles is available in Text or XML format by accessing the URL "http://localhost:8080/osgi/restconsole/bundles/.txt" or "http://localhost:8080/osgi/restconsole/bundles" respectively. Here is how the text output looks like:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16198    0 16198    0     0  1173k      0 --:--:-- --:--:-- --:--:-- 1173kbundles 
     bundle 
          id 
               0 
          symbolic-name 
               org.apache.felix.framework 

. . .

          description 
               Generated using Pax-Construct 
          vendor 
          version 
               1.0.0.SNAPSHOT 
          location 
               file:/Users/arungupta/tools/glassfish/v3/74b/glassfishv3/glassfish/modules/autostart/
com.knokode.osgi.restconsole.main-1.0-PREVIEW01.jar 
          state 
               ACTIVE

The OSGi bundle should be installed by issuing the following command:
```
curl -X PUT file:///Users/arungupta/samples/v3/osgi/helloworld/target/helloworld-1.0-SNAPSHOT.jar http://localhost:8080/osgi/restconsole/bundles
```
but it's giving a "Segmentation fault". Am following with @fdiotalevi.

Anyway, the complete usage information of the REST console is described here.

So how do you manage OSGi bundles in GlassFish v3 - asadmin, file system operations, telnet console, web browser, or REST ?

UPDATE: Osgish is a command-line shell for OSGi and implemented in Perl. See the complete installation instructions and it can be used to manage OSGi runtime in GlassFish as well.

A complete archive of all the TOTDs is available here.

Technorati: totd glassfish v3 osgi apache felix bundles maven

How to pick a headlamp for night running ? - Petzl, Fenix, Princeton, Black Diamond, ...

2010-01-20T04:00:09-08:00

In order to be prepared for the upcoming TheRelay 2010, I'm planning to start running in the night. This is my first venture into night running and there are several tips to follow (reflective gear, run against traffic, no dark colors, no headphones, etc). One of the most important one is to wear a headlamp that can show the trail sufficiently ahead and keep you aware of any breaks in the sidewalk, a fallen branch, debris or may be even a loose pet.

As with any product, there are several headlamps available in the market and it's confusing for a first time buyer. There is Moxie, Petzl, Princeton Tec, Petzl, Black Diamond, Fenix and many others. Fortunately REI.com has a good variety of them and the beauty is that you can visit your local store and try them on. And as always, the staff is very knowledgeable about the product line and don't suck you into higher end products which may be an overkill for your adventure. And of course, you can compare the products on Amazon.com, read blog reviews, see product reviews from actual customers, read about them at epinions.com, tweet about it and get suggestions.

Some of the criteria to keep in mind while making your pick for a headlamp:

Lightweight - It should be lightweight as it'll be strapped to your head all the time you are running. Any extra weight to your head will be a bothering soon.
Good grip - The lamp should fit nicely on your head and not bounce up & down otherwise it'll be a pain very soon. Personally, I'd hate to run with holding headlamp in my hands instead.
Brightness - 35-50 lumens is bright enough for night running as it gives you 9-19 seconds of visibility depending upon your pace from (7 - 10 min/mile). See a more detailed table below.
Cost - The headlamps vary from $10 - $500. As with other products, invest wisely depending upon whether this is a one-time gig or you plan to continue this longer term. There are reasonable ones available close to $50.

And then there are several other factors like what kind and how many batteries are required (adds up to total weight), how long before it runs out, Halogen / LED, does it support multiple intensities, waterproof, and rechargeable unit.

Here is a comparison of the short listed headlamps on the features mentioned above:

Features / Models	Fenix 7	Petzl Tikka XP 2	Petzl Tikka Plus 2
Weight (with batteries)	??	3.1 ounces (88 gms)	2.9 oz (82 gms)
Lumens	7 - 225	60	50
Batteries	4 AA	3 AAA	3 AAA
Running time	2.5 - 210 hrs	80-160 hrs	55 - 140 hrs
Range (meters)	120m	17-60m	35m
Intensity	5 (Strobe, SOS, Warning)	2 (Flood/Spot)	2 (Flood only)
Waterproof	IPX-8	IPX-4	IPX-4
LED	Cree XR-E Q5	1 high-output LED / red LED	1 high-output LED / red LED
Cost	64.95	54.95	33.99
Where to buy ?	Amazon	Amazon	Amazon

After reading forums (here, here, here), product reviews (1, 2), 6 5* reviews @ Amazon, talking to friends, tweeting (1, 2, 3, 4) and getting a strong recommendation from the local REI store, I have decided to purchase Petzl Tikka Plus 2.

Black Diamond Sprinter got good reviews on runnersworld.com but there is no point paying additional $40 for the rechargeable unit. I'd rather buy a recharger separately and use it elsewhere as well. Fenix HP10 is similar to Fenix 7, slightly more expensive and no noticeable difference. It's not worth paying extra money for the lumens that are not required.

Read more about IP waterproof ratings. Basically, IPX-4 provide protection against splashing water and IPX-8 provide protection against continuous immersion beyond 1m.

Here is a table that provides the visibility (in seconds) for a 35m or 50m range headlamp:

Now Amazon has tight restrictions on the usage of pre-paid credit cards and so the payment cannot be split between two of them. All merchants allow such arrangement at least in their physical shop but I guess this is one disadvantage of online shopping.

What headlamp do you use for night running ?

Technorati: running night headlamp petzl fenix therelay gear

TOTD #117: Invoke a JAX-WS Web service from a Rails app deployed in GlassFish

2010-01-12T23:24:28-08:00

A user on GlassFish Forum tried invoking a JAX-WS Web service from a Rails application and faced some issues. This Tip Of The Day (TTOD) will discuss the different approaches and shows their current status.

A Rails app can be deployed on GlassFish in 3 different ways:

Directory Deployment in GlassFish v3 Server - TOTD #72 explains how to deploy a trivial Rails application (with just a scaffold) on GlassFish v3 server. Even though the blog uses a Rails application, any Rack-based application can be deployed on the server. This server is also the Reference Implementation for Java EE 6 and can also run Grails and Django applications.
Directory Deployment using light-weight GlassFish Gem - GlassFish Gem is a light-weight version of the full-blown server and is stripped to run, just like the server, any Rack-based application such as Merb, Rails, and Sinatra. TOTD #70 shows how to deploy the same application using GlassFish Gem.
WAR file in GlassFish v2.x or v3 - TOTD #73 explains how to deploy a Rails application as WAR file on GlassFish v2. The JNDI connection pooling part of the blog may be skipped to simplify the steps but the concepts are still valid. TOTD #44 shows how to do JNDI connection pooling for GlassFish v3. As GlassFish v2 has in-built support for session replication, TOTD #92 demonstrate how Rails application can leverage that functionality.

Now lets get to the issue reported by the user using these 3 deployment models.

First, lets deploy a simple Web service endpoint and generate a JAR file of the client-side artifacts:

This blog will use a simple Web service as defined in screencast #ws7. The Web service endpoint looks like:

package server;

import javax.jws.WebService;

/**
 * @author arungupta
 */
@WebService()
public class HelloService {
 public String sayHello(String name) {
 return "Hello " + name;
 }
}

Generate Web service client-side artifacts as:

~/samples/v3/rails/webservice/tmp >wsimport -keep http://localhost:8080/HelloWebService/HelloServiceService?wsdl
parsing WSDL...


generating code...


compiling code...

Create a Web service client jar file as:
```
jar cvf wsclient.jar ./server
```

Now lets write a Rails application and invoke this Web service:

Create a simple Rails application as:
```
jruby -S rails webservice
```
Optionally you may specify "-d mysql" to use MySQL database. Or better un-comment the following line:
```
# config.frameworks -= [ :active_record, :active_resource, :action_mailer ]
```
in "config/environment.rb" as no database interaction is required.

Create a controller and view as:

jruby script/generate controller home index

Update the Controller in "app/controllers/home_controller.rb" as:

include Java

class HomeController < ApplicationController
 def index
 service = Java::server.HelloServiceService.new
 port = service.getHelloServicePort

 @result = port.sayHello("Duke")
 end

end

Change the View in "app/views/home/index.html.erb" as:

<h1>Home#index</h1%gt;
<p>Find me in app/views/home/index.html.erb</p>

<%= @result %>

Now lets deploy this Web service using the 3 different deployment models mentioned above.

GlassFish v3 allows a directory-based deployment of Rails applications. This application needs to locate the Web service client classes. The "wsclient.jar" can be copied to the "lib" directory of Rails application ("webservice/lib" in our case), "domains/domain1/lib/ext" or "JRUBY_HOME/lib". The library can also be passed during deployment using "--libraries" switch. None of this approach seem to work correctly as explained in issue# 11408. So for now, invoking a JAX-WS Web service from a Rails application deployed directly on GlassFish v3 is not possible, at least until the bug is fixed.

In order to deploy the same application using GlassFish Gem, you can copy "wsclient.jar" to the "lib" directory of your Rails application. And also add the following line to "app/controllers/home_controller.rb":

require 'lib/wsclient.jar'

Alternatively you can copy it to "JRUBY_HOME/lib" directory if this Web service client is accessed my multiple applications. In this case there is no need to add any "require" statement to your Controller. Anyway, running the application as:

jruby -S glassfish

and accessing "http://localhost:3000/home/index" shows the following output:

And finally as explained in TOTD #73, bundle up your original Rails application as WAR and then deploy on GlassFish v3 as:

asadmin deploy webservice.war

Make sure to copy "wsclient.jar" to the "lib" directory of your Rails application and then Warbler will copy it to "WEB-INF/lib" of the generated WAR file. The output is shown as below:

So if you want to invoke a Metro/JAX-WS Web service from a Rails application, then run your Rails application using GlassFish Gem or deploying as a WAR file. It'll work on GlassFish v3 server when issue# 11408 is fixed.

Here are some additional links:

TOTD #104 also shows how popular Rails applications such as Redmine, Typo, and Substruct can be easily deployed on GlassFish.
Rails applications can be easily clustered using Apache + mod_proxy or nginx.

A complete archive of all the TOTDs is available here.

Technorati: totd glassfish v3 jruby rails webservice jax-ws metro

2009 Running Summary - 1286 miles, 71% of running days

2010-01-05T04:31:33-08:00

Here is a summary of my running logs in 2009:

And a bar chart that shows mileage for each day:

And finally a summary for each quarter:

Quarter	Summary
Jan 1 - Mar 31, 2009
Apr 1 - Jun 30, 2009
Jul 1 - Sep 30, 2009
Oct 1 - Dec 31, 2009

The last quarter was just terrible in terms of number of running days and pace but was a good recovery period as well. However I can certainly feel it in terms of the overall reduced pace. The biggest reasons for missed out running in 2009 were falling sick or traveling with no gym facility in the hotel.

Two goals for 2010:

Reduce the number of missed days of running - With no upcoming travel plans, this might be a good time to catch up on this goal.
Increase the overall mileage - This will require more than a few long distance runs and so will try to get them early on.

The charts shown above can be easily generated using using a Rails application or a Wicket application on GlassFish.

Technorati: glassfish running logs 2009

FREE Java EE 6 1-week online Codecamp - Jan 12th, 2010

2010-01-04T11:20:41-08:00

Happy New Year!

Java EE 6, GlassFish v3, and NetBeans 6.8 were released last month. Are you interested in learning how this awesome combination of technologies and products make your life simpler ? Do you want to brush up your skill set and learn to write Java EE 6 code using NetBeans 6.8 and GlassFish v3 ? Would you like to learn tips & techniques from the experts in GlassFish community ? Do you want to start 2010 with a complete immersion in Java EE 6 & GlassFish v3 ?

If answer to any of the above questions is "yes", then you should consider attending the upcoming free Java EE 6 online code camp. You are certainly welcome to attend the sessions otherwise as well :-)

The goal of this code camp is to let you write code, lots of code, exercising key Java EE 6 technologies.

The sessions are distributed over multiple days (schedule subject to change) as shown below:

Topics	Date/Day
Getting Java EE 6 sample codes	Jan 12th, 2010 (Tuesday)
Servlet 3.0	Jan 12th, 2010 (Tuesday)
Context and Dependency Injection (JSR 299)	Jan 13th, 2010 (Wednesday)
JPA 2.0	Jan 14th, 2010 (Thursday)
EJB 3.1	Jan 15th, 2010 (Friday)
JSF 2.0	Jan 18th, 2010 (Monday)
Java EE 6 End-to-end Examples	Jan 19th, 2010 (Tuesday)
GlassFish v3	Jan 20th, 2010 (Wednesday)

Here is what you need to do before attending the hands-on lab session:

Watch the corresponding video-taped sessions from Java EE 6 & GlassFish v3 Virtual Conference.
Send an email to javaee6-codecamp+subscribe@googlegroups.com to register for the course. All discussions can be seen from the web-based forum.
Download & Install JDK 6.0. (1.6.0_017+ for Operating Systems other than MacOS, 1.6.0_015+ for MacOS)
Download & Install NetBeans 6.8 with GlassFish v3 ("Java" or "All" bundle)

If you finish the homework from each lab, yeah there is optional homework ;-), then you'll also be awarded a certificate of completion.

So strap your seat belts and get ready for the Java EE 6 hands-on journey next week!

Always check Java EE 6 Online Codecamp for latest updates.

Technorati: conf glassfish v3 javaee handson lab

Java EE 6 & GlassFish v3 Deep Dive

2009-12-25T14:00:09-08:00

Merry Christmas!

Get a quick overview of Java EE 6 & GlassFish v3 in this 2-part Deep Dive video (running time of 19:17 mins) with Ed Ort from Sun Developer Network.

Here are some other relevant links:

Technorati: javaee glassfish v3 deepdive interview

IndicThreads Conference 2009 - Trip Report

2009-12-17T23:30:39-08:00

I attended my first IndicThreads conference, fourth otherwise, in Pune last week.

This local conference fits very well with "Think Globally, Act Locally" theme. The topics were quite varied ranging from Scala, Lift, Google App Engine, Android, GWT, Distributed Scrum, and of course Java EE 6 & GlassFish v3. All the speakers were well versed with the content and the audience was pretty interactive. Keeping global warming into consideration, the conference adopted the theme of Go Green. The conference setup provided a great opportunity for social networking.

Here are some of the reasons to attend / sponsor IndicThreads:

The conference is the oldest independent event in India focused on Java technology.
Pune contributed Rs 25,000 crore ($5.3 billion) in 2008-09 in IT exports with an impressive growth of 24%.
There are several major companies like Wipro, Infosys, Cognizant, Accenture, Sybase, Tech Mahindra, WebEx based in Pune.
October to March is the best time to visit Pune.
The city of Pune certainly offers a really fine cuisine, as evident in the images below.

I presented on:

and the slides are available. Unfortunately the graphics card of my MacBook failed the evening before the conference. So I had to rush to Apple Care center and retrieve my presentations from the hard disk. Fortunately that worked and the slides could be used. There are several blog pointers through out the presentation for the demos shown during the talk:

NetBeans and Eclipse tooling for Java EE 6 using GlassFish v3
GlassFish v3 Administration and REST interface
Ruby on Rails, Groovy and Grails, Python and Django deployment on GlassFish v3
Develop / Deploy / Debug Rails application using NetBeans and GlassFish v3
GlassFish Gem for Rails / Merb / Sinatra / Rack

Java EE 6 & GlassFish v3: Paving path for the future

Dynamic Languages Web Frameworks Indicthreads 2009

Get the complete set of presentations at the conference from this playlist:

Sun Microsystems raffled a Sunspot to the winner of "Java and Green" quiz. Here are the questions:

When was the GlassFish community started ? Tick the right answer.
1. 2004
2. 2005
3. 2006
4. 2007
Which framework is not supported natively by GlassFish ?
1. Ruby on Rails
2. Django
3. Groovy and Grails
4. Java EE
Which specifications is not new or did not get a major update in Java EE 6.
1. Context & Dependency Injection
2. Managed Beans
3. Servlet 3.0
4. JAX-WS
What 3 IDEs have support for Java EE 6 ?
Name 4 HTTP methods that let you perform RESTful Web services.
Sun Microsystems is now a division of Oracle.
1. True
2. False
Name 3 “green” initiatives at IndicThreads Conference 09.
When was IndicThreads.com created?
1. 2004
2. 2005
3. 2006
4. 2007
The United Nations Climate Change Conference is happening in:
1. Copenhagen
2. Belgium
3. Geneva

Lets see how many can you answer :-) Thanks Aaron Houston for sponsoring the Sunspot.

Watch Harshad Oak, first Java champion in India and founder of the conference, talks about how the conference, intended audience, message to sponsors, and other messages in this short video:

Here are some photographs from the conference:

And here is the complete set of pictures captured by me:

And here is the complete album captured by the conference:

Here are couple of additional reviews of the conference:

Looking forward to participate in this conference next year!

Technorati: conf indicthreads pune india glassfish javaee netbeans eclipse java

Pictures from GlassFish v3 Launch Party @ Santa Clara, California - Dec 16, 2009

2009-12-16T21:34:22-08:00

The GlassFish team celebrated the release of GlassFish v3 at Santa Clara earlier today. There was food, cake, beer, wine, tequila, tee-shirts, quiz contest, iPod shuffle raffles and above all the usual GlassFish spirit which made it extremely fun. See some of the pictures inlined:

And the complete album at:

See the complete set of GlassFish v3 Launch activities.

Did you conduct GlassFish launch party in your geo ? Please feel free to share pictures.

Technorati: glassfish v3 party santaclara

TOTD #116: GlassFish v3 Administration using JavaFX front-end - JNLP available

2009-12-08T04:00:55-08:00

As mentioned in TOTD #113, this Tip Of The Day (TOTD) provides a working version of the JavaFX front-end for GlassFish v3 administration.

Please click here to launch the JNLP or click here to a page that provides some introduction along with the link to JNLP. You may like to enable Java Console as explained in TOTD #114 for any log messages.

See a video of the tool in action:

Many thanks to Rajeshwar for providing feedback and helping me understand the RESTful interface better. TOTD #96 explains how the REST interface can be used.

Here is a TODO list in no particular order:

Show a splash screen after the startup to indicate server status
Allow the administration host/port to be changed
Tie the "server stats" with the server uptime instead of fetching once and then binding it locally
Provide dynamic updates of the monitoring data, currently its a snapshot
Convert the monitoring levels text boxes to radio buttons
Provide complete hints on setting monitoring level based upon the engines
Enable/Disable the buttons based upon the status of server running (or not)
Introduce charts to track dynamic shrink/expand of threads/pools/etc.
Probably something else that I'm forgetting :-)

How are you using JavaFX with GlassFish ?

How will you use GlassFish v3 REST interface in your tools ?

Technorati: totd javafx glassfish v3 rest web jruby rubyonrails rest administration monitoring management

Java EE 6 Training & Certifications - Register Early!

2009-12-07T04:00:23-08:00

Java EE 6 is now an approved specification, the Reference Implementation (GlassFish v3) and TCK will be released soon!

The associated training curriculum and certifications are being worked upon by Sun Learning Services. The curriculum has gone through a complete overhaul for Java EE 6 & GlassFish v3 and will be available in Q1 2010. If you are interested in getting notified when these new courses are released and also receive special introductory promotions, then please register here.

There are technology specific "deep-dive" training courses and tied to new technology specific certifications. You just need to specify your interest in the particular technology and will be contacted once the courses & certifications are available.

In the meanwhile, you can follow any of the existing Learning Paths to brush up your skills.

Technorati: javaee glassfish v3 training certification

TOTD #115: GlassFish in Eclipse - Integrated Bundle, Install Stand-alone or Update Existing plugin

2009-12-04T04:00:37-08:00

There are three options for Eclipse users interested in exploring GlassFish. They can either use an integrated bundle, install the GlassFish plug-in in an existing Eclipse version, or update an older GlassFish plugin in a stand-alone Eclipse to the latest version. These options are explained below.

GlassFish Tools Bundle for Eclipse 1.1 is an integrated bundle based on Eclipse 3.4.2 and includes GlassFish v2 and v3 Prelude pre-registered and configured and optionally JDK 1.6 U12. The work towards version 1.2 can be tracked by following the 1.1.x releases (1.1.7 is the latest). This new version is based on Eclipse 3.5.1, includes GlassFish v3 build 74 pre-registered and configured, several plugins (JSF Facelets, JAX-WS, Maven m2) and several Java EE 6 wizards to provide a seamless development and deployment experience with Java EE 6 & GlassFish v3. There are several other niceties in the newer release like pre-registered MySQL JDBC driver, updated Java EE 5 and Java EE 6 javadoc and code completion.

However what to do if you are already using an Eclipse version in your environment ?

The basic requirement is Eclipse 3.4+. A GlassFish plugin can be easily installed in any Eclipse 3.4+ and provides all the GlassFish-related functionality. The screencast #28 shows how to get started with Eclipse 3.4.2 and configure GlassFish as a standard server adapter.

If you are using Eclipse 3.5.0, then the standard technique described in the above screencast will not work because of the issue #280365. Fortunately, the bug report also has a workaround. Instead of using the "Download additional server adapter", install using the "Help", "Install New Software ..." and explicitly adding the GlassFish plugins update site. A screen snapshot looks like:

If you are using Eclipse 3.5.1, then the standard technique of "Download additional server adapter" works as described in the screencast #28. A screen snapshot looks like:

If you already have an existing version of GlassFish plugin installed, then it can be updated as described in TOTD #66. The process is much more simplified now and menu items have changed little bit in Eclipse 3.5.x - "Check for Updates" instead of "Software Updates ...". The screen snapshot looks like:

Now you can start developing your applications using Eclipse. Several blog entries have already been published:

TOTD #102 explains how to use Servlet 3.0 and EJB 3.1 wizards in Eclipse.
TOTD #99 explains how to create a JPA 2.0 compliant application.
TOTD #98 explains how to create a Metro JAX-WS Web service.
TOTD #54 shows how to create a JavaServer Faces application with Eclipse.

Future blogs will provide more details on the new features added recently. Until then, the GlassFish Plugin Release Notes provide a summary.

On a slightly different note, you can even run GlassFish with Eclipse Equinox OSGi runtime as explained in TOTD #103.

Technorati: totd eclipse glassfish v3 javaee

Java EE 6 & GlassFish v3 All Day Virtual Conference - Dec 15, 2009

2009-12-03T13:56:25-08:00

Java EE 6 specifications are already approved! The Reference Implementation in GlassFish v3 and TCK will be released next week. An all-day virtual conference is planned on Dec 15, 2009 to provide all the details about the platform and the associated RI. The event will allow you to hear from the Java EE 6 specification leads, product leads and the engineering team.

Mark your calendars and get ready to drink from the firehose!

The complete event details with abstracts, speaker bios and more is available here.

Technorati: javaee glassfish v3 conf webinar

TOTD #114: How to enable Java Console in Mac OS X, Windows, ... ?

2009-12-03T03:00:30-08:00

Debugging an applet running with Java plug-in or JNLP application running with Java Web Start in the browser requires the "Java Console" so that debugging messages printed using System.out and System.err can be seen. In Windows, there is a "Show Java Console" menu item in Firefox but clicking it still does not show the console. And this happens because the console window is disabled by default.

However the setting can be easily altered as explained below.

On Mac OS, open "Applications" -> "Utilities" -> "Java Preferences"
On Windows, open "Control Panel" -> "Java"
On any platform, type "javaws -viewer"

Click on the "Advanced" tab to see a window similar to the following on Mac OS X:

And the following on Windows:

Change the "Java Console" setting from "Hide console" to "Show console". Launching your JNLP from the browser next time now will also open the "Java Console" as shown below:

and debugging messages will be nicely printed in the console. Read more about the options displayed in the console here.

Technorati: osxtips windows java console jnlp debugging totd

Java EE 6 & GlassFish swimming to IndicThreads, Pune, India

2009-12-02T06:00:00-08:00

Java EE 6 is now a JCP approved specification. The Reference Implementation in GlassFish v3 is getting a final dressing and will be released soon, along with the TCK. Along with traditional Java EE applications, GlassFish v3 also allows to deploy dynamic languages & associated Web frameworks like Ruby-on-Rails, Groovy and Grails, Python and Django to be easily deployed. I'll be explaining these technologies and much more at Indic Threads 2009.

What sessions ? Java EE 6: Paving The Path for The Future (9:40am) and Dynamic Languages & Web Frameworks in GlassFish (3:40pm)

When ? Dec 11 & 12, 2009

Where ? Hotel Orbett, Pune, India

Register Now! The complete agenda is available and you can follow @indicj for the latest updates. Also learn how Indic Threads is going green!

If you are attending the conference, you can win a copy of the "Beginning Java EE 6 Platform with GlassFish v3" book by entering the quiz here.

This book is authored by Antonio Goncalves, a Java Champion, Paris JUG leader, a profound Open Source Evangelist and a senior software architect living in Paris. This is the first book on Java EE 6 & GlassFish v3 and a provides a good insight in the platform and it's associated implementation.

And unfortunately the Pune International Marathon is on the weekend before the conference. A little bit of heads up would've allowed me to reach the city little earlier and run at least the 1/2 marathon. Even the conference hotel does not seem to have a fitness center :( Guess, I'll try to run by Mutha River. Any other suggestions ?

Would you like to run together ?

What are the local delicacies that I must not miss ?

Anyway, check out the complete GlassFish Events Calendar:

The calendar feeds are available in formats.

Technorati: conf javaee glassfish india pune indicthreads