Eric:
Without consulting the code (much)... if you want
your custom task to recognize any of
<mytask>
<mytypea />
</mytask>
<mytask>
<mytypeb />
</mytask>
<mytask>
<mytypec />
</mytask>
where mytypea|b|c all have one base class, you will
want to make each type available with a typedef and
then the code you have--addConfigured(BaseTypeClass
o)--should work. Beyond that I do wonder why you need
to cast your subtypes... OO would dictate that you
call a designated method and they would simply behave
accordingly, but whatever floats your boat I suppose.
HTH,
Matt
--- Eric Tchepannou <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am developing an ant task extension but face
> problems to have it
> running from the buildfile. I get an error stating
> that a certain
> custom type of mine is not supported by my task.
>
> I think I know where the problem might come from:
> I have implemented multiple types that I have
> defined as extension of
> a base abstract class (that implements an interface)
> and in my Task
> extension I have defined an
> addConfigured(BaseTypeClass o) and do the
> casting in the method implementation.
> Could this be the source of the problem?
> Should I rather for each type subclass implement a
> addConfigured(TypeSubclass o)?
>
> ...or do you think the the problem somewhere else?
>
> My next step will be to test this, but as this might
> be a time
> consuming typing job, I thought I could count on
> your previous
> experiences.
>
> Many thanks for your contributions.
>
> --
> Best Regards,
> Eric Tchepannou
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Discover Yahoo!
Use Yahoo! to plan a weekend, have fun online and more. Check it out!
http://discover.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
