Arun Gupta's Blog

Arun Gupta is a GlassFish Evangelist focusing on Web Tier at Sun. He was the spec lead for APIs in the Java platform, committer in multiple Open Source projects, participated in standard bodies and contributed to Java EE and SE releases.

GlassFish setup for 120 programmers in University of Copenhagen

Sun Tech Days Hyderabad 2009

• WSIT: Security, Reliability, Transactional, and .NET-interoperable Web services (slides). The screencast #ws7 is the demo shown during the talk.
• GlassFish & Future of Java EE (slides)

TOTD #69: GlassFish High Availability/Clustering using Sun Web Server + Load Balancer Plugin on Windows Vista

1. Install the required software
1. Download JDK (if not already installed).
2. Download and Install GlassFish v2.1. Make sure to configure using "ant -f setup-cluster.xml". This will ensure that the created domain is capable of creating clusters and can perform in-memory session replication for applications deployed on the cluster.
3. Download and Install Sun Web Server. The process is very simple by unzipping the downloaded bundle, clicking on "setup.exe" and taking all the defaults.
4. Download GlassFish Enterprise Profile for Load Balancer plugin bits. Start the install by clicking on the downloaded file and select the options as shown below:
   
   
   
5. Copy the following "loadbalancer.xml" in "https-<host>" (replace <host> with the host name of your machine) directory of Sun Web Server installation directory:
   
   

   <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE loadbalancer PUBLIC "-//Sun Microsystems Inc.//DTD Sun Java System Application Server 9.1//EN" "file:///C:/Sun/WebServer7/https-LH-KRKZDW6CJE1V/config/sun-loadbalancer_1_2.dtd "> <loadbalancer>  <cluster name="cluster1" policy="round-robin" policy-module="">   <instance name="instance1" enabled="true" disable-timeout-in-minutes="60" listeners="https://localhost:38080" weight="100"/>   <instance name="instance2" enabled="true" disable-timeout-in-minutes="60" listeners="https://localhost:38081" weight="100"/>   <web-module context-root="/clusterjsp" disable-timeout-in-minutes="30" enabled="true" error-url=""/>   <health-checker interval-in-seconds="7" timeout-in-seconds="5" url="/"/>  </cluster>  <property name="response-timeout-in-seconds" value="120"/>  <property name="reload-poll-interval-in-seconds" value="7"/>  <property name="https-routing" value="false"/>  <property name="require-monitor-data" value="false"/>  <property name="active-healthcheck-enabled" value="false"/>  <property name="number-healthcheck-retries" value="3"/>  <property name="rewrite-location" value="true"/> </loadbalancer>

   
   The parameters to be changed are highlighted in bold and explained below:
   
1. Sun Web Server installation directory
2. HTTP port of instances created in the cluster. The ports specified are the default ones and can be found by clicking on the instance as shown below:
   
   
3. Context root of the application that will be deployed in the cluster. The Domain Administration Server (DAS) can be configured to populate this file whenever any application is deployed to the cluster.
2. Create the cluster as explained in TOTD #67. The admin console shows the following screenshot after the cluster is created and all instances are created/started:
   
    
   
   and the following for 2 instances:
   
   
   
   
3. Deploy "clusterjsp" as explained in TOTD #67. The admin console shows the following screenshot after "clusterjsp" is deployed:
   
   
   
4. Start Sun Web Server using "startserv.bat" in "https-<host>" directory.

• Load balancing for Glassfish V2 deployments using BIG-IP System
• Configure the Cluster/Load Balancer with GlassFish v2

TOTD #68: Installing Zones in Open Solaris 2008/11 on Virtual Box

GlassFish swimming to Singapore, Delhi, Bangalore, and Hyderabad - Feb 2009

	Singapore: Feb 12 & 13
	Delhi: Feb 14, 20, & 21
	Bangalore: Feb 15, 16, & 17
	Hyderabad: Feb 18 & 19

And I'll be there at Sun Tech Days in Hyderabad. Ask me anything about GlassFish :) Did you know James Gosling is going to be there ? Check out agenda, details and register today!

• Singapore Sling (Raffles) - Not a big crab fan ;-)
• Delhi Chaat (multiple venues)
• Bangalore Dosa (multiple venues)
• Hyderabadi Biryani (Paradise, Cafe Bahar)

LOTD #16: Hotspot Flags, JRuby Version String, and JRuby/MRI Benchmark

Rails/Merb and GlassFish at Super Happy Dev House 30

Supper Happy Dev House is "a premier monthly hackathon event that combines serious and not-so-serious productivity with a fun and exciting party atmosphere."

• JRuby - "It's just Ruby!" with passing over 55,000 compliance tests and continuous performance improvements.
• NetBeans - light-weight and intuitive IDE for Rails development/deployment
• GlassFish - robust deployment environment for Rails/Merb applications

TOTD #67: How to front-end a GlassFish Cluster with Apache + mod_jk on Mac OSX Leopard ?

• How to Loadbalance GlassFish Cluster with Apache Loadbalancer
• GlassFish Clustering in under 10 minutes
• How to install tomcat mod_jk on Mac OS X Leopard

1. First, lets create a 3-instance cluster following the screencast at GlassFish Clustering in under 10 minutes. Use the cluster name as "cluster1" and instance names as "instance1", "instance2", "instance3". The admin console will look like:
   
   
   
   Deploy "clusterjsp" and make sure it works using port hopping as explained in the screencast. Click on each instance to identify their associated HTTP port.
2. Define "jvmRoute" and "enableJK" properties on the newly created cluster as:
   
   

   ~/samples/v2/clustering/glassfish/bin >./asadmin create-jvm-options --target cluster1 "-DjvmRoute=\${AJP_INSTANCE_NAME}" Command create-jvm-options executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-jvm-options --target cluster1 "-Dcom.sun.enterprise.web.connector.enableJK=\${AJP_PORT}" Command create-jvm-options executed successfully.

   
   These properties are required to enable "stickiness" for "mod_jk". More details about how these properties are used internally is explained here.
   
