etf
|
Posted: September 09, 2009 20:55 by etf
|
|
Current implementation (from the SAF HEAD) has a number of obvious flaws. It\s less flexible than the original one. http://kenai.com/jira/browse/BSAF-21 |
Reverting to original implementation of the PersistenceStorage.
3 posts
Replies: 2 - Last Post: October 05, 2009 14:38
by: Anonymous User
by: Anonymous User
showing 1 - 3 of 3
Anonymous User
|
Posted: October 05, 2009 14:38 by Anonymous User
|
|
Yes agree with Vity. XmlEncode should do this work! Although other lightweight solutions like xvantage could do it also (in some weeks  ). ..
|
Vity
|
Posted: September 10, 2009 19:26 by Vity
|
|
pros for XMLEncoder - why not to use properties - using properties is some proprietary pseudo-serializing of data - it's almost impossible to store complex data structures, like hashmap or lists - it's easy to make mistake when writing code with +"x" or "y" etc.. you probably know what I mean - properties are breaking compatibility with existing applications based on 1.0.1 cons for XMLEncoder - why to use properties - a bit slower - backward incompatible changes in JDK 7 - see my report http://forums.java.net/jive/thread.jspa?threadID=66054&tstart=0 |
Replies: 2 - Last Post: October 05, 2009 14:38
by: Anonymous User
by: Anonymous User
