Chris Miller wrote:
What would happen if the skins had to be explicitly defined in the
configuration, or if none were defined then XWork would default to "pinned"
paths?
Then there would be an outcry of "too much to configure.. waaah". :-)

That way people that were not using the skinning would be able to use
declaritive security as in a normal webapp, while the skinners could still
use it to with relatively minor inconvenience - they'd have to declare a
separate security constraint for each skin, eg:

      <web-resource-collection>
         <web-resource-name>Management Application</web-resource-name>
         <url-pattern>/admin/*</url-pattern>
         <url-pattern>/skin1/admin/*</url-pattern>
         <url-pattern>/skin2/admin/*</url-pattern>
         <http-method>*</http-method>
      </web-resource-collection>
So those paths would then be duplicated in xwork.xml? Doesn't sound very appealing to me.

/Rickard



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to