Ok, well that's odd they were embeded, but in general On upload glassfish fills in two fields on the deployment screen
The defaults are the name of the file you just uploaded so: Application Name: org.apache.sling.launchpad-6-SNAPSHOT Context Root: org.apache.sling.launchpad-6-SNAPSHOT I changed that so each is set to sling Application Name: sling Context Root: sling After the war file deploys there's a launch link which resolves to: http://localhost:8080/sling And I've tried: http://localhost:8080/sling/system/console and http://localhost:8080/system/console None of those URL's works. Tony On Apr 12, 2010, at 4:28 PM, Justin Edelson wrote: > On 4/12/10 4:19 PM, Tony Giaccone wrote: >> >> ... >> >> So now my questions: >> >> 1) The war file 'org.apache.sling.launchpad-6-SNAPSHOT.war' does that >> include a copy of Jetty? Like the standalone.jar file does. > No. It delegates to the servlet container. > >> 2) I try to upload the war file into glassfish, I >> use org.apache.sling.launchpad-6-SNAPSHOT.war, is that correct? > Yes. > >> >> 3) When I upload that file using the classfish deployment UI, it takes >> the name of the file and fills it in to these two fields: > These images didn't come through, at least for me. You should post them > to a service like screencast.com. > > Justin > >> >> >> I then change them to look like this: >> >> >> >> However, hitting these urls yields nothing: >> >> http://localhost:8080/sling/ >> http://localhost:8080/sling/system/console >> http://localhost:8080/system/console >> >> >> Any suggestions as to how I should proceed? Any thoughts about where >> I've gone wrong? >> >> Any help at all would be appreciated. >> >> >> Tony Giaccone >
