Eelco Hillenius wrote:
I just committed the changes for the core projects (both the 1.3
branch and 2.0 trunk). See
http://issues.apache.org/jira/browse/WICKET-337
So Eugene, this configuration fragment:
wicket.IClusterable+
true
should suffice for Wicket, right?
That is the idea.
Pre
Jonas Bonér wrote:
It's not super important, but would the marker interface be a wicket
type or a terracotta type? I could imagine it could be either actually,
just wondering which one you had in mind.
Clusterable extends Serializable? Why the coupling?
Finally, (and please excuse my ignoranc
Eelco Hillenius wrote:
Finally, (and please excuse my ignorance of annotations), is it feasible
to introduce an annotation without adding any compile time dependencies?
I don't think so. And as we're targetting Wicket 1.3 for JDK 1.4 and
up, annotations are out of the question for us.
You ca
It will work when I'll be done with subtype-based matching. But using
marker interface is somehow ugly (even so it is probably the best fit
for the Terracotta support).
Java5 annotations could be a nicer option for such purpose, but then
Terracotta don't support matching on annotations yet
