Fwd: xml content with Tab special characters in view source
Hi, We observed that in Trinidad 1.2 and 2.x appends the Tab Special Charecters ( #9;) for the xml content on the JSF page. With this behavior we observed xml parsing issues as this not able to find the nodes in this xml document. The same behavior not seen in Trinidad 1.0. Our application event mechanism is fully dependent on xml dataislands as shown below. So could you please let us know is this a bug in the new releases. If so what could be your recommendations for these situations. Also need to mention that the same xml is aligned with the space bar instead Tab the special characters not seen in the view source. #9;#9;#9;#9;#9;xml id=welcomePage2 ondatasetcomplete=top.advisorDesktop.eventManager.registerEvents(this, window); #9;#9;#9;#9;#9;#9;#9;events #9;#9;#9;#9;#9;#9;#9;#9;#9;registerevent #9;#9;#9;#9;#9;#9;#9;#9;#9;#9;eventnamestatusRefresh/eventname #9;#9;#9;#9;#9;#9;#9;#9;#9;#9;eventhandlerfunction refreshStatusBar/eventhandlerfunction #9;#9;#9;#9;#9;#9;#9;#9;#9;/registerevent #9;#9;#9;#9;#9;#9;#9;/events #9;#9;#9;#9;#9;/xml Thanks Suresh Babu S
Issue with tr:inputDate tag in Edit Mode
Hi Team, I had an issue with tr:inputDate tag with trinidad-impl-2.0.1.jar and trinidad-api-2.0.1.jar. We have a page where we have the tr:inputDate components for to select Date on the page. This works fine as expected. But when we go for editing the page which already has the Date, and try to change the date the page hungs and it didn't allow to do anything on the page. And observed a JS error on the console. SCRIPT5007: The value of the property '_getLocaleTimeZoneDifference' is null or undefined, not a Function object Common2_0_0_beta_2.js, line 139 character 1 But, the functionality works when i keep the below conext param in web.xml context-param param-nameorg.apache.myfaces.trinidad.CHANGE_PERSISTENCE /param-name param-valuesession/param-value /context-param I don't understand the relation between the tr:inputDate and the CHANGE_PERSISTENCE context param. The same behaviour/scenario works fine with JSF1.2 Jars without the CHANGE_PERSISTENCE context param. So, Please suggest any resolution for this issue. Thanks Suresh Babu S
