> >> > Yeah, I like the idea of strict-DMI. Right now I could not get it > > working > >> > with the convention pulgin, can investigate next week. > >> > >> That's why I want to have programmable configuration in XWork and then > >> XML or Convention configuration via plugins - there strict path how to > >> add new configuration option, like DMI strict mode. > >> > >> > And I just realized that using "method:foo" parameter names works > >> > independent of DMI. > >> > >> Strange, what ActionMapper do you use? > >> > > > > In the app I tested with I have 2.3.15.1 and default ActionMapper (nothing > > configured). strict-DMI was not explicitly enabled. > > > > I just added "allowed-methods" to one action. Afterwards I could not > > invoke methods via URL (gave me method-not-allowed). > > But a form with "method:add" did still work (while foo!add.action did > > not). > > > > > > When I try to enable strict DMI like this: > > > > <package name="..." extends="..." strict-method-invocation="true"> > > > > I get an exception at app start: > > org.xml.sax.SAXParseException: Attribute "strict-method-invocation" must > > be declared for element type "package". > > Change DTD in the header > >
Oh, yes, that was quite obvious. But still: method:add works while !add does not. Regards, Christoph This Email was scanned by Sophos Anti Virus
