+1 on that solution. It also serves as a work-around in the (unlikely) event that some property gets added to the standard.
Kichline, Don (EM, PTL) wrote:


Searching on the new groups, that is what I have been hearing...  Unfortunately that 
is not going to fly in this case.  What I am proposing is a generic work around for 
this problem that will not tie struts into any single-vendor specific attributes.

Pass in a Properties class with key/value pairs into the tag.  The tag will then 
iterate through the Properties and output the pairs as attributes into the tag.

I would have to agree that supporting a propietary attributes would go against the 
spirit of open source.  On the other hand saying that you have to maintain your own 
copy of the code does not do open source much good either.  I believe a little 
flexability in handling the attributes is in order.  Remember that not everyone has 
the ability to just throw away all vendor-specific items and go completely standard.  
Honestly, the largest culprite here is time and money.  Of course we don't have enough 
of either.

Thanks,

Don Kichline


-----Original Message----- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 19, 2004 4:52 PM To: Struts Users Mailing List Subject: Re: non-standard attributes in taglib


Historically, the Struts developers have been very strict about accepting only W3C standard attributes, and I don't see this changing anytime soon -- it would be somewhat ironic for an open source project to endorse a proprietary single-vendor lock-in by doing something like this :-). I suspect most people who want to use such attributes anyway follow your option (2) but just maintain their own version of the modified tag library.

Since you're talking about a new application here, you should also
take a look at using JavaServer Faces (JSF) components for your user
interface, instead of the Struts HTML tags.  With the standard
components you will run into the same issue (they only support
standard attributes), but it seems a lot more likely that a community
could grow up around custom JSF components that supported these
attributes, because they can be used in any JSF compatible
environment, not just in applications that use Struts.

Craig

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






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



Reply via email to