3. Configure the above system properties for each instance in the cluster as shown:
   
   

   ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance1 AJP_INSTANCE_NAME=instance1 Command create-system-properties executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance1 AJP_PORT=9090 Command create-system-properties executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance2 AJP_INSTANCE_NAME=instance2 Command create-system-properties executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance2 AJP_PORT=9091 Command create-system-properties executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance3 AJP_INSTANCE_NAME=instance3 Command create-system-properties executed successfully. ~/samples/v2/clustering/glassfish/bin >./asadmin create-system-properties --target instance3 AJP_PORT=9092 Command create-system-properties executed successfully.

   
   Note the value of "AJP_PORT" property for each instance, this will be used for configuring "mod_jk" later. You may have to restart the cluster in order for these properties to be synchronized for each instance. This can be easily done using the admin console as explained in the screencast above.
   
4. Install httpd: Mac OS X Leopard 10.5.6 comes bundled with Apache httpd 2.2, so that's cool! Otherwise it can be downloaded from httpd.apache.org. However in the pre-installed version there are some intricacies with directory names that are explained below.
5. Lets install and configure "mod_jk" in "httpd".
1. The mod_jk binaries for Mac OSX are supposedly available at www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/macosx/. But installing the available module in httpd gives the following error:
   
   

   httpd: Syntax error on line 116 of /private/etc/apache2/httpd.conf: Cannot load /usr/libexec/apache2/mod_jk-1.2.25-httpd-2.2.4.so into server: dlopen(/usr/libexec/apache2/mod_jk-1.2.25-httpd-2.2.4.so, 10): no suitable image found.  Did find:\n\t/usr/libexec/apache2/mod_jk-1.2.25-httpd-2.2.4.so: mach-o, but wrong architecture

2. The alternative is to build "mod_jk". Fortunately it turned out to be a straight forward process because of this blog.
1. Download latest Connectors source code (version 1.2.27). The file "BUILD.txt" (included in the source bundle) provide clear instructions to build and described below as well.
2. Configure the build environment as shown:
   
   

   ~/workspaces/tomcat-connectors-1.2.27-src/native >./configure --with-apxs=/usr/sbin/apxs

   
   It shows the output as:
   
   

   . . . checking for target platform... unix no apache given no netscape given configure: creating ./config.status config.status: creating Makefile config.status: creating apache-1.3/Makefile config.status: creating apache-1.3/Makefile.apxs config.status: creating apache-2.0/Makefile config.status: creating apache-2.0/Makefile.apxs config.status: creating common/Makefile config.status: creating common/list.mk config.status: creating common/jk_types.h config.status: creating jni/Makefile config.status: creating common/portable.h config.status: executing depfiles commands

3. Edit Edit "native/apache-2.0/Makefile.apxs" and add "-arch x86_64" as described here. Please note that this string needs to be specified twice.
4. Invoke "make" and "mod_jk.so" is generated in "native/apache-2.0" directory.
3. Copy the generated "mod_jk.so" as:
   
   

   ~/workspaces/tomcat-connectors-1.2.27-src/native/apache-2.0 >sudo cp mod_jk.so /usr/libexec/apache2/

4. Load the "mod_jk" module in httpd by editing "/etc/apache2/httpd.conf". Please note another similar file exists in "/etc/httpd/httpd.conf" but ignore that one. Add the following as the last "LoadModule" line:
   
   

   LoadModule jk_module     libexec/apache2/mod_jk-1.2.25-httpd-2.2.4.so

5. Configure "mod_jk" by adding the following lines immediately below the previously "LoadModule" line:
   
   

   JkWorkersFile /etc/apache2/worker.properties # Where to put jk logs JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " # JkRequestLogFormat set the request format JkRequestLogFormat "%w %V %T" # Send all jsp requests to GlassFish JkMount /*.jsp loadbalancer

   
   The key lines in this configuration are the first and the last one. The first line informs "mod_jk" about the location of "worker.properties" file (explained later). The last line instructs to redirect only JSP requests. This will allow the static content such as images, text files, and media to be served from "httpd" itself.
   
   Also create the log directory specified in the configuration as:
   
   

   sudo mkdir /var/log/httpd

6. Create a new file "/etc/apache2/worker.properties". Again, this is not in "/etc/httpd" directory. Use the following contents:
   
   

   # Define 1 real worker using ajp13 worker.list=loadbalancer # Set properties for instance1 worker.instance1.type=ajp13 worker.instance1.host=localhost worker.instance1.port=9090 worker.instance1.lbfactor=50 worker.instance1.cachesize=10 worker.instance1.cache_timeout=600 worker.instance1.socket_keepalive=1 worker.instance1.socket_timeout=300 # Set properties for instance2 worker.instance2.type=ajp13 worker.instance2.host=localhost worker.instance2.port=9091 worker.instance2.lbfactor=50 worker.instance2.cachesize=10 worker.instance2.cache_timeout=600 worker.instance2.socket_keepalive=1 worker.instance2.socket_timeout=300 # Set properties for instance3 worker.instance3.type=ajp13 worker.instance3.host=localhost worker.instance3.port=9092 worker.instance3.lbfactor=50 worker.instance3.cachesize=10 worker.instance3.cache_timeout=600 worker.instance3.socket_keepalive=1 worker.instance3.socket_timeout=300 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=instance1,instance2,instance3

   
   Read more about worker.properties format. Essentially this file is used to load-balance a 3-instance cluster and specify configuration values for each instance. Note that the value of "worker.instanceX.port" for instance X is exactly same as specified during instance configuration earlier.
   
6. Copy "tomcat-ajp.jar" from the "lib" directory of the latest Tomcat 5.5.x, commons-logging.jar (version 1.1.1), and commons-modeler.jar (version 2.0.1) to GLASSFISH_HOME/lib. This is done as:
   
   

   ~/samples/v2/clustering/glassfish/lib >cp ~/tools/apache-tomcat-5.5.27/server/lib/tomcat-ajp.jar . ~/samples/v2/clustering/glassfish/lib >cp ~/Downloads/commons-logging-1.1.1/commons-logging-1.1.1.jar . ~/samples/v2/clustering/glassfish/lib >cp ~/tools/commons-modeler-2.0.1/commons-modeler-2.0.1.jar .

   
   You may have to restart cluster in order for these JARs to be loaded by each instance.
7. An "httpd" instance is already running on port# 80 in my particular instance of Mac OS X. Instead of mangling with that, I decided to change the listening port for the new instance that will be spawn for out front-end. This can be easily done by editing "/etc/apache2/httpd.conf" and looking for lines similar to:
   
   

   #Listen 12.34.56.78:80 Listen 80

   
   And change "Listen 80" to "Listen 81".

