Removing the REST plugin restores regular S2 .action accessibility. So I guess my questions are: is this by design, and is there a way to combine both in the same app?
Dave --- On Sat, 11/8/08, Dave Newton wrote: > Running 2.1.3, playing with REST plugin again. > > - o.a.s2.d.ng.filter.StrutsPrepareAndExecuteFilter. > - web.xml has actionPackages param, foo.bar > - struts.xml has some actions not in foo.bar pkg > > I can only access non-foo.bar actions through > show!execute.json URLs; I can't do show.action like > I'd expect. > > Why can I access the non-actionPackages actions via > REST-like URLs at all? > > Why don't I have access to non-actionPackages actions > via normal S2 URLs? > > If I disable classpath scanning for *both* REST and > Codebehind plugins and leave the actionPackages param: > > - I can't access RESTy actions at all > - I *can* access non-RESTy actions via REST syntax. > > If I leave the actionPackages param blank and leave > classpath scanning disabled for both plugins it's the > same thing. > > I'm a bit confused at the moment. On startup the > non-actionPackages actions are being picked up from the > struts.xml, but I can't access them. I kinda need both, > though. > > I'm assuming I'm missing something obvious, but so > far I'm not sure what it is. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
