cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Diephouse <>
Subject Re: Proposal to slim down Aegis
Date Thu, 27 Dec 2007 22:32:54 GMT
Benson Margulies wrote:
> A little more reading leaves me somewhat more confused. Even before the
> changes I made last night, the Context did not represent a
> 'cxf-independent' Aegis API. We really don't have one (in the sense of a
> single class). The comment at the top of Context says that it's
> per-message, and indeed it stores a collection of attachments.
Yeah, well I didn't say it was finished. :-) I gave up half way through 
due to time constraints.
> Let's imagine a new class called AegisContext that works like my
> previous email: it has a type mapping registry, it manages overrides and
> configuration behaviors, and an AegisDatabinding uses it.
I.e. a context which stores information configured at the service level? 
That seems to make sense to me.

- Dan

Dan Diephouse
MuleSource |

View raw message