Alexis MP's dashboard

see my answer to your other similar question about "sniffers"...

The problem with the example as it's described in the book is that a single JAR archive contains both a main() class which the ACC could eb interested in and an EJB which is clearly for the EJB Container.

The message you are seeing says that GlassFish doesn't know what to do with this archive. Is it an EJB or is it for the AppClient Container?

Removing the Main.class entry from the archive should let you deploy the EJB.

So GlassFish v3 should be it indeed and yes, the upward compatibility is a rather well kept secret.

You might want to use JDK6 to write a simple JAX-WS client in the form of :

MyWSService service = new MyWSService();
MyWS port = service.getMyWSPort();
port.operation();


with the appropriate wsimport http://localhost:8080/path/to/wsdl

(my personal take here)
Is $25,000 per CPU the way you compete with JBoss, Spring, ...?
Im curious, what would Apache bring to GlassFish that it doesn't have already?

@Antonio, Oracle has *many* databases, *many* portals, etc...

Can you try again with a recent promoted build?
Download one from here: http://download.java.net/glassfish/v3/promoted/

GlassFish supports all versions of Java EE and J2EE (this is actually a specification requirement). There are large companies that have moved away from WebSphere to GlassFish.

Having said this, in practice you need to carefully look at your existing applications and understand how portable they are. In some cases WebSphere-specific features may have been introduced (by development tools in most cases). In which case there may or may not be a direct equivalent in GlassFish.

GlassFish v3 hasn't yet shipped in final version (expected in November '09). You may want to consider GlassFish v2.1 which supports Java EE 5, full clustering, centralized admin, etc (most of which people seem to find quite similar to the WebSphere architecture).

hope this helps,
-Alexis