-
Von: Johan Compagner [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 12. November 2006 20:15
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
what does a page mounted on /* means in your eyes?
/[everything]??
there is no such a thing like wild card mounting
interested in any thoughts about it.
Best Regards,
Korbinian
-Ursprüngliche Nachricht-
Von: Johan Compagner [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 13. November 2006 10:20
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
So this way
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
So this way?
/ == home page
/?p=a == homepage with page params.
/?interface:xxx == an callback to an existing page
/?bookmarkablePage=xxx == an none mounted bookmarkable page request
/input
that swaps around components in
it this doenst sound too exotic for me.
regards
-Ursprüngliche Nachricht-
Von: Johan Compagner [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 13. November 2006 20:29
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
you can have .html just fine.
Only you want to have xxx/param.html?
so like:
/product/110203.html?
or
/product/id/110203.html?
Why that html there?
What does that bring?
I don't find it nicer that is just taste.
And i guess you could build
[mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 12. November 2006 18:39
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
the homepage is always mounted on /
-igor
On 11/12/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
Johan,
i checked all - everything
: Severe Bug in Wicket 2 / WICKET-42
the homepage is always mounted on /
-igor
On 11/12/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
Johan,
i checked all - everything is now behaving as expected. Great Work!
One question however is still to me - why cant i mount a
page
does it always just work if always your first access is the root of your
webapp?
So if you redeploy or restart then your first request should be the root of
your webapp.
Then afterwards should everything just work.
This is a bug yes i have to rollback code for this because getServletPath()
can't
. November 2006 17:30
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
does it always just work if always your first access is the
root of your webapp?
So if you redeploy or restart then your first request should
be the root of your webapp.
Then afterwards
This is a bug yes i have to rollback code for this because getServletPath()
can't be depended on in a filter configuration. Which we do now.
I introduced that bug two weeks ago. Sorry. Johan and I already discussed it.
Eelco
-
Von: Johan Compagner [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 11. November 2006 17:30
An: wicket-dev@incubator.apache.org
Betreff: Re: Severe Bug in Wicket 2 / WICKET-42
does it always just work if always your first access is the
root of your webapp?
So if you redeploy or restart
11 matches
Mail list logo