They both are snapshots, so this is expected now and then, however they don't seem to be being fixed.
In all cases so far, the exceptions that popup during runtime reflection and a common theme is the ModalWindow classes.
For instance:Caused by: java.lang.NoSuchMethodError: org .apache .wicket .extensions.ajax.markup.html.modal.ModalWindow.setPageMapName(Ljava/ lang/String;)V at org .wicketstuff .calendarviews.LargeView.initializeDetailModalWindow(LargeView.java:103)
There is another that I don't have off the top right now, but it's similar (also in ModalWindow, although not the same error). In general one of the reasons I chose to work with Wicket is the easy way it can be tested.
So, to that end I would like to recommend to the WIcket Stuff developers that *aLl example apps* have unit tests. Unit testing the examples would more than likely expose these problems early. To begin with, any library that uses ModalWindow should have unit tests added.
I'm in the process now of checking out the wicketstuff source so I can start trying to fix some of this stuff, time permitting myself.
- Brill
smime.p7s
Description: S/MIME cryptographic signature
