From reading the bug description, it is an expected deployment failure
in this case (the war had some issue). The priority of the bug was
lowered to P4 as the problem to fix was to make the behavior of this
negative test case more user friendly so user realize this war was not
deployed properly. But seems the issue that you want to get fixed here
is to make this war deploy successfully with the GlassFish. For that you
can file a separate issue under the webservices category with the test
case. From the bug description, there seems to be workaround you could
do with editing the web.xml, but I will let the webservices team provide
the accurate answer here for what exactly need to be changed.
Thanks,
- Hong
forums_at_java.net wrote:
> Hi, We have quite a number of web services created using the method
> described
> in this guide creating the webservices:
> http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/webservices/ws.html
>
> But when we deploy this to Glassfish, it will say xxx cannot be cast to
> servlet, after some time web studying, we found the following links (not
> many) and seems it's bug of glassfish?
> http://java.net/jira/browse/GLASSFISH-3297
> http://kingsfleet.blogspot.hk/2007/07/q-why-wont-my-jdeveloper-jax-ws-web.html
>
> It seems that glassfish team will fix it in no schedule. Just wonder
> if there
> is any work around? Any suggestion would be greatly appreciated. Thanks.
> Andrew
>
> --
>
> [Message sent by forum member 'solarkid']
>
> View Post: http://forums.java.net/node/891671
>
>