users@glassfish.java.net

Re: Glassfish and Application Client deployment

From: <glassfish_at_javadesktop.org>
Date: Fri, 08 Jun 2007 07:32:12 PDT

Hi, Kerry.

I think you are suffering from Issue 2239 which is itself a duplicate of 2223. To complicate things slightly more, these two issues are mirrors of bugs filed in Sun's internal bug tracking system. The internal info for 2223 reports that the bug was fixed starting in build 34.

So, if you use a later build things should be much better. This is the full downloads page for GlassFish: https://glassfish.dev.java.net/public/alldownloads.html If you are a bleeding edge type, build 50 (as of this writing) is the latest nightly build which passes a set of tests. Build 41d (listed under the GlassFish V2 beta 2 category) is the latest beta build which passes a much larger set of tests.

By the way, for future reference, you can use the issue tracker to query for issues filed against the standalone-client subcomponent of GlassFish. Such a query returns (among others) this line:

2239 DEFECT P3 All tjquinn RESOLV FIXE <BT6517816>jsf: getting HTTP 404 status when launching appcl

which might have been enough for you to read that issue's description and find a match.

- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]

http://forums.java.net/jive/thread.jspa?messageID=221224