cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: HTTPClientPolicy [updating demos with refactored config]
Date Fri, 23 Feb 2007 15:10:14 GMT
Not yet. Its very high on my list... I just updated the JMS documentation
two days ago.  I'm hoping to get to the samples today.

- Dan

On 2/22/07, Glynn, Eoghan <eoghan.glynn@iona.com> wrote:
>
>
>
>
>
> > -----Original Message-----
> > From: Dan Diephouse [mailto:dan@envoisolutions.com]
> > Sent: 12 February 2007 14:43
> > To: cxf-dev@incubator.apache.org
> > Subject: Re: HTTPClientPolicy
> >
> > Hi Eoghan,
> >
> > I think the HTTP samples got updated, but I'm not sure about
> > the JMS ones.
> > I'll try and spend some time on it today. Thanks,
> > - Dan
>
>
> Hi Dan,
>
> Did you ever get a chance to go through the demos and update these to
> the simplified config?
>
> Just happened to notice that the hello_world_https sample doesn't seem
> to have been done, so there may be others still out of date.
>
> Cheers,
> Eoghan
>
>
>
> > On 2/12/07, Glynn, Eoghan <eoghan.glynn@iona.com> wrote:
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Dan Diephouse [mailto:dan@envoisolutions.com]
> > > > Sent: 11 February 2007 20:45
> > > > To: cxf-dev@incubator.apache.org
> > > > Subject: Re: HTTPClientPolicy
> > > >
> > > > Sorry for the confusion, the samples may be out of date.
> > >
> > > Dan,
> > >
> > > Probably a good idea that we get these samples updated to
> > match your
> > > config changes as a matter of urgency. Can you raise a JIRA
> > describing
> > > what needs to be done?
> > >
> > > Also, were the system tests updated, do you know?
> > >
> > > /Eoghan
> > >
> > > > 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-con
> > > >
> > duit<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 <phumenn@iona.com> 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 <phumenn@iona.com> 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
> >
>



-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message