RE: RE: RE: RE: Re: Dynamic endpoint for BC-SOAP

No,

When you mentionned you want to dynamically call an « endpoint », I think you would say « web service url », that confused the discussion

You want to define a Provide service unit for the BCSOAP, with a jbi endpoint, but do not defined any webservice to call ( or define a ‘null’ web service)

Then the consumer set on the exchange (in a property) the web service it wants to call; and the bcsoap use this property to call a webService

If this is your problem, the consumer can set on the exchange property this url with the wsaddressing TO property

If I understand you, you recommend me to join an external service using a SE component.

If yes, I don’t think it’s the philosophy of the JBI spec.

For me, it’s not the role of a SE consumer to invoke an external endpoint, it’s instead the role of a BC consumer.

Am I right ?

Richard.

Why don’t you connect your consumer BC soap to a special ServiceEngine ?

This service engine takes the request, find the good endpoint, and forward the request to the endpoint ?

Yes that’s my requirement.

At the deployment-time, my BC-SOAP doesn’t know which endpoint will be called.

The endpoint is know only at runtime using a specific SE which searches a service in a service registry and discover its endpoint.

When roughly this feature will be implemted ?

Thanks.

Richard.