Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISPN-3498 Cannot construct org.infinispan.util.KeyValuePair as it does n... #2247

Closed

Conversation

mmarkus
Copy link
Contributor

@mmarkus mmarkus commented Nov 29, 2013

https://issues.jboss.org/browse/ISPN-3498

  • xstream-based serialization doesn't work nicely with azul. I've used an shared instance of the real StreamingMarshaller for instances of the TestObjectStreamMarshaller.
  • this class builds an single local CacheManager instance in order to populate the StreamingMarshaller correctly. This shouldn't be a burden on the test suite and solves the azul problem nicely

import java.io.ObjectInput;
import java.io.ObjectOutput;
import java.io.OutputStream;
import java.io.Serializable;

/**
* A dummy marshaller impl that uses object streams converted via XStream as current JBoss Marshalling implementation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't use XStream any longer

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed the reference to xstream

@anistor
Copy link
Member

anistor commented Dec 2, 2013

I've only spotted two unused imports. Everything else looks fine to me.

@@ -150,7 +152,10 @@ public void testRestrictionOnAddingToAsyncQueue() throws Exception {
}

private TestObjectStreamMarshaller marshaller() {
return testObjectStreamMarshaller;
if (marshaller == null) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason this class is doing this through lazy initialization instead of a BeforeMethod/BeforeTest like the other classes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no reason but the fact that there was no @BeforeMethod annotated method present already. I've created one as obviously this approach raises questions for the readers of the class.

@wburns
Copy link
Member

wburns commented Dec 2, 2013

Pulling.

…s not have a no-args constructor

* an JBossMarshaller is built under the hood for each TestObjectStreamMarshaller instance
* users need to call TestObjectStreamMarshaller.stop explicitly
@wburns
Copy link
Member

wburns commented Dec 2, 2013

Integrated, Thanks @mmarkus !

@wburns wburns closed this Dec 2, 2013
@wburns
Copy link
Member

wburns commented Dec 2, 2013

Sorry closed too early.

@wburns wburns reopened this Dec 2, 2013
@wburns
Copy link
Member

wburns commented Dec 2, 2013

Integrated this time :)

@wburns wburns closed this Dec 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants