The servicemix-http component will activate an external endpoint (when a
consumer)
using the service/endpoint attributes. So it will not conflict in any case
(because external
endpoints and internal endpoints do not conflict).
You can look at the log for endpoint activation and you should be able to
find which component
has activated the endpoint (or maybe using a jmx console and browsing at the
beans)
On 8/7/06, azwan <[EMAIL PROTECTED]> wrote:
Actually I had another http endpoint and use wsdl file ProcessB.wsdl
. From
the error previously, it show that the ProcessB already registered. Is it
because of this http endpoint that use same wsdl file?
<http:endpoint service="demo:processBSoap"
endpoint="processBSoap"
role="consumer"
soap="true"
locationURI="http://localhost:8192/ProcessBService/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
targetService="demo:receiver"
wsdlResource="classpath:ProcessB.wsdl"/>
--
View this message in context:
http://www.nabble.com/2-bpel-component-in-1-servicemix-instance-tf2061589.html#a5680927
Sent from the ServiceMix - User forum at Nabble.com.
--
Cheers,
Guillaume Nodet
