No, we did not change anything in the autodeploy area in 3.1.2
GlassFish. I just tried to manually auto deploy a web application to the
autodeploy directory (by copying the war file to the autodeploy
directory), and the web application foo.war was deployed successfully as
foo and available at localhost:8080/foo (which is the default context
root).
You said you were using MyEclipse IDE, I guess it could be some change
in the plugin too? You could try to autodeploy your application outside
of IDE (just copy the war to the domains/domain1/autodeploy directory)
to see if it makes a difference..
- Hong
On 3/5/12 1:02 PM, forums_at_java.net wrote:
> I've been using the Glassfish 3 series for a while now and, with it, the
> MyEclipse IDE. It autodeploys my application to
> domains/domain1/appname.war. Before the upgrade to 3.1.2 I could then
> access my app at http://localhost:8080/appname. Now, however, I have
> to go
> to http://localhost:8080/appname.war to access it.
>
> Is this an intentional change? For a point release this seems like a
> rather
> breaking change.
>
> Thanks for any info.
>
>
> --
>
> [Message sent by forum member 'stdunbar']
>
> View Post: http://forums.java.net/node/884022
>
>