Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349811

Summary:	XmlSerializationUtils.deserialize(String) doesn't work
Product:	z_Archived	Reporter:	thomas menzel <tmenzel>
Component:	Smila	Assignee:	Peter Wissel <pfreytag>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description thomas menzel

2011-06-20 09:01:17 EDT

the root problem is that the .(de)serialize(byte[]) introduces another wrapper object that is part of the serialized bytes[] and expect that also to be there when deserializing.

this has the effect the a serialize2string() cant be fed into desrialize(String) which makes no sense at all...

Comment 1 thomas menzel

2011-06-20 09:41:48 EDT

so far i have impel'ed a simple workaround that doesnt cover the attachments.

imo the API should look and behave like this:
- by default attachments are not serialized/deserialized - we still put their names in as it is now the case when using searialize2string()
- there are overloads to also do this with attachments. in that case they are contained as base64 with in the XML. i know this is verbose but this makes most sense and what users would expect.

for internal use we could also provide the better performing serialization that is in place ATM (rev 1128).

Comment 2 Igor Novakovic

2011-07-01 04:14:21 EDT

Since Thomas provided the workaround I reduced the severity to minor.

Comment 3 Andreas Weber

2014-11-11 04:56:48 EST

set to WONTFIX cause workaround seems to be sufficient.

Comment 4 Andreas Weber

2015-03-19 06:59:27 EDT

closed