Re: [OS-webwork] releasing a component

2003-12-07 Thread Anoop Ranganath
I don't think that will necessarily solve the problem. Disposable will allow it to tidy up when XWork ends that session, but it doesn't allow me to explicitly ask XWork to ditch that component now. After I get rid of it, I want the next action that is Aware of it to instantiate a new one, eve

RE: [OS-webwork] releasing a component

2003-12-07 Thread Patrick Lightbody
Have your component implement Disposable. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anoop Ranganath Sent: Thursday, December 04, 2003 2:27 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] releasing a component How do I go about telling the IoC contain

RE: Spam:Re: Spam:[OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Jason Carreira
I thought that's how the Introspector finds indexed properties? Doesn't BeanUtils use the Introspector? > -Original Message- > From: Hani Suleiman [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 07, 2003 7:37 PM > To: [EMAIL PROTECTED] > Subject: Spam:Re: Spam:[OS-webwork] WebWork 1.4

Re: Spam:[OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Hani Suleiman
Well, of course not. You'd have to call it yourself, there is no magic to figure out that that's the method you want. Secondly, even if you do call it, it's a pretty stupid idea and won't work anyway, since you'd have to write the impl for it yourself, and last I knew, it's not possible to inde

Re: Spam:[OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Frank Febbraro
I have tried exposing the setAllocation(int index. Allocation alloc) method too. It never gets called and the same error message is generated. - Original Message - From: "Jason Carreira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 07, 2003 1:49 PM Subject: RE: Spam:

Re: [OS-webwork] NEWBIE: addError - Webwork 1.3

2003-12-07 Thread Rajagopal. V
Thanks Hani, Just figured out the controlheader.jsp. Also shouldnt the stylesheet associated with the template pages be included automatically when the controls are present in a page? Maybe a webwork:style taglib that would place the styles.css file in the page. This would make it one less thing

Re: [OS-webwork] NEWBIE: addError - Webwork 1.3

2003-12-07 Thread Hani Suleiman
There are two kinds of error messages, general ones and field specific ones. The field ones go alongside the field, as used by controlheader.jsp which is included in every template: To show other error messages, you have to specifically do so in your own pages, by adding somethin

[OS-webwork] NEWBIE: addError - Webwork 1.3

2003-12-07 Thread Rajagopal. V
Hello All, If we do an addError("FieldName", "error message") , is this supposed to display the error message next to the field in the UI? Can someone explain the difference between doing a addError Vs. addErrorMessage. I looked at templates/xhtml/text.jsp(and other control jsps) and couldnt find a

RE: Spam:[OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Jason Carreira
You might want to expose getters and setters like this: void setAllocation(int index, Allocation alloc) Allocation getAllocation(int index) > -Original Message- > From: Frank Febbraro [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 07, 2003 12:10 PM > To: [EMAIL PROTECTED] > Subject:

Re: [OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Hani Suleiman
I haven't dug through the source, but I'm fairly sure you can't index into a Set. See if changing it to a List helps. On Dec 7, 2003, at 12:10 PM, Frank Febbraro wrote: I am trying to set some indexed properties on an object, Payment, using the WW1.4 BeanUtil class. class Payment { publi

[OS-webwork] WebWork 1.4 and indexed properties

2003-12-07 Thread Frank Febbraro
I am trying to set some indexed properties on an object, Payment, using the WW1.4 BeanUtil class. class Payment { public Set getAllocations() public void setAllocations(Set set) public Allocation getAllocation(int index) } I have the following properties set in the request allocation[

Re: Spam:[OS-webwork] Xwork and hot redeploy

2003-12-07 Thread Petri Wessman
On Friday 05 December 2003 17:53, Jason Carreira wrote: > As far as being able to have the one Xwork.jar and have multiple > configurations, that's a good idea... Please add a Jira issue. I've > always hated that Singleton, so we can look at how to get rid of it. In > the meantime, is it possible

Re: [OS-webwork] can change the way validators use messages?

2003-12-07 Thread Francisco Hernandez
exactly Jason Carreira wrote: Create a Jira... You just want another level of defaulting, right? If there's a message for the key, it's used. Otherwise, if there's a default message, it's used. If there's no default message and the key is provided then use the key, right? -Original Message---

RE: [OS-webwork] can change the way validators use messages?

2003-12-07 Thread Jason Carreira
Create a Jira... You just want another level of defaulting, right? If there's a message for the key, it's used. Otherwise, if there's a default message, it's used. If there's no default message and the key is provided then use the key, right? > -Original Message- > From: Francisco Hernande