Hi Adi,
adimaron wrote:
>
> Thanks for you reply.
> The full stack was as follows:
[snip]
> Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException:
> edu.tau.compbio.io.IOMgr-Constraints
> at
>
com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:56)
[snip]
As already seen here:
> Details: com.thoughtworks.xstream.converters.ConversionException: Could
> not call edu.tau.compbio.util.OrderedHash.readObject() :
> edu.tau.compbio.io.IOMgr-Constraints
> ---- Debugging information ----
> message : Could not call
> edu.tau.compbio.util.OrderedHash.readObject()
> cause-exception :
> com.thoughtworks.xstream.mapper.CannotResolveClassException
> cause-message : edu.tau.compbio.io.IOMgr-Constraints
[snip]
> The IOMgr is my class and it uses OrderedHash which is also my class.
> Will it help if I put the code?
It does not complain about "edu.tau.compbio.io.IOMgr", it complains about a
type "edu.tau.compbio.io.IOMgr-Contraint". Seems to be an inner class.
> When I tried adding the code from the compatibility link that you
> suggested to support 1.1 objects
> Which is initializing xstream as follows:
>
> XStream xstream = new XStream(new XppDriver(new
> XStream11XmlFriendlyReplacer())) {
> protected boolean useXStream11XmlFriendlyMapper() {
> return true;
> }
> };
>
>
> I got a whole different exception:
> java.lang.IndexOutOfBoundsException: only START_TAG can have attributes
> at org.xmlpull.mxp1.MXParser.getAttributeValue(MXParser.java:1005)
> at
> com.thoughtworks.xstream.io.xml.XppReader.getAttribute(XppReader.java:139)
> at
>
com.thoughtworks.xstream.io.ReaderWrapper.getAttribute(ReaderWrapper.java:52)
> at
>
com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.instantiateNewInstance(AbstractReflectionConverter.java:421)
> at
>
com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:233)
> at
>
expander.io.converters.EnrichmentSolConverter.unmarshal(EnrichmentSolConverter.java:72)
What does this method? It seems to corrupt the state of the parser. To me it
looks as if you run now in the next problem, but the type from above can be
resolved now.
[snip]
- Jörg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
