You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by elMateo <so...@gmail.com> on 2012/10/15 14:28:08 UTC
SOAP Web service client problem in ApacheFelix OSGi
Hello all,
I'm developing a SOAP web service bundle into Apache Felix with
cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
I have a wsdl file and I can access to this service from a navigator to see
its properties. But I can't develop a bundle client from Felix. (In other
mails I asked about REST services, but I haven't an interface to access
directly to these REST services)
I attach my Felix container and the error that it shows me.
START LEVEL 1
ID|State |Level|Name
0|Active | 0|System Bundle (4.0.2)
1|Active | 1|Apache Felix Bundle Repository (1.6.6)
2|Active | 1|Apache Felix Gogo Command (0.12.0)
3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
4|Active | 1|Apache Felix Gogo Shell (0.10.0)
5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
6|Active | 1|Distributed OSGi Distribution Software
Single-Bundle Dis
tribution (1.2.0)
10|Active | 1|Apache ANT (1.8.1)
11|Active | 1|ANTLR Runtime (3.1.3)
12|Active | 1|mvel2 (2.1.0.drools6)
13|Active | 1|Java XML Stream API (StAX) (1.0.1)
14|Active | 1|XMLPULL V1 API (1.1.4.c)
15|Active | 1|Thoughtworks XStream (1.3.1)
47|Active | 1|Apache Felix Web Management Console (3.1.8)
163|Active | 1|Eclipse Compiler for Java (3.3.0)
551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
553|Active | 1|Apache Commons Logging (1.1.1)
606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
g! start 608
org.osgi.framework.BundleException: Unresolved constraint in bundle
Mybundle [608]:
Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
(&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
g!
If I have into my container D-OSGi bundle, why I have this error?? I don't
understand :__(
Thank in advance and sorry for the inconvenience
Jesus
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
I'd say all your bundles which works in Felix should also works in Karaf, as Karaf is based on Felix.
And for the CXF, as it will use a lot of specs like jaxb/jaxws/saaj, which not so easy for yourself to handle all of them, you can easily run into lot of issues here and there, but Karaf 2.3 just support CXF OOTB, why not use KARAF directly?
－－－－－－－－－－－－－
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: http://weibo.com/u/1473905042
On 2012-10-18, at 下午7:44, elMateo wrote:
> It's very difficult for me to change all my application from Apache Felix
> to Apache Karaf. I have a lot of bundles into Felix.
>
> Is there other form to develop a web service client bundle to run into
> Apache Felix?
>
> Best regards, Jesus.
>
> On Thu, Oct 18, 2012 at 12:22 PM, elMateo <so...@gmail.com> wrote:
>
>> Ok, I'm going to try with Apache Karaf.
>>
>> Thanks!!
>>
>>
>> On Thu, Oct 18, 2012 at 12:00 PM, Freeman Fang <fr...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3
>>> support CXF OOTB and it could be based on Felix.
>>> －－－－－－－－－－－－－
>>> 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: http://weibo.com/u/1473905042
>>>
>>> On 2012-10-18, at 下午5:47, Jesus wrote:
>>>
>>>> Thank you Daniel.
>>>>
>>>> I add that flag to wsdl2java tool. Now, my code has not errors. But,
>>> when I
>>>> add my bundle into Felix (that is running on Java6), I still have the
>>> same
>>>> errors. I don't understand with your second part of your message :(
>>>>
>>>> Excuse me for all these messages and doubts, but I'm stuck with this
>>> long
>>>> time :(
>>>>
>>>> Thanks in advance for all your help
>>>>
>>>> Jesus.
>>>>
>>>>
>>>> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
>>>> ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>>>>
>>>>>
>>>>> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
>>> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> yes I know, but I don't know how to resolve it. These classes are
>>>>>> autogenerated by wsdl2java tool of CXF
>>>>>
>>>>>
>>>>> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
>>> hitting
>>>>> one of the areas of JAXB that would require the full 2.2 api and
>>> runtime
>>>>> which you may not be getting (unless your Felix container is running on
>>>>> Java7).
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
>>>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1
>>>>>
>>>>> wrote:
>>>>>>
>>>>>>> It is something to do with:
>>>>>>>
>>>>>>> On 17/10/12 15:34, Jesus wrote:
>>>>>>>
>>>>>>>> The createAddActionResponse method has @XmlElementMapping on it, but
>>>>> it
>>>>>>>> doesn't
>>>>>>>> return a sub-type of JAXBElement.
>>>>>>>> this problem is related to the following location:
>>>>>>>> at
>>>>>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
>>>>>>>> javax.x
>>>>>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
>>>>>>>> defaultValue= ,
>>>>>>>> substitutionHeadNamespace=##default,
>>>>>>>> namespace=http://service.backend.connectio
>>>>>>>> n.optimizer/, name=AddActionResponse)
>>>>>>>> at public javax.xml.bind.JAXBElement
>>>>>>>> optimizer.connection.backen
>>>>>>>>
>>>>>>>
>>>>>
>>> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>>>>>
>>>>>>>
>>>>>>>> vice.AddActionResponse)
>>>>>>>> at optimizer.connection.backend.service.ObjectFactory
>>>>>>>
>>>>>>> Cheers, Sergey
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------
>>>>>>> If you reply to this email, your message will be added to the
>>>>> discussion
>>>>>>> below:
>>>>>>>
>>>>>>>
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
>>>>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>>>>> OSGi, click
>>>>>>> here<
>>>>>
>>>>>>> .
>>>>>>> NAML<
>>>>>
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>>>>
>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>>>>>
>>>>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>>>>
>>>>> --
>>>>> Daniel Kulp
>>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2>
>>> -
>>>>> http://dankulp.com/blog
>>>>>
>>>>> Talend Community Coder - http://coders.talend.com
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>> If you reply to this email, your message will be added to the
>>> discussion
>>>>> below:
>>>>>
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
>>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>>> OSGi, click
>>>>> here<
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
>>>>
>>>>> .
>>>>> NAML<
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
>>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>>
>>>
>>
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by elMateo <so...@gmail.com>.
Hello Daniel,
Thanks for all your responses.
I know that is more easy to work with Karaf, but I need to develop into
Felix (while there is any option for this). Anyway I have used my bundle
into Karaf and I have the next error: Activator start error in bundle
bundleDBConnector [57] javax.xml.ws.spi.FactoryFinder$ConfigurationError:
Provider org.apache.cxf.jaxws.spi.ProviderImpl not found.
My first option is Felix, so I'm working in this way; I trying to add into
my container all CXF dependencies.
Best regards and thanks a lot for your help
On Thu, Oct 18, 2012 at 4:12 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On Oct 18, 2012, at 7:44 AM, elMateo <so...@gmail.com> wrote:
>
> > It's very difficult for me to change all my application from Apache Felix
> > to Apache Karaf. I have a lot of bundles into Felix.
> >
> > Is there other form to develop a web service client bundle to run into
> > Apache Felix?
>
> You could try looking at the Karaf features.xml file that CXF provides:
>
>
> http://repo1.maven.org/maven2/org/apache/cxf/karaf/apache-cxf/2.7.0/apache-cxf-2.7.0-features.xml
>
> to see which bundles may be needed. That's really the strength of Karaf
> (IMO) is the ability to group all these things together into features that
> can be more easily tested together.
>
> You MAY be able to get it to work OK if you make sure the
> container/runtime is not exporting the javax.xml.bind and other related
> packages and make sure the SMX versions of those API's are deployed in the
> container. Then make sure you have the latest runtime bundles as well.
> (jaxb-impl for example)
>
> Dan
>
>
> > Best regards, Jesus.
> >
> > On Thu, Oct 18, 2012 at 12:22 PM, elMateo <so...@gmail.com> wrote:
> >
> >> Ok, I'm going to try with Apache Karaf.
> >>
> >> Thanks!!
> >>
> >>
> >> On Thu, Oct 18, 2012 at 12:00 PM, Freeman Fang <freeman.fang@gmail.com
> >wrote:
> >>
> >>> Hi,
> >>>
> >>> If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3
> >>> support CXF OOTB and it could be based on Felix.
> >>> －－－－－－－－－－－－－
> >>> 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: http://weibo.com/u/1473905042
> >>>
> >>> On 2012-10-18, at 下午5:47, Jesus wrote:
> >>>
> >>>> Thank you Daniel.
> >>>>
> >>>> I add that flag to wsdl2java tool. Now, my code has not errors. But,
> >>> when I
> >>>> add my bundle into Felix (that is running on Java6), I still have the
> >>> same
> >>>> errors. I don't understand with your second part of your message :(
> >>>>
> >>>> Excuse me for all these messages and doubts, but I'm stuck with this
> >>> long
> >>>> time :(
> >>>>
> >>>> Thanks in advance for all your help
> >>>>
> >>>> Jesus.
> >>>>
> >>>>
> >>>> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
> >>>> ml-node+s547215n5716878h55@n5.nabble.com> wrote:
> >>>>
> >>>>>
> >>>>> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
> >>> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> >>>>> wrote:
> >>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> yes I know, but I don't know how to resolve it. These classes are
> >>>>>> autogenerated by wsdl2java tool of CXF
> >>>>>
> >>>>>
> >>>>> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
> >>> hitting
> >>>>> one of the areas of JAXB that would require the full 2.2 api and
> >>> runtime
> >>>>> which you may not be getting (unless your Felix container is running
> on
> >>>>> Java7).
> >>>>>
> >>>>> Dan
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> >>>>>> [hidden email] <
> http://user/SendEmail.jtp?type=node&node=5716878&i=1
> >>>>>
> >>>>> wrote:
> >>>>>>
> >>>>>>> It is something to do with:
> >>>>>>>
> >>>>>>> On 17/10/12 15:34, Jesus wrote:
> >>>>>>>
> >>>>>>>> The createAddActionResponse method has @XmlElementMapping on it,
> but
> >>>>> it
> >>>>>>>> doesn't
> >>>>>>>> return a sub-type of JAXBElement.
> >>>>>>>> this problem is related to the following location:
> >>>>>>>> at
> >>>>>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> >>>>>>>> javax.x
> >>>>>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> >>>>>>>> defaultValue= ,
> >>>>>>>> substitutionHeadNamespace=##default,
> >>>>>>>> namespace=http://service.backend.connectio
> >>>>>>>> n.optimizer/, name=AddActionResponse)
> >>>>>>>> at public javax.xml.bind.JAXBElement
> >>>>>>>> optimizer.connection.backen
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
> >>>>>
> >>>>>>>
> >>>>>>>> vice.AddActionResponse)
> >>>>>>>> at
> optimizer.connection.backend.service.ObjectFactory
> >>>>>>>
> >>>>>>> Cheers, Sergey
> >>>>>>>
> >>>>>>>
> >>>>>>> ------------------------------
> >>>>>>> If you reply to this email, your message will be added to the
> >>>>> discussion
> >>>>>>> below:
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> >>>>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
> >>>>> OSGi, click
> >>>>>>> here<
> >>>>>
> >>>>>>> .
> >>>>>>> NAML<
> >>>>>
> >>>
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >>>>
> >>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> View this message in context:
> >>>>>
> >>>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
> >>>>>
> >>>>>> Sent from the cxf-user mailing list archive at Nabble.com.
> >>>>>
> >>>>> --
> >>>>> Daniel Kulp
> >>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2
> >
> >>> -
> >>>>> http://dankulp.com/blog
> >>>>>
> >>>>> Talend Community Coder - http://coders.talend.com
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>> If you reply to this email, your message will be added to the
> >>> discussion
> >>>>> below:
> >>>>>
> >>>>>
> >>>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> >>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
> >>> OSGi, click
> >>>>> here<
> >>>
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
> >>>>
> >>>>> .
> >>>>> NAML<
> >>>
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
> >>>> Sent from the cxf-user mailing list archive at Nabble.com.
> >>>
> >>>
> >>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Daniel Kulp <dk...@apache.org>.
On Oct 18, 2012, at 7:44 AM, elMateo <so...@gmail.com> wrote:
> It's very difficult for me to change all my application from Apache Felix
> to Apache Karaf. I have a lot of bundles into Felix.
>
> Is there other form to develop a web service client bundle to run into
> Apache Felix?
You could try looking at the Karaf features.xml file that CXF provides:
http://repo1.maven.org/maven2/org/apache/cxf/karaf/apache-cxf/2.7.0/apache-cxf-2.7.0-features.xml
to see which bundles may be needed. That's really the strength of Karaf (IMO) is the ability to group all these things together into features that can be more easily tested together.
You MAY be able to get it to work OK if you make sure the container/runtime is not exporting the javax.xml.bind and other related packages and make sure the SMX versions of those API's are deployed in the container. Then make sure you have the latest runtime bundles as well. (jaxb-impl for example)
Dan
> Best regards, Jesus.
>
> On Thu, Oct 18, 2012 at 12:22 PM, elMateo <so...@gmail.com> wrote:
>
>> Ok, I'm going to try with Apache Karaf.
>>
>> Thanks!!
>>
>>
>> On Thu, Oct 18, 2012 at 12:00 PM, Freeman Fang <fr...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3
>>> support CXF OOTB and it could be based on Felix.
>>> －－－－－－－－－－－－－
>>> 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: http://weibo.com/u/1473905042
>>>
>>> On 2012-10-18, at 下午5:47, Jesus wrote:
>>>
>>>> Thank you Daniel.
>>>>
>>>> I add that flag to wsdl2java tool. Now, my code has not errors. But,
>>> when I
>>>> add my bundle into Felix (that is running on Java6), I still have the
>>> same
>>>> errors. I don't understand with your second part of your message :(
>>>>
>>>> Excuse me for all these messages and doubts, but I'm stuck with this
>>> long
>>>> time :(
>>>>
>>>> Thanks in advance for all your help
>>>>
>>>> Jesus.
>>>>
>>>>
>>>> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
>>>> ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>>>>
>>>>>
>>>>> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
>>> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> yes I know, but I don't know how to resolve it. These classes are
>>>>>> autogenerated by wsdl2java tool of CXF
>>>>>
>>>>>
>>>>> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
>>> hitting
>>>>> one of the areas of JAXB that would require the full 2.2 api and
>>> runtime
>>>>> which you may not be getting (unless your Felix container is running on
>>>>> Java7).
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
>>>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1
>>>>>
>>>>> wrote:
>>>>>>
>>>>>>> It is something to do with:
>>>>>>>
>>>>>>> On 17/10/12 15:34, Jesus wrote:
>>>>>>>
>>>>>>>> The createAddActionResponse method has @XmlElementMapping on it, but
>>>>> it
>>>>>>>> doesn't
>>>>>>>> return a sub-type of JAXBElement.
>>>>>>>> this problem is related to the following location:
>>>>>>>> at
>>>>>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
>>>>>>>> javax.x
>>>>>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
>>>>>>>> defaultValue= ,
>>>>>>>> substitutionHeadNamespace=##default,
>>>>>>>> namespace=http://service.backend.connectio
>>>>>>>> n.optimizer/, name=AddActionResponse)
>>>>>>>> at public javax.xml.bind.JAXBElement
>>>>>>>> optimizer.connection.backen
>>>>>>>>
>>>>>>>
>>>>>
>>> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>>>>>
>>>>>>>
>>>>>>>> vice.AddActionResponse)
>>>>>>>> at optimizer.connection.backend.service.ObjectFactory
>>>>>>>
>>>>>>> Cheers, Sergey
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------
>>>>>>> If you reply to this email, your message will be added to the
>>>>> discussion
>>>>>>> below:
>>>>>>>
>>>>>>>
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
>>>>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>>>>> OSGi, click
>>>>>>> here<
>>>>>
>>>>>>> .
>>>>>>> NAML<
>>>>>
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>>>>
>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>>>>>
>>>>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>>>>
>>>>> --
>>>>> Daniel Kulp
>>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2>
>>> -
>>>>> http://dankulp.com/blog
>>>>>
>>>>> Talend Community Coder - http://coders.talend.com
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>> If you reply to this email, your message will be added to the
>>> discussion
>>>>> below:
>>>>>
>>>>>
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
>>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>>> OSGi, click
>>>>> here<
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
>>>>
>>>>> .
>>>>> NAML<
>>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
>>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>>
>>>
>>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by elMateo <so...@gmail.com>.
It's very difficult for me to change all my application from Apache Felix
to Apache Karaf. I have a lot of bundles into Felix.
Is there other form to develop a web service client bundle to run into
Apache Felix?
Best regards, Jesus.
On Thu, Oct 18, 2012 at 12:22 PM, elMateo <so...@gmail.com> wrote:
> Ok, I'm going to try with Apache Karaf.
>
> Thanks!!
>
>
> On Thu, Oct 18, 2012 at 12:00 PM, Freeman Fang <fr...@gmail.com>wrote:
>
>> Hi,
>>
>> If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3
>> support CXF OOTB and it could be based on Felix.
>> －－－－－－－－－－－－－
>> 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: http://weibo.com/u/1473905042
>>
>> On 2012-10-18, at 下午5:47, Jesus wrote:
>>
>> > Thank you Daniel.
>> >
>> > I add that flag to wsdl2java tool. Now, my code has not errors. But,
>> when I
>> > add my bundle into Felix (that is running on Java6), I still have the
>> same
>> > errors. I don't understand with your second part of your message :(
>> >
>> > Excuse me for all these messages and doubts, but I'm stuck with this
>> long
>> > time :(
>> >
>> > Thanks in advance for all your help
>> >
>> > Jesus.
>> >
>> >
>> > On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
>> > ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>> >
>> >>
>> >> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
>> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
>> >> wrote:
>> >>
>> >>> Hello,
>> >>>
>> >>> yes I know, but I don't know how to resolve it. These classes are
>> >>> autogenerated by wsdl2java tool of CXF
>> >>
>> >>
>> >> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
>> hitting
>> >> one of the areas of JAXB that would require the full 2.2 api and
>> runtime
>> >> which you may not be getting (unless your Felix container is running on
>> >> Java7).
>> >>
>> >> Dan
>> >>
>> >>
>> >>>
>> >>> Thanks.
>> >>>
>> >>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
>> >>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1
>> >>
>> >> wrote:
>> >>>
>> >>>> It is something to do with:
>> >>>>
>> >>>> On 17/10/12 15:34, Jesus wrote:
>> >>>>
>> >>>>> The createAddActionResponse method has @XmlElementMapping on it, but
>> >> it
>> >>>>> doesn't
>> >>>>> return a sub-type of JAXBElement.
>> >>>>> this problem is related to the following location:
>> >>>>> at
>> >>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
>> >>>>> javax.x
>> >>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
>> >>>>> defaultValue= ,
>> >>>>> substitutionHeadNamespace=##default,
>> >>>>> namespace=http://service.backend.connectio
>> >>>>> n.optimizer/, name=AddActionResponse)
>> >>>>> at public javax.xml.bind.JAXBElement
>> >>>>> optimizer.connection.backen
>> >>>>>
>> >>>>
>> >>
>> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>> >>
>> >>>>
>> >>>>> vice.AddActionResponse)
>> >>>>> at optimizer.connection.backend.service.ObjectFactory
>> >>>>
>> >>>> Cheers, Sergey
>> >>>>
>> >>>>
>> >>>> ------------------------------
>> >>>> If you reply to this email, your message will be added to the
>> >> discussion
>> >>>> below:
>> >>>>
>> >>>>
>> >>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
>> >>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>> >> OSGi, click
>> >>>> here<
>> >>
>> >>>> .
>> >>>> NAML<
>> >>
>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>> >
>> >>
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> View this message in context:
>> >>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>> >>
>> >>> Sent from the cxf-user mailing list archive at Nabble.com.
>> >>
>> >> --
>> >> Daniel Kulp
>> >> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2>
>> -
>> >> http://dankulp.com/blog
>> >>
>> >> Talend Community Coder - http://coders.talend.com
>> >>
>> >>
>> >>
>> >> ------------------------------
>> >> If you reply to this email, your message will be added to the
>> discussion
>> >> below:
>> >>
>> >>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
>> >> To unsubscribe from SOAP Web service client problem in ApacheFelix
>> OSGi, click
>> >> here<
>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
>> >
>> >> .
>> >> NAML<
>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>> >
>> >>
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
>> > Sent from the cxf-user mailing list archive at Nabble.com.
>>
>>
>
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by elMateo <so...@gmail.com>.
Ok, I'm going to try with Apache Karaf.
Thanks!!
On Thu, Oct 18, 2012 at 12:00 PM, Freeman Fang <fr...@gmail.com>wrote:
> Hi,
>
> If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3
> support CXF OOTB and it could be based on Felix.
> －－－－－－－－－－－－－
> 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: http://weibo.com/u/1473905042
>
> On 2012-10-18, at 下午5:47, Jesus wrote:
>
> > Thank you Daniel.
> >
> > I add that flag to wsdl2java tool. Now, my code has not errors. But,
> when I
> > add my bundle into Felix (that is running on Java6), I still have the
> same
> > errors. I don't understand with your second part of your message :(
> >
> > Excuse me for all these messages and doubts, but I'm stuck with this long
> > time :(
> >
> > Thanks in advance for all your help
> >
> > Jesus.
> >
> >
> > On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
> > ml-node+s547215n5716878h55@n5.nabble.com> wrote:
> >
> >>
> >> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> yes I know, but I don't know how to resolve it. These classes are
> >>> autogenerated by wsdl2java tool of CXF
> >>
> >>
> >> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
> hitting
> >> one of the areas of JAXB that would require the full 2.2 api and runtime
> >> which you may not be getting (unless your Felix container is running on
> >> Java7).
> >>
> >> Dan
> >>
> >>
> >>>
> >>> Thanks.
> >>>
> >>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> >>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
> >> wrote:
> >>>
> >>>> It is something to do with:
> >>>>
> >>>> On 17/10/12 15:34, Jesus wrote:
> >>>>
> >>>>> The createAddActionResponse method has @XmlElementMapping on it, but
> >> it
> >>>>> doesn't
> >>>>> return a sub-type of JAXBElement.
> >>>>> this problem is related to the following location:
> >>>>> at
> >>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> >>>>> javax.x
> >>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> >>>>> defaultValue= ,
> >>>>> substitutionHeadNamespace=##default,
> >>>>> namespace=http://service.backend.connectio
> >>>>> n.optimizer/, name=AddActionResponse)
> >>>>> at public javax.xml.bind.JAXBElement
> >>>>> optimizer.connection.backen
> >>>>>
> >>>>
> >>
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
> >>
> >>>>
> >>>>> vice.AddActionResponse)
> >>>>> at optimizer.connection.backend.service.ObjectFactory
> >>>>
> >>>> Cheers, Sergey
> >>>>
> >>>>
> >>>> ------------------------------
> >>>> If you reply to this email, your message will be added to the
> >> discussion
> >>>> below:
> >>>>
> >>>>
> >>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> >>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
> >> OSGi, click
> >>>> here<
> >>
> >>>> .
> >>>> NAML<
> >>
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
> >>
> >>> Sent from the cxf-user mailing list archive at Nabble.com.
> >>
> >> --
> >> Daniel Kulp
> >> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
> >> http://dankulp.com/blog
> >>
> >> Talend Community Coder - http://coders.talend.com
> >>
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the discussion
> >> below:
> >>
> >>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> >> To unsubscribe from SOAP Web service client problem in ApacheFelix
> OSGi, click
> >> here<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
> >
> >> .
> >> NAML<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >>
> >
> >
> >
> >
> > --
> > View this message in context:
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
> > Sent from the cxf-user mailing list archive at Nabble.com.
>
>
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
If possible, could you run with Apache Karaf 2.3? Apache Karaf 2.3 support CXF OOTB and it could be based on Felix.
－－－－－－－－－－－－－
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: http://weibo.com/u/1473905042
On 2012-10-18, at 下午5:47, Jesus wrote:
> Thank you Daniel.
>
> I add that flag to wsdl2java tool. Now, my code has not errors. But, when I
> add my bundle into Felix (that is running on Java6), I still have the same
> errors. I don't understand with your second part of your message :(
>
> Excuse me for all these messages and doubts, but I'm stuck with this long
> time :(
>
> Thanks in advance for all your help
>
> Jesus.
>
>
> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
> ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>
>>
>> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
>> wrote:
>>
>>> Hello,
>>>
>>> yes I know, but I don't know how to resolve it. These classes are
>>> autogenerated by wsdl2java tool of CXF
>>
>>
>> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be hitting
>> one of the areas of JAXB that would require the full 2.2 api and runtime
>> which you may not be getting (unless your Felix container is running on
>> Java7).
>>
>> Dan
>>
>>
>>>
>>> Thanks.
>>>
>>> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
>> wrote:
>>>
>>>> It is something to do with:
>>>>
>>>> On 17/10/12 15:34, Jesus wrote:
>>>>
>>>>> The createAddActionResponse method has @XmlElementMapping on it, but
>> it
>>>>> doesn't
>>>>> return a sub-type of JAXBElement.
>>>>> this problem is related to the following location:
>>>>> at
>>>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
>>>>> javax.x
>>>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
>>>>> defaultValue= ,
>>>>> substitutionHeadNamespace=##default,
>>>>> namespace=http://service.backend.connectio
>>>>> n.optimizer/, name=AddActionResponse)
>>>>> at public javax.xml.bind.JAXBElement
>>>>> optimizer.connection.backen
>>>>>
>>>>
>> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>>
>>>>
>>>>> vice.AddActionResponse)
>>>>> at optimizer.connection.backend.service.ObjectFactory
>>>>
>>>> Cheers, Sergey
>>>>
>>>>
>>>> ------------------------------
>>>> If you reply to this email, your message will be added to the
>> discussion
>>>> below:
>>>>
>>>>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
>>>> To unsubscribe from SOAP Web service client problem in ApacheFelix
>> OSGi, click
>>>> here<
>>
>>>> .
>>>> NAML<
>> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>>
>>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>> --
>> Daniel Kulp
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
>> http://dankulp.com/blog
>>
>> Talend Community Coder - http://coders.talend.com
>>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
>> To unsubscribe from SOAP Web service client problem in ApacheFelix OSGi, click
>> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
>> .
>> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Jesus <so...@gmail.com>.
Thank you Daniel.
I add that flag to wsdl2java tool. Now, my code has not errors. But, when I
add my bundle into Felix (that is running on Java6), I still have the same
errors. I don't understand with your second part of your message :(
Excuse me for all these messages and doubts, but I'm stuck with this long
time :(
Thanks in advance for all your help
Jesus.
On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>
> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> wrote:
>
> > Hello,
> >
> > yes I know, but I don't know how to resolve it. These classes are
> > autogenerated by wsdl2java tool of CXF
>
>
> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be hitting
> one of the areas of JAXB that would require the full 2.2 api and runtime
> which you may not be getting (unless your Felix container is running on
> Java7).
>
> Dan
>
>
> >
> > Thanks.
> >
> > On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
> wrote:
> >
> >> It is something to do with:
> >>
> >> On 17/10/12 15:34, Jesus wrote:
> >>
> >>> The createAddActionResponse method has @XmlElementMapping on it, but
> it
> >>> doesn't
> >>> return a sub-type of JAXBElement.
> >>> this problem is related to the following location:
> >>> at
> >> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> >>> javax.x
> >>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> >>> defaultValue= ,
> >>> substitutionHeadNamespace=##default,
> >>> namespace=http://service.backend.connectio
> >>> n.optimizer/, name=AddActionResponse)
> >>> at public javax.xml.bind.JAXBElement
> >>> optimizer.connection.backen
> >>>
> >>
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>
> >>
> >>> vice.AddActionResponse)
> >>> at optimizer.connection.backend.service.ObjectFactory
> >>
> >> Cheers, Sergey
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> >> To unsubscribe from SOAP Web service client problem in ApacheFelix
> OSGi, click
> >> here<
>
> >> .
> >> NAML<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
> >
> >
> > --
> > View this message in context:
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>
> > Sent from the cxf-user mailing list archive at Nabble.com.
>
> --
> Daniel Kulp
> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
> http://dankulp.com/blog
>
> Talend Community Coder - http://coders.talend.com
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> To unsubscribe from SOAP Web service client problem in ApacheFelix OSGi, click
> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716917.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Glen Mazza <gm...@talend.com>.
I can't test it because it's importing a schema that you hadn't
included. But if you plug it into my soap_client_tutorial sample:
https://github.com/gmazza/blog-samples/tree/master/soap_client_tutorial,
delete the WSClient.java file there and run mvn clean install you'll get
feedback from CXF on whether it will accept your WSDL. Also, with the
-PMetro option you can test it with Metro's wsdl2java equivalent to see
if you get better results.
HTH,
Glen
On 10/22/2012 06:59 AM, elMateo wrote:
> Sorry for my ignorance, but it's possible that my wsdl isn't
> compatible with CXF??
>
> I attached my wsdl.
>
> Thanks!
>
> On Thu, Oct 18, 2012 at 4:52 PM, Jesus <soyelmateo@gmail.com
> <ma...@gmail.com>> wrote:
>
> I forgot to comment in my last mail that I only want to develop a
> SOAP Web
> Service Client into my Felix container.
>
> So if there is somebody that know other form to do this, it would be
> wonderful comment. I'm not required to do with CXF.
>
> Thanks and forgive me for any inconvenience.
>
> Best regards, Jesús.
>
>
> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
> ml-node+s547215n5716878h55@n5.nabble.com
> <ma...@n5.nabble.com>> wrote:
>
> >
> > On Oct 17, 2012, at 11:14 AM, Jesus <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> > wrote:
> >
> > > Hello,
> > >
> > > yes I know, but I don't know how to resolve it. These classes are
> > > autogenerated by wsdl2java tool of CXF
> >
> >
> > Try adding "-fe jaxws21" flags to the wsdl2java tool. You may
> be hitting
> > one of the areas of JAXB that would require the full 2.2 api and
> runtime
> > which you may not be getting (unless your Felix container is
> running on
> > Java7).
> >
> > Dan
> >
> >
> > >
> > > Thanks.
> > >
> > > On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> > > [hidden email]
> <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
> > wrote:
> > >
> > >> It is something to do with:
> > >>
> > >> On 17/10/12 15:34, Jesus wrote:
> > >>
> > >>> The createAddActionResponse method has @XmlElementMapping on
> it, but
> > it
> > >>> doesn't
> > >>> return a sub-type of JAXBElement.
> > >>> this problem is related to the following location:
> > >>> at
> > >> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> > >>> javax.x
> > >>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> > >>> defaultValue= ,
> > >>> substitutionHeadNamespace=##default,
> > >>> namespace=http://service.backend.connectio
> > >>> n.optimizer/, name=AddActionResponse)
> > >>> at public javax.xml.bind.JAXBElement
> > >>> optimizer.connection.backen
> > >>>
> > >>
> >
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
> >
> > >>
> > >>> vice.AddActionResponse)
> > >>> at
> optimizer.connection.backend.service.ObjectFactory
> > >>
> > >> Cheers, Sergey
> > >>
> > >>
> > >> ------------------------------
> > >> If you reply to this email, your message will be added to the
> > discussion
> > >> below:
> > >>
> > >>
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> > >> To unsubscribe from SOAP Web service client problem in
> ApacheFelix
> > OSGi, click
> > >> here<
> >
> > >> .
> > >> NAML<
> >
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
> > >>
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
> >
> > > Sent from the cxf-user mailing list archive at Nabble.com.
> >
> > --
> > Daniel Kulp
> > [hidden email]
> <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
> > http://dankulp.com/blog
> >
> > Talend Community Coder - http://coders.talend.com
> >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the
> discussion
> > below:
> >
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> > To unsubscribe from SOAP Web service client problem in
> ApacheFelix OSGi, click
> >
> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
> > .
> >
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716941.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by elMateo <so...@gmail.com>.
Sorry for my ignorance, but it's possible that my wsdl isn't compatible
with CXF??
I attached my wsdl.
Thanks!
On Thu, Oct 18, 2012 at 4:52 PM, Jesus <so...@gmail.com> wrote:
> I forgot to comment in my last mail that I only want to develop a SOAP Web
> Service Client into my Felix container.
>
> So if there is somebody that know other form to do this, it would be
> wonderful comment. I'm not required to do with CXF.
>
> Thanks and forgive me for any inconvenience.
>
> Best regards, Jes�s.
>
>
> On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
> ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>
> >
> > On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> > wrote:
> >
> > > Hello,
> > >
> > > yes I know, but I don't know how to resolve it. These classes are
> > > autogenerated by wsdl2java tool of CXF
> >
> >
> > Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be
> hitting
> > one of the areas of JAXB that would require the full 2.2 api and runtime
> > which you may not be getting (unless your Felix container is running on
> > Java7).
> >
> > Dan
> >
> >
> > >
> > > Thanks.
> > >
> > > On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> > > [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
> > wrote:
> > >
> > >> It is something to do with:
> > >>
> > >> On 17/10/12 15:34, Jesus wrote:
> > >>
> > >>> The createAddActionResponse method has @XmlElementMapping on it, but
> > it
> > >>> doesn't
> > >>> return a sub-type of JAXBElement.
> > >>> this problem is related to the following location:
> > >>> at
> > >> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> > >>> javax.x
> > >>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> > >>> defaultValue= ,
> > >>> substitutionHeadNamespace=##default,
> > >>> namespace=http://service.backend.connectio
> > >>> n.optimizer/, name=AddActionResponse)
> > >>> at public javax.xml.bind.JAXBElement
> > >>> optimizer.connection.backen
> > >>>
> > >>
> >
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
> >
> > >>
> > >>> vice.AddActionResponse)
> > >>> at optimizer.connection.backend.service.ObjectFactory
> > >>
> > >> Cheers, Sergey
> > >>
> > >>
> > >> ------------------------------
> > >> If you reply to this email, your message will be added to the
> > discussion
> > >> below:
> > >>
> > >>
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> > >> To unsubscribe from SOAP Web service client problem in ApacheFelix
> > OSGi, click
> > >> here<
> >
> > >> .
> > >> NAML<
> >
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
> > >>
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
> >
> > > Sent from the cxf-user mailing list archive at Nabble.com.
> >
> > --
> > Daniel Kulp
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
> > http://dankulp.com/blog
> >
> > Talend Community Coder - http://coders.talend.com
> >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> > To unsubscribe from SOAP Web service client problem in ApacheFelix
> OSGi, click
> > here<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1
> >
> > .
> > NAML<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716941.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Jesus <so...@gmail.com>.
I forgot to comment in my last mail that I only want to develop a SOAP Web
Service Client into my Felix container.
So if there is somebody that know other form to do this, it would be
wonderful comment. I'm not required to do with CXF.
Thanks and forgive me for any inconvenience.
Best regards, Jesús.
On Wed, Oct 17, 2012 at 8:36 PM, Daniel Kulp [via CXF] <
ml-node+s547215n5716878h55@n5.nabble.com> wrote:
>
> On Oct 17, 2012, at 11:14 AM, Jesus <[hidden email]<http://user/SendEmail.jtp?type=node&node=5716878&i=0>>
> wrote:
>
> > Hello,
> >
> > yes I know, but I don't know how to resolve it. These classes are
> > autogenerated by wsdl2java tool of CXF
>
>
> Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be hitting
> one of the areas of JAXB that would require the full 2.2 api and runtime
> which you may not be getting (unless your Felix container is running on
> Java7).
>
> Dan
>
>
> >
> > Thanks.
> >
> > On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=1>>
> wrote:
> >
> >> It is something to do with:
> >>
> >> On 17/10/12 15:34, Jesus wrote:
> >>
> >>> The createAddActionResponse method has @XmlElementMapping on it, but
> it
> >>> doesn't
> >>> return a sub-type of JAXBElement.
> >>> this problem is related to the following location:
> >>> at
> >> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> >>> javax.x
> >>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> >>> defaultValue= ,
> >>> substitutionHeadNamespace=##default,
> >>> namespace=http://service.backend.connectio
> >>> n.optimizer/, name=AddActionResponse)
> >>> at public javax.xml.bind.JAXBElement
> >>> optimizer.connection.backen
> >>>
> >>
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>
> >>
> >>> vice.AddActionResponse)
> >>> at optimizer.connection.backend.service.ObjectFactory
> >>
> >> Cheers, Sergey
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> >> To unsubscribe from SOAP Web service client problem in ApacheFelix
> OSGi, click
> >> here<
>
> >> .
> >> NAML<
> http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> >>
> >
> >
> >
> >
> > --
> > View this message in context:
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
>
> > Sent from the cxf-user mailing list archive at Nabble.com.
>
> --
> Daniel Kulp
> [hidden email] <http://user/SendEmail.jtp?type=node&node=5716878&i=2> -
> http://dankulp.com/blog
>
> Talend Community Coder - http://coders.talend.com
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716878.html
> To unsubscribe from SOAP Web service client problem in ApacheFelix OSGi, click
> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716941.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Daniel Kulp <dk...@apache.org>.
On Oct 17, 2012, at 11:14 AM, Jesus <so...@gmail.com> wrote:
> Hello,
>
> yes I know, but I don't know how to resolve it. These classes are
> autogenerated by wsdl2java tool of CXF
Try adding "-fe jaxws21" flags to the wsdl2java tool. You may be hitting one of the areas of JAXB that would require the full 2.2 api and runtime which you may not be getting (unless your Felix container is running on Java7).
Dan
>
> Thanks.
>
> On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
> ml-node+s547215n5716836h53@n5.nabble.com> wrote:
>
>> It is something to do with:
>>
>> On 17/10/12 15:34, Jesus wrote:
>>
>>> The createAddActionResponse method has @XmlElementMapping on it, but it
>>> doesn't
>>> return a sub-type of JAXBElement.
>>> this problem is related to the following location:
>>> at
>> @javax.xml.bind.annotation.XmlElementDecl(scope=class
>>> javax.x
>>> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
>>> defaultValue= ,
>>> substitutionHeadNamespace=##default,
>>> namespace=http://service.backend.connectio
>>> n.optimizer/, name=AddActionResponse)
>>> at public javax.xml.bind.JAXBElement
>>> optimizer.connection.backen
>>>
>> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>>
>>> vice.AddActionResponse)
>>> at optimizer.connection.backend.service.ObjectFactory
>>
>> Cheers, Sergey
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
>> To unsubscribe from SOAP Web service client problem in ApacheFelix OSGi, click
>> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
>> .
>> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Jesus <so...@gmail.com>.
Hello,
yes I know, but I don't know how to resolve it. These classes are
autogenerated by wsdl2java tool of CXF
Thanks.
On Wed, Oct 17, 2012 at 4:38 PM, Sergey Beryozkin-5 [via CXF] <
ml-node+s547215n5716836h53@n5.nabble.com> wrote:
> It is something to do with:
>
> On 17/10/12 15:34, Jesus wrote:
>
> > The createAddActionResponse method has @XmlElementMapping on it, but it
> > doesn't
> > return a sub-type of JAXBElement.
> > this problem is related to the following location:
> > at
> @javax.xml.bind.annotation.XmlElementDecl(scope=class
> > javax.x
> > ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> > defaultValue= ,
> > substitutionHeadNamespace=##default,
> > namespace=http://service.backend.connectio
> > n.optimizer/, name=AddActionResponse)
> > at public javax.xml.bind.JAXBElement
> > optimizer.connection.backen
> >
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
>
> > vice.AddActionResponse)
> > at optimizer.connection.backend.service.ObjectFactory
>
> Cheers, Sergey
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716836.html
> To unsubscribe from SOAP Web service client problem in ApacheFelix OSGi, click
> here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5716645&code=c295ZWxtYXRlb0BnbWFpbC5jb218NTcxNjY0NXwtODU2MzA5NTk1>
> .
> NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716841.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Sergey Beryozkin <sb...@gmail.com>.
It is something to do with:
On 17/10/12 15:34, Jesus wrote:
> The createAddActionResponse method has @XmlElementMapping on it, but it
> doesn't
> return a sub-type of JAXBElement.
> this problem is related to the following location:
> at @javax.xml.bind.annotation.XmlElementDecl(scope=class
> javax.x
> ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
> defaultValue= ,
> substitutionHeadNamespace=##default,
> namespace=http://service.backend.connectio
> n.optimizer/, name=AddActionResponse)
> at public javax.xml.bind.JAXBElement
> optimizer.connection.backen
> d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
> vice.AddActionResponse)
> at optimizer.connection.backend.service.ObjectFactory
Cheers, Sergey
Re: SOAP Web service client problem in ApacheFelix OSGi
Posted by Jesus <so...@gmail.com>.
Hello all,
I'm trying to develop a web service client with CXF into Apache Felix.
This is the error that shows me Felix:
/INFO: Can not initialize the default wsdl from
ServiceBackEndConnection.wsdl
17-oct-2012 16:26:48
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromWSDL
INFO: Creating Service
{http://service.backend.connection.optimizer/}ServiceBack
EndConnection from WSDL:
file:/C:/felix-framework-4.0.2Lunes/ServiceBackEndConne
ction.wsdl
org.osgi.framework.BundleException: Activator start error in bundle
bundleDBConn
ector [625].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2027)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1895)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)
at org.apache.felix.gogo.command.Basic.start(Basic.java:729)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:
82)
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:4
03)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessi
onImpl.java:89)
at org.apache.felix.gogo.shell.Console.run(Console.java:62)
at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:
82)
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:4
03)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessi
onImpl.java:89)
at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.Serv
iceConstructionException
at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:332)
at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:317)
at javax.xml.ws.Service.getPort(Service.java:40)
at
optimizer.connection.backend.service.ServiceBackEndConnection_Service
.getServiceBackEndConnectionPort(ServiceBackEndConnection_Service.java:76)
at
com.database.bundle.bridgeDB.BackEndConnection.invokeService(BackEndC
onnection.java:37)
at com.database.bundle.Activator.start(Activator.java:34)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
ion.java:641)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1977)
... 31 more
Caused by: org.apache.cxf.service.factory.ServiceConstructionException
at
org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:3
39)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServ
iceFromWSDL(ReflectionServiceFactoryBean.java:432)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ
eServiceModel(ReflectionServiceFactoryBean.java:528)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re
flectionServiceFactoryBean.java:278)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServ
iceFactoryBean.java:179)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoi
nt(AbstractWSDLBasedEndpointFactory.java:99)
at
org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.ja
va:51)
at
org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFact
oryBean.java:102)
at
org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBe
an.java:115)
at org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:458)
at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:330)
... 38 more
Caused by: javax.xml.bind.JAXBException: Unable to create context
- with linked exception:
[java.lang.reflect.InvocationTargetException]
at javax.xml.bind.ContextFinder.find(ContextFinder.java:93)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:65)
at
org.apache.cxf.jaxb.JAXBDataBinding.createContext(JAXBDataBinding.jav
a:562)
at
org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContextAndSchemas(JAXBD
ataBinding.java:502)
at
org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:3
22)
... 48 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:91)
... 52 more
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 4 counts
of
IllegalAnnotationExceptions
The createHello method has @XmlElementMapping on it, but it doesn't return a
sub
-type of JAXBElement.
this problem is related to the following location:
at @javax.xml.bind.annotation.XmlElementDecl(scope=class
javax.x
ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
defaultValue= ,
substitutionHeadNamespace=##default,
namespace=http://service.backend.connectio
n.optimizer/, name=hello)
at public javax.xml.bind.JAXBElement
optimizer.connection.backen
d.service.ObjectFactory.createHello(optimizer.connection.backend.service.Hello)
at optimizer.connection.backend.service.ObjectFactory
The createHelloResponse method has @XmlElementMapping on it, but it doesn't
retu
rn a sub-type of JAXBElement.
this problem is related to the following location:
at @javax.xml.bind.annotation.XmlElementDecl(scope=class
javax.x
ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
defaultValue= ,
substitutionHeadNamespace=##default,
namespace=http://service.backend.connectio
n.optimizer/, name=helloResponse)
at public javax.xml.bind.JAXBElement
optimizer.connection.backen
d.service.ObjectFactory.createHelloResponse(optimizer.connection.backend.service
.HelloResponse)
at optimizer.connection.backend.service.ObjectFactory
The createAddActionResponse method has @XmlElementMapping on it, but it
doesn't
return a sub-type of JAXBElement.
this problem is related to the following location:
at @javax.xml.bind.annotation.XmlElementDecl(scope=class
javax.x
ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
defaultValue= ,
substitutionHeadNamespace=##default,
namespace=http://service.backend.connectio
n.optimizer/, name=AddActionResponse)
at public javax.xml.bind.JAXBElement
optimizer.connection.backen
d.service.ObjectFactory.createAddActionResponse(optimizer.connection.backend.ser
vice.AddActionResponse)
at optimizer.connection.backend.service.ObjectFactory
The createAddAction method has @XmlElementMapping on it, but it doesn't
return a
sub-type of JAXBElement.
this problem is related to the following location:
at @javax.xml.bind.annotation.XmlElementDecl(scope=class
javax.x
ml.bind.annotation.XmlElementDecl$GLOBAL, substitutionHeadName=,
defaultValue= ,
substitutionHeadNamespace=##default,
namespace=http://service.backend.connectio
n.optimizer/, name=AddAction)
at public javax.xml.bind.JAXBElement
optimizer.connection.backen
d.service.ObjectFactory.createAddAction(optimizer.connection.backend.service.Add
Action)
at optimizer.connection.backend.service.ObjectFactory
at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check
(IllegalAnnotationsException.java:102)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContex
tImpl.java:438)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.ja
va:286)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
139)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
117)
... 57 more
javax.xml.ws.WebServiceException:
org.apache.cxf.service.factory.ServiceConstruc
tionException/
Can anyone help me? Please
Thanks in advance.
Jesus wrote
> Hello all,
>
> I'm developing a SOAP web service bundle into Apache Felix with
> cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
>
> I have a wsdl file and I can access to this service from a navigator to
> see
> its properties. But I can't develop a bundle client from Felix. (In other
> mails I asked about REST services, but I haven't an interface to access
> directly to these REST services)
>
> I attach my Felix container and the error that it shows me.
>
> START LEVEL 1
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.0.2)
> 1|Active | 1|Apache Felix Bundle Repository (1.6.6)
> 2|Active | 1|Apache Felix Gogo Command (0.12.0)
> 3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)
> 5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
> 6|Active | 1|Distributed OSGi Distribution Software
> Single-Bundle Dis
> tribution (1.2.0)
> 10|Active | 1|Apache ANT (1.8.1)
> 11|Active | 1|ANTLR Runtime (3.1.3)
> 12|Active | 1|mvel2 (2.1.0.drools6)
> 13|Active | 1|Java XML Stream API (StAX) (1.0.1)
> 14|Active | 1|XMLPULL V1 API (1.1.4.c)
> 15|Active | 1|Thoughtworks XStream (1.3.1)
> 47|Active | 1|Apache Felix Web Management Console (3.1.8)
> 163|Active | 1|Eclipse Compiler for Java (3.3.0)
> 551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
> 552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
> 553|Active | 1|Apache Commons Logging (1.1.1)
> 606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
> 608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
> g! start 608
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> Mybundle [608]:
> Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
> g!
>
> If I have into my container D-OSGi bundle, why I have this error?? I don't
> understand :__(
>
> Thank in advance and sorry for the inconvenience
>
> Jesus
Jesus wrote
> Hello all,
>
> I'm developing a SOAP web service bundle into Apache Felix with
> cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
>
> I have a wsdl file and I can access to this service from a navigator to
> see
> its properties. But I can't develop a bundle client from Felix. (In other
> mails I asked about REST services, but I haven't an interface to access
> directly to these REST services)
>
> I attach my Felix container and the error that it shows me.
>
> START LEVEL 1
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.0.2)
> 1|Active | 1|Apache Felix Bundle Repository (1.6.6)
> 2|Active | 1|Apache Felix Gogo Command (0.12.0)
> 3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)
> 5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
> 6|Active | 1|Distributed OSGi Distribution Software
> Single-Bundle Dis
> tribution (1.2.0)
> 10|Active | 1|Apache ANT (1.8.1)
> 11|Active | 1|ANTLR Runtime (3.1.3)
> 12|Active | 1|mvel2 (2.1.0.drools6)
> 13|Active | 1|Java XML Stream API (StAX) (1.0.1)
> 14|Active | 1|XMLPULL V1 API (1.1.4.c)
> 15|Active | 1|Thoughtworks XStream (1.3.1)
> 47|Active | 1|Apache Felix Web Management Console (3.1.8)
> 163|Active | 1|Eclipse Compiler for Java (3.3.0)
> 551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
> 552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
> 553|Active | 1|Apache Commons Logging (1.1.1)
> 606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
> 608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
> g! start 608
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> Mybundle [608]:
> Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
> g!
>
> If I have into my container D-OSGi bundle, why I have this error?? I don't
> understand :__(
>
> Thank in advance and sorry for the inconvenience
>
> Jesus
Jesus wrote
> Hello all,
>
> I'm developing a SOAP web service bundle into Apache Felix with
> cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
>
> I have a wsdl file and I can access to this service from a navigator to
> see
> its properties. But I can't develop a bundle client from Felix. (In other
> mails I asked about REST services, but I haven't an interface to access
> directly to these REST services)
>
> I attach my Felix container and the error that it shows me.
>
> START LEVEL 1
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.0.2)
> 1|Active | 1|Apache Felix Bundle Repository (1.6.6)
> 2|Active | 1|Apache Felix Gogo Command (0.12.0)
> 3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)
> 5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
> 6|Active | 1|Distributed OSGi Distribution Software
> Single-Bundle Dis
> tribution (1.2.0)
> 10|Active | 1|Apache ANT (1.8.1)
> 11|Active | 1|ANTLR Runtime (3.1.3)
> 12|Active | 1|mvel2 (2.1.0.drools6)
> 13|Active | 1|Java XML Stream API (StAX) (1.0.1)
> 14|Active | 1|XMLPULL V1 API (1.1.4.c)
> 15|Active | 1|Thoughtworks XStream (1.3.1)
> 47|Active | 1|Apache Felix Web Management Console (3.1.8)
> 163|Active | 1|Eclipse Compiler for Java (3.3.0)
> 551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
> 552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
> 553|Active | 1|Apache Commons Logging (1.1.1)
> 606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
> 608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
> g! start 608
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> Mybundle [608]:
> Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
> g!
>
> If I have into my container D-OSGi bundle, why I have this error?? I don't
> understand :__(
>
> Thank in advance and sorry for the inconvenience
>
> Jesus
Jesus wrote
> Hello all,
>
> I'm developing a SOAP web service bundle into Apache Felix with
> cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
>
> I have a wsdl file and I can access to this service from a navigator to
> see
> its properties. But I can't develop a bundle client from Felix. (In other
> mails I asked about REST services, but I haven't an interface to access
> directly to these REST services)
>
> I attach my Felix container and the error that it shows me.
>
> START LEVEL 1
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.0.2)
> 1|Active | 1|Apache Felix Bundle Repository (1.6.6)
> 2|Active | 1|Apache Felix Gogo Command (0.12.0)
> 3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)
> 5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
> 6|Active | 1|Distributed OSGi Distribution Software
> Single-Bundle Dis
> tribution (1.2.0)
> 10|Active | 1|Apache ANT (1.8.1)
> 11|Active | 1|ANTLR Runtime (3.1.3)
> 12|Active | 1|mvel2 (2.1.0.drools6)
> 13|Active | 1|Java XML Stream API (StAX) (1.0.1)
> 14|Active | 1|XMLPULL V1 API (1.1.4.c)
> 15|Active | 1|Thoughtworks XStream (1.3.1)
> 47|Active | 1|Apache Felix Web Management Console (3.1.8)
> 163|Active | 1|Eclipse Compiler for Java (3.3.0)
> 551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
> 552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
> 553|Active | 1|Apache Commons Logging (1.1.1)
> 606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
> 608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
> g! start 608
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> Mybundle [608]:
> Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
> g!
>
> If I have into my container D-OSGi bundle, why I have this error?? I don't
> understand :__(
>
> Thank in advance and sorry for the inconvenience
>
> Jesus
Jesus wrote
> Hello all,
>
> I'm developing a SOAP web service bundle into Apache Felix with
> cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar<http://repository.apache.org/service/local/repositories/releases/content/org/apache/cxf/dosgi/cxf-dosgi-ri-singlebundle-distribution/1.3.1/cxf-dosgi-ri-singlebundle-distribution-1.3.1.jar>
>
> I have a wsdl file and I can access to this service from a navigator to
> see
> its properties. But I can't develop a bundle client from Felix. (In other
> mails I asked about REST services, but I haven't an interface to access
> directly to these REST services)
>
> I attach my Felix container and the error that it shows me.
>
> START LEVEL 1
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.0.2)
> 1|Active | 1|Apache Felix Bundle Repository (1.6.6)
> 2|Active | 1|Apache Felix Gogo Command (0.12.0)
> 3|Active | 1|Apache Felix Gogo Runtime (0.10.0)
> 4|Active | 1|Apache Felix Gogo Shell (0.10.0)
> 5|Resolved | 1|osgi.cmpn (4.2.0.200908310645)
> 6|Active | 1|Distributed OSGi Distribution Software
> Single-Bundle Dis
> tribution (1.2.0)
> 10|Active | 1|Apache ANT (1.8.1)
> 11|Active | 1|ANTLR Runtime (3.1.3)
> 12|Active | 1|mvel2 (2.1.0.drools6)
> 13|Active | 1|Java XML Stream API (StAX) (1.0.1)
> 14|Active | 1|XMLPULL V1 API (1.1.4.c)
> 15|Active | 1|Thoughtworks XStream (1.3.1)
> 47|Active | 1|Apache Felix Web Management Console (3.1.8)
> 163|Active | 1|Eclipse Compiler for Java (3.3.0)
> 551|Active | 1|Apache HttpClient OSGi bundle (4.2.1)
> 552|Active | 1|Apache HttpCore OSGi bundle (4.2.1)
> 553|Active | 1|Apache Commons Logging (1.1.1)
> 606|Active | 1|ServiceInterfaceBackEnd (1.0.0.SNAPSHOT)
> 608|Installed | 1|Mybundle (1.0.0.SNAPSHOT)
> g! start 608
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> Mybundle [608]:
> Unable to resolve 608.0: missing requirement [608.0] osgi.wiring.package;
> (&(osgi.wiring.package=javax.xml.bind)(version>=2.1.0)(!(version>=3.0.0)))
> g!
>
> If I have into my container D-OSGi bundle, why I have this error?? I don't
> understand :__(
>
> Thank in advance and sorry for the inconvenience
>
> Jesus
--
View this message in context: http://cxf.547215.n5.nabble.com/SOAP-Web-service-client-problem-in-ApacheFelix-OSGi-tp5716645p5716835.html
Sent from the cxf-user mailing list archive at Nabble.com.