Arun Gupta, Miles to go ...

TOTD #112: Exposing Oracle database tables as RESTful entities using JAX-RS, GlassFish, and NetBeans

Content available at: http://blog.arungupta.me/2009/10/totd-112-exposing-oracle-database-tables-as-restful-entities-using-jax-rs-glassfish-and-netbeans/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #111: Rails Scaffold for a pre-existing table using Oracle and GlassFish

Content available at: http://blog.arungupta.me/2009/10/totd-111-rails-scaffold-for-a-pre-existing-table-using-oracle-and-glassfish/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #110: JRuby on Rails application using Oracle on GlassFish

Content available at: http://blog.arungupta.me/2009/10/totd-110-jruby-on-rails-application-using-oracle-on-glassfish/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #109: How to convert a JSF managed bean to JSR 299 bean (Web Beans) ?

Content available at http://blog.arungupta.me/2009/10/totd-109-how-to-convert-a-jsf-managed-bean-to-jsr-299-bean-web-beans/.

Posted by Arun Gupta in General  |  Comments[3]

TOTD #105: How to install Oracle Database 10g on Mac OS X (Intel) ?

Content available at: http://blog.arungupta.me/2009/09/totd-105-how-to-install-oracle-database-10g-on-mac-os-x-intel/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #104: GlassFish v3 Monitoring – How to monitor a Rails app using asadmin, JavaScript, jConsole, REST ?

Content available at: http://blog.arungupta.me/2009/09/totd-104-glassfish-v3-monitoring-how-to-monitor-a-rails-app-using-asadmin-javascript-jconsole-rest/

Posted by Arun Gupta in General  |  Comments[0]

TOTD #103: GlassFish v3 with different OSGi runtimes – Felix, Equinox, and Knoplerfish

Content available at http://blog.arungupta.me/2009/09/totd-103-glassfish-v3-with-different-osgi-runtimes-felix-equinox-and-knoplerfish/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #102: Java EE 6 (Servlet 3.0 and EJB 3.1) wizards in Eclipse

Content available at http://blog.arungupta.me/2009/09/totd-102-java-ee-6-servlet-3-0-and-ejb-3-1-wizards-in-eclipse/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #101: Applying Servlet 3.0/Java EE 6 “web-fragment.xml” to Lift – Deploy on GlassFish v3

TOTD #100 explained how to deploy Lift framework applications on GlassFish v3. As explained in TOTD #91, Java EE 6 defines how the framework configuration deployment descriptor can be defined in “META-INF/web-fragment.xml” in the JAR file of the framework instead of mixing it with "WEB-INF/web.xml" which is intended for application deployment descriptor aspects.

This Tip Of The Day (TOTD) explains how to leverage ”web-fragment.xml” to deploy a Lift application on a Java EE 6 compliant container. The original "lift-*.jar" files are untouched and instead a new JAR file is included that contains only the framework configuration deployment descriptor.

The generated "web.xml" from TOTD #100 looks like:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>
<filter>
 <filter-name>LiftFilter</filter-name>
 <display-name>Lift Filter</display-name>
 <description>The Filter that intercepts lift calls</description>
 <filter-class>net.liftweb.http.LiftFilter</filter-class>
</filter>
 

