Re: Re: Re: [xdoclet-user] Newbie question on plugins and templates

[karthik Guru]

Getting to know xdoclet 2 has been fun!. I had another question on MetaDataProvider interface. I just want to understand the process of making things generic and how it is done in frameworks.

ConfigurableDocletTagFactory getDocletTagFactory();

This method is tied to a QDox interface DocletTagFactory? -
MetaDataProvider interface does'nt look generic to me.

Do you guys have any plans of refactoring this interface and making it generic? Any idea as to how it could/should look like if that is the case?

I mean i'm just trying to understand how generama can retrieve metadata from other sources.

thanks,
karthik

On Tue, 24 May 2005 Anatol Pomozov wrote :
>Probably
> > >    String getOriginalFileName(Object metadata);
> > >    String getOriginalPackageName(Object metadata);
>are worth to move to QDoxMetaDataProvider??
>
>On 5/23/05, Konstantin Priblouda <[EMAIL PROTECTED]> wrote:
> >
> > --- karthik Guru <[EMAIL PROTECTED]> wrote:
> >
> > > Sorry for the stupid questions. I had not even heard
> > > of picocontainer, generama etc until couple of days
> > > back.  I'm looking at the code and trying to figure
> > > out what is going on here.
> >
> > Well, picocontainer is wort learning about. It is
> > really good for a lot of puproses ( mostly simplyfying
> > your code by eliminating management / wiring stuff )
> >
> > It also forces you to provide maningfull constructors.
> >
> > ( this is great for testing. )
> >
> > > Ok here is another question :)
> >
> > > Any idea as to where is the dependency being
> > > injected for this constructor?  I mean i want to
> > > know the name of the class that does it...may be am
> > > too lazy to figure that out :)
> > >
> > > That class probably does it for all plugins
> > > registered through ant?.
> > >
> > >    public
> > > LocalInterfacePlugin(VelocityTemplateEngine
> > > templateEngine, QDoxCapableMetadataProvider
> > > metadataProvider,WriterMapper writerMapper)
> >
> >
> > You seen xdoclet invocation - there you specify
> > plugins and template engines.  Everything lands  in
> > internal picocontainer ( see org.nanocontainer.ant.*
> > or alike )
> > then xdoclet / generama registers metadata provider,
> >
> > and then container is started. this means, it finds
> > everything imlpementing org.picocontainer.Startable
> > ( plugins do it by chance ) , instantiates them
> > and cals start().
> >
> > container takes care about instatiaton and injecting
> > necessary components.
> >
> >
> > > Another question:
> > >
> > > Can someone provide me with a simple explanation for
> > > this interface/interface methods? If the metadata
> > > could come from anywhere as the doc indicates, why
> > > do we have methods like getOriginalFileName, etc in
> > > this interface.
> > >
> > > public interface MetadataProvider {
> > >    public static final String ROLE =
> > > MetadataProvider.class.getName();
> > >
> > >    String getOriginalFileName(Object metadata);
> > >    String getOriginalPackageName(Object metadata);
> > >    ConfigurableDocletTagFactory
> > > getDocletTagFactory();
> > > }
> >
> > I would say this is for historical reasons. ( and
> > happened before I joined ).
> >
> >
> > regards,
> >
> >
> > ----[ Konstantin Pribluda ( ko5tik ) ]----------------
> > ... Auf der Suche nach einen Projekt in Rhein-Main
> > ab 18.4.2005
> > ----[ http://www.pribluda.de ]------------------------
> >
> >
> >
> > Yahoo! Mail
> > Stay connected, organized, and protected. Take the tour:
> > http://tour.mail.yahoo.com/mailtour.html
> >
> >
>
>
>--
>anatol