> But that's not what my point was.  It was more of, do we take the
> valid_values and split them.  Or do what it's doing now, which is take
> the field value and index into valid_values.
> 
> But now, an aditional issue.  Do we split up the tag value also?  I
don't
> think we should.  Is there any case where we allow multiple values for
> the same tag?  (ie view-type="local,remote") (yes i know this doesn't
> work. it's just an example)
> 
> IMHO, valid_values should have been a String[] with each value
seperate.
> the way it is now limits the content of what's valid (ie: no commas
can
> be present in the value).  Not to mention the performance hit we get
for
> tokenizing the same strings over and over.

The problem is values="blabla" attribute of classTagValue/friends.
There's no way to use String[] in xml-ish template
(<XDtClass:classTagValue tagName="aa" paramName="bb" values="a,b,c"/>).

We will eventually remove this comma-separated format because we're
going to specify the valid values and stuff like that in a tag
deployment xml file. So: fix is there's a mini bug, and wait for the xml
tag def stuff.

Cheers,
Ara.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to