<filter-mapping>
 <filter-name>LiftFilter</filter-name>
 <url-pattern>/*</url-pattern>
</filter-mapping>

</web-app>

The deployment descriptor defines a Servlet Filter (LiftFilter) that registers the Lift framework with the Web container. And then it defines a URL mapping to "/*". All of this information is required by the Lift framework for request dispatching. And so that makes this fragment suitable for "web-fragment.xml".

Here are simple steps to make this change:

1. Remove “src/main/webapp/WEB-INF/web.xml” because no application specific deployment descriptors are required.
2. Include “lift-web-fragment.jar” in the “WEB-INF/lib” of your application by adding the following fragment in your “pom.xml”:
   

   <dependencies>
           
   . . .
   
     <!– web-fragment –>
     <dependency>
       <groupId>org.glassfish.extras</groupId>
       <artifactId>lift-web-fragment</artifactId>
       <version>1.0</version>
       <scope>runtime</scope>
     </dependency>
   </dependencies>
   
   . . .
   
   <repositories>
     <repository>
       <id>maven2-repository.dev.java.net</id>
       <name>Java.net Repository for Maven</name>
       <url>http://download.java.net/maven/2/</url>
     </repository>
   </repositories>
   
   

   This file contains only “META-INF/web-fragment.xml” with the following content:

   <web-fragment>
    <filter>
    <filter-name>LiftFilter</filter-name>
    <display-name>Lift Filter</display-name>
    <description>The Filter that intercepts lift calls</description>
    <filter-class>net.liftweb.http.LiftFilter</filter-class>
    </filter>
    
   
    <filter-mapping>
    <filter-name>LiftFilter</filter-name>
    <url-pattern>/*</url-pattern>
    </filter-mapping>
   </web-fragment>
   
   

3. Create the WAR file without “web.xml” by editing “pom.xml” and adding the following fragment:
   

   <build>
      . . .
     <plugins>
       . . .
       <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>
   

That's it, now now you can create a WAR file using “mvn package” and deploy this web application on GlassFish v3 latest promoted build (61 as of today) as explained in TOTD #100.

Technorati: totd glassfish v3 lift scala javaee6 servlet web-fragment

Posted by Arun Gupta in General  |  Comments[0]

TOTD #100: Getting Started with Scala Lift on GlassFish v3

Content available at: http://blog.arungupta.me/2009/09/totd-100-getting-started-with-scala-lift-on-glassfish-v3/.

Posted by Arun Gupta in General  |  Comments[0]

TOTD #99: Creating a Java EE 6 application using MySQL, JPA 2.0 and Servlet 3.0 with GlassFish Tools Bundle for Eclipse

TOTD #97 showed how to install GlassFish Tools Bundle for Eclipse 1.1. Basically there are two options - either install Eclipse 3.4.2 with WTP and pre-bundled/configured with GlassFish v2/v3, MySQL JDBC driver and other features. Or if you are using Eclipse 3.5, then you can install the plug-in separately and get most of the functionality.

TOTD #98 showed how to create a simple Metro/JAX-WS compliant Web service using that bundle and deploy on GlassFish.

This Tip Of The Day (TOTD) shows how to create a simple Java EE 6 application that reads data from a MySQL database using JPA 2.0 and Servlet 3.0 and display the results. A more formal support of Java EE 6/Servlet 3.0 is coming but in the meanwhile the approach mentioned below will work.

Lets get started!

1. Configure database connection - The key point to notice here is that the MySQL Connector/J driver is already built into the tool so there is no need to configure it explicitly.
   1. From "Window", "Show Perspective", change to the database perspective as shown below:
      
      
   2. In the "Data Source Explorer", right-click and click on "Database Connections" and select "New ...":
      
      
   3. Search for "mysql" and type the database name as "sakila":
      
      
      
      This blog uses MySQL sample database sakila. So please download and install the sample database before proceeding further.
   4. Click on "Next >" and specify the database configuration:
      
      
      
      Notice the "Drivers" indicate that the JDBC driver is pre-bundled so there is no extra configuration required. If you are using a stand-alone Eclipse bunde and installing the plugin separately, then you need to configure the MySQL JDBC driver explictily.
      
      The URL indicates the application is connecting to the sakila database. Click on "Test Connection" to test connection with the database and see the output as:
      
      
      
      and click on "Finish" to complete. The expanded database in the explorer looks like:
      
      
      
      The expanded view shows all the tables in the database.
2. Create the Web project & configure JPA
   1. Switch to JavaEE perspective by clicking "Window", "Choose Perspective", "Other ..." and choosing "Java EE".
   2. Create a new dynamic web project with the following settings:
      
      
      
      Only the project name needs to be specified and everything else is default. Notice the target runtime indicates that this is a Java EE 6 application. Click on "Finish".
   3. Right-click on the project, search for "facets" and enable "Java Persistence" as shown below:
      
      
   4. Click on "Further configuration available ..." and modify the facet as shown below:
      
      
      
      Make sure to disable "orm.xml" since we are generating a standard Java EE 6 web application. Choose "sakila" as the database. Click on "OK" and again on "OK" to complete the dialog.
3. Generate the JPA entities
   1. Right-click on the project, select "JPA Tools", "Generate Entities" as shown:
      
      
   2. Choose the schema "sakila":
      
      
      
      and click on "Next >". If no values are shown in the schema drop-down, then click on "Reconnect ...".
   3. Specify a package name for the generated entities as "model" and select "film" and "language" table:
      
      
      
      and click on "Finish". The "film" and "language" table are related so it would be nice if all the related tables can be identified and picked accordingly.
      
      Anyway this generates "model.Film" and "model.Language" classes and "persistence.xml" as shown below:
      
      
      
      Also notice that "web.xml" and "sun-web.xml" have been explicitly removed since they are not required by a Java EE 6 application.
   4. "model.Film" class needs to modified slightly because one of the columns is mapped to "Object" which is not a Serializable obect. So change the type of "specialFeatures" from Object to String and also change the corresponding getters/setters accordingly. The error message clearly conveyed during the initial deployment and so could be fixed. But it would be nice to generate the classes that will work out-of-the-box.
4. Create a Servlet client to retrieve/display data from the database
   1. Right-click on the project, select "New", "Class" and specify the values as:
      
      
      
      and click on "Finish". This class will be our Servlet client.
   2. Change the class such that it looks like:
      

      @WebServlet(urlPatterns="/ServletClient")
      public class ServletClient extends HttpServlet {
        @PersistenceUnit
        EntityManagerFactory factory;
      
        protected void doGet(HttpServletRequest req, HttpServletResponse resp)
               throws ServletException, IOException {
          ServletOutputStream out = resp.getOutputStream();
          List list = factory.createEntityManager().createQuery("select f from Film f where f.title like 'GL%';").getResultList();
          out.println("<html><table>");
          for (Object film : list) {
            out.print("<tr><td>" + ((Film)film).getTitle() + "</tr></td>");
          }
          out.println("</table></html>");
        }
      }
      

      
      and the imports as:
      

      import java.io.IOException;
      import java.util.List;
      
      import javax.persistence.EntityManagerFactory;
      import javax.persistence.PersistenceUnit;
      import javax.servlet.ServletException;
      import javax.servlet.ServletOutputStream;
      import javax.servlet.annotation.WebServlet;
      import javax.servlet.http.HttpServlet;
      import javax.servlet.http.HttpServletRequest;
      import javax.servlet.http.HttpServletResponse;
      
      import model.Film;
      
      

      Basically, this is a Servlet 3.0 specification compliant Servlet that uses @WebServlet annotation. It uses @PersistenceUnit to inject the generated JPA Persistence Unit which is then used to query the database. The database query return all the movies whose title start with "GL" and the response is displayed in an HTML formatted table.
   3. Right-click on the project and select "Run As", "Run on Server" and select GlassFish v3 latest promoted build (this blog used build 61) as:
      
      
      
      and click on "Finish". The output at "http://localhost:8080/HelloJPA/ServletClient" looks like:
      
      

Simple, easy and clean!

How are you using Eclipse and GlassFish - the consolidated bundle or standalone Eclipse + GlassFish plugin ?

Download GlassFish Tools Bundle for Eclipse now.

Please send your questions and comments to users@glassfishplugins.dev.java.net.

Please leave suggestions on other TOTD that you’d like to see. A complete archive of all the tips is available here.

Technorati: glassfish eclipse mysql jpa database

Posted by Arun Gupta in General  |  Comments[0]

TOTD #98: Create a Metro JAX-WS Web service using GlassFish Tools Bundle for Eclipse

Now that you've installed GlassFish Tools Bundle for Eclipse 1.1, lets use this bundle to create a simple Metro/JAX-WS compliant Web service and deploy on GlassFish. These steps will work with either Eclipse 3.4.2 or 3.5 with WTP Java EE support.

1. Lets create a simple "Dynamic Web Project" as shown below:
   
   
   
2. Name the project "HelloMetro" and take all other defaults:
   
   
   
   Click on "Finish" to complete the project creation.
3. Metro allows to create a Web service from a POJO class. So let's add a POJO to the project by right-clicking on the project and selecting "New", "Class" as shown below:
   
     
   
   Specify the package name as "server", class name as "HelloService" and click on "Finish".
4. Add a simple method to the newly generated class as:
   
   

   public String sayHello(String name) {
         return "Hello " + name + "!!";
   
   }
   

5. Expand the project, go to "HelloService.java" in "server" package, right-click, select "Web Services", "Create Web service".
6. Click on "Web service runtime: Apache Axis" and select "Metro (JAX-WS) Runtime" as the Web service runtime as shown below:
   
   
7. Move the slider on the left to top. This will enable testing of the deployed Web service. The completed configuration looks like:
   
   
   
   and click on "Next >".
8. Select the checkbox "Copy Metro library jars to the project" to resolve the references correctly as shown below:
   
   
   
   and click on "Next >". This bundles the application and deploys to GlassFish and provides an option to test the deployed Web service as shown below:
   
   
   
   Clicking on the "Launch" button shows the following output in the browser:
   
   
   
   The WSDL is hosted at "http://localhost:8083/HelloMetro/HelloServiceService?wsdl".
9. Click on "sayHello" method, click on "Add" and enter the value as "Duke" as shown below:
   
   
   
   Click on "Go" and the response is shown as:
   
   
   
   Clicking on "Source" in the response window shows the SOAP request/response messages as shown below:
   
   
10. Alternatively, you can click on "Finish" to complete the dialog. Then click on "Run" menu item, "Launch the Web Services Explorer" to see a screen as:
    
    
    
    Enter the URL of the WSDL in "WSDL URL" box as "http://localhost:8083/HelloMetro/HelloServiceService?wsdl" and click on "Go". Now you are seeing the similar screen to test the Web service within the integrated browser as shown below:
    
    
    

Posted by Arun Gupta in webservices  |  Comments[3]

TOTD #97: GlassFish Plugin with Eclipse 3.5

A new version of GlassFish Tools Bundle for Eclipse (ver 1.1) was recently released. The build contains

• Eclipse 3.4.2 IDE with WTP Java EE support
• GlassFish v2.1 pre-registered and configured
• GlassFish v3 Prelude pre-registered and configured
• JavaDB sample database pre-registered and configured
• GlassFish Plugin (1.0.29)
• MySQL JDBC driver registered to the IDE
• Maven m2 plugins
• JAX-WS Metro plugin
• GlassFish documentation
• And optionally, a JDK 1.6.

1. In "Help", "Install New Software", click on "Available Software Sites":
   
   
2. Search for "ajax" to see the output as:
   
   
3. Click on "Enabled" button to enable the site and see the change as below:
   
   
   
   click on "OK".
4. Expand the drop-down list box and chose the recently added "update site" as shown below:
   
   
   
   and it shows all the software available from that site as:
   
   
5. Take the defaults, click on "Next" and it shows the GlassFish plugin version number as shown below:
   
   
6. Click on "Next", accept the license by clicking on  "I accept ..." and click on "Finish" to start the installation.
   
   
   
   The IDE restarts after the installation is complete.
7. Now a new server can be added using "Servers" tab and it shows GlassFish as an option as shown below:
   
   

Posted by Arun Gupta in General  |  Comments[2]

TOTD #96: GlassFish v3 REST Interface to Monitoring and Management - JSON, XML, and HTML representations

GlassFish Monitoring allows you to monitor the state of various runtime components of the application server. This information is used to identify performance bottlenecks and tuning the system for optimal performance, to aid capacity planning, to predict failures, to do root cause analysis in case of failures and sometimes to just ensure that everything is functioning as expected.

GlassFish Management allows you to manage the running Application Server instance such as query/create/delete resources (JDBC, JMS, etc), stop/restart the instance, rotate the log and other similar functions.

GlassFish v3 exposes Monitoring and Management data using a REST Interface. This Tip Of The Day (TOTD) shows how to play with this new functionality. Rajeshwar's blog has lot of useful information on this topic.

Most of the functionality available in web-based Admin Console and CLI (asadmin) is now available using the REST interface. Both of these are pre-built tools that ships with the GlassFish bundle. The REST interface is a lower level API that enables toolkit developers and IT administrators to write their custom scripts/clients using language of their choice such as Java, JavaScript, Ruby or Groovy.

The default URL for the REST interface of monitoring is "http://localhost:4848/monitoring/domain" and for the management is "http://localhost:4848/management/domain". Each URL provides an XML, JSON and HTML representation of the resources. If a web browser is used then a HTML representation is returned and displayed nicely in the browser. Rajeshwar's blog described a Java client written using Jersey Client APIs that can be used to make all the GET/PUT/POST/DELETE requests. This blog will use something more basic, and extremely popular, to make all the RESTful invocations - cURL.

At this time the monitoring resources are read-only (GET) and management can be done using GET/POST/DELETE methods. POST is used for creating and updating resources/objects and the updates can be partial.
 
Lets get started.

1. Download the latest continuous build from the trunk and unzip. This functionality is also available in the Web profile bundle. This blog is using build #2023.
2. Start the application server as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >./bin/asadmin start-domain --verbose Aug 19, 2009 9:52:45 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info INFO: JVM invocation command line: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java -cp . . . INFO: felix.fileinstall.dir            /Users/arungupta/tools/glassfish/v3/2023/glassfishv3/glassfish/domains/domain1/autodeploy-bundles Aug 19, 2009 9:53:05 AM  INFO: felix.fileinstall.debug          1 Aug 19, 2009 9:53:05 AM  INFO: felix.fileinstall.bundles.new.start          true

   
   
3. Monitoring information - Lets monitor this GlassFish instance using the REST interface.
1. Retrieve JSON information - As mentioned above, the monitoring resources are read-only and so the information can be accessed as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/json" http://localhost:4848/monitoring/domain -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /monitoring/domain HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/json > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 17:40:29 GMT < {Domain:{},"child-resources":["http://localhost:4848/monitoring/domain/server"]} * Connection #0 to host localhost left intact * Closing connection #0

   
   The command explicitly asks for JSON representation of the resources. The outbound headers are prepended with ">" and inbound headers with "<". And the JSON representation is shown in the last line as:
   
   

   {Domain:{},"child-resources":["http://localhost:4848/monitoring/domain/server"]}

   
   The key element to remember here is "http://localhost:4848/monitoring/domain/server" which can be used to retrieve more monitoring information.
   
2. XML represetation: Lets change the command to ask for XML representation as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/xml" http://localhost:4848/monitoring/domain -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /monitoring/domain HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/xml > < HTTP/1.1 200 OK < Content-Type: application/xml < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 17:43:51 GMT < <Domain>     <child-resource>http://localhost:4848/monitoring/domain/server</child-resource> </Domain> * Connection #0 to host localhost left intact * Closing connection #0

   
   The command changes the "Accept" header to "application/xml" and now the XML representation of the monitoring resources is returned as:
   
   

   <Domain>     <child-resource>http://localhost:4848/monitoring/domain/server</child-resource> </Domain>

   
   
3. HTML representation: The command can be altered to get the HTML representation as "curl -H "Accept: text/html" http://localhost:4848/monitoring/domain -v". But HTML is more pleasant when rendered by a browser and so viewing the page "http://localhost:4848/monitoring/domain" in the browser is shown as:
   
   
4. Get more information: As mentioned above, more information about this GlassFish instance can be accessed by GETing from "http://localhost:4848/monitoring/domain/server" and here is the result:
   
   

   </tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/json" http://localhost:4848/monitoring/domain/server -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /monitoring/domain/server HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/json > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 17:56:41 GMT < {Server:{},"child-resources":["http://localhost:4848/monitoring/domain/server/webintegration", "http://localhost:4848/monitoring/domain/server/transaction-service", "http://localhost:4848/monitoring/domain/server/network", "http://localhost:4848/monitoring/domain/server/jvm", "http://localhost:4848/monitoring/domain/server/web", "http://localhost:4848/monitoring/domain/server/realm", "http://localhost:4848/monitoring/domain/server/http-service"]} * Connection #0 to host localhost left intact * Closing connection #0

   
   An HTML rendering of this representation looks like:
   
   
   
   You can keep clicking on the links and more detailed information about that resource is displayed. This is just one HTML representation and is purposely kept light-weight. You can certainly grab the XML representation and apply an XSLT to generate your own HTML rendering.
   
   The monitoring levels for different modules can be easily changed using the management REST interface as explained below.
4. Management of the GlassFish instance
1. Lets see all the options supported by management REST interface as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -X OPTIONS http://localhost:4848/management/domain -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > OPTIONS /management/domain HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: */* > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 18:07:14 GMT < {   "Method":"GET"   "Method":"PUT" } * Connection #0 to host localhost left intact * Closing connection #0

   
   Specifying "-X OPTIONS" switch displays the various HTTP methods supported by the REST interface. Even though the results show GET and PUT, but it really means GET and POST (issue #9177). Lets try "GET" first. 
2. GET JSON information as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/json" http://localhost:4848/management/domain -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /management/domain HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/json > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 18:14:46 GMT < {Domain:{"log-root" : "${com.sun.aas.instanceRoot}/logs","application-root" : "${com.sun.aas.instanceRoot}/applications","locale" : "","version" : "re-continuous"},"child-resources":["http://localhost:4848/management/domain/configs", "http://localhost:4848/management/domain/resources","http://localhost:4848/management/domain/servers", "http://localhost:4848/management/domain/property","http://localhost:4848/management/domain/applications", "http://localhost:4848/management/domain/system-applications","http://localhost:4848/management/domain/stop", "http://localhost:4848/management/domain/restart","http://localhost:4848/management/domain/uptime", "http://localhost:4848/management/domain/version","http://localhost:4848/management/domain/rotate-log", "http://localhost:4848/management/domain/host-port"]} * Connection #0 to host localhost left intact * Closing connection #0

   
   As the result shows, there are several RESTful URLs available (in "child-resources" element) to manage this GlassFish instance. For example:
   
1. Show the host/port of GlassFish instance as:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/host-port -v

   
   will show the result as:
   
   

   {"GetHostAndPort":{"value" : "dhcp-usca14-132-79.SFBay.Sun.COM:8080"}}

   
   
2. Show that web-based Admin Console is pre-installed as system application using:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/system-applications/application/__admingui -v

   
   will show the result as:
   
   

   {__admingui:{"libraries" : "","availability-enabled" : "false","enabled" : "true","context-root" : "","location" : "${com.sun.aas.installRootURI}/lib/install/applications/__admingui","description" : "","name" : "__admingui","directory-deployed" : "true","object-type" : "system-admin"},"child-resources":["http://localhost:4848/management/domain/system-applications/application/__admingui/module"]}

   
   
3. Query the monitoring levels of different modules as:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels -v

   
   to see the result as:
   
   

   {ModuleMonitoringLevels:{"transaction-service" : "OFF","ejb-container" : "OFF","jdbc-connection-pool" : "OFF","orb" : "OFF","http-service" : "OFF","connector-connection-pool" : "OFF","jms-service" : "OFF","connector-service" : "OFF","jvm" : "OFF","thread-pool" : "OFF","web-container" : "OFF"},"child-resources":[]}

   
   And then change the monitoring level of Web container as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -X POST -d "web-container=ON" -H "Accept: application/json" http://localhost:4848/management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > POST /management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/json > Content-Length: 16 > Content-Type: application/x-www-form-urlencoded > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 22:01:31 GMT < * Connection #0 to host localhost left intact * Closing connection #0 "http://localhost:4848/management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels" updated successfully

   
   The last line shows that the monitoring level is successfull updated and can be verified again as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/json" http://localhost:4848/management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /management/domain/configs/config/server-config/monitoring-service/module-monitoring-levels HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/json > < HTTP/1.1 200 OK < Content-Type: application/json < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 22:36:47 GMT < * Connection #0 to host localhost left intact * Closing connection #0 {ModuleMonitoringLevels:{"transaction-service" : "OFF","ejb-container" : "OFF","jdbc-connection-pool" : "OFF","orb" : "OFF","http-service" : "OFF","connector-connection-pool" : "OFF","jms-service" : "OFF","connector-service" : "OFF","jvm" : "OFF","thread-pool" : "OFF","web-container" : "ON"},"child-resources":[]}

4. Stop this GlassFish instance using:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/stop -v

   
   Or restart the instance using:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/restart -v

5. Create a JDBC resource using an existing connection pool
   
1. Lets see all the resources that are available:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/resources -v

   
   and the results are shown as:
   
   

   {Resources:{},"child-resources":["http://localhost:4848/management/domain/resources/jdbc-connection-pool", "http://localhost:4848/management/domain/resources/jdbc-resource"]}

   
   
2. View all the JDBC connection pools as:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/resources/jdbc/connection-pool -v

   
   and the results are shown as:
   
   

   {JdbcConnectionPool:{},"child-resources":["http://localhost:4848/management/domain/resources/jdbc-connection-pool/__TimerPool", "http://localhost:4848/management/domain/resources/jdbc-connection-pool/DerbyPool"]}

   
   
3. See all the JDBC resources available as:
   
   

   curl "Accept: application/json" http://localhost:4848/management/domain/resources/jdbc-resource -v

   
   and the results are shown as:
   
   

   {JdbcResource:{},"child-resources":["http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/__TimerPool", "http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/__default"]}

   
   
4. See all the OPTIONS accepted for JDBC resource creation as:
   
   

   curl -X OPTIONS -H "Accept: application/json" http://localhost:4848/management/domain/resources/jdbc-resource -v

   
   with the result as:
   
   

   {   "Method":"POST",   "Message Parameters":{     "id":{"Acceptable Values":"","Default Value":"","Type":"class java.lang.String","Optional":"false"},     "enabled":{"Acceptable Values":"","Default Value":"true","Type":"class java.lang.Boolean","Optional":"true"},     "description":{"Acceptable Values":"","Default Value":"","Type":"class java.lang.String","Optional":"true"},     "target":{"Acceptable Values":"","Default Value":"","Type":"class java.lang.String","Optional":"true"},     "property":{"Acceptable Values":"","Default Value":"","Type":"class java.util.Properties","Optional":"true"},     "connectionpoolid":{"Acceptable Values":"","Default Value":"","Type":"class java.lang.String","Optional":"false"}   }   "Method":"GET"

   
   
5. Finally, create the JDBC resource as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -d "id=jdbc/sample&connectionpoolid=DerbyPool" http://localhost:4848/management/domain/resources/jdbc-resource -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > POST /management/domain/resources/jdbc-resource HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: */* > Content-Length: 42 > Content-Type: application/x-www-form-urlencoded > < HTTP/1.1 201 Created < Content-Type: text/html < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 20:45:51 GMT < * Connection #0 to host localhost left intact * Closing connection #0 "http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/sample" created successfully.

   
   Note, this is a POST request. The JDBC resource name and JDBC connection pool id are passed as CLI parameters using "-d" switch. The last line shows that the JDBC resource was created successfully.
6. And finally query the JDBC Resources again as:
   
   

   curl -H "Accept: application/json" http://localhost:4848/management/domain/resources/jdbc-resource -v

   
   to see the updated result as:
   
   

   {JdbcResource:{},"child-resources":["http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/__TimerPool", "http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/__default", "http://localhost:4848/management/domain/resources/jdbc-resource/jdbc/sample"]}


Similarly JDBC connection pools can be created.
3. POST can be used to update the top-level attributes such as "log-root" and "application-root". The name of these attributes are shown in the result of GET.
   
4. As earlier, XML representation of management resources can be obtained as:
   
   

   ~/tools/glassfish/v3/2023/glassfishv3 >curl -H "Accept: application/xml" http://localhost:4848/management/domain -v * About to connect() to localhost port 4848 (#0) *   Trying ::1... connected * Connected to localhost (::1) port 4848 (#0) > GET /management/domain HTTP/1.1 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3 > Host: localhost:4848 > Accept: application/xml > < HTTP/1.1 200 OK < Content-Type: application/xml < Transfer-Encoding: chunked < Date: Wed, 19 Aug 2009 18:17:07 GMT < <Domain log-root="${com.sun.aas.instanceRoot}/logs" application-root="${com.sun.aas.instanceRoot}/applications" locale="" version="re-continuous">     <child-resource>http://localhost:4848/management/domain/configs</child-resource>     <child-resource>http://localhost:4848/management/domain/resources</child-resource>     <child-resource>http://localhost:4848/management/domain/servers</child-resource>     <child-resource>http://localhost:4848/management/domain/property</child-resource>     <child-resource>http://localhost:4848/management/domain/applications</child-resource>     <child-resource>http://localhost:4848/management/domain/system-applications</child-resource>     <child-resource>http://localhost:4848/management/domain/stop</child-resource>     <child-resource>http://localhost:4848/management/domain/restart</child-resource>     <child-resource>http://localhost:4848/management/domain/uptime</child-resource>     <child-resource>http://localhost:4848/management/domain/version</child-resource>     <child-resource>http://localhost:4848/management/domain/rotate-log</child-resource>     <child-resource>http://localhost:4848/management/domain/host-port</child-resource> * Connection #0 to host localhost left intact * Closing connection #0

   
   Just changing the "Accept" header to "application/xml" did the trick.
   
5. And an HTML representation can be obtained by viewing the URL "http://localhost:4848/management/domain" in the browser with result as:
   
   
   

Posted by Arun Gupta in General  |  Comments[8]

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 #93 showed how to get started with Java EE 6 using NetBeans 6.8 M1 and GlassFish v3 by building a simple Servlet 3.0 + JPA 2.0 web application. TOTD #94 built upon it by using Java Server Faces 2 instead of Servlet 3.0 for displaying the results. However we are still using a POJO for all the database interactions. This works fine if we are only reading values from the database but that's not how a typical web application behaves. The web application would typically perform all CRUD operations. More typically they like to perform one or more CRUD operations within the context of a transaction. And how do you do transactions in the context of a web application ? Java EE 6 comes to your rescue.

The EJB 3.1 specification (another new specification in Java EE 6) allow POJO classes to be annotated with @EJB and bundled within WEB-INF/classes of a WAR file. And so you get all transactional capabilities in your web application very easily.

This Tip Of The Day (TOTD) shows how to enhance the application created in TOTD #94 and use EJB 3.1 instead of the JSF managed bean for performing the business logic. There are two ways to achieve this pattern as described below.

Lets call this TOTD #95.1

1. The easiest way to back a JSF page with an EJB is to convert the managed bean into an EJB by adding @javax.ejb.Stateless annotation. So change the  "StateList" class from TOTD #94 as shown below:
   
   

   @javax.ejb.Stateless @ManagedBean public class StateList {     @PersistenceUnit     EntityManagerFactory emf;     public List<States> getStates() {         return emf.createEntityManager().createNamedQuery("States.findAll").getResultList();     } }

   
   The change is highlighted in bold, and that's it!

1. Right-click on the project, select "New", "Session Bean ..." and create a stateless session bean by selecting the options as shown below:
   
   
   
   This creates a stateless session with the name "StateBeanBean" (bug #170392 for redundant "Bean" in the name).
2. Simplify your managed bean by refactoring all the business logic to the EJB as shown below:
   
   

   @Stateless public class StateBeanBean {     @PersistenceUnit     EntityManagerFactory emf;          public List<States> getStates() {         return emf.createEntityManager().createNamedQuery("States.findAll").getResultList();     } }

   
   and
   
   

   @ManagedBean public class StateList {     @EJB StateBeanBean bean;     public List<States> getStates() {         return bean.getStates();     } }

   
   In fact the EJB code can be further simplified to:
   
   

   @Stateless public class StateBeanBean {     @PersistenceContext     EntityManager em;         public List<States> getStates() {         return em.createNamedQuery("States.findAll").getResultList();     } }

   
   The changes are highlighted in bold.
   

Posted by Arun Gupta in General  |  Comments[1]