Byron Nevins - Byron's Pointless Ramblings
Java
EE 6 has greatly simplified
life for the EE developer. New annotations like @Startup and packaging options
such as EJBs inside a war file save time and brain cycles. However, this makes writing
the web UI for an application all the more time-consuming by comparison. If you're like me,
you may have found yourself creating some entities and a session bean or two for controlling
them, and then you just want to test it all out.
We already support running GlassFish V3 as a service on Solaris 10 and Windows platforms (see my blog). I have been investigating how to provide support for automatically starting GlassFish V3 as a service on Linux. Of course before I can hope to do that -- I must be able to set it up manually. In this blog I will take you through the manual steps needed to run GlassFish V3 as a service on Linux.
A typical GlassFish v2 enterprise installation consists of one administration domain controlled by the Domain Administration Server (DAS) which handles all of the administration duties of the domain. The domain provides a common authentication and administration point for a collection of Java EE server instances.
Refer to my other blog for general details about setting up Platform Services
Having gone through this a couple times now, I wanted to capture a couple tips that make
JDeveloper
installation easy for MacOS X users. The installation itself is very simple: a 'java -jar <jar_file>' does it all. But
there is one helpful and one mandatory step you should take first. Thanks go to
Steve DiMilla for trying these steps as well.

I'm very grateful for the past nine years Sun. Looking forward to see what the future holds...
As you probably know by now, Java EE 6
has made life simpler for developers (ear files not required, local EJB interfaces optional, singletons, all good stuff!). But of course you want to run your old applications as well. With GlassFish
v3, moving them over to the newest application server is also a lot easier. In fact, you can upgrade a domain from GlassFish v2.1 or GlassFish v3-Prelude in zero steps.
A user on GlassFish Forum tried invoking a JAX-WS Web service from a Rails application and faced some issues. This Tip Of The Day (TTOD) will discuss the different approaches and shows their current status.
A Rails app can be deployed on GlassFish in 3 different ways:
A user on GlassFish Forum tried invoking a JAX-WS Web service from a Rails application and faced some issues. This Tip Of The Day (TTOD) will discuss the different approaches and shows their current status.
A Rails app can be deployed on GlassFish in 3 different ways:
There's a lot of buzz today around the release of GlassFish V3.
Instead of duplicating content, I would recommend reading this blog entry about the release posted to The Aquarium.
As mentioned in TOTD #113, this Tip Of The Day (TOTD) provides a working version of the JavaFX front-end for GlassFish v3 administration.
Grizzly Comet is a very powerful feature in GlassFish v2 and GlassFish v3.
It provides a framework for writing many interesting applications.
However, the same application will not run in other servlet containers (without Grizzly).
One can resolve this by porting the code to use asynchronous API in Servlet 3.0
as in the glassfish sample, asyn-request-war, code
This blog is a follow-up of my earlier monitoring blog, and I recommend reading that one first.
I was sad to miss attending the Devoxx conference in Antwerp, Belgium this year. But the Sun engineering team was definitely there - participating in a full schedule of conference keynotes, sessions and BOFs.
From the reports I've heard from the team, as well as various Twitter feeds, there was a lot of excitement building around the upcoming release of Java EE 6 and the GlassFish community.
GlassFish v3 provides a REST interface to management and monitoring information as discussed in TOTD #96. As mentioned in that blog "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". This blog introduces a tool that uses the REST API to provide management and monitoring of GlassFish v3 and is written using JavaFX.
Vaadin and ZK are both popular RIA frameworks that have been tested to work with GlassFish v3.
The JavaDude has a detailed blog on "ZK 3.6.3 with Netbeans 6.8 Beta on Glassfish V3" (this is the ZK release from a few days ago). It discusses developing with or without the ZK community plugin for NetBeans (which is mostly about adding meta-data to a Java EE project), creating ZUML pages with a component palette and deploying to GlassFish v3.
The GlassFish application server has quickly become the open source platform of choice for enterprises of all types and sizes, and its advantages have proven particularly compelling for small businesses.
In May 2009, I discussed the Servlet 3.0 security annotations in one of my blogs,
Servlet 3.0 Security Annotations.
At that time, the annotations were defined similar to those in EJB.
During the discussion in JSR 315 expert group, two issues were identified as follows:
The Sun GlassFish Enterprise Server v2.1.1 with HADB is a comprehensive commercial offering for GlassFish, the leading open source platform for building and deploying next-generation applications and services. GlassFish Enterprise Server delivers enterprise features including 99.999% availability, centralized administration, and record-setting performance.
Mojarra 2.0.0 is now available!
There are several ways to obtain the release.
GlassFish v3 is nearing its FCS. Though primarily considered a development platform, it has several deployment features. One such feature is administrative security. Through my various interactions, it is clear that users are rather confused about the asadmin passwords, how asadmin communicates to the server, how server can be configured to use a (corporate) LDAP to authenticate (and authorize) administrative access to GlassFish domains (a GF domain or domain or a server mean the same thing) and so on.
In MacOS (I'm running 10.5), the open command is one of those little tools that keeps giving and giving. Sure, it seems simple enough. From the man page:
The Java.Net folks are running this poll: What future do you foresee for GlassFish?.
This type of polls are very unscientific (e.g the Java.Net and TA readeris is unrepresentative of the larger population), but, if you want to participate, I believe the poll is open for the whole week.
• Servlet 3.0 (JSR 315) support in Maia
• How to install and use JRebel with Glassfish and Eclipse IDE
• ColdFusion - Installation, deployment, and platforms
I think I also saw something recently on either EHCache or TerraCotta as well...
TOTD #110 explained how to create a brand new Rails application using Oracle database and run it using GlassFish v Gem. This Tip Of The Day explains how to create a scaffold for a sample schema that ships with Oracle database. Even though Rails Scaffold are good for, well, scaffolding but they do get you started easily.