I use ISC integrated with Railo (CFML) on Tomcat; in my newest installation, the following error occurs: Umlauts - or, more generally speaking, multi-byte UNICODE chars - fetched from a MySQL DB are no longer displayed correctly in SmartClient widgets ...
This is - of course - a showstopper issue for me !
Therefore, I have done a LONG investigation ! And fortunately I have found out the following rock solid reasons for this showstopper issue:
- On the SmartClient side:
* Using newer versions - currently 'SmartClient_SNAPSHOT_v90d_2012-09-08' - of the two JARs 'isomorphic_core_rpc.jar' and 'isomorphic_sql.jar' causes this issue
* When using older versions from 'SmartClient_SC_SNAPSHOT-2011-09-23', this issue does NOT occur
* I cannot tell You, however, from which version onwards this issue occurs
- On the Railo side:
* A call to
'<cfset getPageContext().getSession().setAttribute("attrName", attrValue) />'
causes this issue
* Obviously, there's something going on which disturbs the J2EE session for newer ISC versions ...
- Setting a session variable in a pure JSP WITHOUT Railo:
* I have done a short test for this like so:
<%@ page language="java" import="java.util.*"%>
<%
request.getSession().setAttribute("attrName", attrValue);
%>
* The showstopper issue does NOT occur
So yes: Unfortunately I could NOT reproduce this showstopper issue with a pure ISC installation; the more grateful I would be if You could shed at least some light on it: Why later versions of those two JARs can behave differently when ISC is integrated into Railo on Tomcat ...
Furthermore, I could make a testcase available which is accessible from a public website !
And: I will post about this showstopper issue into the Railo Google Group, too. Hopefully there will come rescue for this showstopper issue from at least one direction ...
This is - of course - a showstopper issue for me !
Therefore, I have done a LONG investigation ! And fortunately I have found out the following rock solid reasons for this showstopper issue:
- On the SmartClient side:
* Using newer versions - currently 'SmartClient_SNAPSHOT_v90d_2012-09-08' - of the two JARs 'isomorphic_core_rpc.jar' and 'isomorphic_sql.jar' causes this issue
* When using older versions from 'SmartClient_SC_SNAPSHOT-2011-09-23', this issue does NOT occur
* I cannot tell You, however, from which version onwards this issue occurs
- On the Railo side:
* A call to
'<cfset getPageContext().getSession().setAttribute("attrName", attrValue) />'
causes this issue
* Obviously, there's something going on which disturbs the J2EE session for newer ISC versions ...
- Setting a session variable in a pure JSP WITHOUT Railo:
* I have done a short test for this like so:
<%@ page language="java" import="java.util.*"%>
<%
request.getSession().setAttribute("attrName", attrValue);
%>
* The showstopper issue does NOT occur
So yes: Unfortunately I could NOT reproduce this showstopper issue with a pure ISC installation; the more grateful I would be if You could shed at least some light on it: Why later versions of those two JARs can behave differently when ISC is integrated into Railo on Tomcat ...
Furthermore, I could make a testcase available which is accessible from a public website !
And: I will post about this showstopper issue into the Railo Google Group, too. Hopefully there will come rescue for this showstopper issue from at least one direction ...
Comment