Alright, I think what I'll do is restore the ability to supply your own
MessageObserver. If no MessageObserver is supplied we'll let the binding
create one. This will give the Binding a chance to set up a chain for
scenarios where we don't know the endpoint ahead of time, and allow people
to override this.

That sound good?

- Dan

On 4/17/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:

I have just found a work around:

            server = new ServerImpl(getBus(), ep, null, new
AbstractBindingFactory() {
                public Binding createBinding(BindingInfo binding) {
                    return null;
                }
                public void addListener(Destination d, Endpoint e) {
                    d.setMessageObserver(chain);
                }
            });

where chain is a previously created ChainInitiationObserver.
Thought it seems a bit weird ;-)

On 4/17/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>
> Same question here :-)
> I used my own MessageObserver to set up some properties on the message
> before launching the interceptor chain...
> Btw, how can I retrieve the BindingFactory ?
>
> On 4/17/07, Dan Diephouse <[EMAIL PROTECTED]> wrote:
> >
> > Hi William,
> >
> > Mind if I ask a few questions first? I think there are some cases
where
> > you
> > probably do want to specify your own MessageObserver, but this seems
> > opposed
> > to the goal of letting a binding manage how endpoint resolution
happens.
> > I
> > would like to unify the two better though - so maybe you can help me
> > figure
> > that out :-)
> >
> > Why are you specifying a different messageobserver?
> >
> > Where were you previously specifying your own messageobserver -
> > ServerImpl?
> >
> > Thanks
> > - Dan
> >
> > On 4/17/07, William Tam <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Dan,
> > >
> > > Is it possible to specific my own MessageObserver rather than using
> > the
> > > default "ChainInitiationObserver"?  Prior to this change, I could
name
> > my
> > > MessageObserver in the constructor of ServerImpl().  I could no
longer
> > do
> > > that.  The MessageObserver is now hardcorded in
> > > AbstractBindingFactory.addListener().  It is not possible for me to
> > > override
> > > it because I don't have control over the BindingFactories.
> > >
> > > Thanks,
> > > William
> > >
> > >
> > >
> > --
> > Dan Diephouse
> > Envoi Solutions
> > http://envoisolutions.com | http://netzooid.com/blog
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/




--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/




--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Reply via email to