Erik,
If the external webservice doesn't change too often, I would recommend
you to define as many <http:endpoint/>s as the number of external
services.
There is a way to override the location URI specified on an HTTP
provider endpoint, by adding a property
(JbiConstants.HTTP_DESTINATION_URI) to the normalized message you're
sending into the endpoint, so you might try to do that if the external
webservice changes very often.
Finally, I think it is also possible to use a URI to resolve the HTTP
endpoint you want to use
(http://incubator.apache.org/servicemix/uris.html for more) but I'm not
entirely sure about that. Perhaps someone else can confirm if this is
an option or not?
Gert
Erik Allais wrote:
Ok, but i must redeploy a new JBI if i have a new external WS to call and
undeploy the old
I cant have something like a config file to parse to see the endpoint ?
Ok i dream :)
bsnyder wrote:
On 7/4/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
Bruce,
Wouldn't it be possible to define multiple HTTP provider endpoints, one
for every location where the service is located and just send a SOAP XML
message to the correct endpoint (e.g. using a content-based router to
determine the endpoint)?
Yeah definitely. What I failed to mention is that you can define as
many <http:endpoint> elements as you like and as Gert suggests, choose
the correct endpoint.
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
