Yes i got this line in webwork.properties:
webwork.action.extension=jhtml
On Fri, 2003-11-28 at 16:02, Jason Carreira wrote:
I think there's a property you need to set in webwork.properties to tell
it you want to use .jhtml as the extension...
-Original Message-
From: David
Why is there a distinction made b/w how to you reference a interceptor
stack within a package and stack or action reference?
Why for instance is it default-interceptor-ref instead of
interceptor-ref.
If you define an interceptor-ref for the package isn't that implicitly
the default
for all
Umm.. So you realize you're setting the default for every action in the
package?
-Original Message-
From: Robert Nicholson [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 30, 2003 4:24 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Referencing default stack from a package?
But doesn't the fact that I've even referencing something at package
level do that?
and if I don't want what I referenced at package level then I'll
override it in my action.
On Nov 30, 2003, at 4:29 PM, Jason Carreira wrote:
Umm.. So you realize you're setting the default for every action in
Not that I know of... One problem with doing this is having different
validations for different contexts... This type of multiple-deployment
issue is something Xdoclet sucks at, in my experience, and I don't know
if there's a way to make it better.
-Original Message-
From: Robert
I'm missing something here
so you want external validators, specified in an external xml
configuration file...and you want to generate this file by adding
javadoc comments to the source file that needs the validation, thus
putting in validation code right alongside the code that needs it,
But they're fundamentally different... One is directly setting a
reference into an Action... The other is setting a default for all
Actions.
-Original Message-
From: Robert Nicholson [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 30, 2003 6:13 PM
To: [EMAIL PROTECTED]
Subject:
I don't think you're understanding me.
If I put an interceptor-ref outside of an action at the package level
why isn't
that the same as setting a default?
On Nov 30, 2003, at 7:14 PM, Jason Carreira wrote:
But they're fundamentally different... One is directly setting a
reference into an
I'll be even more specific just in case you're still not understanding.
If you set something at package level then it's implicit that those
items are defaulted for actions within that package. So why is it
necessary to have default-interceptor-ref at the package level when
interceptor-ref at
Because it is not valid according to the DTD, for one.
I understand what you're saying. I'm explaining why it's designed this
way. The DTD is designed to be simple yet easy to understand, and it's
too confusing and error-prone to have the interceptor-ref used for
multiple different purposes.
Is it possible to define a default error result (dispatcher) simply by
defining a result at the package level instead of the action level? I
don't have to say default-result for that right?
Consistency is better than simplicity.
---
This
You can define global results for all of your actions inside a
global-results block like this:
global-results
result name=login !-- should be chain type since it is
the default --
param name=actionNamelogin/param
/result
/global-results
Well I guess I'll accept the way things are as I wasn't contributing
when you guys were hammering this stuff out way back when.
I just thought that it was easier to think of it simply as anything
global
would be defined at the default package level and simply inherited thru
all child
packages
To answer your question: not currently. No one has written support for
XDoclet, but I would expect that to happen one of these days :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robert Nicholson
Sent: Sunday, November 30, 2003 4:42 PM
To: [EMAIL
Title: Message
Fred,
I think that I am seeing eye-to-eye with
you on your vision. This is good stuff and I hope it doesnt get lost in
the near future. If you can, can you open a jira issue with these various
aspects and/or continue to keep tabs on progress towards this goal?
-Pat
What does it mean to be a default?
Am I confusing default with inheritance?
My understanding is that a defaulted definition can be inherited.
Therefore anything
you define at the package level can be inherited by the actions and
subpackages of that package. I just don't understand why it is
16 matches
Mail list logo
