I'd backtrack and deploy a simple app with only a single annotated action and the convention plugin and start from there; it's loading the plugin. I'd also check the configuration parameter reference:
http://struts.apache.org/2.1.8/docs/convention-plugin.html#ConventionPlugin-Configurationreference I also always put the action classes in a package whose name ends in "actions"; I vaguely remember having an issue if it was named anything else, but I could be *completely* misremembering that. Dave <http://struts.apache.org/2.1.8/docs/convention-plugin.html#ConventionPlugin-Configurationreference> On Thu, Nov 18, 2010 at 9:41 AM, Aaron Brown <aa...@thebrownproject.com>wrote: > Gently bringing this thread back to the topic in the subject line... > > Does anyone have any ideas about why my WebSphere 6.1 server would be > ignoring the convention plugin and not loading any of my struts2 > annotations into the context? > > I did see some references in the websphere patch info to fixing some > broken annotation processing with respect to web services, but I'm not > using any web services in this particular app (SOAP, etc.). Is this a > patch that I need to apply anyway? I hadn't done it yet since it's > clear my server IS processing annotations for other things like > hibernate and spring (@Autowire, for example, works like a charm). > > Anyway, I'm stumped. > > -- > Aaron Brown : aa...@thebrownproject.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
