Eclipse Issue with UX Studio / Demandware PIpeline Debugger Cannot Initialize TreeMapConverter

[Dominic Caballero]

Hello 

    I am unable to create an debugger in eclipse. I am getting an error that says it cannot inialize TreeMapConverter. What can I do to resolve this issue?

[Jörg Schaible]

Hi,

What has XStream to do with an debugger in Eclipse?

Regards,
Jörg

[Dominic Caballero]

I do not know.  It is giving me this errors for UX Studio Pipeline Degugger when I try to select a site on my SFCC sandbox.

--
You received this message because you are subscribed to the Google Groups "XStream User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xstream-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xstream-user/2682052.JkK7atc5sO%40floh.

--

Dom Caballero

[Jörg Schaible]

Hi

On Tuesday, 25. November 2021, 23:03:17 CET Dominic Caballero wrote:
> I do not know. It is giving me this errors for UX Studio Pipeline Degugger
> when I try to select a site on my SFCC sandbox.

And "UX Studio Pipeline Degugger" or "SFCC sandbox" don't tell me anything.

Regards,
Jörg

[Dominic Caballero]

When I create a pipeline debugger in eclipse and try to select a site this error shows up in eclipse.  Here is a reference on how I create a pipeline debugger: 

https://documentation.b2c.commercecloud.salesforce.com/DOC3/index.jsp?topic=%2Fcom.demandware.dochelp%2FLegacyDevDoc%2FDebugging.html

Step 6 is where I get this error.

To view this discussion on the web visit https://groups.google.com/d/msgid/xstream-user/5415719.e0kSNy7j67%40floh.

--

Dom Caballero

[Jörg Schaible]

Hi

On Friday, 26. November 2021, 01:28:37 CET Dominic Caballero wrote:
> When I create a pipeline debugger in eclipse and try to select a site this
> error shows up in eclipse. Here is a reference on how I create a pipeline
> debugger:
> https://documentation.b2c.commercecloud.salesforce.com/DOC3/index.jsp?topic=

> %2Fcom.demandware.dochelp%2FLegacyDevDoc%2FDebugging.html Step 6 is where I
> get this error.

Well, XStream is a library to marshal Java objects to XML and back. It is
heavily based on reflection and has therefore to run in the classpath, it will
fail currently in the module path. I am not involved in any development of
Salesforce, you will have to ask there, what they do with XStream.

Regards,
Jörg

[Dominic Caballero]

Thanks. After your last message.  I think I should have asked them before XStream, which I already did. Thanks for telling me what Xstrem does. 

--
You received this message because you are subscribed to the Google Groups "XStream User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xstream-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/xstream-user/2177830.MoNKp5zXxS%40floh.

--

Dom Caballero

[Elias David]

Hi,

I am using XStream over JAXB and have been succesfully for a while, however I recently discovered an exception that was being gobbled. 

I am doing with Redis.

Normally, I would serializeToBytes myself, and then I can deserializeFromBytes eventually.

However, in this particular instance, I can also receive bytes from Redis that I myself have not serialized with XStream.

This is causing issues, particularly this:

The logic used:

My XStream instance setup:

XStream seems to only be able to deserialize objects from byte[] that itself have generated which is fine most of the time.

But here, it is the the event bus, which at times, I may push messages on to, and I might also get events from Redis which are plain Strings as byte[].

Is there a way to have XStream return the right object when it detects that is not its own object, and in this case a byte[] representing a String or a primitive?

I know it might be asking for too much, but Ideally this type of exception could be handled if configurable to do so?

// Elias

[Elias David]

More particularly, the code that is not (!!!) overridable is in Token.Java:

[Jörg Schaible]

Hi Elias,

this does not make sense to me. The binary driver uses an internal binary
protocol to marshal/unmarshal the object graph.

So what should happen, if suddenly some arbitrary bytes are mixed into this
stream at deserialization time? How many of them? What happens, if those
arbitrary bytes start by accident with one of the tokens?

Regards,
Jörg

Am Sonntag, 12. Dezember 2021, 10:11:12 CET schrieb Elias David:
> More particularly, the code that is not (!!!) overridable is in

> *Token.Java*:

>
> On 12/12/21 10:06, Elias David wrote:
> > Hi,
> >
> > I am using XStream over JAXB and have been succesfully for a while,
> > however I recently discovered an exception that was being gobbled.
> >
> > I am doing with Redis.
> >
> > Normally, I would serializeToBytes myself, and then I can
> > deserializeFromBytes eventually.
> >
> > However, in this particular instance, I can also receive bytes from
> > Redis that I myself have not serialized with XStream.
> >
> > This is causing issues, particularly this:
> >
> >

> > The logic used:
> >
> >
> > My XStream instance setup:

> >
> >
> > XStream seems to only be able to deserialize objects from byte[] that
> > itself have generated which is fine most of the time.
> >
> > But here, it is the the event bus, which at times, I may push messages
> > on to, and I might also get events from Redis which are plain Strings
> > as byte[].
> >

> > *Is there a way to have XStream *return the right object when it