[ http://issues.apache.org/jira/browse/MYFACES-702?page=comments#action_12361332 ]
Henrik Bentel commented on MYFACES-702: --------------------------------------- I discovered one thing in my case. The Id's of all the components are "automagically" prefixed with the name of the portlet. So unless the ID is manually set, the ID's generated in my case look like this: "_reporting__id0","_reporting__id1","_reporting__id2", where "reporting" is the name of the portlet. DOn't know what or who generates the IDs yet. In the case of verbatim tags there is no way of specifying an ID so span is injected regardless. -Henrik > 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
