HI Kristian,
Thanks for migrating to GFv3 and reporting this issue. I will help
forward to the right engineer.
How was your migration experience from v2 to v3? Would you like to
share it with us?
You have a good week :-)
Judy
Kristian Rink wrote:
> Folks;
>
> about to get productive with GFv3, I figured a slightly different
> behaviour compared to v2 related to JAX-WS web services: In some of
> our modules, we use Spring and JAX-WS remoting per
> annotation-configuration (see "17.5.5. Exposing servlet-based web
> services using JAX-WS..." in [1] for further info). In GFv2, this
> works rather well - I can deploy the war file in question into the
> application server, can access the SOAP endpoint exposed this way,
> test it, generate WSDL, ... . Deploying the same app to GFv3, trying
> to access what I suppose to be the URL of the SOAP endpoint just ends
> up in a 404.
>
> I am aware that this eventually is a little vague and an issue
> somewhere amidst "interoperability" and having Spring into this.
> However: Any ideas where to look to get hold of this? Any input I
> could provide in order to help figuring out what's goin' on? Known
> problem, eventually?
>
> TIA and all the best,
> Kristian
>
> [1]http://static.springsource.org/spring/docs/2.5.x/reference/remoting.html
>
>
>