You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Sander Sõnajalg (JIRA)" <ji...@apache.org> on 2009/09/07 13:12:34 UTC
[jira] Created: (WW-3241) ShowCase demo application still uses the
CodeBehind plugin.
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.
[jira] Commented: (WW-3241) ShowCase demo application still uses
the CodeBehind plugin.
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46731#action_46731 ]
Musachy Barroso commented on WW-3241:
-------------------------------------
I agree with that. What makes it extra confusing is that there used to be a be a ZeroConfig plugin that was rolled into the CodeBehind and then Convention came to the scene and we deprecated CodeBehind. Convention is pretty stable and is the way to go in the future. Showcase has not been updated and it need some serious love overall. The rest showcase app does use convention.
If you are working on a JRebel plugin, feel free to start a thread on the dev mailing list as we can give you some pointers on where to look. We already have a builtin class reloading/configuration reloading mechanism that could give you some integration ideas.
> 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.
[jira] Commented: (WW-3241) ShowCase demo application still uses
the CodeBehind plugin.
Posted by "Sander Sõnajalg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (WW-3241) ShowCase demo application still uses
the CodeBehind plugin.
Posted by "Musachy Barroso (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46728#action_46728 ]
Musachy Barroso commented on WW-3241:
-------------------------------------
did you mean to say "showcase is not using the convention plugin, please update it"?
> 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.