On 5/20/05, Achim Huegen <[EMAIL PROTECTED]> wrote:
> I just made a graph of the dependencies on the parse and schema packages.
> Have a look here http://wiki.apache.org/jakarta-hivemind/XMLDependencies
> Maybe this can give you some hints about what other classes has to be changed.
>
Nice.
> I think lazy loading will get difficult, if you plan to work with typed
> objects.
> Example :
> A contribution to configuration 'symbolsources' could work like this:
>
> SymbolSourceContribution contr = new SymbolSourceContribution();
> contr.setName('newSource');
> ...
> registrybuilder.addContribution('symbolsource', contr);
>
> Do you have something different in mind or how would you implement lazy
> loading her?
>
I had something different in mind. Something which much closer
resembles what the current API with the *Descriptor classes looks
like. Just interfaces instead of classes and with XML specifics
stripped of. So for example:
public interface Contribution
{
String getExtensionPointId();
Object[] getElements();
}
There would of course be an "owning" Module interface with a
getContributions() method to establish the module relationship.
An implementation of this interface would return the
SymbolSourceContribution objects with a call to getElements(). The
implementation could then chose to implement a lazy loading strategy
or not.
Does that make sense?
--knut
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
