I had a problem a while back with the JiBX marshaller/unmarshaller. It
seems that one certain locked down machines running Windows XP, the
unmarshaller did not work properly, and the result was a truncated output
xml file. This was due to the way JiBX was handling optional elements. I'm
not really sure what the problem was, but I think it had to do with JiBX not
instantiating the optional elements when the object was initially
marshalled, even though the constructor explicitly instantiated the optional
objects.
The main problem was that I never experienced this problem in my testing.
In fact, I could not even duplicate the problem. It only came to my
attention because some of my users, who were in very secure environments,
could not open their application data all of a sudden, because their data
was corrupt. I tried to make a limited user account on my xp machine but I
still could not duplicate the environment they were in that caused the
error. Eventually I was able to create a workaround, but not before I got
into some hot water. I'm still a bit concerned that my workaround might
break in the future.
Now I think this is a huge problem, JiBX acting one way in normal settings,
and another way in locked down environments. Has anyone else experienced
similar problems and has this ever been addressed?
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
