Hi guys,
I have just upgraded a large project from wicket 1.3 to 1.4(.18) and needed to
update wicketstuff-animator.
I now have a patch against the import-backup on github but have no idea how /
where to contribute this.
Should I fork the backup (weird) or can I start a new repo from the code i
area and
would be happy to come and speak.
If not I would still be interested in any useful material or tips for such a
topic.
Many thanks in advance for any responses,
Andrew Williams
Java User Group Scotland
-
To unsubscribe, e
On 24 Feb 2008, at 13:35, Martin Makundi wrote:
first I'd ask, why do you hesitate to install the Libraries to your
local repository?
I am in prototyping phase and being new to wicket it is a mess ;) I
consider it more flexible and less messy not to install such jars into
maven repository -
I use onBeginRequest and onEndRequest from the WebRequestCycle, seems
to work well.
Andy
On 13 Feb 2008, at 07:59, Sébastien Piller wrote:
Hello,
I'm searching for a best practice to integrate some hibernate
transaction with Wicket. I'd like to implement the "session-per-
request" that i
1.3.0 and 1.3.0-beta4 both exhibit this behaviour.
In fact, 1.3.0 seems worse - it is not just the single most recent
page int he history that still bombs.
Andy
On 1 Feb 2008, at 17:12, Igor Vaynberg wrote:
what wicket version are you using?
-igor
On Feb 1, 2008 4:06 AM, Andrew Williams
2008, at 22:21, Andrew Williams wrote:
Bad form to reply to myself, but if anyone else had problems with
this there is an undocumented protected method
"onlyTargetActivePage()" which should be called from an overridden
constructor.
Best wishes,
Andrew
On 27 Jan 2008, at 15:01, Andre
Bad form to reply to myself, but if anyone else had problems with this
there is an undocumented protected method "onlyTargetActivePage()"
which should be called from an overridden constructor.
Best wishes,
Andrew
On 27 Jan 2008, at 15:01, Andrew Williams wrote:
I have a peculi
I have a peculiar problem that I hope can be solved by the experts!
I have on my application pages a panel that is updated using an
AbstractAjaxTimerBehavior to update the style attribute making it
visible or not.
This works just fine on the current page. If, however, I press the
back butto
