[ http://issues.apache.org/jira/browse/MYFACES-702?page=comments#action_12356577 ]
Greg Hester commented on MYFACES-702: ------------------------------------- I re-read the initial comment and noticed the note about the id starting with "_id". I changed all of my <h:outputText> tags which are generating URLs to contain id attributes starting with "_id" and that fixed my problem. So, I have a workaround but don't think that the format of an id attribute value should have such an impact. I'll look at the source with my team to see if we can offer a suggestion for a fix. BTW: I would rather use <h:outputLink> but it seems to only allow absolute urls and I have relative urls. Have I missed the boat on this? > outputText generates wrapped span element in a portal > ----------------------------------------------------- > > Key: MYFACES-702 > URL: http://issues.apache.org/jira/browse/MYFACES-702 > Project: MyFaces > Type: Bug > Components: Implementation > Versions: 1.1.0 > Reporter: Gavin Cornwell > > We have a JSF app that runs as a portlet and normal webapp. > In the webapp the <h:outputText value="some text"/> appears as I would expect > (i.e. just the text) however the same thing in the portlet gets rendered as: > <span id="form-id:handleMetaDataEvent_id36">some text</span> > This becomes a problem when you are trying to use outputText to render part > of a URL or to become a JavaScript string as the output includes the span > element! > Looking at the renderer code for outputText it appears the span gets > generated when the id does not start with "_id", so the question is where has > the "handleMetaDataEvent" prefix for the id come from? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
