[
http://jira.jboss.com/jira/browse/JBREM-609?page=all ]
Ron Sigal closed JBREM-609.
---------------------------
Resolution: Done
Changed CallbackStore to look in its configuration map for key
InvokerLocator.SERIALIZATIONTYPE (whose value is "serializationtype") and create
the appropriate ObjectInputStreams and ObjectOutputStreams.
Unit test
org.jboss.test.remoting.callback.pull.memory.callbackstore.jbossSerialization.CallbackStoreCallbackTestCase,
derived from the classes in package
org.jboss.test.remoting.callback.pull.memory.callbackstore, creates enough callbacks to
force ServerInvokerCallbackHandler to persist Callbacks to Callback store. The
serialization type is set to "jboss" in the server's InvokerLocator.
Unit test
org.jboss.test.remoting.callback.pull.memory.callbackstore.nonserializable.NonserializableCallbackTestCase
directly tests the ability of CallbackStore to store and retrieve Callbacks with
nonserializable payloads.
Support nonserializable callbacks in CallbackStore
--------------------------------------------------
Key: JBREM-609
URL:
http://jira.jboss.com/jira/browse/JBREM-609
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Beta1 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
A connection using JBoss serialization will transfer nonserializable callbacks, but
currently CallbackStore cannot persist them to a file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira