It's configurable via a system property (serialization.jboss). I see now the default is to use JBoss serialization; thought it was to use Java serialization.

Sure, if we want to force JBoss serialization, then this JIRA is irrelevant. Re: reason to have it be configurable, it provides a fallback option if there is any issue with jboss serialization. IMHO, that's valid.

Manik Surtani wrote: > I don't believe this is a configurable option ... ? > Is there any good reason to make it so? > > >> From: "Brian Stansberry (JIRA)" <jira-events(a)jboss.com&gt; >> Date: 26 October 2006 15:12:41 BDT >> To: manik.surtani(a)jboss.com >> Subject: [JBoss JIRA] Created: (JBCACHE-815) Eliminate need for >> jboss-serialization.jar if it's not used >> >> Issue (View Online) >> >> Key: JBCACHE-815 >> Issue Type: Task >> Status: Open >> Priority: Minor >> Assignee: Manik Surtani >> Reporter: Brian Stansberry >> Operations >> >> View all >> View comments >> View history >> >> Eliminate need for jboss-serialization.jar if it's not used >> Updated: 26/Oct/06 10:11 AM Created: 26/Oct/06 10:11 AM >> Project:JBoss Cache Components: Replication >> Affects Versions: 1.4.0.SP1, 1.4.0 >> Security Level: Public (Everyone can see) >> >> Description >> 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 was automatically generated by Atlassian JIRA >> Enterprise >> Edition, Version: 3.6.2-156 - Bug/feature request. >> If you think it was sent incorrectly, contact one of this server's >> administrators. Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat Ph: 510-396-3864 skype: bstansberry