On Sun, 10 Feb 2002 18:59, Adam Murdoch wrote:
> Sure, but you have to have a tag for each of the role interfaces the type
> happens to implement, directly or indirectly. This isn't a bad thing if
> you want complete control over where a type can be used.
Im a control junky with respect to my builds and my code environments ;)
> Personally, I couldn't care less where a type that I write gets used. I
> want Ant to figure it out for me. Same with the implicit TypeInstanceTask
> - I want that to just happen. So, when I write a type, I don't want to
> have to do anything more than add a *single* tag that says 'this is a
> data-type, and this is its name', and have Ant do the rest for me.
Possible to do with xdoclet if we write an xdoclet extension.
> The solution we come up with should deal with both styles. Unfortunately,
> I don't think we can do all this via XDoclet, some of it's going to have to
> happen when the type is deployed.
XDoclet is extremely flexible - we would have to write our own tag evaluator
(like a jsp tag handler I suppose) but it is possible.
--
Cheers,
Pete
----------------------------------------------------
"The only way to discover the limits of the possible
is to go beyond them into the impossible."
-Arthur C. Clarke
----------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
