Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.1
-
Fix Version/s: 1.4.6
-
Component/s: Converters
-
Labels:None
Description
I've been using this for a month now, and I am happy with it. Joe does not like it though, he suggests there is potential for race.
As suggested, I will try more permutations to register a PureJavaReflectionProvider exclusively & report back.
-
- faster_safer.patch
- 10 kB
- Paul Hammant
-
- gae3-xstream.patch
- 4 kB
- Sean Sullivan
-
- gae4-xstream.patch
- 4 kB
- DEWITTE Pierre-Alban
-
- gae-xstream.patch
- 12 kB
- Paul Hammant
-
- gae-xstream2.patch
- 9 kB
- Paul Hammant
-
Hide
- xstream_src.zip
- 16 kB
- Galoch
-
- xstream_src/AppEngineXStream.java 2 kB
- xstream_src/HarmonyReflectionProvider.java 5 kB
- xstream_src/JVM.java 10 kB
- xstream_src/XStream.java 71 kB
-
Hide
- xstreamGae.jar
- 853 kB
- Galoch
-
- META-INF/MANIFEST.MF 0.0 kB
- com/thoughtworks/.../XStreamException.class 1 kB
- com/thoughtworks/xstream/XStream$1.class 2 kB
- com/thoughtworks/xstream/XStream$2.class 2 kB
- com/.../XStream$InitializationException.class 0.7 kB
- com/thoughtworks/xstream/XStream.class 33 kB
- com/thoughtworks/.../AppEngineXStream.class 2 kB
- com/thoughtworks/xstream/XStreamer.class 3 kB
- com/.../MarshallingStrategy.class 0.6 kB
- com/.../InitializationException.class 0.7 kB
- com/thoughtworks/.../XStreamConverter.class 0.6 kB
- com/.../AnnotationProvider.class 1.0 kB
- com/thoughtworks/.../XStreamOmitField.class 0.4 kB
- com/.../XStreamAsAttribute.class 0.5 kB
- com/thoughtworks/.../XStreamImplicit.class 0.5 kB
- com/thoughtworks/.../XStreamConverters.class 0.5 kB
- com/.../XStreamImplicitCollection.class 0.5 kB
- com/.../AnnotationReflectionConverter.class 6 kB
- com/.../XStreamContainedType.class 0.5 kB
- com/thoughtworks/.../XStreamInclude.class 0.5 kB
- com/thoughtworks/.../XStreamAlias.class 0.6 kB
- com/thoughtworks/.../Annotations.class 0.8 kB
- com/.../MarshallingContext.class 0.3 kB
- com/thoughtworks/.../ConverterRegistry.class 0.2 kB
- com/.../ConversionException.class 4 kB
- com/.../SingleValueConverterWrapper.class 2 kB
- com/thoughtworks/.../ErrorWriter.class 0.3 kB
- com/.../SingleValueConverter.class 0.3 kB
- com/thoughtworks/.../ConverterLookup.class 0.2 kB
- com/.../UnmarshallingContext.class 0.5 kB
Issue Links
Activity
@Ferran Maylinch
Short answer: you can't use xstream in the client side of GWT.
Longer answer: GWT can't emulate java reflection on the client side (see http://code.google.com/intl/en-EN/webtoolkit/doc/latest/DevGuideCodingBasicsCompatibility.html and http://code.google.com/intl/en-EN/webtoolkit/doc/latest/RefJreEmulation.html ) so you won't be able to make Xstream work.
Also: this isn't the place to ask for such questions, they're completely unrelated to this Xstream issue and there are better places to do it (such as the gwt users google group or even the xstream forum)
Hope that helps
Paul, can you give this a try with the latest snapshot?
Version in trunk should no longer fail for the identified converters at registration time.
GAE restriction works differently than thought. Issue is unfortunately still not fixed.
XStream converters try now to ensure already in the canConvert methods that they can handle the requested type in practice and not only theoretically. Additionally the implementations even better take care, that the initialization of a converter will not break the setup of XStream itself.
Paul, I think this was the wrong patch. IMHO the second one, you've sent to the list makes this one obsolete anyway.