I actually fixed this...It was a bug.
On 11/17/05, Ture Hoefner <[EMAIL PROTECTED]> wrote: > > FYI, I worked around this by intercepting my databound > Map<String,String> before forwarding to my JSP page. I added an entry > with the empty String as a key - "" for my "null" option. My Map, a > LinkedHashMap, allows null keys, but when I tried using a null key for > my "null" option the <netui:select> tag seemed to ignore it and did not > add an option for it. Once I changed the key to "" it worked OK. > > So...I'm happily using the netui:select tag and moving on now...just > thought you may be able to use some of this info in case there are some > bugs. > > Thanks. > > ------------------- > Ture Hoefner > WebLogic Portal Engineering > BEA Systems, Inc. > > > -----Original Message----- > From: Ture Hoefner > Sent: Thursday, November 17, 2005 10:45 AM > To: 'Beehive Users' > Subject: RE: netui:select tag - defaultValue and nullable attributes > clash? > > Yes, the option that I wanted to set as default it still in the list. > The only problem is that the "selected" attribute seems to stick to the > option with the value="netui_null" > > BTW, the sample <netui:select> and generated HTML I pasted below were > edited by hand to simplify the example by removing a bunch of the other > options that are not necessary and I got rid of the EL used to get the > nullableOptionText. (but I forgot to change the generated value of the > nullableOptionText from "<none>" to "none" so it looks a little > weird the way it is in my sample) > > > ------------------- > Ture Hoefner > WebLogic Portal Engineering > BEA Systems, Inc. > > > -----Original Message----- > From: Daryl Olander [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 17, 2005 10:37 AM > To: Beehive Users > Subject: Re: netui:select tag - defaultValue and nullable attributes > clash? > > Ture, when you say stops working do you mean that it stops being the > selected option? It's still in the list correct? > > On 11/17/05, Ture Hoefner <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I can successfully use the netui:select JSP tag while databinding to a > > Map in my pageflow. I am successfully using the defaultValue > attribute, > > which is set equal to the key of some desired item in the databound > Map. > > > > Here is the problem: when I add the nullable and nullableOptionText > > attributes, the defaultValue stops working and the null option is > always > > the selected one: > > > > > > > > <netui:select dataSource="actionForm.type" > > > > tagId="updateNameAndTypeDialog_contentTypes" > > > > optionsDataSource="${pageFlow.availableTypes}" > > > > defaultValue="/Tools_Repository/1" > > > > nullable="true" > > > > nullableOptionText="none" > > > > size="8" /> > > > > > > > > generates: > > > > > > > > <select > name="contentNodeSummaryPortletwlw-select_key:{actionForm.type}" > > id="n0.updateNameAndTypeDialog_contentTypes" size="8"> > > > > <option value="/Tools_Repository/1">ad</option> > > > > <option value="/Tools_Repository/2">ad_shockwave</option> > > > > <option value="/Tools_Repository/3">article</option> > > > > <option value="netui_null" selected><none></option></select> > > > > > > > > I don't see this when I search JIRA, maybe I am doing something goofy? > > By the way, is there some reason that we don't have a nullableTop > > attribute to make the null option appear at the top of the list > instead > > of the bottom? > > > > > > > > I will try working around this by modifying my Map to contain an empty > > option. > > > > > > > > Thanks, > > > > Ture > > > > > > > >
