I had problems with sourceforge too today. Thanks Ingram,
Eelco
On 6/28/06, Ingram Chen [EMAIL PROTECTED] wrote:
I will post it after sourceforge allow login.
On 6/29/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Thanks. Would you mind attaching that to an issue on sourceforge please?
Thanks. Would you mind attaching that to an issue on sourceforge please?
Eelco
On 6/27/06, Ingram Chen [EMAIL PROTECTED] wrote:
Is there any progress on this issue ?
I tried Wicket 1.2 + SiteMesh but still out of luck...
I create a quick-start to reproduce this problem:
The attachment
I will post it after sourceforge allow login. On 6/29/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Thanks. Would you mind attaching that to an issue on sourceforge please?Eelco
On 6/27/06, Ingram Chen [EMAIL PROTECTED] wrote: Is there any progress on this issue ? I tried Wicket 1.2 + SiteMesh but
I have never used Sitemesh or Wicket on a real project, although I've
played with both and they both seem to work exactly as advertised --
now I'm trying to use them both together on a real project for the
first time and I'm having a problem. The problem only happens
when I'm accessing a
I do believe, that Sitemesh is really not required when using
Wicket... since you can inherit page markup via Border, Panel's, and
the wicket:head/wicket:head wicket:extendwicket:child //
wicket:extend.
Doesn't negate that Sitemesh isn't working correctly with your
environment though, but
That was the issue exactly -- we want to have several applications all
branded exactly the same, but my group is only writing this one
application (using wicket) On 11/21/05, Andrew Lombardi [EMAIL PROTECTED] wrote:
I do believe, that Sitemesh is really not required when usingWicket... since
In case you have a small test project or something, I would be very
interested in taking a look at that and see if there's anything we
need to do to make Wicket behave better with sitemesh. There has been
more interest in it, so we might setup a small project for it too
(wicket-stuff).
Eelco
On
