You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Jaime Hablutzel Egoavil <ha...@gmail.com> on 2009/10/26 20:07:55 UTC
cxf client inside servicemix
Hi, I'm testing servicemix 4 for a week until now and I can't get working a
cxf web service inside servicemix, that queries another external web service
inside its implementation and connects to ldap using DirContext (its fails
because of an intercepting stuff inside servicemix).
Can someone give me an example of I cxf web service inside servicemix, with
a ws client inside of it? And, an example of an application connecting to
ldap from inside of one cxf web service?
Thank you very much.
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by rsmaoui <s-...@hotmail.com>.
Hi,
thanks for your responce.
In fact i need more explanation,
i want to invoke externalwebservice, this webservice return message, then i
need to send this message to another external webservice. i created quartz
servicemix component to trigger cxf-bc provider and now i don't know how
send this message to second bc. can you explain me more please.
i used jbi component because there is an existing project and i need to add
new components. it's possible to recreate the project, but i don't know if
all JBI components have similar components in camel like servicemix-quartz
component.
thanks.
--
View this message in context: http://servicemix.396122.n5.nabble.com/cxf-client-inside-servicemix-tp401919p5713449.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: cxf client inside servicemix
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
First of all, cxf-bc provider can also process response message, so
you can use it with other JBI component which expect a response.
But we don't suggest you still use JBI component if you start as a new
project, as JBI is kinda deprecated, you should use camel related
component instead.
Freeman
On 2012-6-1, at 上午12:48, rsmaoui wrote:
> Hi Jean,
>
> in the case of an external webservice that return value and this
> value will
> be used by anothor servicemix component, so i think it's not
> possible to use
> cfx-bc component in provider mode as a webservice client, else how
> recover
> the value and send it to the second component !!
>
>
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/cxf-client-inside-servicemix-tp401919p5713437.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
Re: cxf client inside servicemix
Posted by rsmaoui <s-...@hotmail.com>.
Hi Jean,
in the case of an external webservice that return value and this value will
be used by anothor servicemix component, so i think it's not possible to use
cfx-bc component in provider mode as a webservice client, else how recover
the value and send it to the second component !!
--
View this message in context: http://servicemix.396122.n5.nabble.com/cxf-client-inside-servicemix-tp401919p5713437.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: cxf client inside servicemix
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jaime,
in fact your question is very wide.
You have several ways to do it :
- you can use a pure JBI packaging into SMX4. In this case, you can use
a servicemix-bean based SU (in consumer mode/scheduler) to query the
LDAP and send a message to a servicemix-cxf-bc based SU (in provider
mode). You build your SA and deploy it directly in SMX4 (by copying it
in the deploy directory or using mvn jbi:mvn:... provisioning).
- another solution is to use component from an OSGi point of view using
the EndpointExporter. In that case, you can merge your xbean in a single
XML file and add the EndpointExporter bean to deploy. In that case, you
can package your business logic in an OSGi bundle, registering a service
that you can use.
Regards
JB
Jaime Hablutzel Egoavil wrote:
> ok, now I can see new concepts:
>
> CXF-BC: Where can I find an example of this for servicemix 4?
>
> Can you please example that about servicemix-bean to interact with LDAP,
> is a way to avoid servicemix interceptors?
>
> And yes, I heard bout servicemix-ldap to work with ldap, should I
> install it as an osgi bundle?
>
> Thank you.
>
>
> On Mon, Oct 26, 2009 at 2:14 PM, Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> wrote:
>
> Why don't using CXF-BC in provider mode ?
> CXF-BC in provider mode acts as a WebService client.
>
> You can use the provider from a servicemix-bean to interact with
> your LDAP.
>
> FYI, a servicemix-ldap component already exists. I'm still working
> on it but it's already usable.
>
> Regards
> JB
>
>
> Jaime Hablutzel Egoavil wrote:
>
> Hi, I'm testing servicemix 4 for a week until now and I can't
> get working a
> cxf web service inside servicemix, that queries another external
> web service
> inside its implementation and connects to ldap using DirContext
> (its fails
> because of an intercepting stuff inside servicemix).
> Can someone give me an example of I cxf web service inside
> servicemix, with
> a ws client inside of it? And, an example of an application
> connecting to
> ldap from inside of one cxf web service?
>
> Thank you very much.
>
>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net <ma...@nanthrax.net>
> PGP : 17D4F086
>
>
>
>
> --
> Jaime Hablutzel
>
> (tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Jaime Hablutzel Egoavil <ha...@gmail.com>.
ok, now I can see new concepts:
CXF-BC: Where can I find an example of this for servicemix 4?
Can you please example that about servicemix-bean to interact with LDAP, is
a way to avoid servicemix interceptors?
And yes, I heard bout servicemix-ldap to work with ldap, should I install it
as an osgi bundle?
Thank you.
On Mon, Oct 26, 2009 at 2:14 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Why don't using CXF-BC in provider mode ?
> CXF-BC in provider mode acts as a WebService client.
>
> You can use the provider from a servicemix-bean to interact with your LDAP.
>
> FYI, a servicemix-ldap component already exists. I'm still working on it
> but it's already usable.
>
> Regards
> JB
>
>
> Jaime Hablutzel Egoavil wrote:
>
>> Hi, I'm testing servicemix 4 for a week until now and I can't get working
>> a
>> cxf web service inside servicemix, that queries another external web
>> service
>> inside its implementation and connects to ldap using DirContext (its fails
>> because of an intercepting stuff inside servicemix).
>> Can someone give me an example of I cxf web service inside servicemix,
>> with
>> a ws client inside of it? And, an example of an application connecting to
>> ldap from inside of one cxf web service?
>>
>> Thank you very much.
>>
>>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
>
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Why don't using CXF-BC in provider mode ?
CXF-BC in provider mode acts as a WebService client.
You can use the provider from a servicemix-bean to interact with your LDAP.
FYI, a servicemix-ldap component already exists. I'm still working on it
but it's already usable.
Regards
JB
Jaime Hablutzel Egoavil wrote:
> Hi, I'm testing servicemix 4 for a week until now and I can't get working a
> cxf web service inside servicemix, that queries another external web service
> inside its implementation and connects to ldap using DirContext (its fails
> because of an intercepting stuff inside servicemix).
> Can someone give me an example of I cxf web service inside servicemix, with
> a ws client inside of it? And, an example of an application connecting to
> ldap from inside of one cxf web service?
>
> Thank you very much.
>
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086
Re: cxf client inside servicemix
Posted by Jaime Hablutzel Egoavil <ha...@gmail.com>.
I´ll try it ASAP, thank you
On Tue, Oct 27, 2009 at 2:24 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> Other than the soapenv:encodingStyle attribute which I don't think you'll
> ever
> get output other than writing an interceptor to add it, you could probably
> do
> something like:
>
> @WebService(targetNamespace="http://hndac.gob.pe/soasighhc/message/"
> ....)
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> public interface MyService {
>
> @WebResult(name = "result)
> @WebMethod(operationName = "getHCdataRow")
> public String getHCdataRow(
> @WebParam(name = "tcHcNum") int tcHcNum,
> @WebParam(name = "tnYear") int tnYear);
> }
>
> With RPC/Lit like that, it should namespace qualify the child Body with the
> targetNamespace of the service. The children of that element would not
> be
> qualified. Thus, it should look similar to your first message below.
> Again, the main issue will be the encodingStyle, which we would never
> output.
> Not sure if that's an issue for you or not. If it is, you may need to
> resort to Dispatch style clients and do the XML payload stuff yourself.
>
> Dan
>
>
> On Tue October 27 2009 11:50:25 am Jaime Hablutzel Egoavil wrote:
> > I think I will need definetely to create annotated jax-ws client from
> > scratch, but I want use as a base the code generated by wsdl2java for
> > another web service, but, I'm getting into issues when jax-ws tries to
> > validate (does it? ) against the wsdl, is there anyway to make a jax-ws
> > client to forget about the need of the wsdl, for changing just the port
> and
> > the message namespace, I just want to be able to send this:
> >
> > <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="
> > http://schemas.xmlsoap.org/soap/envelope/" xmlns:mes="
> > http://hndac.gob.pe/soasighhc/message/">
> > <soapenv:Header/>
> > <soapenv:Body>
> > <mes:getHCdataRow soapenv:encodingStyle="
> > http://schemas.xmlsoap.org/soap/encoding/">
> > <tcHcNum>3</tcHcNum>
> > <tnYear>5</tnYear>
> > </mes:getHCdataRow>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> > instead of:
> >
> > <soapenv:Envelope xmlns:soapenv="
> http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:cxf="http://cxf.examples.servicemix.apache.org/">
> > <soapenv:Header/>
> > <soapenv:Body>
> > <cxf:getHCdataRow>
> > <!--Optional:-->
> > <tcHcNum>1</tcHcNum>
> > <tnYear>3</tnYear>
> > </cxf:getHCdataRow>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> >
> >
> > On Mon, Oct 26, 2009 at 3:59 PM, Jaime Hablutzel Egoavil <
> >
> > hablutzel1@gmail.com> wrote:
> > > Ok, I'll try it, then I'll post it, thank you.
> > >
> > > On Mon, Oct 26, 2009 at 3:38 PM, Daniel Kulp <dk...@apache.org> wrote:
> > >> On Mon October 26 2009 4:00:38 pm Jaime Hablutzel Egoavil wrote:
> > >> > yes, I hardcoded the style="document". Do you think that coding the
> > >> > stub classes instead of using wsdl2java could solve my problem?
> > >>
> > >> Possibly. Not really sure. As I said, we don't support
> soap-encoded
> > >> so if
> > >> the service is actually expecting any of the soap-encoded stuff,
> you're
> > >> going
> > >> to run into issues.
> > >>
> > >> In general, though, yes. If you start with the SEI interface and
> make
> > >> sure
> > >> you pass "null" for the wsdl location to the service thing and slowly
> > >> tweak
> > >> all the annotations, particularly targetNamespace attributes, you may
> be
> > >> able
> > >> to get it to work.
> > >>
> > >> Dan
> > >>
> > >> > On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org>
> wrote:
> > >> > > Just took a quick look at your wsdl. The wsdl is using
> > >>
> > >> soap-encoding
> > >>
> > >> > > which
> > >> > > is not supported by CXF. That alone would keep it from working:
> > >> > >
> > >> > > <soap:body use="encoded"
> > >> > > namespace="http://hndac.gob.pe/soasighhc/message/ "
> > >> > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> > >>
> > >> parts="tcHcNum
> > >>
> > >> > > tnYear"/>
> > >> > >
> > >> > >
> > >> > > However, you also have it set to style="document". Thus, even
> > >>
> > >> removing
> > >>
> > >> > > the
> > >> > > encoding stuff leaves it with doc/literal, which would normally be
> > >> > > OK, except
> > >> > > WSI-BasicProfile only allows a single part for doc/literal.
> > >> > >
> > >> > > Anyway, to me, it looks like your entire problem is centered
> around
> > >> > > an unsupportable wsdl.
> > >> > >
> > >> > > Dan
> > >> > >
> > >> > > On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> > >> > > > Hi, I'm testing servicemix 4 for a week until now and I can't
> get
> > >> > > > working
> > >> > >
> > >> > > a
> > >> > >
> > >> > > > cxf web service inside servicemix, that queries another external
> > >> > > > web service inside its implementation and connects to ldap using
> > >> > > > DirContext (its fails because of an intercepting stuff inside
> > >> > > > servicemix). Can someone give me an example of I cxf web service
> > >>
> > >> inside
> > >>
> > >> > > > servicemix,
> > >> > >
> > >> > > with
> > >> > >
> > >> > > > a ws client inside of it? And, an example of an application
> > >>
> > >> connecting
> > >>
> > >> > > > to ldap from inside of one cxf web service?
> > >> > > >
> > >> > > > Thank you very much.
> > >> > >
> > >> > > --
> > >> > > Daniel Kulp
> > >> > > dkulp@apache.org
> > >> > > http://www.dankulp.com/blog
> > >>
> > >> --
> > >> Daniel Kulp
> > >> dkulp@apache.org
> > >> http://www.dankulp.com/blog
> > >
> > > --
> > > Jaime Hablutzel
> > >
> > > (tildes omitidas intencionalmente) 9 8964 0369
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Daniel Kulp <dk...@apache.org>.
Other than the soapenv:encodingStyle attribute which I don't think you'll ever
get output other than writing an interceptor to add it, you could probably do
something like:
@WebService(targetNamespace="http://hndac.gob.pe/soasighhc/message/"
....)
@SOAPBinding(style = SOAPBinding.Style.RPC)
public interface MyService {
@WebResult(name = "result)
@WebMethod(operationName = "getHCdataRow")
public String getHCdataRow(
@WebParam(name = "tcHcNum") int tcHcNum,
@WebParam(name = "tnYear") int tnYear);
}
With RPC/Lit like that, it should namespace qualify the child Body with the
targetNamespace of the service. The children of that element would not be
qualified. Thus, it should look similar to your first message below.
Again, the main issue will be the encodingStyle, which we would never output.
Not sure if that's an issue for you or not. If it is, you may need to
resort to Dispatch style clients and do the XML payload stuff yourself.
Dan
On Tue October 27 2009 11:50:25 am Jaime Hablutzel Egoavil wrote:
> I think I will need definetely to create annotated jax-ws client from
> scratch, but I want use as a base the code generated by wsdl2java for
> another web service, but, I'm getting into issues when jax-ws tries to
> validate (does it? ) against the wsdl, is there anyway to make a jax-ws
> client to forget about the need of the wsdl, for changing just the port and
> the message namespace, I just want to be able to send this:
>
> <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="
> http://schemas.xmlsoap.org/soap/envelope/" xmlns:mes="
> http://hndac.gob.pe/soasighhc/message/">
> <soapenv:Header/>
> <soapenv:Body>
> <mes:getHCdataRow soapenv:encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/">
> <tcHcNum>3</tcHcNum>
> <tnYear>5</tnYear>
> </mes:getHCdataRow>
> </soapenv:Body>
> </soapenv:Envelope>
>
> instead of:
>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:cxf="http://cxf.examples.servicemix.apache.org/">
> <soapenv:Header/>
> <soapenv:Body>
> <cxf:getHCdataRow>
> <!--Optional:-->
> <tcHcNum>1</tcHcNum>
> <tnYear>3</tnYear>
> </cxf:getHCdataRow>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
>
> On Mon, Oct 26, 2009 at 3:59 PM, Jaime Hablutzel Egoavil <
>
> hablutzel1@gmail.com> wrote:
> > Ok, I'll try it, then I'll post it, thank you.
> >
> > On Mon, Oct 26, 2009 at 3:38 PM, Daniel Kulp <dk...@apache.org> wrote:
> >> On Mon October 26 2009 4:00:38 pm Jaime Hablutzel Egoavil wrote:
> >> > yes, I hardcoded the style="document". Do you think that coding the
> >> > stub classes instead of using wsdl2java could solve my problem?
> >>
> >> Possibly. Not really sure. As I said, we don't support soap-encoded
> >> so if
> >> the service is actually expecting any of the soap-encoded stuff, you're
> >> going
> >> to run into issues.
> >>
> >> In general, though, yes. If you start with the SEI interface and make
> >> sure
> >> you pass "null" for the wsdl location to the service thing and slowly
> >> tweak
> >> all the annotations, particularly targetNamespace attributes, you may be
> >> able
> >> to get it to work.
> >>
> >> Dan
> >>
> >> > On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org> wrote:
> >> > > Just took a quick look at your wsdl. The wsdl is using
> >>
> >> soap-encoding
> >>
> >> > > which
> >> > > is not supported by CXF. That alone would keep it from working:
> >> > >
> >> > > <soap:body use="encoded"
> >> > > namespace="http://hndac.gob.pe/soasighhc/message/ "
> >> > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> >>
> >> parts="tcHcNum
> >>
> >> > > tnYear"/>
> >> > >
> >> > >
> >> > > However, you also have it set to style="document". Thus, even
> >>
> >> removing
> >>
> >> > > the
> >> > > encoding stuff leaves it with doc/literal, which would normally be
> >> > > OK, except
> >> > > WSI-BasicProfile only allows a single part for doc/literal.
> >> > >
> >> > > Anyway, to me, it looks like your entire problem is centered around
> >> > > an unsupportable wsdl.
> >> > >
> >> > > Dan
> >> > >
> >> > > On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> >> > > > Hi, I'm testing servicemix 4 for a week until now and I can't get
> >> > > > working
> >> > >
> >> > > a
> >> > >
> >> > > > cxf web service inside servicemix, that queries another external
> >> > > > web service inside its implementation and connects to ldap using
> >> > > > DirContext (its fails because of an intercepting stuff inside
> >> > > > servicemix). Can someone give me an example of I cxf web service
> >>
> >> inside
> >>
> >> > > > servicemix,
> >> > >
> >> > > with
> >> > >
> >> > > > a ws client inside of it? And, an example of an application
> >>
> >> connecting
> >>
> >> > > > to ldap from inside of one cxf web service?
> >> > > >
> >> > > > Thank you very much.
> >> > >
> >> > > --
> >> > > Daniel Kulp
> >> > > dkulp@apache.org
> >> > > http://www.dankulp.com/blog
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://www.dankulp.com/blog
> >
> > --
> > Jaime Hablutzel
> >
> > (tildes omitidas intencionalmente) 9 8964 0369
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: cxf client inside servicemix
Posted by Jaime Hablutzel Egoavil <ha...@gmail.com>.
I think I will need definetely to create annotated jax-ws client from
scratch, but I want use as a base the code generated by wsdl2java for
another web service, but, I'm getting into issues when jax-ws tries to
validate (does it? ) against the wsdl, is there anyway to make a jax-ws
client to forget about the need of the wsdl, for changing just the port and
the message namespace, I just want to be able to send this:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:mes="
http://hndac.gob.pe/soasighhc/message/">
<soapenv:Header/>
<soapenv:Body>
<mes:getHCdataRow soapenv:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/">
<tcHcNum>3</tcHcNum>
<tnYear>5</tnYear>
</mes:getHCdataRow>
</soapenv:Body>
</soapenv:Envelope>
instead of:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:cxf="http://cxf.examples.servicemix.apache.org/">
<soapenv:Header/>
<soapenv:Body>
<cxf:getHCdataRow>
<!--Optional:-->
<tcHcNum>1</tcHcNum>
<tnYear>3</tnYear>
</cxf:getHCdataRow>
</soapenv:Body>
</soapenv:Envelope>
On Mon, Oct 26, 2009 at 3:59 PM, Jaime Hablutzel Egoavil <
hablutzel1@gmail.com> wrote:
> Ok, I'll try it, then I'll post it, thank you.
>
>
> On Mon, Oct 26, 2009 at 3:38 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>> On Mon October 26 2009 4:00:38 pm Jaime Hablutzel Egoavil wrote:
>> > yes, I hardcoded the style="document". Do you think that coding the stub
>> > classes instead of using wsdl2java could solve my problem?
>>
>> Possibly. Not really sure. As I said, we don't support soap-encoded so
>> if
>> the service is actually expecting any of the soap-encoded stuff, you're
>> going
>> to run into issues.
>>
>> In general, though, yes. If you start with the SEI interface and make
>> sure
>> you pass "null" for the wsdl location to the service thing and slowly
>> tweak
>> all the annotations, particularly targetNamespace attributes, you may be
>> able
>> to get it to work.
>>
>> Dan
>>
>>
>> >
>> > On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org> wrote:
>> > > Just took a quick look at your wsdl. The wsdl is using
>> soap-encoding
>> > > which
>> > > is not supported by CXF. That alone would keep it from working:
>> > >
>> > > <soap:body use="encoded"
>> > > namespace="http://hndac.gob.pe/soasighhc/message/ "
>> > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>> parts="tcHcNum
>> > > tnYear"/>
>> > >
>> > >
>> > > However, you also have it set to style="document". Thus, even
>> removing
>> > > the
>> > > encoding stuff leaves it with doc/literal, which would normally be OK,
>> > > except
>> > > WSI-BasicProfile only allows a single part for doc/literal.
>> > >
>> > > Anyway, to me, it looks like your entire problem is centered around an
>> > > unsupportable wsdl.
>> > >
>> > > Dan
>> > >
>> > > On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
>> > > > Hi, I'm testing servicemix 4 for a week until now and I can't get
>> > > > working
>> > >
>> > > a
>> > >
>> > > > cxf web service inside servicemix, that queries another external web
>> > > > service inside its implementation and connects to ldap using
>> > > > DirContext (its fails because of an intercepting stuff inside
>> > > > servicemix). Can someone give me an example of I cxf web service
>> inside
>> > > > servicemix,
>> > >
>> > > with
>> > >
>> > > > a ws client inside of it? And, an example of an application
>> connecting
>> > > > to ldap from inside of one cxf web service?
>> > > >
>> > > > Thank you very much.
>> > >
>> > > --
>> > > Daniel Kulp
>> > > dkulp@apache.org
>> > > http://www.dankulp.com/blog
>> >
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://www.dankulp.com/blog
>>
>
>
>
> --
> Jaime Hablutzel
>
> (tildes omitidas intencionalmente) 9 8964 0369
>
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Jaime Hablutzel Egoavil <ha...@gmail.com>.
Ok, I'll try it, then I'll post it, thank you.
On Mon, Oct 26, 2009 at 3:38 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Mon October 26 2009 4:00:38 pm Jaime Hablutzel Egoavil wrote:
> > yes, I hardcoded the style="document". Do you think that coding the stub
> > classes instead of using wsdl2java could solve my problem?
>
> Possibly. Not really sure. As I said, we don't support soap-encoded so
> if
> the service is actually expecting any of the soap-encoded stuff, you're
> going
> to run into issues.
>
> In general, though, yes. If you start with the SEI interface and make
> sure
> you pass "null" for the wsdl location to the service thing and slowly tweak
> all the annotations, particularly targetNamespace attributes, you may be
> able
> to get it to work.
>
> Dan
>
>
> >
> > On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org> wrote:
> > > Just took a quick look at your wsdl. The wsdl is using soap-encoding
> > > which
> > > is not supported by CXF. That alone would keep it from working:
> > >
> > > <soap:body use="encoded"
> > > namespace="http://hndac.gob.pe/soasighhc/message/ "
> > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> parts="tcHcNum
> > > tnYear"/>
> > >
> > >
> > > However, you also have it set to style="document". Thus, even
> removing
> > > the
> > > encoding stuff leaves it with doc/literal, which would normally be OK,
> > > except
> > > WSI-BasicProfile only allows a single part for doc/literal.
> > >
> > > Anyway, to me, it looks like your entire problem is centered around an
> > > unsupportable wsdl.
> > >
> > > Dan
> > >
> > > On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> > > > Hi, I'm testing servicemix 4 for a week until now and I can't get
> > > > working
> > >
> > > a
> > >
> > > > cxf web service inside servicemix, that queries another external web
> > > > service inside its implementation and connects to ldap using
> > > > DirContext (its fails because of an intercepting stuff inside
> > > > servicemix). Can someone give me an example of I cxf web service
> inside
> > > > servicemix,
> > >
> > > with
> > >
> > > > a ws client inside of it? And, an example of an application
> connecting
> > > > to ldap from inside of one cxf web service?
> > > >
> > > > Thank you very much.
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@apache.org
> > > http://www.dankulp.com/blog
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Daniel Kulp <dk...@apache.org>.
On Mon October 26 2009 4:00:38 pm Jaime Hablutzel Egoavil wrote:
> yes, I hardcoded the style="document". Do you think that coding the stub
> classes instead of using wsdl2java could solve my problem?
Possibly. Not really sure. As I said, we don't support soap-encoded so if
the service is actually expecting any of the soap-encoded stuff, you're going
to run into issues.
In general, though, yes. If you start with the SEI interface and make sure
you pass "null" for the wsdl location to the service thing and slowly tweak
all the annotations, particularly targetNamespace attributes, you may be able
to get it to work.
Dan
>
> On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org> wrote:
> > Just took a quick look at your wsdl. The wsdl is using soap-encoding
> > which
> > is not supported by CXF. That alone would keep it from working:
> >
> > <soap:body use="encoded"
> > namespace="http://hndac.gob.pe/soasighhc/message/ "
> > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="tcHcNum
> > tnYear"/>
> >
> >
> > However, you also have it set to style="document". Thus, even removing
> > the
> > encoding stuff leaves it with doc/literal, which would normally be OK,
> > except
> > WSI-BasicProfile only allows a single part for doc/literal.
> >
> > Anyway, to me, it looks like your entire problem is centered around an
> > unsupportable wsdl.
> >
> > Dan
> >
> > On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> > > Hi, I'm testing servicemix 4 for a week until now and I can't get
> > > working
> >
> > a
> >
> > > cxf web service inside servicemix, that queries another external web
> > > service inside its implementation and connects to ldap using
> > > DirContext (its fails because of an intercepting stuff inside
> > > servicemix). Can someone give me an example of I cxf web service inside
> > > servicemix,
> >
> > with
> >
> > > a ws client inside of it? And, an example of an application connecting
> > > to ldap from inside of one cxf web service?
> > >
> > > Thank you very much.
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: cxf client inside servicemix
Posted by Jaime Hablutzel Egoavil <ha...@gmail.com>.
yes, I hardcoded the style="document". Do you think that coding the stub
classes instead of using wsdl2java could solve my problem?
On Mon, Oct 26, 2009 at 2:53 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> Just took a quick look at your wsdl. The wsdl is using soap-encoding
> which
> is not supported by CXF. That alone would keep it from working:
>
> <soap:body use="encoded" namespace="http://hndac.gob.pe/soasighhc/message/
> "
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="tcHcNum
> tnYear"/>
>
>
> However, you also have it set to style="document". Thus, even removing
> the
> encoding stuff leaves it with doc/literal, which would normally be OK,
> except
> WSI-BasicProfile only allows a single part for doc/literal.
>
> Anyway, to me, it looks like your entire problem is centered around an
> unsupportable wsdl.
>
> Dan
>
>
> On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> > Hi, I'm testing servicemix 4 for a week until now and I can't get working
> a
> > cxf web service inside servicemix, that queries another external web
> > service inside its implementation and connects to ldap using DirContext
> > (its fails because of an intercepting stuff inside servicemix).
> > Can someone give me an example of I cxf web service inside servicemix,
> with
> > a ws client inside of it? And, an example of an application connecting to
> > ldap from inside of one cxf web service?
> >
> > Thank you very much.
> >
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
--
Jaime Hablutzel
(tildes omitidas intencionalmente) 9 8964 0369
Re: cxf client inside servicemix
Posted by Daniel Kulp <dk...@apache.org>.
Just took a quick look at your wsdl. The wsdl is using soap-encoding which
is not supported by CXF. That alone would keep it from working:
<soap:body use="encoded" namespace="http://hndac.gob.pe/soasighhc/message/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="tcHcNum
tnYear"/>
However, you also have it set to style="document". Thus, even removing the
encoding stuff leaves it with doc/literal, which would normally be OK, except
WSI-BasicProfile only allows a single part for doc/literal.
Anyway, to me, it looks like your entire problem is centered around an
unsupportable wsdl.
Dan
On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> Hi, I'm testing servicemix 4 for a week until now and I can't get working a
> cxf web service inside servicemix, that queries another external web
> service inside its implementation and connects to ldap using DirContext
> (its fails because of an intercepting stuff inside servicemix).
> Can someone give me an example of I cxf web service inside servicemix, with
> a ws client inside of it? And, an example of an application connecting to
> ldap from inside of one cxf web service?
>
> Thank you very much.
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: cxf client inside servicemix
Posted by Daniel Kulp <dk...@apache.org>.
Just took a quick look at your wsdl. The wsdl is using soap-encoding which
is not supported by CXF. That alone would keep it from working:
<soap:body use="encoded" namespace="http://hndac.gob.pe/soasighhc/message/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="tcHcNum
tnYear"/>
However, you also have it set to style="document". Thus, even removing the
encoding stuff leaves it with doc/literal, which would normally be OK, except
WSI-BasicProfile only allows a single part for doc/literal.
Anyway, to me, it looks like your entire problem is centered around an
unsupportable wsdl.
Dan
On Mon October 26 2009 3:07:55 pm Jaime Hablutzel Egoavil wrote:
> Hi, I'm testing servicemix 4 for a week until now and I can't get working a
> cxf web service inside servicemix, that queries another external web
> service inside its implementation and connects to ldap using DirContext
> (its fails because of an intercepting stuff inside servicemix).
> Can someone give me an example of I cxf web service inside servicemix, with
> a ws client inside of it? And, an example of an application connecting to
> ldap from inside of one cxf web service?
>
> Thank you very much.
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: cxf client inside servicemix
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Why don't using CXF-BC in provider mode ?
CXF-BC in provider mode acts as a WebService client.
You can use the provider from a servicemix-bean to interact with your LDAP.
FYI, a servicemix-ldap component already exists. I'm still working on it
but it's already usable.
Regards
JB
Jaime Hablutzel Egoavil wrote:
> Hi, I'm testing servicemix 4 for a week until now and I can't get working a
> cxf web service inside servicemix, that queries another external web service
> inside its implementation and connects to ldap using DirContext (its fails
> because of an intercepting stuff inside servicemix).
> Can someone give me an example of I cxf web service inside servicemix, with
> a ws client inside of it? And, an example of an application connecting to
> ldap from inside of one cxf web service?
>
> Thank you very much.
>
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086