Excellent, Thanks Guillaume and James. I have two comments: - James, does the client API intentionally allow invoking a service without specifying an operation? - Guillaume, would it be possible to inject a DeliveryChannel instance into the web application context?
Hossam Karim On 6/30/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Great ! I already love Destinations + URIs. This is a very useful addition. One thing we might want on the client api is maybe a factory that we could bind to JNDI so that you can access this API from anywhere. I have discussed that with Aaron Mulder in Dublin (about ServiceMix integration with Geronimo). We currently lack a simple way for web application to access an existing JBI container. We could use gbeans inside Geronimo, but this is not portable, so a JNDI factory seems a good fit. Does anyone think about a better way ? Cheers, Guillaume Nodet On 6/30/06, James Strachan <[EMAIL PROTECTED]> wrote: > > I've added support for a Destination interface which makes it easier > to work with destinations (endpoints) in JBI from a client API rather > like working with Destinations in JMS. > > You can create a destination from a URI then use it as a factory of > MessageExchange / Message objects to simplify working with JBI. > > I've updated the documentation to describe this... > http://servicemix.org/site/client-api.html > > (see the section on working with URIs and Destinations). > > I've tried my best to make this as simple as possiblie for folks to > use to interact with the NMR though I'm open to suggestions - can > anyone think of any ways to improve this API and make it simpler? > > -- > > James > ------- > http://radio.weblogs.com/0112098/ >
