Before:
<bean name="{
http://cxf.apache.org/greeter_control}GreeterPort.http-conduit";
abstract="true">
<property name="client">
<value>
<http-conf:client DecoupledEndpoint="
http://localhost:9995/decoupled_endpoint"/>
</value>
</property>
<property name="sslClient">
<value>
<http-conf:sslClient .../>
</value>
</property>
<property name="authorization">
<value>
<http-conf:authorization .../>
</value>
</property>
<property name="proxyAuthorization">
<value>
<http-conf:proxyAuthorization .../>
</value>
</property>
</bean>
After:
<conduit id="{http://apache.org/hello_world_soap_http}Greeter1.http-conduit
<http://apache.org/hello_world_soap_http%7DGreeter1.http-conduit>">
<client.../>
<ssClient../>
<authorization.../>
<proxyAuthorization.../>
</conduit>
So yes, I reckon the later is a LOT simpler. :-)
- Dan
On 2/12/07, Sergey Beryozkin <[EMAIL PROTECTED]> wrote:
Hi Dan
> Sorry for the confusion, the samples may be out of date. I started
changing
> the way configuration works last week to simplify it a lot. People
shouldn't
> have to do all the <bean.../> stuff now.
Do you reckon <conduit> is a simpler term than <bean> ?
Cheers, Sergey
> Hi Polar,
>
> Sorry for the confusion, the samples may be out of date. I started
changing
> the way configuration works last week to simplify it a lot. People
shouldn't
> have to do all the <bean.../> stuff now.
>
> The rough format for http config is now:
>
> <conduit
> id="{http://apache.org/hello_world_soap_http}Greeter1.http-conduit<
http://apache.org/hello_world_soap_http%7DGreeter1.http-conduit>
> ">
> <client.../>
> <ssClient../>
> <authorization.../>
> <proxyAuthorization.../>
> </conduit>
>
> It is all in one namespace now too:
> http://cxf.apache.org/transports/http/configuration
>
> - Dan
>
> On 2/11/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
>>
>> Dan,
>>
>> Thanks for the prompt response.
>>
>> Dan Diephouse wrote:
>> > You can see the schema in the http transport module for more detail,
but
>> > here is a sample:
>> >
>> > <conduit id="{your:service:namespace}EndpointName.http-conduit"
xmlns="
>> > http://cxf.apache.org/transports/http/configuration";>
>> > <client AllowChunking="false"/>
>> > </conduit> \
>>
>> Well, that's quite not what I was expecting! Does the above just go in
>> the top level client.xml file? How does that interact with something
>> like below, which works with the sample directories? What happens if
you
>> have both? What takes precedence, if there is precedence?
>>
>> <bean
>> name="{http://apache.org/hello_world_soap_http}Greeter1.http-conduit";
>> abstract="true">
>> <property name="authorization">
>> <value>
>> <sec:authorization>
>> <sec:UserName>Polar</sec:UserName>
>> <sec:Password>querty</sec:Password>
>> </sec:authorization>
>> </value>
>> </property>
>> </bean>
>>
>> Cheers,
>> -Polar
>> > - Dan
>> >
>> > On 2/10/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Greetings, what is the way to write XML in a client.xml file that
>> allows
>> >> me to configure the HTTPClientPolicy for a particular endpoint? I
am
>> >> having trouble tracking this down. I want to shut off streaming() or
>> >> chunking which seams to be the default.
>> >> I have to set some <AllowChunking>false</AllowChunking> item
somewhere,
>> >> but where?
>> >>
>> >> Thanks,
>> >> -Polar
>> >>
>> >
>> >
>> >
>>
>>
>
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
