[
https://issues.apache.org/struts/browse/WW-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46730#action_46730
]
Sander Sõnajalg commented on WW-3241:
-------------------------------------
yes, that's more or less what i meant to say, if you put it this way :)
i mean the point of the demo-apps should be to set an example of the
conventional usage of the framework. the only place that uses annotations
configuration at all is the "person" part of the showcase app, and it uses the
old deprecated API.. which in my eyes kind-of falls short of the original goal.
besides, really, you should probably put some more stress on the fact that
setting up struts filters and actions has changed quite significantly between
2.0 and 2.1... somebody armed with a struts2 book written for minor version 2.0
can get really-really confused, as he doesn't expect that the configuration has
changed so much between two minor versions. on one hand, you seem to want to
put more emphasis on configuring everything with annotations and lessening the
xml configuration, and on the other hand, all your demo apps are still using
xml configuration and there is not even a single completely up-to-date example
of how one should set it up. just reading your conventions plugin manual and
assuming that "most of the things probably haven't changed between minor
versions" will guarantee the user a long and painful setup process. i see some
room for improvement here : )
> ShowCase demo application still uses the CodeBehind plugin.
> -----------------------------------------------------------
>
> Key: WW-3241
> URL: https://issues.apache.org/struts/browse/WW-3241
> Project: Struts 2
> Issue Type: Bug
> Components: Example Applications
> Affects Versions: 2.1.6
> Environment: ubuntu linux 8.10, tomcat 6.1
> Reporter: Sander Sõnajalg
> Priority: Minor
>
> ShowCase demo application still uses the CodeBehind plugin. This means there
> is no demo or good-enough documentation on how to configure my application in
> case i *DON'T* want to use the "intelligent" defaults, i.e. i don't want to
> rename my action package to "actions" or sthg. Yes i know i can set the
> searched packages by hand, but anyhow, there seem to be some bugs in the
> Conventions plugin... (but how would i know, if you don't provide a nice
> example on how you actually *intend* it to be used, and provide a demo-app
> relaying on the depracated old plugin instead..?). i'll report my suspicions
> in a separate ticket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
