http://issues.apache.org/bugzilla/
Actually, in general, I think it's better to have some discussion on the lists before filing bugs or enhancement requests, unless the issue is very clear.
In this case, I'm not sure which dirty work David is suggesting that Struts handle. Is the issue with localized converters for things like dates? I'm not sure where else such an issue applies.
What would probably make the most sense would be for David to handle all his dirty work using Struts, and extending it where necessary to achieve a solution, and then present the solution to the Struts community for review and commentary. I don't say this as in "geez, David is so lazy," but more from the perspective that enhancement requests of this scope are always best discussed with more detail than he has yet provided, and often best using working code.
If David doesn't understand Struts well enough to achieve this goal, then hopefully he can do some research and post some pointed questions to the Struts users list until he has an idea of how to do it. If it turns out that Struts isn't flexible enough to support him achieving this goal, then lets make simpler and more general changes to Struts which promote extension in general, and save extensions for rather specific use cases until they've been tested in a running application or two.
I would start by pointing out that in general, the RequestProcessor is designed for extensibility, and for a local solution you could probably start by extending it. It is well understood that the single-inheritance limitations of RequestProcessor make this a difficult way to make a general solution available to the rest of the Struts community -- but the struts-chain RequestProcessor is available already for those who are interested in applying it and developing more generalized extensions to the Request Processing chain, and we do intend to steer Struts to using the chained request processor as the base implementation as one of the next major changes -- but you certainly don't have to wait, as you can already use it, and in fact, it needs more people to use it to flush out any bugs in the adaptation of the existing RequestProcessor functionality.
I hope this helps,
Joe
On Tue, 5 Oct 2004 14:21:50 -0500, David Suarez <[EMAIL PROTECTED]> wrote:How does one go about requesting an enhancement to Struts?
For my particular problem today it seems like Struts could handle all the dirty work for me if it used a version of bean utils that could be registered "per request". Struts could then set the Locale and then populate all of the fields. I guess this would be a bean utils enhancement as well.
Is there one-point place that the above can be suggested? I think the benefit of this is that Struts can host business beans directly and get/set them fully requiring less developer intervention to handle relatively mundane formatting details. This would be less code to be written as well.
Thanks!...djsuarez
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
