What's your environment?
Can you double check the jars in the class path?

I know if CXF can't load the @WebService annotation rightly, it will ignore the setting on the @WebService.


On 5/23/11 4:29 PM, Michael Täschner wrote:
Hi again,

any idea why CXF 2.3.4 ignores the contained namespace from the SEI
@WebService annotation and instead uses the SEI package name as namespace ??

Thanks and Regards,
Michael

Am 20. Mai 2011 10:01 schrieb Michael Täschner<[email protected]>:

Hi,

I am currently updating from CXF 2.3.0-SNAPSHOT to 2.3.4. In the project
the Server is created manually via JaxWsServerFactoryBean. With
2.3.0-SNAPSHOT the namespace was picked up from the SEI (or the implementing
bean?) but with 2.3.4 the namespace is generated from the SEI package name
(which is different to the namespace). This leads to the operations not
being visible and no wsdl types being contained in the generated wsdl by the
server. Do I have to set the namespace explicitly or how can I tell CXF to
pick it from the annotated SEI ?

Endpoint Registration:
         // create new ServerFactoryBean
         final JaxWsServerFactoryBean svrFactory = new
JaxWsServerFactoryBean();
         svrFactory.setServiceClass(serviceInterface);
         svrFactory.setAddress(contextPath);
         svrFactory.setServiceBean(serviceBean);

         // create the server and save the reference
         final Server server = svrFactory.create();


Thanks and Regards,
Michael




--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang

Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com

Reply via email to