RE: [OS-webwork] Partition XWork [Was: Re: XWork flux]

2003-01-31 Thread Jason Carreira
-Original Message- From: Erik Beeson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 7:57 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Partition XWork [Was: Re: XWork flux] Jason says 7 jars, Hani says 1, Pat says 2. I have two things to say. Ummm... No. I

Re: [OS-webwork] Parameters and the ValueStack

2003-01-31 Thread Erik Beeson
I'm talking about webwork 2.0. Should everything be lookedup on the stack? Pat's TextfieldTag currently doesn't. I just want some clear standard to be decided upon. --Erik On Sat, 1 Feb 2003, Scott Farquhar wrote: Erik, Which values are not looked up on the stack? I know that id isn't (in

[OS-webwork] how to access bean property?

2003-01-31 Thread Andre Mermegas
Hey all, If I'm doing something like: In my Action.doExecute() ActionContext ac = new ActionContext(); BeanUtil.setProperties(ac.getParameters(),new TestBean()); TestBean has one property name. How do I access the name property using the ww taglibs? ww:property value=name/ doesn't seem to be

[OS-webwork] Report to Recipient(s)

2003-01-31 Thread notes . mis
Incident Information:- Originator: [EMAIL PROTECTED] Recipients: [EMAIL PROTECTED] Subject:[OS-webwork] how to access bean property? Message from [EMAIL PROTECTED] was quarantined because it contained something potentially damaging to the computers and/or may affect the performance of the

RE: [OS-webwork] Parameters and the ValueStack

2003-01-31 Thread Jason Carreira
I think id is the only thing not looked up, and should be the only thing not looked up. The reason is that id is a standard attribute to set something into the page request with a certain name, and it's not dynamic anywhere else. -Original Message- From: Erik Beeson [mailto:[EMAIL

RE: [OS-webwork] how to access bean property?

2003-01-31 Thread Jason Carreira
Title: RE: [OS-webwork] how to access bean property? Andre, You'll want to do ActionContext.getContext() instead of new ActionContext(). ActionContext.getContext() gets the ThreadLocal instance which is populated by the ServletDispatcher. You'll probably also want to maintain a

RE: [OS-webwork] how to access bean property?

2003-01-31 Thread Andre Mermegas
Title: RE: [OS-webwork] how to access bean property? Thanks, for the help Jason, Great explanation. Its working now and Im back on my way to happily exploring more stuff =D Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On

RE: [OS-webwork] how to access bean property?

2003-01-31 Thread Erik Beeson
Read Jason's email again carefully. For that to work, you need to have the ww:property value=name / tag inside the body of the first tag. Like I said, check Jason's example again carefully. To the developers who don't want to break up PropertyTag, here we see the problem with a single tag that

RE: [OS-webwork] how to access bean property?

2003-01-31 Thread Andre Mermegas
Ahh ok. Thanks. Read it too quickly. Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Erik Beeson Sent: Friday, January 31, 2003 10:34 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] how to access bean property? Read Jason's

RE: [OS-webwork] how to access bean property?

2003-01-31 Thread Jason Carreira
I agree. PropertyTag does too much. In WW 2.0 we're planning on having ww:property JUST do the output of the value, and have the pushing onto the value stack be done by ww:push ...use value here... /ww:push -Original Message- From: Erik Beeson [mailto:[EMAIL PROTECTED]] Sent:

RE: [OS-webwork] Xwork 1.0 / Webwork 2.0 design session

2003-01-31 Thread Jason Carreira
Oops, forgot to list the time... I was thinking 2PM Eastern time Monday 2/3... -Original Message- From: Jason Carreira Sent: Saturday, February 01, 2003 12:23 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Xwork 1.0 / Webwork 2.0 design session On the table is the ThreadLocal