Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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

RE: [OS-webwork] Type Conversion Handling

2003-11-30 Thread Patrick Lightbody
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 doesn’t 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  

RE: [OS-webwork] webwork2 xwork.xml

2003-11-30 Thread Patrick Lightbody
Actually, I don't think that does anything. Shouldn't it just work? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Nielsen Sent: Sunday, November 30, 2003 2:39 AM To: webwork-list Subject: RE: [OS-webwork] webwork2 xwork.xml Yes i got this line in

RE: [OS-webwork] XDoclet and XWork validators

2003-11-30 Thread Patrick Lightbody
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 PROTE

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Patrick Lightbody
Hi Robert :) I think the core reason for this is because you define multiple interceptor-refs at the package level, so assuming it is the default wouldn't always be the case. The real question is: is this is a good idea? Personally, I've had situations where I've needed the defaultStack and other

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Jason Carreira
Global results are only global for the package where they are defined. They are also inherited, as are default interceptors, etc. There is no configuration outside the scope of a package. > -Original Message- > From: Robert Nicholson [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 30

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Jason Carreira
You can define global results for all of your actions inside a block like this: login > -Original Message- > From: Robert Nicholson [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 30, 2003 9:15 PM > To: [EMAIL PROTECTED] >

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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 SF.

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
I have to disagree with you here. They aren't different purposes... you're just referencing them in different places? The scope is simply broader when referencing at a higher level. I thought the whole point of packages was to use inheritance ie. anything defined at the package level was avail

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Jason Carreira
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. >

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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 at the package level when at the package level would mean the same th

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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 Action

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Jason Carreira
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

Re: [OS-webwork] XDoclet and XWork validators

2003-11-30 Thread Hani Suleiman
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,

RE: [OS-webwork] XDoclet and XWork validators

2003-11-30 Thread Jason Carreira
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 Nich

[OS-webwork] XDoclet and XWork validators

2003-11-30 Thread Robert Nicholson
Can XDoclet currently generate these from javadoc comments in your action? I don't see any references to doing this in the JOSP book. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more produc

Re: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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

RE: [OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Jason Carreira
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? >

[OS-webwork] Referencing default stack from a package?

2003-11-30 Thread Robert Nicholson
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 a

RE: [OS-webwork] webwork2 xwork.xml

2003-11-30 Thread David Nielsen
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

Re: [OS-webwork] upload and the action

2003-11-30 Thread David Nielsen
Its webwork1 and it's pretty anoying... David On Sat, 2003-11-29 at 04:41, Tracy Snell wrote: > On Nov 28, 2003, at 6:43 AM, David Nielsen wrote: > > > why isnt the action class called if u upload a file larger than the max > > size in webwork.multipart.maxSize property > > Webwork 1 or 2? I'm