ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <gno...@gmail.com>
Subject Re: JBI component enhancements ...
Date Thu, 08 Feb 2007 22:51:09 GMT
Sounds good.
Will try to implement that asap.

On 2/8/07, Alex Boisvert <boisvert@intalio.com> wrote:
> On 2/8/07, Guillaume Nodet <gnodet@gmail.com> wrote:
> >
> > I have a project where the BPEL calls JBI endpoints that
> > are not deployed in the same service assembly.  Unfortunately,
> > the start order between service assemblies is not specified
> > so that when the JBI container restarts, the SA may be started
> > in the wrong order.  The problem is that when the SU is started,
> > endpoints are resolved in the BindingContextImpl.createPartnerRoleChannel
> > method, and thus throws an exception if the endpoint has not been
> > activated.  Is there any reason why this is done at startup time, or
> > could this be defered when the partner is first used ?
>
>
>
> I've run into the same problem before and I agree it should be deferred as
> well.
>
>
> Another question is about the possibility to use interface based
> > routing in JBI, thus allowing the NMR to choose the actual target
> > endpoint, rather than specifying the service QName and port name.
> > I think this would need a change in the deployment descriptor, but
> > how would this affect the axis integration ?
>
>
>
> Perhaps we could use interface-based routing if no service binding is
> defined?  (For JBI only)
>
> alex
>


-- 
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Mime
View raw message