• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • hhuynh
  • Reporter: siyer
  • June 22, 2007
  • 0
  • Watchers: 0
  • September 24, 2007
  • September 10, 2007

Description

User(s) of wicket 1.3 config bundle report that they had to add more Configuration to tc-config.xml to get Wicket 1.3 to cluster correctly (ofcourse after including the published Wicket 1.3 module)- could we investigate if this is an edge-case that was not covered by the config-bundle provided.

org.apache.wicket.MetaDataEntry

……….

org.apache.wicket.MetaDataEntry.object

I don’t know much about this class but for what’s here http://jsourcery.com/api/sourceforge/wicket/1.2.4/wicket/MetaDataEntry.html

Comments

Eugene Kuleshov 2007-06-22

The MetaDataEntry class itself should be included automatically, because it has IClusterable marker interface (in Wicket 1.3), but I don’t know what kind of stuff is stored in the object field. So, it would be great to get some input from Wicket developers.

Steve Harris 2007-06-22

Is this a dupe?

Fiona OShea 2007-06-25

Eugene can you resolve this if it is fixed?