I have been doing Swing/AWT development for about three years now. Over and over again I have implemented the same types of interface devices, scouring the Swing source code, examining stack traces and ever perfecting my use of Threads. I am just now beginning to get good at it. Every time a new Swing release comes out, I can't wait to find out what bugs have been fixed, what new devices are available for Linux that have been taken for granted on Windows, and the like. At the same time I see libraries emerge that promoters claim are the result of Swing's shortcomings, and I mostly find it ridiculous, given the context (time) and my own experience (Swing and Graphics 2D can do all sorts of amazing things). I hope Sun isn't affected much by it and continues on building and documenting Swing. Everyone is in too much of a hurry to go on to the next tool. Programmers who end up building things of substance reach for their trusted tools, devices, paradigms, etc., when they are inspired and want to get something done with confidence. Some of the best Java GUI applications I have seen will run on a (pre-Swing) 1.1 JVM, and here there are people saying Swing is a wash.
Based on what I have read as a subscriber to this list, I conclude that many Struts users feel the same way about Struts as I do about Swing. They (myself included) greatly appreciate James' taglib tests, the ongoing efforts to build a better dispatch action and the work of all other contributors (not only committers). They breathe a collective sigh of relief when they see that Craig is writing papers about Struts 2.
Erik
P.S. This is no attack on Eddie's advice to prefer JSTL to the Struts tags. I often give the same advice.
James Mitchell wrote:
As an FYI. I don't think it is wise to say that the Struts taglibs will be going away. I am of the opinion that they will be around for quite some time. At least until JSF is adopted considered as the default choice for all new web development.
On a somewhat related note, do you even know how many hours I spent creating those taglib tests? ;)
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
----- Original Message ----- From: "Eddie Bush" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, November 04, 2004 11:43 PM Subject: Re: Need an alternative to bean:define
My condolences :-( I now see your rock and hard spot.
It's not about bleeding edge though. Of course, what counts in that regard is your clients' opinion of what bleeding edge is.
Best of luck!
Eddie
----- Original Message ----- From: "Janice" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Thursday, November 04, 2004 12:25 PM Subject: RE: Need an alternative to bean:define
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]
--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0445-1, 11/03/2004 Tested on: 11/4/2004 10:43:32 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
