Hi, You probably need post your SEI/Impl class here, as well as the full stack trace. －－－－－－－－－－－－－ Freeman(Yue) Fang
Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 www.camelone.org : The open source integration conference: On 2013-5-13, at 下午4:20, James Green wrote: > Hi, > > We have written a web tier with a number of classes exposed using the > @WebService annotation including a targetNamespace value e.g. > > @WebService(targetNamespace="http://ourco.com/doc";) > class Service { > } > > Inside these services the public methods are, as expected, exposed as > methods with parameters. We can build clients using auto-generated wsimport > and indeed wsdl2java and use them as expected. So far so good. > > We recently added another couple of these classes using the above recipe. > This time disaster - the server (TomEE 1.6 snapshot - last week) issues an > exception that the parameter has a namespace - but that none was expected. > That's the conclusion reached from Googling the error... > > The parameters are just POJOs with @XmlRootElement - no namespace > specified. This is the same across the app. We began playing with different > combinations of empty namespaces on @WebParam etc and came up with > inconsistent results. > > In fact right now one method requires a parameter with a namespace, another > in the same class requires an empty namespace! > > I'm baffled by SOAP most of the time but this has be stumped. Any ideas > what to do next? > > Thanks, > > James
