Hello,
I am writing a simple stateless form with validation based on annotations in
Wicket 7.0.0-SNAPSHOT. When the model's field is annotated @NotNull and
PropertyValidator is added to its form component, the validation error is not
generated if user's input is empty. It seems to me that the "R
Hello, thank you for responding, I have already implemented the calender
using Wicket-JQuery-UI, now I need to fetch the details of a user from his
Google calender which I could display in the user's account calender in my
application also.
--
View this message in context:
http://apache-wicket.18
For this you will have to consult with
http://fullcalendar.io/docs/google_calendar/ and the provided integration
in Wicket JQuery UI project.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Jan 28, 2015 at 12:39 PM, jayeshps wrote:
> Hello, thank you for re
Hi,
Yes. It is a bug. Please create a ticket.
The problem comes from the fact that you use stateless form. The required
flag is set for the form component on the rendered page, but later when the
form is submitted a new page with a new form (and components) is created
and the flag is gone.
Since t
Ticket created, thank you for your time and explanation!
Adam
-- Původní zpráva --
Od: Martin Grigorov
Komu: users@wicket.apache.org
Datum: 28. 1. 2015 12:36:21
Předmět: Re: PropertyValidator sets "Required" flag too late
"Hi,
Yes. It is a bug. Please create a ticket.
The pro
I forked Wicket to my github repo and took a look at it. Compiling
wicket-native-websocket-javax with Java 6 and Wicket 6.19.0-SNAPSHOT was no
problem at all, my problem popped up when I tried to get the embedded jetty
server to run the test case. It fails with "WebSocket connection to
'ws://localh
url to your github repo ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Jan 28, 2015 at 5:02 PM, Alexander Landsnes Keül <
alexander.landsnes.k...@visma.com> wrote:
> I forked Wicket to my github repo and took a look at it. Compiling
> wicket-native-websoc
https://github.com/alexanderlk/wicket
It's under the wicket-6.x branch, same exact structure as the one in
7.0.0-M4
Alex
On Wed, Jan 28, 2015 at 4:25 PM, Martin Grigorov
wrote:
> url to your github repo ?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
>
Hi,
We use the great rest-annotation from wicketstuff.
One thing that bothers is if the AbortWithHttpErrorCodeException with a
specific code (404, 402, etc) is thrown by the mapped method, those error
codes do not make it to the calling client. The client always seems to get a
500.
I debugged thr
Sorry but this won't be reusable for the community.
I've suggested to put it in WicketStuff, not in Wicket.
If I spend time to help you now then next week perhaps another user will
ask the same. It doesn't scale :-/
I'll put it in WicketStuff (
https://github.com/wicketstuff/core/tree/wicket-6.x)
Hans,
I handle all exceptions and set status codes in my mapped method with
AbstractRestResource#setResponseStatusCode(…). I don’t ever throw any
exceptions from there. Setting a status code is the only thing that is really
happening in AbstractRestResource#invokeMappedMethod(…) when an excepti
Hi Warren,
life can be so easy sometimes. Thanks :-)
-- Cheers, Hans
-Ursprüngliche Nachricht-
Von: Warren Bell [mailto:warrenbe...@gmail.com]
Gesendet: Donnerstag, 29. Januar 2015 05:53
An: users@wicket.apache.org
Betreff: Re: Wicketstuff Restannotations AbortWithHttpErrorCodeExceptio
12 matches
Mail list logo