• High Availability Adminstration Guide (online, pdf).
• GlassFish High Availability Reference Configurations.
• GlassFish High Availability Webinar.

"Sparks of passion" in the "world of Open Source" - Archana N contributes to GlassFish Documentation

Free GlassFish Webinar for Students at OSUM

GlassFish in CEUI and Campus Party

• Plática de Glassfish en CEUI (GlassFish chat in CEUI)
• Historia de Glassfish (History of GlassFish)
• Qué es Glassfish? (What is GlassFish ?)
• Running Glassfish v2 UR2 on Windows 7
  
• Corriendo Glassfish v2 UR2 en Windows 7

Singapore Tech Days 2009 - Wrapup

Singapore Tech Days 2009 - Talent Show, Cloud Camp, GlassFish Demo

Sun Tech Days 2009, Singapore - Welcome Reception

Sun Tech Days 2009, Singapore - Day 1

1. GlassFish v3 OSGi-compliance and quick startup time
   
   Download GlassFish v3 Prelude from here, unzip, and start the server as
   
   

   glassfish/bin/asadmin start-domain --verbose

   
   to see a message something like:
   
   

   INFO: GlassFish v3 Prelude startup time : Felix(1732ms) startup services(1091ms) total(2823ms)

   
   The GlassFish v3 container starts up fairly quickly, 2.8 secs in this case, without starting any application-specific container. The container is using OSGi R4 APIs and Apache Felix as the runtime. This allows any standard OSGi bundle to be easily deployed in GlassFish v3. The underlying OSGi runtime can be easily replaced with Knopflerfish or Equinox because standard R4 APIs are used. As you notice, Felix start up time is explicitly shown in the startup message.
   
   The quick start up is possible because containers, such as Web container that serves web applications, is started only when the first Web application is deployed. No web application, no web container - simple! The same is true as other types of applications are deployed, for example a Rails application. The containers are started and stopped on demand giving a higher utilization of resources.
2. Auto-deploy of Servlets and preserving servlet session state across multiple re-deploys using NetBeans and Eclipse. This feature is really useful as it tremendously reduces your development time. Focus on what you are good at i.e. adding business logic and let NetBeans and GlassFish together take care of your deployment worries. And why should you loose your session state just because the application is re-deployed!
3. Modularity and Extensibility of GlassFish v3 by running/debugging a Rails application. GlassFish certainly supports traditional Java EE applications. But starting with GlassFish v3 the newer Web frameworks like Rails can also be deployed natively. The screencast #26 shows how to develop, run and debug a Rails application natively deployed on GlassFish. And this capability of deploying a Rails application is added as an OSGi module and also demonstrates the extensibility of GlassFish.
   
   It provides future protection as well because any other Web framework can be easily deployed as a standard OSGi module.
4. Extensibility of GlassFish v3 by dropping a JAR in the "/modules" directory. The admin console is a one-stop interface for the administration of your GlassFish instance such as deploying WAR/EAR, creating JDBC/JMS resource, and creating clusters. Starting with GlassFish v3, even the admin console is extensible. There are clearly defined extension points that allows you to write a "admin console module" and extend the capability of your admin console. The demo showed dropping a JAR in the standard "modules" directory and admin cosole recognizing the module. A sample project that shows all the integration points to GlassFish v3 Admin Console is available here.
   

EJBs in a WAR - Simplified packaging defined by EJB 3.1, Available in GlassFish v3

• Using Update Center as described here.
• Or using the "pkg" command which is described below

DOWNLOAD                                    PKGS       FILES     XFER (MB)
Completed                                    1/1       11/11     0.45/0.45

PHASE                                        ACTIONS
Install Phase                                  24/24

NAME (AUTHORITY)                              VERSION         STATE      UFIX
felix                                         1.2.2-0         installed  ----
glassfish-amx                                 3.0-28.3        installed  ----
glassfish-api                                 3.0-28.3        installed  ----
glassfish-common                              3.0-28.3        installed  ----
glassfish-ejb                                 3.0-28.3        installed  ----
glassfish-grizzly                             1.8.6.2-0       installed  ----
glassfish-gui                                 3.0-28.3        installed  ----
glassfish-hk2                                 3.0-28.3        installed  ----
glassfish-jca                                 3.0-28.3        installed  ----
glassfish-jdbc                                3.0-28.3        installed  ----
glassfish-jdbc-gui                            3.0-28.3        installed  ----
glassfish-jdbc-management                     3.0-28.3        installed  ----
glassfish-jpa                                 3.0-28.3        installed  ----
glassfish-jsf                                 1.2.10-1        installed  u---
glassfish-jta                                 3.0-28.3        installed  ----
glassfish-management                          3.0-28.3        installed  ----
glassfish-nucleus                             3.0-28.3        installed  ----
glassfish-registration                        3.0-28.3        installed  ----
glassfish-scripting                           3.0-28.3        installed  ----
glassfish-web                                 3.0-28.3        installed  ----
glassfish-web-gui                             3.0-28.3        installed  ----
glassfish-web-management                      3.0-28.3        installed  ----
javadb                                        10.2.2.1-0      installed  ----
pkg                                           1.0.7-15.1269   installed  ----
pkg-java                                      1.0.7-15.1269   installed  ----
python2.4-minimal                             2.4.4.0-15.1269 installed  ----

1. Create a POJO, choose the class name as "HelloEJB" and package as "server" as shown
   
   
   
2. Declare a public method "sayHello" and add @javax.ejb.Stateless annotation to mark it a stateless EJB as shown
   
   
3. Create a new Servlet by selecting the option as shown
   
   
   
   and specify the name as "EJBClient" in "client" package
   
   
   
   and click on "Finish".
4. In the generated Servlet, declare a dependency on the EJB using @javax.ejb.EJB as shown
   
   
5. Invoke the EJB by uncommenting the code in "processRequest" method and add "ejbClient.sayHell("Duke")" invocation as shown:
   
   
   

OSUM - Open Source University Meetup - awesome venue for students!

TOTD #66: GlassFish Eclipse Plugin 1.0.16 - Install v3 Prelude from the IDE

GlassFish Swimming to Singapore Tech Days

• Complete Agenda
• Dedicated University Day for students
• Tons of Technical Sessions by star speakers
• Deep-dive Hands-on-Labs
• Refer-a-friend and stand a chance to win Nintendo Wii

GlassFish spotted on Salvador, Bahia - a Brazilian beach!

