Hi It appears it is a CXF level issue. Does this NPE occur even if you use a standalone client, without DOSGI ?
cheers, Sergey On Mon, Oct 18, 2010 at 2:52 PM, <[email protected]> wrote: > Hi, > > I'm still on this issue and I could really use som help. > > I don't understand why I get an IndexOutOfBoundException in this class with > cxf-dosgi-ri-singlebundle-distribution. > > As mentionned early by mail, we are using > cxf-dosgi-ri-singlebundle-distribution-1.1.jar modified according Ronald > instructions plus one (replacing cxf-bundle-minimal-2.2.4 with > cxf-bundle-minimal-2.2.10 because of a NullPointerException in same method > (known bug it appears)). > > How could I possibly get rid of that Exception ? > > Thanks a lot. > > -----Message d'origine----- > De : [email protected] [mailto:[email protected]] > Envoyé : vendredi 15 octobre 2010 18:41 > À : [email protected] > Objet : RE: DOSGi wsdl-first approach > > Hi, > > Thanks Ronald for your answer, it "almost" worked for me too. > > I get it to work for some web services but it fails every time with axis > powered web services. I get this exception: > > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:547) > at java.util.ArrayList.get(ArrayList.java:322) > at > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeClassInfo(ReflectionServiceFactoryBean.java:692) > at > org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.initializeWSDLOperation(JaxWsServiceFactoryBean.java:224) > at > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeWSDLOperations(ReflectionServiceFactoryBean.java:636) > at > org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.initializeWSDLOperations(JaxWsServiceFactoryBean.java:260) > at > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromWSDL(ReflectionServiceFactoryBean.java:386) > at > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:490) > at > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:240) > at > org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:180) > at > org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:99) > at > org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:51) > at > org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:102) > at > org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:121) > at org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:458) > at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:330) > at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:317) > at javax.xml.ws.Service.getPort(Service.java:40) > > I'm testing with this web service : > http://webservices.wolfram.com/services/SearchServices/WolframSearch2.wsdl > > We are using cxf-dosgi-ri-singlebundle-distribution-1.1.jar modified > according Ronald instructions plus one (replacing cxf-bundle-minimal-2.2.4 > with cxf-bundle-minimal-2.2.10 because of a NullPointerException in same > method (known bug it appears)). > > Our customized cxf-dosgi-ri-singlebundle-distribution bundle works great > with cxf powered web services. That's strange. > > Any help great appreciated. > > Thanks. > > > -----Message d'origine----- > De : David Bosschaert [mailto:[email protected]] > Envoyé : vendredi 15 octobre 2010 11:58 > À : [email protected] > Objet : Re: DOSGi wsdl-first approach > > On 15 October 2010 10:48, Ronald Müller <[email protected]> > wrote: > > > > Finally i solved my issue by kicking the following bundles: > > > > * geronimo-activation_1.1_spec-1.0.2.jar > > * org.apache.servicemix.bundles.jaxb-impl-2.1.6_1.jar > > * org.apache.servicemix.specs.jaxb-api-2.1-1.3.0.jar > > * org.apache.servicemix.specs.stax-api-1.0-1.3.0.jar > > > > out of the cxf-dosgi-singlebundle.jar, as these are also provided by the > > JDK6. So i configured the bootdelegation-property as following: > > > > > org.osgi.framework.bootdelegation=com.sun.*,javax.xml.bind.*,javax.activation.*,javax.xml.stream.* > > > > And it just works now :-) ! > > That's excellent news! Does anyone know whether these bundles actually > provide any value for JSE 6 users? You obviously need them for JSE 5 > but I'm wondering do we really need to support JSE 5 in our releases > given that JSE 5 reached end of life about a year ago? > > Best regards, > > David > > ********************************* > This message and any attachments (the "message") are confidential and > intended solely for the addressees. > Any unauthorised use or dissemination is prohibited. > Messages are susceptible to alteration. > France Telecom Group shall not be liable for the message if altered, > changed or falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender. > ******************************** > > > ********************************* > This message and any attachments (the "message") are confidential and > intended solely for the addressees. > Any unauthorised use or dissemination is prohibited. > Messages are susceptible to alteration. > France Telecom Group shall not be liable for the message if altered, > changed or falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender. > ******************************** > >
