You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/01/25 13:25:04 UTC
[jira] Resolved: (WW-2343) radio tag is missing labelSeparator
attribute support
[ https://issues.apache.org/struts/browse/WW-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown resolved WW-2343.
---------------------------
Resolution: Fixed
Assignee: Don Brown
I've confirmed this is working on 2.1.1 with a unit test. Note that any labelSeparator values will be escaped, so your nice <br/> tag will turn into <br/> If you want a way to use unescaped tags, please open a new improvement ticket.
> radio tag is missing labelSeparator attribute support
> -----------------------------------------------------
>
> Key: WW-2343
> URL: https://issues.apache.org/struts/browse/WW-2343
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Tags
> Affects Versions: 2.0.11
> Environment: Windows XP
> Reporter: Jim Cornelius
> Assignee: Don Brown
> Fix For: 2.1.1
>
>
> The 2.0.11 documentation http://struts.apache.org/2.0.11/docs/radio.html states that the radio tag supports the labelSeparator attribute. However, the struts-tags.tld does not include this attribute and I receive an error at runtime stating the labelSeparator is not supported.
> weblogic.servlet.jsp.CompilationException: Failed to compile JSP /test.jsp
> test.jsp:21:49: This attribute is not recognized.
> <s:radio name="myAttr" labelSeparator="<br/>" list="myMap" value="app.myAttr"/>
> ^------------^
> at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:294)
> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:200)
> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:164)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
> at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:391)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:309)
> at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
> at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:500)
> at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
> at org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletDispatcherResult.java:139)
> at org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:178)
> at com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:348)
> at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:253)
> at org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:50)
> at org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:504)
> at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:419)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
> at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
> at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
> at com.wellsfargo.fmg.fame.client.servlet.BasePageFilter.doFilter(BasePageFilter.java:29)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
> at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
> at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.