GlassFish @ Manipal Institute of Technology, India - Go Campus Ambassadors!

Blog Fan

GlassFish @ University of Essex and Frankfurt - Go Campus Ambassadors!

Jenya Kovalchuk (Campus Ambassador in the University of Essex, UK) gave a talk on GlassFish. The pre- and post-conditions of talk are really compelling:

Igor Geier from University of Frankfurt developed a A MySQL GlassFish application. The application is a work-in-progress but it sure will show the ease-of-use of GlassFish and tight integration with NetBeans.

TOTD #64: OpenSolaris 2008/11 using Virtual Box

• Open Solaris at The Observatory and twitter.com/opensolaris. 
• Virtual Box at Virtual Box Buzz.
• GlassFish at The Aquarium and twitter.com/glassfish.
• Rails at Riding Rails and twitter.com/rails.
• MySQL at Planet MySQL.
• JRuby at #jruby (archived).
• NetBeans at NetBeans Planet and twitter.com/netbeans.

TOTD #63: jmx4r gem - How to manage/monitor your Rails/Merb applications on JRuby/GlassFish ?

• How to remotely manage your Rails/Merb applications using JMX API ?
• How to publish your own metrics that can be managed using JMX API ?
• How to use jmx gem to manage/monitor ?
• How to use VisualVM to get more information about the underlying VM ?
• How to use NewRelic/FiveRuns to manage/monitor an application ?

TOTD #62: How to remotely manage/monitor your Rails/Merb applications on JRuby/GlassFish using JMX API ?

• Do include/import for Java classes
• Connect with the JMX Agent where JRuby MBeans are registered and obtain a MBean Server Connection (explained here)
• Query for all the MBeans in "org.jruby" domain
• Create proxies for ClassCache and Config MBeans
• Flush the ClassCache if its full and print some debugging information

• How to remotely manage your Rails/Merb applications using JMX API ?
• How to publish your own metrics that can be managed using JMX API ?
• How to use jmx gem to manage/monitor ?
• How to use VisualVM to get more information about the underlying VM ?
• How to use NewRelic/FiveRuns to manage/monitor an application ?

TOTD #61: How to locally manage/monitor your Rails/Merb applications on JRuby/GlassFish using JMX ?

GlassFish Gem can easily run both Rails and Merb application. Using JRuby, as opposed to MRI, allows you to use standard Java monitoring framework and tools. Java Management Extensions (JMX) is a standard management and monitoring solution for Java platform. This Tip Of The Day shows how to apply JMX techniques to monitor Rails/Merb applications.

• How to remotely manage your Rails/Merb applications using JMX API ?
• How to publish your own metrics that can be managed using JMX API ?
• How to use VisualVM to get more information about the underlying VM ?
• How to use NewRelic/FiveRuns to manage/monitor an application ?

TOTD #60: Configure MySQL 6.0.x-alpha to NetBeans 6.5

How to Configure a MySql database to be able to connect Netbeans6.5.?

I've tried using mysql Server 6 many times, but it fails.
Please, let me know how to fix that problem.

• Download MySQL 6.0 from here.
• Install and start MySQL 6.0 on Mac OSX using the clearly written installation instructions.
• Basically the download is available in .tar or .dmg format. Using .dmg format is the easiest way, double-click and follow the instructions taking all defaults.
• MySQL is installed in "/usr/local/mysql-6.0.8-alpha-osx10.5-x86_64" and the soft link is adjusted so that its available from "/usr/local/mysql". The directory structure looks like:
  
  

  lrwxr-xr-x   1 root  wheel   32 Jan  5 14:00 mysql -> mysql-6.0.8-alpha-osx10.5-x86_64 drwxr-xr-x   3 root  wheel  102 Jan  5 14:00 mysql-5.0.45-osx10.4-i686 drwxr-xr-x  17 root  wheel  578 Nov  3 21:02 mysql-6.0.8-alpha-osx10.5-x86_64

• Start MySQL server as: "sudo mysqld_safe" to see the output as:
  
  

  ~ >sudo mysqld_safe 090105 14:20:51 mysqld_safe Logging to '/usr/local/mysql/data/dhcp-usca14-133-38.SFBay.Sun.COM.err'. 090105 14:20:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data

• In NetBeans 6.5, Services tab, right-click on "Databases" and click on "Register MySQL Server..." as shown below:
  
  
• Take the default values, if your MySQL instance is running on the default ports, as shown below:
  
  
  
  and click on "OK". If your database is already running then NetBeans will automatically connect with the database. If the database is not running then start it as explained above, right-click on the newly added database as shown below:
  
  
  
  and the default databases are then shown as:
  
  

TOTD # 59: Alternative JSF implementations on GlassFish - MyFaces and Tomahawk

MyFaces also provides several component libraries such as Tomahawk, Trinidad, and Tobago for building web applications. This blog shows how MyFaces Tomahawk samples can be deployed on GlassFish v2 and v3. The basic integration hooks between GlassFish and other JSF implementations remain the same and are independent of the component library.

