Hi Polly,
I've checked a fix for this issue into the EclipseLink
1.1 stream. The bug I have opened to track this issue is 315786.
--Dave
polly.c.chang wrote:
Hi Blaise,
Thanks for the quick response! We are nearing completion on our
development, but we should have just enough time to pick up your 1.1.4
release. How soon will that be available? The next couple of days? Also,
can you point me to a list of bugs that have been fixed for 1.1.3 and 1.1.4?
Thanks!
Polly
Blaise Doughan wrote:
Hi Polly,
Yes that is a bug. You could get around it with a converter, but we
should be able to supply you with a path for this quickly. Once we have
the patch ready, are you able to uptake the EclipseLink 1.1.4 stream.
-Blaise
polly.c.chang wrote:
Hi,
Sometimes we have String data that contains special characters like
double-quotes. When we marshal this String, the double-quotes are
rendered
as-is. This results in invalid XML. For example, notice the
double-quotes
around the word "quoted" below:
<?xml version="1.0" encoding="UTF-8"?>
<Foo documentation="A "quoted" value that creates invalid xml.">
...
</Foo>
Then of course when we try to use MOXy to unmarshal the invalid XML, we
get
an exception. We have tested both XML attributes and text() nodes. Both
have the same marshalling behavior. Does EclipseLink automatically
escape
special characters? Or do we need to write a Converter to do this?
We are using EclipseLink 1.1.2 if it makes any difference.
Thanks!
Polly
_______________________________________________
eclipselink-users mailing list
--
David McCann | Principal Software Engineer | +6132884636
Oracle Server Technologies, EclipseLink
Product
ORACLE Canada | 45 O'Connor St., Suite 400 | Ottawa, Ontario | K1P 1A4
 |
Oracle is committed to developing practices and
products that help protect the environment |
|
