Your format definition says this serializer/deserializer works with
String values (converts Strings to other Strings, in other words), but
you're actually converting Date values. Because of this JiBX is looking
for methods with the signatures String serializerDate(String date) and
String
How are you configuring your output, and what actual byte values are
written to the output document?
- Dennis
Bao Trang wrote:
In my Java application, I am inserting unicode greek letters into some
of my fields. When I try to marshall to XML, the output is a question
mark ('?') for each
You need to turn off forward reference support to do this, I think. Try
forward=false on your binding element. Of course, that assumes that
you really aren't using forward references in your document. See my
email from earlier today Re: Using IDs for some more discussion of
this issue.
-
I suspect your timer jar includes the data classes that are used by the
binding, since it would need these classes in order to communicate with
the EJBs. It sounds like Weblogic plays some games with the classloading
for the timer and gets the class files from different places depending
on
Here is my marshalling/unmarshalling code. I think what is actually
written out is a question mark for each character. Do you mean what
do I see if I read the file with a hex reader? '3F' for each
character.
public void saveAs(File aFile) {
try {
IBindingFactory bfact =
Your problem is probably due to using a FileWriter without specifying
the encoding to the writer. The FileWriter is what actually converts the
characters to bytes, and it will use the default encoding for your
system. What you probably need to do is use a FileOutputStream instead,
in which
thanks Dennis.
On Sat, 23 Oct 2004 19:14:04 -0700, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Your problem is probably due to using a FileWriter without specifying
the encoding to the writer. The FileWriter is what actually converts the
characters to bytes, and it will use the default encoding
