Re: Options for making AT schemas more adaptive

Martin Aspeli wrote:
> On Tue, 02 May 2006 20:01:20 +0100, Rob Miller 
> <ra-UE+B0n23d/[email protected]> wrote:
> 
>>>  As I mentioned to whit, I think there's some more thought to be had 
>>> around having multiple schemas aggregated by this mechanism. E.g. a 
>>> site policy could install some fields, a tagging product could 
>>> install its own fields, and the type could have a few of its own. We 
>>> could get all adapters to ISchemaProvider from self, of course, but 
>>> we'd then also have to have some component responsible for sorting 
>>> and merging the schemata.
>>
>> i'd say to take things one step at a time.  but yes, that's what you'd 
>> be able to do.  it seems pretty straightforward to have 
>> ISchemaProvider fire some events and include a bit of an API for 
>> manipulating the schema before it was actually provided back to the 
>> consumer.
> 
> True, though I think it's important to cover off the use cases before we 
> settle on an implementation. My feeling would be that it's more useful 
> to be able to have schema snippets come from many different places, than 
> to be able to wholesale replace (possibly extend as an implementation 
> detail) the schema of one or more types.

yeah, fair enough, but i'd encapsulate all of that into the 
functionality of the adapter providing ISchemaProvider.  in which case, 
we don't really lose anything by starting w/ a trivial implementation of 
this adapter, and then experimenting w/ more sophisticated 
implementations that support the aggregation.  that's one of the nicest 
things about the CA, it makes this sort of refactoring much simpler.

-r



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642