Hi experts,
I'm facing yet another interesting migration issue.
Some values of the coloms used for CMP EJBs entity mappings have umlauts.
Using the (3rd party app) on GF 2.1.1 on the SAME machine with the
SAME runtime user against the SAME database (Oracle 11g) shows correct
encoded data.
However using the app on GF 3.1.1 results in wrong encoded data.
It seems to be related to CMP implementation of GF 3.1.1 ... could
this be the case?
I've already used 'capture schema' of GF 3.1.1 to include it within
the app, referenced by the schema element in sun-cmp-mappings.xml.
How could I track down the issue?
Increasing jdo-logger verbosity does not really help.
TIA,
Bernhard
--
IT-Consulting Bernhard Thalmayr
- Painstaking Minds -
83620 Vagen (Munich area)
Germany