Hi,
On Thu, Jan 26, 2012 at 10:36 PM, Wooldridge, Keith A
keith.wooldri...@mantech.com wrote:
I'm trying to create a custom hibernate validator , based on bradhouse's
solution in this StackOverflow
No luck with this. I tried checking message.getReporter() and it's always the
form instead of the field.
Keith Wooldridge
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Friday, January 27, 2012 3:24 AM
To: users@wicket.apache.org
Subject: Re: Wicket
Hi!
One more benefit for MashupWebPage is that you can use it for creating tests:
public void testSomeFieldComponent() {
Page page = new MashupWebPage();
Form form;
page.add(form = new MashUpForm(GID));
FormComponent customField;
form.add(customField = new
Hi!
Could you help me with some examples?
In what way?
Normally you have a panel like this:
html
button wicket:id=button/
/html
class Panel {
add(new Button(button));
}
You cannot change the panel content flexibly at runtime.
Now if you have a MashupContainer you can do:
Sorry, when I wrote Scala and Grails I meant Scala and Groovy.
Em 28/12/2009 18:43, Ricardo Mayerhofer escreveu:
Hi Igor,
Em 23/12/2009 20:28, Igor Vaynberg escreveu:
On Wed, Dec 23, 2009 at 12:51 PM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Good discussion.
Em 23/12/2009
Hi Igor,
Em 23/12/2009 20:28, Igor Vaynberg escreveu:
On Wed, Dec 23, 2009 at 12:51 PM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Good discussion.
Em 23/12/2009 15:32, Igor Vaynberg escreveu:
On Wed, Dec 23, 2009 at 7:02 AM, Ricardo Mayerhofer
So you just want to throw all the components of a page or panel (the one
with markup) in 1 big place.
then all those have to be uniquely named ofcourse. Throughout the complete
page.
Repeaters will then be a bit special i guess. Because they are generation
ListItem components for you
that then
Hi!
you have the sources, you can build whatever infrastructure you need
that is missing. lets see it.
I had a quick look into it. IComponentResolver could probably
implement such quirk.
My first problem in trying to implement it is that I cannot actually
come up with a real world use
Maybe all I need is an ide that would show me the hierarchy on-line
while editing in java and maybe alert whenever there is a mismatch.
I think wicket bench might help with that... but in any case you can
write test cases for your code using WicketTester the simplest being
that the
I do all that (except haven't tried wicket bench!!) but I still want
to develop FASTER!! I want to get rid of all friction. Currently I get
friction from incoherent markup (I add replace a component via ajax
update but mistakenly add it into the wrong parent element.. I would
like a compile-time
Hi Igor,
Thanks for your response. Here goes my observations:
Em 22/12/2009 14:41, Igor Vaynberg escreveu:
On Tue, Dec 22, 2009 at 5:19 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi all,
We've just finished with success a wicket project for a large online
retailer. I think
not always like being
taught
From: Igor Vaynberg igor.vaynb...@gmail.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 12:03:05 AM
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 10:20 AM, sudhir543-...@yahoo.com wrote:
Yes, from my little
I vote +1 for more OO Wicket. Way to go Ricardo!
**
Martin
2009/12/23 Ricardo Mayerhofer ricardo.ekm.lis...@gmail.com:
Hi Igor,
Thanks for your response. Here goes my observations:
Em 22/12/2009 14:41, Igor Vaynberg escreveu:
On Tue, Dec 22, 2009 at 5:19 AM, Ricardo Mayerhofer
On Wed, Dec 23, 2009 at 07:32, Sudhir N sudhir_nima...@yahoo.com wrote:
One more thing I am still looking for is, integrating GWT. I did that
before with other framework.
i asked this question more
How do you see this integration? What should be integrated. What should
wicket do? What
an interesting question... i had some thoughts about this as related to my
sprockets experiment a few years back...
http://mail-archives.apache.org/mod_mbox/wicket-users/200804.mbox/%3c16411092.p...@talk.nabble.com%3e
unfortunately, i know as little about GWT now as i did then.
jon
On
wicket does two things: provides a way to render javascript to
bootstrap a gwt widget in a page and provides callbacks for the gwt
widget to access serverside data.
-igor
On Wed, Dec 23, 2009 at 7:38 AM, Johan Compagner jcompag...@gmail.com wrote:
On Wed, Dec 23, 2009 at 07:32, Sudhir N
and where is this more OO?
-igor
On Wed, Dec 23, 2009 at 7:24 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
I vote +1 for more OO Wicket. Way to go Ricardo!
**
Martin
2009/12/23 Ricardo Mayerhofer ricardo.ekm.lis...@gmail.com:
Hi Igor,
Thanks for your response. Here goes
On Wed, Dec 23, 2009 at 7:02 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi Igor,
Thanks for your response. Here goes my observations:
Em 22/12/2009 14:41, Igor Vaynberg escreveu:
On Tue, Dec 22, 2009 at 5:19 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi
It is HTTP! and we can use OOP very well.
Wicket makes it possible.
+1 for wicket :)
NM
On Wed, Dec 23, 2009 at 1:51 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
and where is this more OO?
-igor
On Wed, Dec 23, 2009 at 7:24 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
More OO is less synchronization between markup and wicket.
It should be sufficient that the artist thinks the gfx are immacculate
and that the java developer thinks the code is immacculate. Why do we
need to couple java with html hierarchies and stuff? Some namespace
attribute could suffice to
On Wed, Dec 23, 2009 at 10:53 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
More OO is less synchronization between markup and wicket.
what does that have to do with OO exactly?
It should be sufficient that the artist thinks the gfx are immacculate
and that the java developer
i think it is a trade off.
we synchronize with the markup and lose some OOP, but we gain in desing.
Have you ever change the look and feel of your application? with wicket it
is really easy, in other frameworks it is a nightmare.
NM
On Wed, Dec 23, 2009 at 3:53 PM, Martin Makundi
what does that have to do with OO exactly?
hmm..
It should be sufficient that the artist thinks the gfx are immacculate
and that the java developer thinks the code is immacculate. Why do we
need to couple java with html hierarchies and stuff? Some namespace
attribute could suffice to allow
you have the sources, you can build whatever infrastructure you need
that is missing. lets see it.
-igor
On Wed, Dec 23, 2009 at 11:15 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
what does that have to do with OO exactly?
hmm..
It should be sufficient that the artist thinks
Good discussion.
Em 23/12/2009 15:32, Igor Vaynberg escreveu:
On Wed, Dec 23, 2009 at 7:02 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi Igor,
Thanks for your response. Here goes my observations:
Em 22/12/2009 14:41, Igor Vaynberg escreveu:
On Tue, Dec 22, 2009 at
On Wed, Dec 23, 2009 at 12:51 PM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Good discussion.
Em 23/12/2009 15:32, Igor Vaynberg escreveu:
On Wed, Dec 23, 2009 at 7:02 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi Igor,
Thanks for your response. Here goes my
+1 for last point Too many finals modifiers
and subclassing isnt always better than listeners - My 2cents
Sudhir NimavatSenior software engineer.
Quick start global PVT LTD.
Baroda - 390007
Gujarat, India
Personally I'm always ready to learn, although I do not always like being
Ajax with wicket is easy.. if you do it the wicket way.. But integration with
other engines isnt going to be easy.
Not only Ajax, from my little wicket experience, I would say wicket works great
in isolation, however integrating it to any other framework would take (and it
takes)
On Tue, Dec 22, 2009 at 6:21 AM, sudhir543-...@yahoo.com wrote:
lol
Ajax with wicket is easy.. if you do it the wicket way.. But integration
with other engines isnt going to be easy.
maybe if you have little experience you should not be making such
sweeping statements. there are projects
On Tue, Dec 22, 2009 at 7:51 PM, sudhir543-...@yahoo.com wrote:
Ajax with wicket is easy.. if you do it the wicket way.. But integration
with other engines isnt going to be easy.
IMHO integration with other engines is actually quite easy, and certainly
far easier than other frameworks, see
On Tue, Dec 22, 2009 at 5:19 AM, Ricardo Mayerhofer
ricardo.ekm.lis...@gmail.com wrote:
Hi all,
We've just finished with success a wicket project for a large online
retailer. I think wicket is the best framework out there, but as any other
project there is room for improvement. I will talk
: Igor Vaynberg igor.vaynb...@gmail.com
To: users@wicket.apache.org
Sent: Tue, 22 December, 2009 9:46:45 PM
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 6:21 AM, sudhir543-...@yahoo.com wrote:
lol
Ajax with wicket is easy.. if you do it the wicket way.. But integration
with other engines
: Re: Wicket feedback
On Tue, Dec 22, 2009 at 6:21 AM, sudhir543-...@yahoo.com wrote:
lol
Ajax with wicket is easy.. if you do it the wicket way.. But integration
with other engines isnt going to be easy.
maybe if you have little experience you should not be making such
sweeping
...@gmail.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 12:03:05 AM
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 10:20 AM, sudhir543-...@yahoo.com wrote:
Yes, from my little experience, I just started learning it [Because I feel it
has some thing different to offer]
orly? so what
...@gmail.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 12:03:05 AM
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 10:20 AM, sudhir543-...@yahoo.com wrote:
Yes, from my little experience, I just started learning it [Because I feel
it has some thing different to offer]
orly? so
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 11:13 AM, sudhir543-...@yahoo.com wrote:
Thanks for clarifying the things,
show me a framework that makes this easier...
I think that when I when I was working with Webwork (Struts2 now) I dint need
to do any thing else other than specifying
From: sudhir543-...@yahoo.com sudhir543-...@yahoo.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 11:57:34 AM
Subject: Re: Wicket feedback
so how does webwork know which properties of your actions should be injected
from spring and which from
igor.vaynb...@gmail.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 12:03:05 AM
Subject: Re: Wicket feedback
On Tue, Dec 22, 2009 at 10:20 AM, sudhir543-...@yahoo.com wrote:
Yes, from my little experience, I just started learning it [Because I feel
it has some thing different
: sudhir543-...@yahoo.com sudhir543-...@yahoo.com
To: users@wicket.apache.org
Sent: Wed, 23 December, 2009 11:57:34 AM
Subject: Re: Wicket feedback
so how does webwork know which properties of your actions should be injected
from spring and which from the request or session objects
39 matches
Mail list logo
