Mike Cannon-Brookes wrote:
Because you'd then mix referring to an interceptor and defining one. Take a look again. If you can think of a better name I'm all for it, but there do need to be two.Copmments: - <interceptor-ref name=""> is ugly XML! Why not just <interceptor ref="" /> ? It's obvious that the name="" attribute refers to the name of an interceptor from the tag name
No, that's why there's the "depends" thing, which usually includes "standard" which in a sense is the global package.- is there a global package?
I didn't know that was a goal. The implementation that is currently in CVS sets these parameters on each request, which is a lot of reflection. It seemed too heavy to me. Isn't it better to have configuration be handled in a traditional way? (i.e. by calling some config API) Remember that actions are going to be instantiated ALL THE TIME. Using the Preferences API might be an option here.- how are parameterised actions handled? (one of the other main xwork goals?)
/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
