Why not use the Terracotta Integration Module's capabilities to AOP-
inject the "implements interface" specification onto the class you want?
Remember, a TIM is not just an OSGi bundle of XML and new code, but
also tools to replace methods / classes when clustered as well as a
full-powered AOP engine to augment classes / methods as necessary.
--Ari
On Jul 4, 2008, at 1:19 AM, richardwilko wrote:
I'm not trying to cluster the diskpagestore, im trying to implement a
PageStore than can be clustered.
I needed to instrument the AbstractPagStore class becauase it is
referenced
by the inner classes of the TerracottaPageStore (the ones which are
clustered), however I was thinking about this and have decided that
I need
to come up with a better way so that it does not need to be
instrumented,
probably by not using inner classes. I wasnt actually wanting to
cluster
the entire AbstractPageStore class.
The
org.apache.wicket.protocol.http.pagestore.AbstractPageStore
$SerializedPage
class definitely does need to be clustered though as this is the
object
which holds the page in the clustered page store.
I havent created a JIRA issue yet as I wanted to get the code
working first.
Cheers,
Richard
Eelco Hillenius wrote:
On Thu, Jul 3, 2008 at 11:37 AM, Ari Zilka <[EMAIL PROTECTED]>
wrote:
This is the agreed upon approach mimicking the DiskPageStore. No?
Well, the DiskPageStore takes care of storing pages, but by itself
would never be transferred across a cluster. So making it
IClusterable
wouldn't make sense.
Eelco
--
View this message in context:
http://www.nabble.com/Terracotta-integration-tp18168616p18275042.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
