Hi Doug, On 5/23/06, Doug Fischer <[EMAIL PROTECTED]> wrote:
Question 1: Would it be possible to to dynamically configure things like the locationURI, service, endpoint, targetService, targetEndpoint, etc... Through JMX on an HTTP endpoint? (I don¹t think this can be done right now, I am just wondering if this is something that could potentially be done) I guess this data would then need to be persisted somewhere so that if the system is restarted, the same values are still set.
For provider endpoints, you can already create endpoints on the fly (short lived) using EPR resolution and URI. See http://servicemix.goopen.org/site/uris.html For binding components, I was thinking about creating a management JBI endpoint which would process requests on proxy endpoints (mainly consumers). This would enable SEs to ask for proxy endpoint creation when a SU is deployed. For example you would be able to specify when deploying a POJO on servicemix-jsr181, or a BPEL process, to ask bindings components to create proxy endpoints for these. This could also work for provider endpoints. We could also implement a JMX mbean on top of this jbi management endpoint, but I would rather have a method that receive all the parameters needed to create the endpoint, instead of having to modify the endpoint after it has been created (which is more complex to handle). Would that suit your needs ? Question 2:
Would it be possible to create JMX operation that would deploy a duplicate component, with a temporary service name to avoid collisions. (This is of course, if the answer to question 1 was yes since the component would then need to be configured).
What is the purpose ? to ease the creation of the endpoints without having to retype all the parameters ? I'm still not sure about all this stuff. I'm nearly thinking that we would not need all that if we have a good design tool, where you could see all endpoints, create new service units easily, wire them, etc... Cheers, Guillaume Nodet Thank you,
Doug
-- Cheers, Guillaume Nodet
