cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: things that lurk under a bus
Date Wed, 27 Feb 2008 00:52:43 GMT
Hi Benson,

You could think the bus as a static components repository, you could put 
your type map into as you want.
But if you want to meet the requirement with putting the type maps into 
a bus extension, it is not easy to deal with the multi type maps with 
one bus extension entrance, especially you want to it be thread-safe.

How about put the type map into the data binding or some other place 
which instance is per service?

Benson Margulies wrote:
> Folks,
> I'm thinking through an occasionally-discussed plan to clean up Aegis,
> removing some xfire-artifact architecture.
> The proposal, originating with DanD, is to eliminate the
> TypeMappingRegistry. There will still be type maps, but not so many of them.
> I would expect the usual situation to be that each service has a type map
> that falls back to one of the two stock SOAP type maps.
> Which brings me to my question. I've never had a terribly firm grip on the
> Bus architecture. It seems to me that Aegis wants to have a bus extension in
> which it can initialize, once-per-jvm, the two standard soap type maps. We
> want this to initialize only if needed, but we want it to be thread-safe.
> Can some kind soul point me at a pattern of this sort of thing?

View raw message