gmane.comp.java.xstream.user

change close tags ?

juan pablo — 2008-12-04T01:37:18

hi XStream people :-) First off all, thanks to XStream, this library is really helpful to our project. thanks again. I 'm writing some converts and my xml is: ** 2 8 Test Case Radio Button ** and I need this: * * 2 8 Test Case Radio Button ** the differences is in the close node of OperationEvent. some ideas ? maybe some subString ggrrrrr ... thanks! jp

RE: RE: PropertiesConverter with custom name for property?

Jörg Schaible — 2008-12-03T18:03:40

Hi Henrik, Henrik Dohlmann wrote: yes. No problem, keep asking. In this case you can register your Property converter as local converter (either using the API of the XStream facade or using the annotation). The implicit stuff is a special mode of the reflection based converters. Normally they would pass the marshalling to the converter handling the object kept in the field. For the implicit case they ignore the colleciton converter and handle the elements on their own. - Jörg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

RE: RE: PropertiesConverter with custom name for property?

Henrik Dohlmann — 2008-12-03T16:50:54

If I just register my converter for Properties.class, then all Properties would have to have that format? I might be slow, but could you please explain how I would create the converter so that the following ... ... would be the result of marshalling an instance of this Class: < at >XStreamAlias("data") public class Data { private Properties paths = new Properties(); private Properties properties = new Properties(); public String getProperty(String name) { return properties.getProperty(name); } public String getPath(String name) { return paths.getProperty(name); } ... } Forgive me for being persistant, but I really do not understand how to :-) If the above is not possible, then that would be a nice answer as well. I was misled by the possibility to use < at >XStreamImplicit(itemF

RE: PropertiesConverter with custom name for property?

Jörg Schaible — 2008-12-03T16:17:32

Hi Henrik, Henrik Dohlmann wrote at Mittwoch, 3. Dezember 2008 17:05: it's as Mark explained - you have to write an own converter. The PropertyConverter delivered by XStream is nothing else (and it is not configurable). You may even take a copy of the code and adjust that part. Register it and you're done. - Jörg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

RE: PropertiesConverter with custom name for property?

Henrik Dohlmann — 2008-12-03T16:05:31

Okay, I'll expand a bit on my question :-) Can I configure the PropertiesConverter and tell it that I would like to substitute "path" for "property"? I can see from the code that I can actually already unmarshal the following: And have it stored in a Properties instance: private Properties paths = new Properties(); But, what if I would like to unmarshal this and end with the above format? Do I have to invent a new Class for this and write and new Converter for that Class? Even if I hack a PathPropertiesConverter with a setStartNodeName, I cannot see any way to set this up properly... What I would have hoped for was something like the < at >XStreamImplicit() so that I could write something like: < at >XStreamNodeAlias("path") private Properties paths = new Properties(); Thanks, /Henrik

Re: PropertiesConverter with custom name for property?

Mark Waschkowski — 2008-12-03T15:31:54

You'll need to use a custom converter for custom conversions. http://xstream.codehaus.org/converter-tutorial.html Sparse question, sparse answer ;) On Wed, Dec 3, 2008 at 10:10 AM, Henrik Dohlmann public.gmane.org> wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

PropertiesConverter with custom name for property?

Henrik Dohlmann — 2008-12-03T15:10:04

Is it possible to somehow configure the PropertiesConverter so it is able to parse the following? What I can parse now is the following: Thanks, /Henrik

Re: Re: Re: Issue implementing Serializable interface

Mark Codere — 2008-12-03T14:40:25

Great, that works too. Thanks. On Tue, Dec 2, 2008 at 6:07 PM, Jörg Schaible public.gmane.org> wrote:

Re: Re: How to avoid conversion of quote

Hongyi Jiang — 2008-12-03T10:21:04

I can give you the correct code, which was tested: public String toXML(Object obj) { Writer out = new StringWriter(); HierarchicalStreamWriter writer = new XmlPrintWriter(out, new XmlFriendlyReplacer()); stream.marshal(obj, writer); writer.flush(); return out.toString(); } Regards Hongyi 2008/12/3 Jörg Schaible public.gmane.org>

Re: References between two separate XML's

Jörg Schaible — 2008-12-02T23:30:18

Hi, xjn wrote: Normally no. The object reference stuff is realized by the MarshallingStrategy and it this object is created newly with every call to XStream.toXML() or XStream.marshal(). This prevents concurrency problems though. Nevertheless, there's a "faked" alternative in one of your acceptance tests: com.thoughtworks.acceptance.MultipleObjectsInOneStreamTest.testSupportsOptionToPreserveReferencesAcrossDifferentObjectsInStream() If you look at this implementation, you'll see that it reuses the Marshaller and Unmarshaller created the first time. However, this is a really bad hack, but it demonstrates the principle. What you really should do is to implement a MarshallingStrategy that use a provided the reference map. Feel free to copy the appropriate portions of the code and adjust it. But read on. You might be interested in the SNAPSHOT version of the upcoming 1.3.1 release (see download section). It will provide you a possibility to generate the ids for the objects on your own (these might be no

Re: Re: Issue implementing Serializable interface

Jörg Schaible — 2008-12-02T23:07:25

Hi Mark, Mark Codere wrote: Basically, yes. I cannot say what is normally done in the read/writeObject methods, but they're often simply around to create binary serilazation compatibility with an older version of the class. If that's the only reason, you can also use the ReflectionConverter, because it will set the values of the class "the hard way". If the unmarshalled object is properly initialized (ensure with some kind of equals method), it's fine. Short form: xstream.registerConverter(new ReflectionConverter(xstream.getMapper(), xstream.getReflectionProvider()){ boolean canConvert(Class type) { return type == Request.class; } }); Cheers, Jörg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: How to avoid conversion of quote

Jörg Schaible — 2008-12-02T23:00:52

Hi, TouDick wrote: You will have to overwrite the writeText method of the PrettyPrintWriter: xstream.marshal(object, new PrettyPrintWriter(out) { protected void writeText(QuickWriter writer, String text) { // write any text you like to the writer ... keep care that its valid XML ... } }); - Jörg --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: modification done to XStream 1.3 and enhancement request

Jörg Schaible — 2008-12-02T22:57:51

Hi Alex, Alex Shields wrote: Well, I see that you did some digging of yourself and found a solution, that's great. However, you also might have asked a question here ;-) It is by design that a converter marshals the value, but does nothing know about it usage i.e. it does not take care wether its value is written within a tag or an attribute or if it is not called at all, since somebody else identified that the marshalled object has already been written. The complete object reference stuff is handled by the MarshallingStrategy (as you have found out). Bascially you could have used a simple TreeMarshallingStrategy (calling xstream.setMode(XSTREAM.NO_REFERENCES)) that does know nothing about references at all. Or - if you use references for different objects - you could have called xstream.addImmutableType(Person.class) to configure XStream to write a Person instance always. For more complicated referencing algorithms you could have implemented an own MarshallingStrategy. For now I see no need to add a m

Re: Conversion Exception

Jörg Schaible — 2008-12-02T22:36:18

Hi Lucas, Lucas Eskopinski wrote: actually you cannot. Main point is that a converter is only responsible for the content of the tag, but not for the tag itself. While you can write a converter for integers that can unmarshal an empty string to 0, it is not possible the other way round, since your converter is never called for null values. This is how the ReflectionConverter represents "null" (as explained it is his responsibility here). Therefore you will have to write a converter for you class Segurado. A simple call to the writer's startNode/endNode methods will create the empty tag. - Jörg < at >Mark: Thanks for helping out, it is really appreciated! --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

References between two separate XML's

xjn — 2008-12-02T17:39:42

Hi, from the docs and samples it seems that references are only possible in one XML, but not cross-XML. Is there a way to have references between two separate XML's ? For example, i have two classes Reference and Entity : < at >XStreamAlias("reference") public class Reference { public String id; ... } < at >XStreamAlias("entity") public class Entity { public String id; public Reference reference; ... } I need to serialize object instances to separate XML-Files. I cannot use a single object-graph. < at >Test public void testEntityWithReference() { ... // setup im memory Reference ref = new Reference("ref"); Entity entity = new Entity("entity"); entity.reference = ref; assertSame(ref, entity.reference); // write to directory Map writeMap = new XmlMap(new FileStreamStrategy(directory_, xstream_)); writeMap.put(ref.getId(), ref); writeMap.put(entity.getId(), entity); // read from directory Map readMap = new XmlMap(new

Re: Re: Issue implementing Serializable interface

Mark Codere — 2008-12-02T16:39:37

Hi Jörg, Thanks for your response. I have a workaround that seems to work, however, I want to run it by you to make sure it's a suitable workaround. public class Request extends (some object that implements Serializable and contains a readObject() and writeObject()) { public class RequestConverter extends AbstractReflectionConverter { ...all super calls - no new logic } } xstream.registerConverter(new RequestConverter(xstream.getMapper(), xstream.getReflectionProvider())); Will this be ok? Thanks, Mark On Mon, Dec 1, 2008 at 3:50 PM, Jörg Schaible public.gmane.org> wrote:

How to avoid conversion of quote

TouDick — 2008-12-02T15:14:17

Hi, I have problem with converting quotes, what I can't do in my target XML. My class: class A { String B = "\"VALUE\""; } Target XML should look like: "VALUE" but now I get "VALUE" How can I avoid of conversion " to "? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

modification done to XStream 1.3 and enhancement request

Alex Shields — 2008-12-02T14:21:32

Hi. This is Alex Shields. This email is to inform you (as requested by my boss) of a change I made to the code for XStream 1.3 and a request to the developers of XStream to make some similar change to the code permanent. Problem: We want objects to not be referred to with the xpath notation like so: "../../..". Instead, we want some objects to have an id reference that may have come from a database, for example. Basically, we want to run our Converter class methods _before_ the check that an object is already one of the parents of the current object. So it'll bypass the part in the code where the xpath references are written. Scenario (the code below is modified for brevity): 1. We have a class called Person. It looks like this: class Person { < at >XStreamConverter(SimplePersonConverter.class) public Person father; < at >XStreamConverter(SimplePersonConverter.class) public Person mother; public Family family; public String firstName; } 2. We have a Family class: class Family { < at >XStreamConverte

Re: Conversion Exception

Mark Waschkowski — 2008-12-02T02:23:06

Hi, I would assign reader.getValue to a variable, and you don't have to write an xml element without a value, shouldn't be needed. Regards, Mark On Mon, Dec 1, 2008 at 8:27 PM, Lucas Eskopinski public.gmane.org> wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: Conversion Exception

Lucas Eskopinski — 2008-12-02T01:27:37

Hi, I created a class "IntegerConverter implements Converter" with the method: < at >Override public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext arg1) { System.out.println("unmarshal!"); if ((reader.getValue() != null) && (!reader.getValue().equals(""))) { return Integer.parseInt(reader.getValue()); } else { return null; } } how could I write marshal method for writing the attribute without value? < at >Override public void marshal(Object obj, HierarchicalStreamWriter writer, MarshallingContext context) { //???? } Thanks. Lucas Vargas Eskopinski. Mark Waschkowski wrote:

Re: Conversion Exception

Mark Waschkowski — 2008-12-02T00:42:29

OK, if you have special needs, then you will have to create a custom converter, see: http://xstream.codehaus.org/converter-tutorial.html Its fairly straightforward, and when you are unmarshalling you can just write some code to ignore empty strings. Cheers, Mark On Mon, Dec 1, 2008 at 5:44 PM, Lucas Eskopinski public.gmane.org> wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email