Yes, we do mark Showcase examples to be non-functional when we realize
they are not working properly. Unfortunately, it's not always obvious
how some of these example are suppose to work. In the past, when I've
found an example is not working, we've tagged it as such ("broken"),
and most of these were ultimately fixed. If you would like to help,
please open a JIRA ticket so that the problem is addressed before the
next release.It might even be a good idea for someone to start a new Showcase application that uses a consistent set of practices. The current implementation kicked around the WebWork project for several years before landing here, and it might be showing its age. Honestly, I wouldn't consider even the MailReader a model application. In a lot of ways, it is a typical and realistic implementation, but I would not call it ideally designed. What I would really like to do is create a model Petshop application for Struts 2. I've setup a Google Code site for this purpose, but I haven't had a chance to seriously pursue it yet. * http://code.google.com/p/sq1-petstore/ My dream would be to have a full set of use cases, a reasonable set of formal requirements, and full suite of JUnit and Selenium tests for Petstore, along the lines of what I do for my own projects. -Ted. On 8/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I think it should not be "ShowCase'd" if it is known not to work. > Developers like me, are pouring over this code trying to glean insight into > how to wire up these bits and parts. After many hours of exploration and > finally going to a several other semi-related web sites, I began to realize > there was no way the example could be expected to work! I would rather have > those hours back or have spent them looking at code that was expected to be > used as model code. > > Scott > > On 8/13/07, Ted Husted <[EMAIL PROTECTED]> wrote: > > > > We do try to tag the examples that are broken, in the hope that > > someone will someday fix them. I just didn't realize that this one > > wasn't working the way it should. The Showcase could use a lot of > > work, especially in terms of explaining exactly what the example > > should do. If you can fix the example, please submit a patch. > > Otherwise, feel free to open a JIRA ticket suggesting that the example > > be tagged as broken for the next release. > > > > -Ted. > > > > On 8/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Do you think leaving known broken code on the "Showcase" is a good idea > > > realizing developers are flocking to this resource to figure out how to > > do > > > things? If it is known not to work, maybe it should say this or be > > removed > > > from the Showcase! > > > > > > On 8/10/07, Musachy Barroso <[EMAIL PROTECTED]> wrote: > > > > > > > > Yes the example had several problems on 2.0.x, some of them were > > > > fixed, others are still there. > > > > > > > > musachy > > > > > > > > On 8/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > I'm studying the dynamic tree example in the showcase, and there are > > a > > > > > couple problems. First, when you view sources, the configuration > > for > > > > the > > > > > dynamicTreeSelectAction is not visible. Also, as I inspect this > > action, > > > > I'm > > > > > discovering that its dynamicTreeSelect.jsp never displays the node > > > > > selected! Is this example not finished? > > > > > > > > > > -- > > > > > Scott > > > > > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
