On 6/11/06, Don Brown [EMAIL PROTECTED] wrote:
Thoughts?
We used the ! idiom extensively in the WW MailReader and WW CookBook
in the sandbox. I'll update those for the latest build to see how
effective if the wildcard workaound.
Are we going to introduce wildcard support in WebWork 2.2.2.1?
Ted Husted wrote:
On 6/11/06, Don Brown [EMAIL PROTECTED] wrote:
Thoughts?
We used the ! idiom extensively in the WW MailReader and WW CookBook
in the sandbox. I'll update those for the latest build to see how
effective if the wildcard workaound.
Are we going to introduce wildcard support in
Don,
I'm totally in favor of that, but only if we make sure that
struts-action-default.xml (originally webwork-default.xml) includes this
pattern as a default. Does that seem fair?
-
Posted via Jive Forums
What do you mean? Every action would have the option to use this
pattern. How would we set it as the default for all actions?
Don
Patrick Lightbody wrote:
Don,
I'm totally in favor of that, but only if we make sure that
struts-action-default.xml (originally webwork-default.xml) includes
With XWork now supporting wildcards in xwork.xml, I think it is time to
remove the explicit support for the fooAction!barMethod.action syntax.
From a reading of our tickets, the legacy support for that syntax is
affecting the framework in strange ways, and now that we have wildcards,
they can
I finally understand wildcards! Can you give an example of using more
than one wildcard in an action name?
Bob
On 6/11/06, Don Brown [EMAIL PROTECTED] wrote:
With XWork now supporting wildcards in xwork.xml, I think it is time to
remove the explicit support for the fooAction!barMethod.action
Sure... Building on the last example...
action name=*!*.* class=foo.bar.{1}Action method={2}
param name=id{3}/param
...
result name=success/{1}.jsp/result
/action
Eventually, I'd like to get to the point where we define a couple of
generic patterns, and make xwork.xml optional. Then, you
