Our real app has numerous cases where the URL namespace doesn't match the Java package structure. I was hoping we could make this work without restructuring the application and/or modifying URLs. Is this something that is fixable, i.e., should I submit a jira ticket, or do I need to just bite the bullet and change our app?
Thanks, Jim On Tue, Oct 29, 2013 at 7:23 AM, Lukasz Lenart <lukaszlen...@apache.org>wrote: > The problem is with @Namespace annotation in HelloWorldAction which > doesn't play well with init-param actionPackages. Simple move > HelloWorkAction to package org.apache.struts.helloworld.test and set > actionPackages tp org.apache.struts.helloworld and remove @Namespace > annotation. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2013/10/22 Greuel, Jim <jim_gre...@fws.gov>: > > Thanks Lukasz. Yes, setting defaultParentPackage fixes the problem for > the > > sample app, but my real app has multiple custom struts packages, so I > can't > > specify a single default that works in all cases. > > > > Jim > > > >> In 2.0.11 the Codebehind plugin was just a .... UnknownHandler ;-) > > > >> Try add this: > >> <constant name="struts.configuration.classpath.defaultParentPackage" > >> value="basicstruts2"/> > > > >> And you don't have to include "struts-plugin.xml" - framework does it > >> for you ;-) > > > > > >> Regards> -- > Łukasz> + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
