I think the really simplest thing to do is use curl.
curl <options>
http://url/to/your/ws
Don't be scared when you look at the curl man page and see that there are 100+ options, just find the ones you need to make it be a POST, GET, PUT or HEAD request etc. For a PUT request example:
curl -T some-file.txt
http://url/to/PUT/service
You can make the calls with no args, with args... whatever.. and receive or not receive a response
Alex Sherwin
alex.sherwin_at_acadiasoft.com
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Wednesday, October 01, 2008 1:32 PM
To: users_at_glassfish.dev.java.net
Subject: Re: Problems deploying to GlassFish from Eclipse + EclipseLink
euqaz, nice detective work!
I am not sure how much the locked JAR contributes to your earlier problem, but it definitely looks as if you have identified a bug in EclipseLink. This is not something that GlasFish can correct, so opening an EclipseLink issue (if there is not one already open for this) is probably best.
As you seem to understand, the warning message during deployment/undeployment says basically that the file used to be part of the app but is not a part of it in the later deployment. But because it still resides in the directory it might continue to be accessible to your application, which is typically not what people intend when they remove a JAR from an app!
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=302785
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net