Yeah, that's true. Though using the new endpoints (http:provider, http:consumer), it should be much easier to do that. You can easily plug marshalers that will transform the request to a jbi exchange and from the exchange to a provider on the other side. These feature has not been implemented yet, but if you want are interested, we can guide you on writing this patch and submitting it back to the community.
On 10/5/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: > L.S., > > I think this feature is mainly about posting XML message to external > services and sending SOAP/HTTP requests. As far as I know, you cannot > use it to access an entire web application... > > Gert > > imorales wrote: > > But in the servicemix website, > > http://incubator.apache.org/servicemix/servicemix-http.html > > One of the main features of the http component is: > > - HTTP Client using Jakarta Commons HTTP Client. > > > > I dont know if I´m mistaken, but this feature allows to do this ?¿ > > > > > > Gert Vanthienen wrote: > > > >> L.S., > >> > >> > >> You can use it to act as a proxy for external web services or for > >> posting XML messages to an external machine, but I don't think you can > >> use ServiceMix to act this way for entire web application. > >> > >> > >> Gert > >> > >> imorales wrote: > >> > >>> Yes I have another post where I explain my scenario. The title of the > >>> post > >>> is: > >>> > >>> > >>> "component http, wsdl for no soap endpoints is needed ?¿ by imorales" > >>> --> > >>> Oct 03 imorales > >>> > >>> I want to publish a web application in servicemix, in that post I show > >>> all > >>> the configuration, but doesn´'t work. > >>> > >>> So many thanks for tour answer, I will take a look to the bridge example. > >>> > >>> > >>> Gert Vanthienen wrote: > >>> > >>>> L.S., > >>>> > >>>> > >>>> It tries to access the main.wsdl by default, but because you're not > >>>> using SOAP, you cannot get a WSDL. You can still POST an XML message to > >>>> the URL though, this should work fine. Have a look at the bridge > >>>> example in the distribution, which also uses a simple POST for sending > >>>> XML. > >>>> > >>>> I don't think GET requests are currently support by servicemix-http > >>>> though. What is your use case for it? From another post, I had the > >>>> impressions you were trying to useServiceMix to act as some kind of > >>>> 'reverse proxy' to another web application... > >>>> > >>>> > >>>> Gert > >>>> > >>>> imorales wrote: > >>>> > >>>>> I forget it ... I get this error when accesing the consumer url > >>>>> "http://platinoa:8192/xforms"; > >>>>> > >>>>> HTTP ERROR: 404 > >>>>> > >>>>> Unable to find requested resource > >>>>> > >>>>> RequestURI=/xforms/main.wsdl > >>>>> > >>>>> Powered by Jetty:// > >>>>> > >>>>> ...... > >>>>> > >>>>> I don´t know why is trying to acces main.wsdl, because both endpoinst > >>>>> has > >>>>> the attribute soap="false". > >>>>> > >>>>> > >>>>> > >>>>> imorales wrote: > >>>>> > >>>>>> Hi all. > >>>>>> I would like to know if servicemix-http supports GET, POST operations. > >>>>>> If it supports, how have to configure de endpoints (consumer, > >>>>>> provider) > >>>>>> . > >>>>>> > >>>>>> My xbean.xml: > >>>>>> > >>>>>> <beans xmlns:http="http://servicemix.apache.org/http/1.0"; > >>>>>> xmlns:cmp="http://mycompany.com/";> > >>>>>> > >>>>>> <http:endpoint service="cmp:xformspublicador" > >>>>>> endpoint="miChibaWebCliente" > >>>>>> soap="false" > >>>>>> locationURI="http://platinoa:8192/xforms"; > >>>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > >>>>>> role="consumer"/> > >>>>>> > >>>>>> <http:endpoint service="cmp:xormspublicador" > >>>>>> endpoint="miChivaWebServidor" > >>>>>> role="provider" > >>>>>> soap="false" > >>>>>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > >>>>>> > >>>>>> locationURI="http://192.168.1.9:9393/xformspublicador"/> > >>>>>> </beans> > >>>>>> > >>>>>> > >>>>>> > >>>>>> Thanks in advance. > >>>>>> > >>>>>> > >>>> > >> > > > > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
