cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <>
Subject Re: Release Update
Date Fri, 16 Mar 2007 19:31:50 GMT
On 3/15/07, Liu, Jervis <> wrote:
> > -----Original Message-----
> > From: Dan Diephouse []
> > Sent: 2007?3?15? 21:44
> > To:
> > Subject: Re: Release Update
> >
> >
> > Hi Jervis,
> >
> > I wanted to ensure that we can setup an endpoint on a URL and route to
> > different services based on headers (such as ws-a) or other
> > logic.  I made a
> > series of proposals about how to do this a while back, but I
> > don't think we
> > ever came to any concrete conclusion.
> >
> Ok, I see what you mean. I believe you are referring to this proposal [1].
> One thing I have not figured out from the proposal yet is how we know the
> addresses of services to which the routing service is about to redirect?
> Through some kind of registries or a configuration loaded from a separate
> file or a WSDL extension.? Once this kind of discussion gets started, I do
> not see how it can end by the end of this release. Service routing is a huge
> topic anyway. However we will have much less to worry about if we are not
> after a complete resolution of service routing. For example, if we only
> support the routing among different endpoints within the same Destination,
> would this feature be considered helpful for some certain use cases? Reading
> your proposal, I believe this is also what you want to do, start from sth
> simple first. If this is the case, I am ready to get my hands dirty now.
> BTW, I am in a traveling at the moment, I may not respond in time until I
> get back to office next Tuesday.
> [1].

Yes, I'm really just concerned about the simple case. Namely being able to
create some type of routing endpoint which routes to other types of
services. My main use cases is versioning of services. Ideally many services
can share the same URL and I can route by headers or the namespace of the
body part.

Regarding how to know what services to route to - I think its up to the user
to write that code. I was kind of envisioning that it'd be an interceptor
that a user writes. We could build something more formal like a registry,
but we would need something low level first :-)

- Dan

Dan Diephouse
Envoi Solutions |

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message