1. Deploy using Mojarra on GlassFish v2
1. Deploying "myfaces-example-simple-1.1.8.war" on GlassFish v2 using "asadmin deploy myfaces-example-simple-1.1.8.war" and it shows the following message:
   
   

   [#|2008-12-05T11:00:43.710-0800|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=22;_ThreadName=Thread-43;| deployed with moduleid = myfaces-example-simple-1.1.8|#] [#|2008-12-05T11:00:44.296-0800|INFO|sun-appserver9.1|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=21; _ThreadName=httpWorkerThread-4848-1;/myfaces-example-simple-1.1.8;|Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03) for context '/myfaces-example-simple-1.1.8'|#]

   
   The bold text indicates that Mojarra 1.2 bundled with GlassFish v2 is used as the JSF runtime, the exact version is shown in the bold text. The deployed web application is accessible at "https://localhost:8080/myfaces-example-simple-1.1.8/home.jsf" and looks like:
   
   
   
   The following error message is shown as you click through the samples:
   
   

   [#|2008-12-03T16:27:43.935-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=24;_ThreadName=httpSSLWorkerThread-8080-1;| 2008-12-03 16:27:43,935 [httpSSLWorkerThread-8080-1] INFO  org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Starting up Tomahawk on the MyFaces-JSF-Implementation |#] [#|2008-12-03T16:27:43.935-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=24;_ThreadName=httpSSLWorkerThread-8080-1;| 2008-12-03 16:27:43,935 [httpSSLWorkerThread-8080-1] ERROR org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations.

   
   This error message is generated by MyFaces and may be ignored. I think the message should be a WARNING instead of an ERROR.
   
2. Deploy using MyFaces on GlassFish v2
1. Create a directory "simple" and unjar "myfaces-example-simple-1.1.8.war" in there.
2. Add "WEB-INF/sun-web.xml" and specify the contents as:
   
   

   <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "https://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd"> <sun-web-app> <class-loader delegate="false"/> <property name="useMyFaces" value="true"/> </sun-web-app>

   
   The key point to notice is the property name "useMyFaces". The name is slightly mis-leading because the switch essentially tells GlassFish runtime to use the bundled Java Server Faces runtime and is not restricted to MyFaces only. This is fixed in GlassFish v3 and is discussed later.
   
3. Create a WAR file in "simple" directory as "jar cvf myfaces-simple-v2.war *".
4. Deploy the generated WAR on GlassFish v2 as "asadmin deploy myfaces-simple-v2.war". It shows the following message:
   
   

   . . . [#|2008-12-05T11:11:25.615-0800|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=24;_ThreadName=Thread-257;| deployed with moduleid = myfaces-simple-v2|#] [#|2008-12-05T11:11:26.266-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;| 2008-12-05 11:11:26,266 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading standard config org/apache/myfaces/resource/standard-faces-config.xml |#] [#|2008-12-05T11:11:26.290-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;| 2008-12-05 11:11:26,290 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config jar:file:/Users/arungupta/tools/glassfish/v2/ur2/glassfish/domains/domain1/applications/j2ee-modules/myfaces-simple-v2/WEB-INF/lib/tomahawk-1.1.8.jar!/ META-INF/faces-config.xml |#] [#|2008-12-05T11:11:26.309-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,308 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config /WEB-INF/examples-config.xml |#] [#|2008-12-05T11:11:26.337-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,337 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config /WEB-INF/testSuite-config.xml |#] [#|2008-12-05T11:11:26.349-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,349 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : myfaces-api in version : 1.1.6 from path : file:/Users/arungupta/tools/glassfish/v2/ur2/glassfish/domains/domain1/applications/j2ee-modules/myfaces-simple-v2/WEB-INF/lib/myfaces-api-1.1.6.jar |#] [#|2008-12-05T11:11:26.350-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,350 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : myfaces-impl in version : 1.1.6 from path : file:/Users/arungupta/tools/glassfish/v2/ur2/glassfish/domains/domain1/applications/j2ee-modules/myfaces-simple-v2/WEB-INF/lib/myfaces-impl-1.1.6.jar |#] [#|2008-12-05T11:11:26.350-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,350 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - MyFaces-package : tomahawk-sandbox not found. |#] [#|2008-12-05T11:11:26.350-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:26,350 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : tomahawk in version : 1.1.8 from path : file:/Users/arungupta/tools/glassfish/v2/ur2/glassfish/domains/domain1/applications/j2ee-modules/myfaces-simple-v2/WEB-INF/lib/tomahawk-1.1.8.jar |#] . . . [#|2008-12-05T11:11:27.069-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:27,069 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.shared_impl.config.MyfacesConfig - Starting up Tomahawk on the RI-JSF-Implementation. |#] [#|2008-12-05T11:11:27.069-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:27,069 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.shared_impl.config.MyfacesConfig - Starting up Tomahawk on the MyFaces-JSF-Implementation |#] [#|2008-12-05T11:11:27.070-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:27,070 [httpWorkerThread-4848-1] ERROR org.apache.myfaces.shared_impl.config.MyfacesConfig - Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations. |#] [#|2008-12-05T11:11:27.070-0800|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-1;|2008-12-05 11:11:27,070 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.webapp.StartupServletContextListener - ServletContext '/Users/arungupta/tools/glassfish/v2/ur2/glassfish/domains/domain1/applications/j2ee-modules/myfaces-simple-v2/' initialized. |#]

   
   The first thing to note is that the message "Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03)" is not shown. That indicates Mojarra is not used as the JSF runtime. Then you can see how MyFaces 1.1.6 API and Implementation are loaded, Tomahaw 1.1.8 is loaded and finally started using MyFaces JSF implementation.
   
   The main page from this deployed application at "https://localhost:8080/myfaces-simple-v2" is very similar as shown below:
   
   
3. Deploy using Mojarra on GlassFish v3 Prelude - This is very similar experience as with GlassFish v2.
1. Deploying "myfaces-example-simple-1.1.8.war" on GlassFish v3 shows the following message:
   
   

   Dec 5, 2008 11:27:17 AM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Mojarra (1.2_10-b01-FCS) for context '/myfaces-example-simple-1.1.8' Dec 5, 2008 11:27:18 AM com.sun.enterprise.web.WebApplication start INFO: Loading application myfaces-example-simple-1.1.8 at /myfaces-example-simple-1.1.8 Dec 5, 2008 11:27:18 AM org.glassfish.deployment.admin.DeployCommand execute INFO: Deployment of myfaces-example-simple-1.1.8 done is 3470 ms

   
   The bold text clearly indicates that Mojarra 1.2 bundled, exact version shown in the bold text, with GlassFish v3 is used as the JSF runtime. The deployed web application is accessible at "https://localhost:8080/myfaces-example-simple-1.1.8/home.jsf". Viewing the sample in browser shows:
   
   

   Dec 5, 2008 11:54:54 AM   INFO: 2008-12-05 11:54:54,083 [httpWorkerThread-8080-0] INFO  org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Starting up Tomahawk on the RI-JSF-Implementation. Dec 5, 2008 11:54:54 AM   INFO: 2008-12-05 11:54:54,083 [httpWorkerThread-8080-0] INFO  org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Starting up Tomahawk on the MyFaces-JSF-Implementation Dec 5, 2008 11:54:54 AM   INFO: 2008-12-05 11:54:54,083 [httpWorkerThread-8080-0] ERROR org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations.

   
   and may be ignored. None of the messages that indicate classloading, as shown for GlassFish v2 above, are displayed. I suspect these are standard messages displayed by MyFaces without taking into consideration that an alternate JSF runtime can be used to run these samples.
4. Deploy using MyFaces on GlassFish v3 Prelude - There is no way to override JSF implementation with GlassFish v3 Prelude. So even though deploying "myfaces-simple-v2.war" will work fine but viewing the web page at "https://localhost:8080/myfaces-simple-v2/" will show the following exception:
   
   
   
   Basically, a web application cannot use MyFaces implementation on GlassFish v3 Prelude. However Mojarra provides a fully-compliant and feature-rich JSF implementation and is already baked in GlassFish v3 Prelude.
   
5. Deploy using Mojarra on GlassFish v3 Trunk
1. Pick your GlassFish v3 Build Flavor, this blog uses the trunk.
2. Deploy the original sample as "asadmin deploy myfaces-example-simple-1.1.8.war" and the following log messages are shown:
   
   

   Dec 5, 2008 12:35:17 PM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Mojarra 2.0.0 (SNAPSHOT b05) for context '/myfaces-example-simple-1.1.8' Dec 5, 2008 12:35:18 PM org.apache.catalina.core.ApplicationContext log SEVERE: WebModule[/myfaces-example-simple-1.1.8]PWC1275: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener java.lang.NoClassDefFoundError: com/sun/facelets/tag/jsf/ComponentHandler         at java.lang.ClassLoader.defineClass1(Native Method)         at java.lang.ClassLoader.defineClass(ClassLoader.java:675)         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)         at org.glassfish.web.loader.WebappClassLoader.findClass(WebappClassLoader.java:974)

   
   This happens because the application has dependencies on internal classes of Facelets 1.1.x. That makes the application non-compatible with Mojarra 2.x which comes bundled with Facelets 2.0.
3. Lets instruct the application to disable the Facelets 2.0 baked in Mojarra by adding the following application wide context parameter in "web.xml":
   
   

   <context-param>        <param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>        <param-value>true</param-value>  </context-param>

   
   Now the Facelets 1.1.x classes bundled with the application are used. With this change, the application gets deployed correctly and shows the following log message:
   
   

   Dec 5, 2008 2:50:21 PM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Mojarra 2.0.0 (SNAPSHOT b05) for context '/myfaces-simple-v3' Dec 5, 2008 2:50:21 PM com.sun.enterprise.web.WebApplication start INFO: Loading application myfaces-simple-v3 at /myfaces-simple-v3 Dec 5, 2008 2:50:21 PM org.glassfish.deployment.admin.DeployCommand execute INFO: Deployment of myfaces-simple-v3 done is 1513 ms

   
   The important thing to note here is that Mojarra 2.0.0 implementation (as indicated by the bold text) is used as JSF runtime. This is the newest and the greatest runtime that implements JSF 2.0 specification and baked in GlassFish v3 trunk. The main page from this deployed application at "https://localhost:8080/myfaces-simple-v3/" looks like:
   
   
6. Deploy using MyFaces on GlassFish v3 Trunk
1. Download the latest GlassFish v3 Nightly.
2. Lets deploy the WAR file previously created as "asadmin deploy myfaces-simple-v2.war". The main page of the application is accessible at "https://localhost:8080/myfaces-simple-v2".
3. The "useMyFaces" property, as specified in "sun-web.xml", is expected to work for any bundled JSF implementation. The recommended way to deploy such a web application in GlassFish v3 is to use the property "useBundledJsf". The updated "sun-web.xml" is shown below:
   
   

   <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "https://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd"> <sun-web-app> <class-loader delegate="false"/> <property name="useBundledJsf" value="true"/> </sun-web-app>

4. Create a WAR file in "simple" directory as "jar cvf myfaces-simple-v3-usebundled.war *".
5. Deploy the generated WAR on GlassFish v3 as "asadmin deploy myfaces-simple-v3-usebundled.war". It shows the following message:
   
   

   . . . Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,786 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config jar:file:/Users/arungupta/tools/glassfish/v3/snapshot/glassfish/domains/domain1/applications/myfaces-simple-v3-usebundled/WEB-INF/lib/tomahawk-1.1.8.jar!/ META-INF/faces-config.xml Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,806 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config /WEB-INF/examples-config.xml Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,828 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Reading config /WEB-INF/testSuite-config.xml Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,841 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : myfaces-api in version : 1.1.6 from path : file:/Users/arungupta/tools/glassfish/v3/snapshot/glassfish/domains/domain1/applications/myfaces-simple-v3-usebundled/WEB-INF/lib/myfaces-api-1.1.6.jar Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,841 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : myfaces-impl in version : 1.1.6 from path : file:/Users/arungupta/tools/glassfish/v3/snapshot/glassfish/domains/domain1/applications/myfaces-simple-v3-usebundled/WEB-INF/lib/myfaces-impl-1.1.6.jar Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,841 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - MyFaces-package : tomahawk-sandbox not found. Dec 5, 2008 3:19:54 PM   INFO: 2008-12-05 15:19:54,841 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.config.FacesConfigurator - Starting up MyFaces-package : tomahawk in version : 1.1.8 from path : file:/Users/arungupta/tools/glassfish/v3/snapshot/glassfish/domains/domain1/applications/myfaces-simple-v3-usebundled/WEB-INF/lib/tomahawk-1.1.8.jar . . . Dec 5, 2008 3:19:55 PM   INFO: 2008-12-05 15:19:55,763 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.shared_impl.config.MyfacesConfig - Starting up Tomahawk on the RI-JSF-Implementation. Dec 5, 2008 3:19:55 PM   INFO: 2008-12-05 15:19:55,764 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.shared_impl.config.MyfacesConfig - Starting up Tomahawk on the MyFaces-JSF-Implementation Dec 5, 2008 3:19:55 PM   INFO: 2008-12-05 15:19:55,764 [httpWorkerThread-4848-1] ERROR org.apache.myfaces.shared_impl.config.MyfacesConfig - Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF-implementations. Dec 5, 2008 3:19:55 PM   INFO: 2008-12-05 15:19:55,764 [httpWorkerThread-4848-1] INFO  org.apache.myfaces.webapp.StartupServletContextListener - ServletContext '/Users/arungupta/tools/glassfish/v3/snapshot/glassfish/domains/domain1/applications/myfaces-simple-v3-usebundled/' initialized. Dec 5, 2008 3:19:55 PM com.sun.enterprise.web.WebApplication start INFO: Loading application myfaces-simple-v3-usebundled at /myfaces-simple-v3-usebundled Dec 5, 2008 3:19:55 PM org.glassfish.deployment.admin.DeployCommand execute INFO: Deployment of myfaces-simple-v3-usebundled done is 1994 ms

   
   The first thing to note is that the message "Initializing Sun's JavaServer Faces implementation (1.2_04-b20-p03)" is not shown. That indicates Mojarra is not used as the JSF runtime. Then you can see how MyFaces 1.1.6 API and Implementation are loaded, Tomahawk 1.1.8 is loaded and finally started using MyFaces JSF implementation.
   
   The main page from this deployed application at "https://localhost:8080/myfaces-simple-v3-usebundled" is very similar as shown below:
   
   
   
   

JavaFX 1.0 launched - access services hosted on embedded GlassFish

JavaFX SDK includes JavaFX script compiler and runtime tools, and a host of libraries to create RIAs for desktop, browser and mobile platforms, command-line tools & Ant tasks and other goodies. NetBeans 6.5 support (as plugin or bundled with IDE) that allows to build, preview and debug JavaFX applications using NetBeans IDE. If you prefer CLI support then SDK can be downloaded. Production Suite is a suite of tools and plugins for creative tools (such as Illustrator CS3+) that allows graphical assets to be exported to JavaFX applications.

This blog shows how to create a simple JavaFX application using NetBeans IDE. The application plays a movie, allows the viewer to cast a vote if they liked it, and see aggregate response from other viewers. The application is developed using NetBeans 6.5, JavaFX 1.0 plugin, and coded using JavaFX Script. The voting engine is deployed as a RESTful Web service using Jersey on GlassFish.

1. In NetBeans 6.5 IDE, install JavaFX plugin as explained here and RESTful Web services plugin as explained here. Both the plugins may be installed in one step by selecting the required plugins together.
2. Download NetBeans project for JavaFX client from here and add Jersey dependencies as explained in bullet #5 below. 
3. Download Web service endpoint Maven project from here and deploy the endpoint as explained in bullet #4 below.
4. Run the JavaFX application as explained here.

1. In NetBeans 6.5, install "JavaFX SDK" plugin.  In the "Tools" menu, "Plugins", search on "JavaFX", select "JavaFX SDK" and click on "Install".
2. Create a new project of type "JavaFX", "JavaFX Script Application". Take the default values as shown below:
   
   
   
   and click on "Finish".
3. The source code for this class can be downloaded from here or alternatively constructed as explained in the sub-bullets.
1. In the newly created class, change the Stage (root area for all scene content) to:
   
   

   Stage {    title: "GlassFish Media Player"    width: 625    height: 360    resizable: false    scene: myScene }

2. Create a scene that contains the view of the media to be played and controls the display of the Vote or Result nodes:
   
   

   var myScene: Scene = Scene {    content: MediaView {            fitWidth: 625            fitHeight: 360            mediaPlayer: bind myPlayer            onMouseEntered: function( e: MouseEvent ):Void {                println("mouse entered");                if (voted == false) {                    insert Vote{} into myScene.content;                } else {                    insert Result{} into myScene.content;                }            }            onMouseExited: function( e: MouseEvent ):Void {                delete myScene.content[1]            }        } }

3. Create a Media Player to use with the scene:
   
   

   var myPlayer: MediaPlayer = MediaPlayer{     autoPlay: true     media: bind myMedia };

4. Create the media object to be used with the Media Player:
   
   

   var myMedia: Media = Media {     source: "https://sun.edgeboss.net/download/sun/media/1460825906/1460825906_2957290001_DayEarth-Bluray.flv"    };

   
   You can change the location of the movie here in the media player. For example, changing it to "https://mediacast.sun.com/users/ArunGupta/media/v3prelude-nb65-webapp.flv" will start playing the screencast #27.
   
5. Create a Vote class that is a CustomNode and appears when a user's mouse enters the scene where the video is playing. The user can select whether he likes the clip or not and the vote is recorded making a Web service call using Jersey Client APIs:
   
   

   class Vote extends CustomNode {    override function create():Node {        return Group {            content: [                Rectangle {                    fill: Color.GREEN                    x: 185                    y: 145                    width: 243                    height: 38                    arcWidth: 20                    arcHeight: 20                },                Text {                    x: 195                    y: 170                    fill: Color.WHITE                    font: Font {                        size: 18                    }                    content: "I love it"                },                Rectangle{                    x: 191                    y: 148                    smooth: false                    width: 73                    height: 32                    fill: Color.TRANSPARENT                    onMouseClicked: function( e: MouseEvent ):Void {                        println("clicked I love it");                        voted = true;                        wsClient.voteLoveIt();                        delete myScene.content[1]                    }                },                Text{                    x: 305                    y: 170                    fill: Color.WHITE                    font: Font {                        size: 18                    }                    content: "Not so great"                    },                Rectangle {                    x: 301                    y: 148                    smooth: false                    width: 118                    height: 32                    fill: Color.TRANSPARENT                                       onMouseClicked: function( e: MouseEvent ):Void {                        voted = true;                        println("clicked Not so great");                        wsClient.voteNotSoGreat();                        delete myScene.content[1]                    }                }            ]        }    } };

6. Create a Result class that is a CustomNode and simply reports on how many voters like this clip:
   
   

   class Result extends CustomNode {    override function create():Node {        var resultPercent = wsClient.showResults();        var resultString = "{resultPercent} voters liked this clip";        return Group {            content: [                Rectangle {                    fill: Color.BLUE                    x: 187                    y: 145                    width: 244                    height: 38                    arcWidth: 20                    arcHeight: 20                    onMouseClicked: function( e: MouseEvent ):Void {                        delete myScene.content[1]                    }                },                Text {                    x: 199                    y: 170                    fill: Color.WHITE                    font: Font {                        size: 18                    }                    content: resultString                }            ]        }    } };

7. Add two instance variables:
   
   

   var voted = false; var wsClient = new WebserviceClient;

   
   The first variable captures if the viewer has already voted and the second variable is an instance to the RESTful Web service client.
   
8. Add the following import statements:
   
   

   import javafx.scene.*; import javafx.scene.input.MouseEvent; import javafx.scene.media.Media; import javafx.scene.media.MediaPlayer; import javafx.scene.media.MediaView; import javafx.scene.paint.Color; import javafx.scene.shape.Rectangle; import javafx.scene.text.Font; import javafx.scene.text.Text; import javafx.stage.Stage;

   
   "Fix Imports" should be able to fix them and bug #154307 is already filed for that.
4. Create a new class that is used to capture the Vote as:
   
   

   @javax.xml.bind.annotation.XmlRootElement public class VoteBean {     public static enum VOTE { LOVE_IT, NOT_SO_GREAT };         public VOTE vote;     public VoteBean() { vote = VOTE.LOVE_IT; }     public VoteBean(VOTE vote) {         this.vote = vote;     } }

   
   This is a simple Javabean with a standard JAXB annotation. This ensures that XML is used as the data format for transfering results between client and endpoint. The source code for this class is available here.
   
5. Add Jersey libraries to the project by right-clicking on Project, select Libraries, click on "Add Library...", select "JAX-RS 1.0" and "Jersey 1.0 (JAX-RS RI)", and click on "Add Library".
   
   
   
   If these libraries are not available then install the "RESTful Web Services" plugin from the Plugin Center.
6. And finally add the class that invokes the RESTful Webservice endpoint:
   
   

   public class WebserviceClient {     private static com.sun.jersey.api.client.WebResource createWebResource() {         return com.sun.jersey.api.client.Client.create().                 resource("https://localhost:8080/movie-feedback-webapp/webresources/myresource");     }     public static void voteLoveIt() {         createWebResource().type("application/json").                 post(new VoteBean(VoteBean.VOTE.LOVE_IT));     }     public static void voteNotSoGreat() {         createWebResource().type("application/json").                 post(new VoteBean(VoteBean.VOTE.NOT_SO_GREAT));     }     public static String showResults() {         return createWebResource().get(String.class);     } }

   
   The Webservice endpoint will be hosted at "https://localhost:8080/movie-feedback-webapp/webresources/myresource". A WebResource is created from the Client. The POST methods are used to cast the user vote and GET method is used to retrieve the aggregated results. The source code for this class is available here.

1. Create and deploy a RESTful Web service endpoint
1. Create a template RESTful Web service endpoint as described in TOTD #56. Lets use the artifactId as "movie-feedback-webapp".
2. Create the bean "VoteBean" in "org.glassfish.samples" package. This is the exactly same bean used earlier by the client:
   
   

   @javax.xml.bind.annotation.XmlRootElement public class VoteBean {     public static enum VOTE { LOVE_IT, NOT_SO_GREAT };     public VOTE vote;     public VoteBean() { vote = VOTE.LOVE_IT; }     public VoteBean(VOTE vote) {         this.vote = vote;     } }

3. Update the generated resource
1. Add @com.sun.jersey.spi.resource.Singleton as class annotation so that only one instance of the resource is created for the entire web application. This allows to save state (preferences from other users) in the RESTful resource.
   
2. Add two instance variables:
   
   

   int loveIt;     int noSoGreat;

3. Add a method that will process HTTP POST requests as:
   
   

   @POST     public void postOneVote(VoteBean bean) {         if (bean.vote == VoteBean.VOTE.LOVE_IT) {             loveIt++;         } else {             noSoGreat++;         }         System.out.println("In POST: " + bean.vote);     }

   
   This method stores the vote in the resource. The handling of POST request messages by Jersey is explained in TOTD #58.
   
4. Add a method that will process HTTP GET requests as:
   
   

   @GET     @Produces("text/plain")     public String getOpinion() {         if (loveIt == 0 && noSoGreat == 0)             return "No votes cast yet!";         return (loveIt * 100) / (loveIt + noSoGreat) + "%";     }

   
   This method calculates the percentage of viewers who liked the movie.
4. Deploy the endpoint using "mvn glassfish:run" in "movie-feedback-webapp" directory.

• How to install JavaFX capabilities to an existing NetBeans 6.5 installation
• How to create a simple JavaFX application that plays media files
• Integrate it with existing Java libraries (Jersey client libraries in this case)
• Invoke services hosted on GlassFish

LOTD #15: Deploying Merb application on GlassFish v3 using Warbler

TOTD #58: Jersey and GlassFish - how to process POST requests ?

1. Add a new method to "MyResource.java" from TOTD# 56 as:
   
   

   @POST     @Consumes("application/json")     @Produces("application/json")     public Greeting postIt(Greeting greeting) {         System.out.println("In POST: " + greeting.greeting);         return greeting;     }

   
   The first line indicates that the Java method will process HTTP POST requests. The second and third line shows that the method consumes and produces JSON data format.
   
2. Add a new method to "AppTest.java" from TOTD# 57 as:
   
   

   public void testPost() {         Greeting result = createResource().                 type("application/json").                 post(Greeting.class, new Greeting("yo!"));         assertTrue(result.greeting.equals("yo!"));     }

   
   The main difference from the "testApp()" method is specifying the MIME type of the generated outbound request as "application/json".
   
3. Running the test as "mvn test" shows the following output:
   
   

   Running org.glassfish.samples.AppTest 1 * Out-bound request 1 > GET https://localhost:8080/helloworld-webapp/webresources/myresource 1 > 1 < 200 1 < X-Powered-By: Servlet/2.5 1 < Transfer-Encoding: chunked 1 < Content-Type: text/plain 1 < Server: GlassFish/v3 1 < Date: Tue, 25 Nov 2008 20:19:34 GMT 1 < <?xml version="1.0" encoding="UTF-8" standalone="yes"?><greeting><greeting>Hi there!</greeting></greeting> 1 * In-bound response 1 * Out-bound request 1 > POST https://localhost:8080/helloworld-webapp/webresources/myresource 1 > Content-Type: application/json 1 > {"greeting":"yo!"} 1 < 200 1 < X-Powered-By: Servlet/2.5 1 < Transfer-Encoding: chunked 1 < Content-Type: application/json 1 < Server: GlassFish/v3 1 < Date: Tue, 25 Nov 2008 20:19:34 GMT 1 < {"greeting":"yo!"} 1 * In-bound response Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.191 sec

   
   The output shows request/response messages when both the tests are run together. Here are some highlights:
1. "GET" and "POST" methods are clearly highlighted.
2. The two "Content-Type" headers with value "text/plain" and "application/json" are output from two tests. The output from POST method has two Content-Type headers, one for outbound request and another one for inbound response.
3. The body content of POST method is using JSON format.
   

February 2009

Search this blog:

Categories

Archives

February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005

Recent Entries

GlassFish setup for 120 programmers in University of Copenhagen

Sun Tech Days Hyderabad 2009

TOTD #69: GlassFish High Availability/Clustering using Sun Web Server + Load Balancer Plugin on Windows Vista

This work is licensed under a Creative Commons License.