One suggestion would be from the osgi command line run "imports 52" and 
"imports" on your application bundle and make sure the javax.ws imports are 
being resolved from the same place.   It looks like you have two bundles that 
provide it:


> 12      ACTIVE      com.springsource.javax.jws_2.0.0

> 36      ACTIVE
> org.apache.geronimo.specs.geronimo-ws-metadata_2.0_spec_1.1.2

(along with the JDK if you are on JDK 1.6)

And I'm wondering if there is some sort of conflict there or something where 
your bundles may be getting a different version than the CXF bundle.


Dan



On Tuesday, May 24, 2011 7:56:44 AM Michael Täschner wrote:
> Hi again,
> 
> this is the set of bundles in my environment.
> 
> Framework is launched.
> 
> id      State       Bundle
> 0       ACTIVE      org.eclipse.osgi_3.5.1.R35x_v20090827
> 1       ACTIVE      osgi.core_4.2.0.200908310645
> 2       ACTIVE      osgi.cmpn_4.2.0.200908310645
> 3       ACTIVE      com.springsource.slf4j.api_1.5.6
> 4       ACTIVE      jcl.over.slf4j_1.5.6
> 5       ACTIVE      log4j.over.slf4j_1.5.9-RC0
> 6       ACTIVE      com.springsource.ch.qos.logback.classic_0.9.15
>                     Fragments=85
> 7       ACTIVE      com.springsource.ch.qos.logback.core_0.9.15
> 8       ACTIVE      org.ops4j.pax.web.pax-web-jetty-bundle_0.7.4
> 9       ACTIVE      org.springframework.osgi.jetty.start.osgi_1.0.0
>                     Fragments=11
> 10      RESOLVED
> org.springframework.osgi.jetty.web.extender.fragment.osgi_1.0.1
>                     Master=31
> 11      RESOLVED    com.lhsystems.gsp.core.jetty.config_1.0.0.SNAPSHOT
>                     Master=9
> 12      ACTIVE      com.springsource.javax.jws_2.0.0
> 13      ACTIVE      com.springsource.org.aopalliance_1.0.0
> 14      ACTIVE      org.springframework.core_3.0.5.RELEASE
> 15      ACTIVE      org.springframework.aop_3.0.5.RELEASE
> 16      ACTIVE      org.springframework.beans_3.0.5.RELEASE
> 17      ACTIVE      org.springframework.asm_3.0.5.RELEASE
> 18      ACTIVE      org.springframework.expression_3.0.5.RELEASE
> 19      ACTIVE      org.springframework.context_3.0.5.RELEASE
> 20      ACTIVE      org.springframework.context.support_3.0.5.RELEASE
> 21      ACTIVE      org.springframework.transaction_3.0.5.RELEASE
> 22      ACTIVE      org.springframework.web_3.0.5.RELEASE
> 23      ACTIVE      com.springsource.org.objectweb.asm_2.2.3
> 24      ACTIVE      com.springsource.edu.emory.mathcs.backport_3.1.0
> 25      ACTIVE      com.springsource.net.sf.cglib_2.1.3
> 26      ACTIVE      org.springframework.osgi.extensions.annotations_1.2.1
> 27      ACTIVE      org.springframework.osgi.core_1.2.1
> 28      ACTIVE      org.springframework.osgi.extender_1.2.1
> 29      ACTIVE      org.springframework.osgi.io_1.2.1
> 30      ACTIVE      org.springframework.osgi.web_1.2.1
> 31      ACTIVE      org.springframework.osgi.web.extender_1.2.1
>                     Fragments=10
> 32      ACTIVE      com.springsource.javax.servlet_2.5.0
> 33      ACTIVE
> org.apache.geronimo.specs.geronimo-annotation_1.0_spec_1.1.1
> 34      ACTIVE
> org.apache.geronimo.specs.geronimo-activation_1.1_spec_1.0.2
> 35      ACTIVE
> org.apache.geronimo.specs.geronimo-javamail_1.4_spec_1.2.0
> 36      ACTIVE
> org.apache.geronimo.specs.geronimo-ws-metadata_2.0_spec_1.1.2
> 37      ACTIVE      com.springsource.org.jdom_1.0.0
> 38      ACTIVE      com.springsource.org.apache.log4j_1.2.15
> 39      ACTIVE      org.apache.servicemix.bundles.jaxb-impl_2.1.6.1
> 40      ACTIVE      org.apache.servicemix.bundles.wsdl4j_1.6.1.1
> 41      ACTIVE      org.apache.servicemix.bundles.xmlsec_1.3.0.1
> 42      ACTIVE      org.apache.servicemix.bundles.wss4j_1.5.4.1
> 43      ACTIVE      org.apache.servicemix.bundles.xmlschema_1.4.3.1
> 44      ACTIVE      org.apache.servicemix.bundles.asm_2.2.3.1
> 45      ACTIVE      org.apache.servicemix.bundles.xmlresolver_1.2.0.1
> 46      ACTIVE      org.apache.servicemix.bundles.neethi_2.0.4.1
> 47      ACTIVE      org.apache.servicemix.bundles.woodstox_3.2.7.1
> 48      ACTIVE      org.apache.servicemix.specs.saaj-api-1.3_1.1.1
> 49      ACTIVE      org.apache.servicemix.specs.stax-api-1.0_1.1.1
> 50      ACTIVE      org.apache.servicemix.specs.jaxb-api-2.1_1.1.1
> 51      ACTIVE      org.apache.servicemix.specs.jaxws-api-2.1_1.1.1
> 52      ACTIVE      org.apache.cxf.bundle-minimal_2.3.4
> 53      ACTIVE      cxf-dosgi-ri-discovery-local_1.2.0
> 54      ACTIVE      cxf-dosgi-ri-dsw-cxf_1.2.0
> 55      ACTIVE      com.springsource.org.apache.commons.lang_2.4.0
> 56      ACTIVE      com.springsource.org.apache.commons.collections_3.2.1
> 57      ACTIVE      com.springsource.org.apache.commons.pool_1.3.0
> 58      ACTIVE      com.springsource.org.quartz_1.6.2
> 59      ACTIVE      com.springsource.org.apache.commons.fileupload_1.2.0
> 60      ACTIVE      com.springsource.org.apache.commons.io_1.4.0
> 61      ACTIVE      com.springsource.org.apache.commons.net_1.4.1
> 62      ACTIVE      com.springsource.org.apache.commons.vfs_1.0.0
> 63      ACTIVE      com.springsource.org.apache.commons.httpclient_3.1.0
> 64      ACTIVE      com.springsource.org.apache.commons.codec_1.4.0
> 65      ACTIVE      com.springsource.org.apache.tools.ant_1.7.1
> 66      ACTIVE      com.springsource.com.jcraft.jsch_0.1.25
> 67      ACTIVE      com.springsource.org.apache.oro_2.0.8
> 68      ACTIVE      com.springsource.javax.transaction_1.1.0
> 69      ACTIVE      com.springsource.com.mysql.jdbc_5.1.6
> 70      ACTIVE      com.springsource.com.mchange.v2.c3p0_0.9.1.2
> 71      ACTIVE      com.springsource.org.apache.commons.logging_1.1.1
> 72      ACTIVE      com.springsource.javax.resource_1.5.0
> 73      ACTIVE      org.eclipse.persistence.core_2.0.0.v20091127-r5931
> 74      ACTIVE      org.eclipse.persistence.jpa_2.0.0.v20091127-r5931
> 75      ACTIVE      javax.persistence_2.0.0.v201002051058
> 76      ACTIVE      org.eclipse.persistence.asm_2.0.0.v20091127-r5931
> 77      ACTIVE      org.eclipse.persistence.antlr_2.0.0.v20091127-r5931
> 78      ACTIVE      javax.sql.jdbc-stdext_2.0.0
> 79      ACTIVE      com.springsource.javax.mail_1.4.1
> 80      ACTIVE      org.apache.felix.webconsole_3.1.6
> 81      ACTIVE      com.lhsystems.gsp.core.monitor_1.0.0.SNAPSHOT
> 82      ACTIVE
> com.lhsystems.gsp.app.serviceRegistration.common_1.0.0.SNAPSHOT
> 83      ACTIVE
> com.lhsystems.gsp.app.serviceRegistration.webapp_1.0.0.SNAPSHOT
> 84      ACTIVE
> com.lhsystems.gsp.app.serviceRegistration.webservice_1.0.0.SNAPSHOT
> 85      RESOLVED    logback-config_1.0.0
>                     Master=6
> 
> Any idea, what may have an impact on the @Webservice namespace usage or why
> it may not be resolved at all ?
> 
> Thanks and Cheers,
> Michael
> 
> Am 24. Mai 2011 08:39 schrieb Michael Täschner <[email protected]>:
> > Hi Willem,
> > 
> > my environment is an OSGi container using Pax-Runner. The only updates I
> > included with the switch to CXF 2.3.4 were Spring (2.5.6 -->
> > 3.0.5.RELEASE) and Spring DM (1.2.0 --> 1.2.1). The package imports and
> > other settings have not changed. This is why I am a bit confused with
> > the changed behavior.
> > 
> > Regards,
> > Michael
> > 
> > 
> > 2011/5/24 Willem Jiang <[email protected]>
> > 
> >> 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

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog
Talend - http://www.talend.com

Reply via email to