Hi,

the http:endpoint is the "old" HTTP component endpoint. It's quite deprecated now and replaced by the "new" HTTP endpoints :

http:provider
http:consumer
http:soap-consumer
...

Regards
JB

skkm786 wrote:
The xbean.xml file of http SU contains.

<http:endpoint service="test:MyConsumerService"
               endpoint="myConsumer"
               role="consumer" targetService="ftp0"
               locationURI="http://localhost:8192/bridge/";
               defaultMep="http://www.w3.org/2004/08/wsdl/in-only"; />


The same can be achieved through the following


  <http:consumer service="test:MyConsumerService"
                 endpoint="myConsumer"
                 targetService="ftp0"
                 locationURI="http://localhost:8192/bridge/";

                 defaultMep="http://www.w3.org/2004/08/wsdl/in-only"; />



What is the difference between the above two approaches ?


When I used http:consumer, the example worked well as expected.

But when I used http:endpoint, tested using JMeter I'm getting the below
exception.



DEBUG - HttpComponent                  - Received exchange: status: Error,
role: consumer
DEBUG - HttpComponent                  - Retrieved correlation id:
ID:10.11.21.10-1273c8c6319-10:5
DEBUG - ConsumerProcessor              - Resuming continuation for exchange:
ID:10.11.21.10-1273c8c6319-10:5
DEBUG - JettyContextManager            - Dispatching job:
retrycontinuat...@13317442,pending,resumed
DEBUG - jetty                          - resume continuation
retrycontinuat...@13317442,pending,resumed
DEBUG - jetty                          - REQUEST /bridge/ on
org.mortbay.jetty.httpconnect...@16396f5
DEBUG - jetty                          - servlet=jbiServlet
DEBUG - jetty                          - chain=null
DEBUG - jetty                          - servlet holder=jbiServlet
DEBUG - ConsumerProcessor              - Receiving HTTP request: POST
/bridge/ HTTP/1.1
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 69
User-Agent: Java/1.6.0_17
Host: localhost:8192
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2


WARN  - jetty                          - /bridge/
java.io.IOException: No output stream available for output name: null. Maybe
the file already exists?
        at
org.apache.servicemix.ftp.FtpSenderEndpoint.processInOnly(FtpSenderEndpoint.java:255)
        at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:102)
        at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
        at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
        at
org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
        at
org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
        at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:623)
        at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
DEBUG - jetty                          - POST /bridge/ HTTP/1.1
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 69
User-Agent: Java/1.6.0_17
Host: localhost:8192

Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2


----------------------------------------------------------------------------------------------------

Reply via email to