Wiwit Tjahjana/HQ/FHLMC is out of the office.
I will be out of the office starting 01/18/2005 and will not return until 02/04/2005. I will be out on a paternity leave/vacation from Tue, Jan 18, 2005 to Wed, Feb 2, 2005. On Thu, Feb 3, 2005, I will be working from home and could be contacted at this e-mail address. I will be returning to the office on Friday, Feb 4, 2005. During this time, please contact: (1) Lee Guan, for Product 5.0 questions, including Derived Requirements, NFR, and Application Architecture (2) Roland Cuellar, for Product 5.1 planning (3) Ravi Singh, for Product 4.2 Warranty (4) Lee Guan and Mark Coble, for CFD for Servicing design and development (Release 5.1) (5) Gregory Bohmer, for CSX 5.0 Support and Application Architecture (6) Gregory Bohmer and Santhosh Ananthakrishnan, for CSX Reuse opportunities for projects in Freddie Mac outside PE. Thank you. wiwit -a proud father of two, a 4-yr old and a newborn baby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: grab form bean was Re: form reset
If you have a request- or session-scoped regular formBean called myform,
a simple call like this will output the value of property myfield
c:out value=${myform.myfield} /
But with dynaBean, you have to qualify the property name with map:
c:out value=${myform.map.myfield} /
Hope that helps!
wiwit
[EMAIL PROTECTED]
10/07/2004 11:05 AM
Please respond to
Struts Users Mailing List [EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
grab form bean was Re: form reset
Hey guys,
Thanks for the response on my first question. Turns out I'm an idiot and
was pre-filling a form element via the value parameter of a html-el...
tag.
However this now leads to a second question. How do I grab the form bean
and the fields? I'd like to print the value of a form field either on an
error or success.
Searching the list, it looks like I can do something like this:
jsp:useBean id=myform class=package.class scope=session/
c:out value=${myform.myField}/
Trying this in my app doesn't seem to work... any clues?
I have my action... setup with scope session and my forward success
with a redirect of false.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Iterate tag issue with an array
I'd recommend this site, which covers JSTL 1.0, that is supported by Struts 1.1. http://demo.pramati.com/jstl-standard-examples.war/index.html Wiwit Tjahjana The information transmitted in this Email is for the exclusive use of the person or entity to which it is addressed and may contain confidential information. If you are not the intended recipient of this Email, you are prohibited from reading, printing, duplicating, disseminating or otherwise using this information. If you have received this information in error, please notify the sender at Freddie Mac immediately, delete this information from your computer, and destroy all copies of the information. Wendy Smoak [EMAIL PROTECTED] 10/06/2004 01:39 PM Please respond to Struts Users Mailing List [EMAIL PROTECTED] To Struts Users Mailing List [EMAIL PROTECTED] cc Subject Re: Iterate tag issue with an array From: [EMAIL PROTECTED] I am willing to use the jstl if needed. What is that syntax? Google should turn up a bunch of examples to get you started if you really want to go that route. I think there's a simpler solution, and would first try to get that *one* item out of the array somehow, so you can test whether it's null or not without messing with the array subscript. Did you try the two other things I suggested, using the [0] subscript with 'property' or doing bean:define, did either of those do anything interesting? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: inheritance in tiles
Dear Amar: If what you mean by parameters is values of Tiles attributes, then the answer is yes. Simply define new attribute in your tiles-defs.xml or override a parent attribute. Or, should you need to derive the value dynamically from request or other scope, do it in a TilesController. Hope that helps Wiwit Tjahjana The information transmitted in this Email is for the exclusive use of the person or entity to which it is addressed and may contain confidential information. If you are not the intended recipient of this Email, you are prohibited from reading, printing, duplicating, disseminating or otherwise using this information. If you have received this information in error, please notify the sender at Freddie Mac immediately, delete this information from your computer, and destroy all copies of the information. Jirole, Amar [EMAIL PROTECTED] 10/06/2004 02:39 PM Please respond to Struts Users Mailing List [EMAIL PROTECTED] To 'Struts Users Mailing List' [EMAIL PROTECTED] cc Subject RE: inheritance in tiles A stupid question : Can we pass parameters in this extension. TIA -Amar -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Vic Cekvenich Sent: Wednesday, October 06, 2004 2:25 PM To: [EMAIL PROTECTED] Subject: Re: inheritance in tiles yes. josh wrote: Can a tile definition that extends another definition itself be extended again? definition ^ | child definition ^ | grandchild definition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Modifying an object within the form bean?
Dear Mike: Within your Javascript, try to find your drop down by Id or Name. I think the statement looks something like: mySelectBox = document.findElementById(yourIdHere) or mySelectBox = document.findElementByName(yourIdHere) Hope that helps! Wiwit Tjahjana The information transmitted in this Email is for the exclusive use of the person or entity to which it is addressed and may contain confidential information. If you are not the intended recipient of this Email, you are prohibited from reading, printing, duplicating, disseminating or otherwise using this information. If you have received this information in error, please notify the sender at Freddie Mac immediately, delete this information from your computer, and destroy all copies of the information. Mike Elliott [EMAIL PROTECTED] 10/06/2004 03:22 PM Please respond to Struts Users Mailing List [EMAIL PROTECTED]; Please respond to Mike Elliott [EMAIL PROTECTED] To Struts Users Mailing List [EMAIL PROTECTED] cc Subject Modifying an object within the form bean? I have a situation where the form bean contains objects inside it which represent sets of things which will appear in an html:select tag. In particular, the objects have three properties: selected_ndx ndx_set label_set One of these objects is the 'moderator' property of the form bean. The overall design intent was to have an object which could provide the values and labels for an html:select statement and have selected_ndx be the value which is changed via the selection process in the web page. If I write the JSP like this, it works: html:select property=moderator.selected_ndx html:options property=moderator.ndx_set labelProperty=moderator.label_set/ /html:select This generates the following HTML: select name=moderator.selected_ndxoption value=0/option option value=1First Selection/option option value=2Second Selection/option option value=3Third Selection/option/select This successfully displays the selected entity and allows it to be changed via selection through the web page. However, additionally I need to be able to set the value of this select from a popup window. That generally means I need to specify the form element as the target of a javascript assignment. What has worked in similar circumstances in the past is something like opener.document.formBean.selectElementName = newValue where selectElementName is the value of the 'name' attribute from the select element. Here that name is moderator.selected_ndx. That causes a problem. When the javascript runs (from a popup window) the following javascript error occurs: Error: opener.document.formBean.moderator has no properties Which I interpret as the javascript interpreter being able to find the formBean property (which I assume is being furnished by the html:form tag) but that there is no attribute of that called moderator. If I didn't use the dotted notation in the html:select tag, the correct attribute gets created, or whatever, and the javascript works OK. So -- how can I solve this problem? Assuming that the naming is the problem, I've tried introducing a bean like this: bean:define id=mod name=formBean property=moderator/ html:select name=mod property=selected_ndx html:options name=mod property=ndx_set labelName=mod labelProperty=label_set/ /html:select Which generates HTML: select name=selected_ndxoption value=0/option etc. But that causes the select element to be unselectable; that is, while the getter method (getSelected_ndx()) gets invoked, the setter method (setSelected_ndx()) does not, so that changes to the field no longer get propagated back to the form bean. Even if I could get this to work, I'm dubious that I could have multiple select elements working properly in the same form since they would all have the same name attribute (selected_ndx). While I'm unconvinced that the failure to invoke the setter method isn't a bug, I still need to solve the problem through some combination of Struts/JavaScript. Any suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
