OK, I got farther, but now the EIPComponent doesn't forward the request to
our JBI Component.
Why is the EIPComponent not finding the service description. Is it because
our JBI Component doesn't implement the getServiceDescription method (or it
returns null). And ServiceMix doesn't require it and
OpenESB does? This same ServiceAssembly works perfectly in ServiceMix 3.0.
BTW RonTenHove got back to me and I plan on submitting a bug.
Here is the output:
org.apache.servicemix.http.processors.ConsumerProcessor|ClassName=org.apache.servicemix.http.processors.ConsumerProcessor;MethodName=process;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Receiving
HTTP request: POST /Encoding/HttpProxySaService/ HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: file://C:\dev\current\nettoolkit\pingpong.ws\sample-IE-client.html
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
Host: b-0648:8192
Content-Length: 156
Connection: keep-alive
Cache-Control: no-cache
org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Querying
service description for Endpoint Type: InternalEndpoint
Owner: servicemix-eip Active: True
Service:
{http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router
Endpoint: pingpong-encoding-router
|#]
org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|No
description found for
{http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router:pingpong-encoding-router|#]
--
View this message in context:
http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8300043
Sent from the ServiceMix - User mailing list archive at Nabble.com.
