Your BEA man is correct. b.t.w., using single quotes IS valid syntax, but only if it's consistent within the tag:
valid: <bean:write name='cer' property='<%= "cerNbr" %>' /> not valid: <bean:write name="cer" property='<%= "cerNbr" %>' /> You also cannot do this in most containers: <bean:write name="cer" property='ConcatHTMLLiteralWithJSPExpression<%= "cerNbr" %>' /> Also, in your initial post, I thought that you had mentioned that the tag/scriplet combination below did NOT work as well for the <html:radio> tag, which doesn't have the nested double quotes as does the above example: <logic:iterate id="cer" name="cers" type="com.fedex.ess.site.entity.CER"> <html:radio property="shipper" value="<%= cer.getCerNbr() %>" /> CER: <bean:write name="cer" property="cerNbr"/> </logic:iterate> Is this issue resolved as well? peace, Joe -----Original Message----- From: Austin Lowry [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 15, 2002 1:32 PM To: Struts Users Mailing List Subject: Re: radio button with scriptlet does not render Thanks to BEA support I finally found the answer. The tech guy said that tags and scriptlets seem to have a problem with double quotes. He said that he has seen the problem in more containers than Weblogic. The answer is to use single quotes before and after the scriptlet, while using double quotes inside the scriptlet. So, where I used: <bean:write name="cer" property="<%= "cerNbr" %>" /> I now use: <bean:write name="cer" property='<%= "cerNbr" %>' /> This doesn't seem quite right since I don't think double quotes are valid XML syntax, but this works and gets me going. Thanks for everyone's help ~Austin Lowry Cliff Rowley wrote: >Very odd, what application server are you using? And what version? >Perhaps it may be an idea to crawl through the bug list (if available) >for your server and see what comes up. > >On Thu, 2002-08-15 at 18:05, Austin Lowry wrote: > > >>I apparently get the same problem any time I try to use a scriptlet >>inside of a custom tag. The custom tag gets sent as HTML with the proper >>data inserted from my scriptlet. So if I did somthing like: >> >><td> >> CER Number: <bean:write name="cer" property="<%= "cerNbr" %>" /> >></td> >> >>the HTML would look like: >><td> >> CER Number: <bean:write name="cer" property="cerNbr" /> >></td> >> >>Any ideas how to get the scriptlet code to evaluate before the tag code?? >> >>Thanks. >> >>Austin Lowry wrote: >> >> >> >>>I thought I had solved my problem with radio buttons and scriptlets, >>>but apparently not quite. >>> >>>What is happening now is that if I include a scriptlet to populate the >>>value attribute of a radio tag, the scriptlet is run and prints the >>>proper data, but the radio button itself is not rendered and appears >>>in the html the same way it is in the jsp, but with the proper value >>>statement. >>> >>>JSP code: >>><logic:iterate id="cer" name="cers" type="com.fedex.ess.site.entity.CER"> >>><html:radio property="shipper" value="<%= cer.getCerNbr() %>" /> >>>CER: <bean:write name="cer" property="cerNbr"/> >>></logic:iterate> >>> >>>Everything is right in the resulting HTML, except that instead of an >>>HTML radio tag, I get this: >>><html:radio property="shipper" value="3345043516" /> >>> >>>If I do not include the scriptlet and just set the value attribute to >>>somthing random like value="1", the radio button renders as expected. >>> >>>Any ideas? Thanks in advance for your help. >>> >>>~Austin Lowry >>> >>> >>> >>>-- >>>To unsubscribe, e-mail: >>><mailto:[EMAIL PROTECTED]> >>>For additional commands, e-mail: >>><mailto:[EMAIL PROTECTED]> >>> >>> >>> >>-- >>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> >> >> >> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
