I should point out that it isn't my company that has the restrictions. My employer would quite happily move to the bleeding edge of any technology if there were any benefit to do so. In this case the client has very definite parameters we need to work within. Their servers are set up in a certain way and they have standards that must be followed or else we don't get paid. I don't have to agree with their standards in order to take their money. ;)
Thanks for the input all the same. J -----Original Message----- From: Eddie Bush [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 5:17 PM To: Struts Users Mailing List Subject: Re: Need an alternative to bean:define I would question anyone who told me I had to use something that is going away in the future (most of Struts' taglibs), instead of using a standard technology (the JSTL). Are they fully-aware of the decision they're making? Are you running within a container that supports Servlet Specification 2.3 and JSP Specification 1.2? I can't conceive of anyone being so narrow-minded. If I told my boss I wanted to use the JSTL over Struts' taglibs (a conversation that would never take place because I'm able to do whatever I feel is best), citing that the JSTL was a standard technology and that the Struts taglibs would be going away, he'd thank me for the FYI and tell me to do what I felt was best. We're very into using standards-compliant methodologies where it makes sense to do so though. Eddie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
