OK guys, I found the problem. Turns out that the problem is actually to do with resolving actionBeans on start up. Seems that 1.5 doesn't like a '*' in the package filtering config - it finds no actionBeans if it's int there in my config.
To be more specific: In my stripes 1.4X config I had the filter packages defined as: <init-param> <param-name>ActionResolver.PackageFilters</param-name> <param-value>com.mypackage.*</param-value> </init-param> So when I upgraded to 1.5 I followed the upgrade guide and changed that to: <init-param> <param-name>ActionResolver.Packages</param-name> <param-value>com.mypackage.*</param-value> </init-param> Now - although the param value is the same the ResolverUtil.find method no longer discovers any actionBeans on startup. BUT - this works: <init-param> <param-name>ActionResolver.Packages</param-name> <param-value>com.mypackage</param-value> </init-param> So - It's either a bug or the upgrade guide needs updating to tell people not to use '*' char anymore. -- View this message in context: http://www.nabble.com/%40DefaultHandler-tag-just-stopped-working...-tp18325728p18412465.html Sent from the stripes-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
