Martin,
I have logged the issue in Jira with a quick start project. the ticket id
is
WICKET-5707 https://issues.apache.org/jira/browse/WICKET-5707. I do not
like the work-around as it makes the code messy.
Thanks you in anticipation of a quick fix.
On 21 September 2014 20:06, Ajayi Yinka
We are doing that, but wanted to get a confirmation .
Thank you,
Rakesh.A
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WiQuery-for-Wicket-6-17-0-tp4667564p4667634.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi,
In short, to accomplish all this you will need several custom impls of
Wicket interfaces.
1) custom IRequestMapper that just ignores PageInfo when generating the url
for IPageRequestHandler. Search in the archives for NoVersionRequestMapper
2) a completely new IPageManager (interface!) that
See http://markmail.org/message/ofyvgybcjp5cvf75
You talk about the same idea.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Sep 16, 2014 at 12:10 PM, Bernard bht...@gmail.com wrote:
Martin,
First I appreciate very much your hard work in the mailing
Hello,
is it possible to get the incorrect url when error 404 occurs?
I would like to inspect this url and react differently for
- users who want access but did a mistake in the url or
bookmarked an url which is no longer valid
- show StartPage (with some more functionality)
- others who
Hi,
You can use
http://docs.oracle.com/javaee/7/api/javax/servlet/RequestDispatcher.html#ERROR_REQUEST_URI
to get the original uri.
It is stored as request attribute.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Sep 23, 2014 at 4:00 PM, Karl-Heinz Golz
Hi,
I have a really strange one...
I am using
Apache 2.x
Jboss 7 (EAP 6.3) and also tried in Tomcat 7
Wicket 6.16.0
I used the HelloWorld application here
https://wicket.apache.org/learn/examples/helloworld.html
It works fine on http://localhost:8080/myapp
I add Apache virtual host with the
OMG. What a sad email to wake up to. :(
Let me let all that digest for a while. I never would have imagined a
situation this dire. Imagine if every time you went to Facebook, it
generated a new https://www.facebook.com/jdoe?124154451 version! So
basically Facebook could never use Wicket
Hello All,
As I can see ListView constructor signature was changed since 7.0.0-M3
it is now
public ListView(final String id, final IModel? extends ListT model)
public ListView(final String id, final ListT list)
was
public ListView(final String id, final IModel? extends List? extends T
model)
In our project we are using NoVersionRequestMapper to create user friendly
URLs
seems to work as expected
On 23 September 2014 20:44, Garret Wilson gar...@globalmentor.com wrote:
OMG. What a sad email to wake up to. :(
Let me let all that digest for a while. I never would have imagined a
It is an interesting question whether other web frameworks (also
outside JVM world) use any similar page versioning scheme to wicket. I
am not aware of any.
In any case I guess most projects using wicket would have to make
design decisions based on whether the page version is acceptable in
the
On Tue, Sep 23, 2014 at 4:44 PM, Garret Wilson gar...@globalmentor.com
wrote:
OMG. What a sad email to wake up to. :(
Let me let all that digest for a while. I never would have imagined a
situation this dire. Imagine if every time you went to Facebook, it
generated a new
It is true that page version does seem kind of redundant or even annoying
at times. If you have a wicket app that is full ajax (remember that ajax
requests don't increment the page version), the only reason you need the
page version is so you can have the same page open in two different tabs
with
On 9/23/2014 12:08 PM, Martin Grigorov wrote:
On Tue, Sep 23, 2014 at 4:44 PM, Garret Wilson gar...@globalmentor.com
wrote:
OMG. What a sad email to wake up to. :(
Let me let all that digest for a while. I never would have imagined a
situation this dire. Imagine if every time you went to
14 matches
Mail list logo
