[
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.
