Thanks for the response Daniel.
I'll look into the namespaces, although I'm a little unsure if that is the
real issue as I have two other web services packaged along the same lines
that both work, the only real difference being the param passed in the
message.
One sends through a POJO with three properties, the other has no params.
All three apps have :
the service interface in {standardcompanypackage}.webservicename.services
the implementation of the interface in
.{standardcompanypackage}.webservicename.service.impls
a test client in seperate test source
{standardcompanypackage}.webservicename.cient that is excluded from the
generated .war file.
The test clients are all run as basic java applications inside eclipse after
deploying the war to a tomcat container.
All three were built following the basic tutorial here :
http://wheelersoftware.com/articles/spring-cxf-web-services.html
dkulp wrote:
>
>
> It's quite possible (probable actually) that there is a mismatch between
> the
> namespace expectations on client and server, especially if the interface
> and
> impl are in different packages. Definitely add the namespace attributes
> to
> the @WebService annotations on both client and server.
>
> Next thing to note:
> On the server side, you are configuring in the AegisServiceConfiguration,
> but
> you aren't on the client the side. That might also cause an issue.
>
> Barring those fixing it, if you can create a jir and attach the full test
> case, that would be a help.
>
> Dan
>
>
>
> --
> Daniel Kulp
> [email protected]
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://old.nabble.com/Argument-appears-in-message-but-is-null-in-implementation-method-tp26305475p26319105.html
Sent from the cxf-user mailing list archive at Nabble.com.
