"Costin Manolache" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Magesh Umasankar wrote:
>
> > Hi,
> >
> > I am in need of a mechanism to be able to define
> > user defined Tag->Class mappings *before* the
> > names of the default types and tasks are mapped.
> > I have attached a patch herewith.  Comments?
>
> What about droping the tag->class loading in init(),
> and doing it on-demand ?

I am cool with that.

>
> It can be done fully backward compatible - and it
> would allow a cleaner solution ( IMO ) and integrated
> with any antlib.
>
> Assuming ProjectComponentHelper hook is accepted, you'll
> be able to hook in any Tag->Class factory and override
> the defaults in a consistent way.
>
> My tests show the initial loading of all tasks/types
> takes 3-4 second - so the startup time will also be reduced.
>
> I'm +0 on your patch as a temporary solution, but I really
> want to later add the lazy loading.

It is a temporary solution, yes.  It doesn't
break anything and is harmless enough by itself.

>
> It can be done in a backward compatible way - by populating
> the hashtable on demand, antcall needs the hashtable and
> the API is public. If no antcall is made ( or no other task
> calls this method ) then the full task definition will not
> happen.
>

+1 on the approach.

> Costin

Cheers,
Magesh



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to