[
http://jira.jboss.com/jira/browse/JBCACHE-815?page=comments#action_12346126 ]
Clebert Suconic commented on JBCACHE-815:
-----------------------------------------
I don't think you have solved the low coupling on ObjectSerializationFactory...
You are using reflection to create the streaming Out... and you are using a hard class
reference on the Input.
You should use reflection to instantiante the factory's implementation... or always
use reflection. I doubt the implementation as is now will not load
jboss-serialization.jar
you should try using the implementation I have introduced.
I don't mean to be annoying but i will reopen the issue since I think it was not
solved. :-) If you disagree simply close it back.
Eliminate need for jboss-serialization.jar if it's not used
-----------------------------------------------------------
Key: JBCACHE-815
URL:
http://jira.jboss.com/jira/browse/JBCACHE-815
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Replication
Affects Versions: 1.4.0.SP1, 1.4.0.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Priority: Minor
Fix For: 1.4.1.GA, 2.0.0.GA
Attachments: JavaSerializationFactoryImpl.java,
JBossSerializationFactoryImpl.java, ObjectSerializationFactory.java,
SerializationFactory.java, Test.java
If we're going to stick making use of JBoss serialization a configurable option, we
should refactor ObjectSerializationFactory so no jboss-serialization classes are loaded if
it's not used. Allows users to drop one more jar from their footprint.
--
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