What do you use to navigate to another tab? Probably a link (ajax or
not)? If so, you could put the logic in there.
Eelco
On 4/4/07, jamieballing <[EMAIL PROTECTED]> wrote:
>
> We have a modal window with several tabs. We want to validate the data on the
> tab after when the user navigates away
Instead of pre-loading in the input field, try pre-loading the property in
your form backing object (model) - so call setArrivalDate() or just ensure
that PaymentInfoInput.arrivalDate is not null
On 4/7/07, V. Jenks <[EMAIL PROTECTED]> wrote:
I feel like I've asked this question before...but h
Thank you, that worked perfect.
-kurt
On Thu, 2007-04-05 at 16:23 +0200, Sven Meier wrote:
> You have to give the radio group a model, that is backed by your question
> object, not only the current value of its answer:
>
> RadioGroup answer = new RadioGroup("answer", new PropertyModel(questi
Patches are always welcome at: https://issues.apache.org/jira/browse/WICKET
Eelco
On 4/6/07, Philip Weaver <[EMAIL PROTECTED]> wrote:
> Basically, would be nice if instructions as simple as the following were
> part of the build file:
>
>
> failonerror="true" maxmemory="128m" class
Basically, would be nice if instructions as simple as the following were
part of the build file:
I'll see if I can add something to the wiki - but I want to play now.
On 4/6/07, Philip Weaver <[EMAIL PROTECTED]> wro
In summary, the intent of the QuickStart with a bundled Jetty is fabulous.
However, I feel that it falls short by only offering means to run the
project using NetBeans, IDEA, or Eclipse. And I think this is a little
disappointing. I happen to use jEdit - so I think it's a little annoying
that the
* Carlos Pita:
> Maybe this could be relevant:
>
> * I'm using jetty:run maven plugin. I run it from the console
> * and from apache. I run it on top sun jdk 1.6.0 and ibm jdk 5.
Hi Carlos,
You're running jetty:run so I guess your Eclipse classpath is
setup with Maven as well. So clas
Maybe this could be relevant:
* I'm using jetty:run maven plugin.
* I run it from the console and from apache.
* I run it on top sun jdk 1.6.0 and ibm jdk 5.
Carlos
On 4/6/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> Maybe I'm missing something but I can't get ReloadingWicketServlet to
> work. I
Maybe I'm missing something but I can't get ReloadingWicketServlet to
work. I have subclassed it and included a pattern for my web tier
package as documented. The relevant code and configuration is given
below. If I modify a class residing at home.web and then re-enter its
page (not just refresh it
I'm pointing my pom repositories to
http://wicketstuff.org/maven/repository just right now. I will keep
you informed of my experiences along next week, toying with it at home
and more seriously using it with my development team at work.
Cheers,
Carlos
On 4/6/07, Eelco Hillenius <[EMAIL PROTECTED]>
Please keep us informed when you play with the reloading filter. I
think Jean-Baptiste deems it usable in it current state. But any
improvements/ suggestions (especially in the form of patches!) would
be welcome.
Eelco
On 4/6/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> I'd read that thread befor
> Seems there might not be a full-proof fix for this problem:
> http://forum.java.sun.com/thread.jspa?threadID=572396&tstart=0
But at least they're working on it, and any improvement would be welcome imo.
Eelco
-
Tak
I'd read that thread before. I think I understand your point Igor. But
I don't pretend that old instances keep somehow up to date with new
incompatible reloaded classes. If I could start all again from a
bookmarkable page, everything being reinstantiated again, I will be
happy, even if some margina
I feel like I've asked this question before...but here I am again. I'm
simply trying to set a selected value for a DropDownChoice when a page is
loaded.
I've tried pre-loading it into the input class, setting it in
getDefaultChoice, and also by trying to pass a model into the control w/ the
valu
Seems there might not be a full-proof fix for this problem:
http://forum.java.sun.com/thread.jspa?threadID=572396&tstart=0
Gili
Carlos Pita wrote:
>> See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
>
> I will give this filter a try. I see it's included in the trun
this is mostly a dream anyways for early stages where you are still adding
fields
see
http://www.theserverside.com/news/thread.tss?thread_id=44119#226916
hls' reply here
http://www.theserverside.com/news/thread.tss?thread_id=44119#226916
my rebuttal that drives the point home
http://www.thes
> > See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
> I will give this filter a try. I see it's included in the trunk but
> not in 1.2.x releases. Is it compatible with wicket 1.2.5?
Nope. Not planned either, sorry. If you are starting out, 1.3 (from
svn or get snapshots her
in quickstart you can do mvn eclipse:eclipse to generate an eclipse project,
or mvn idea:idea for idea.
you can writeup a document on the wiki, and if we all like it we can export
it into quickstart's readme or something like that
-igor
On 4/6/07, Philip Weaver <[EMAIL PROTECTED]> wrote:
Ca
> See wicket.protocol.http.ReloadingWicketFilter. YMMV though, as Wicket
I will give this filter a try. I see it's included in the trunk but
not in 1.2.x releases. Is it compatible with wicket 1.2.5?
> the JDK provides. Some SDK implementations are working on improved
> support (I think Johan has
Can anyone send me pointers for setting up quickstart manually? (scripts,
build file w/ exec, etc)
Who to talk to to create a generic quickstart setup document?
I am interested in helping to improve the Quickstart download. I would be
more pleased if the quickstart first presented a generic quick
> I find that reloading the entire app stack (wicket + spring +
> hibernate) every time I change a page class is somewhat overkiller.
> When coding simple toy examples restricted to just wicket, the
> jetty:run maven plugin monitors my target folder and reload the
> application in a matter of a sec
Hi all,
I find that reloading the entire app stack (wicket + spring +
hibernate) every time I change a page class is somewhat overkiller.
When coding simple toy examples restricted to just wicket, the
jetty:run maven plugin monitors my target folder and reload the
application in a matter of a seco
> > I've been coding some
> > examples with convoluted entity lazy-loaded associations and, despite
> > my previous fears, detaching/re-attaching it from/to the hibernate
> > session works like a charm. I think I will tag all my editable
> > entities as Serializable and embrace this approach.
>
> S
> > the object is reloaded just for setting a property and discarded
> > again; also, depending on how you configure your transactions, you
> > could end up persisting partial non-validated changes (although I
> > should say that from my observations this doesn't happen inside a
> > vanilla OpenSes
> Also, reloading the entity from "state zero" every time could be
> problematic when incrementally updating it using ajax.
Not if you save it every time :) But yes, if you do an update in
steps, and only want to commit changes at the end (relevant not only
with Ajax, but also e.g. with a wizard)
On 4/6/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> On 4/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > It's not a good idea to use LoadableDetachableModel for entities that
> > > you edit. Because they are detached after every request.
> >
> > Sorry, but I don't agree with that :) LDMs are
> On 4/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > It's not a good idea to use LoadableDetachableModel for entities that
> > > you edit. Because they are detached after every request.
> >
> > Sorry, but I don't agree with that :) LDMs are my favorite models for
> > such use. The only thi
>
> If it works well, anything outside of a transaction should well... be
> outside the transaction :) So anything touched in a read-only (auto
> started) transaction should never be upgraded to a write one. I'm not
> a Spring expert though. But that's what you can expect from the
> library.
This
Eelco Hillenius wrote:
>
> I've never worked with T myself, but read a book on it and browsed
> through the source code. The funny thing is that I was about to start
> a proof of concept in it for the company I worked for three years ago.
> But Johan just got out of a project that used it, and e
On 4/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > It's not a good idea to use LoadableDetachableModel for entities that
> > you edit. Because they are detached after every request.
>
> Sorry, but I don't agree with that :) LDMs are my favorite models for
> such use. The only thing you have
> Anyway, I've done little tests with spring OpenSessionInViewFilter and
> things DO work as I desire. I mean changes are committed only when a
> @Transactional method is invoked, not during events that simply update
> the model without submitting.
Imo, have separate transaction methods (service/
i think that can work, please add an rfe. we do have global js hooks that
you can use to create a global indicator.
-igor
On 4/6/07, Alex Objelean <[EMAIL PROTECTED]> wrote:
In wicket 1.2.5, is not possible (at least I didn't manage to find a way)
to
add AjaxIndicator image to a page for all
> It's not a good idea to use LoadableDetachableModel for entities that
> you edit. Because they are detached after every request.
Sorry, but I don't agree with that :) LDMs are my favorite models for
such use. The only thing you have to keep in mind is to persist any
changes coming in with a requ
> I am definitely going to check out 1.3. Any idea when it will become
> less of a "moving target"?
In a couple of weeks. Basically when all the items listed here
http://cwiki.apache.org/confluence/display/WICKET/Backporting+features+from+trunk
are backported. We'll announce it on the list when t
I am definitely going to check out 1.3. Any idea when it will become
less of a "moving target"?
-scott
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wicket-user-
> [EMAIL PROTECTED] On Behalf Of Matej Knopp
> Sent: Thursday, April 05, 2007 6:14 PM
> To: wicket-user@lists.sourcef
Hi
Wicket applications shouldn't be affected by javascript hijacking. To
be able to use this kind of hijacking, ajax response has to be
directly executable javascript. Wicket's Ajax response is a xml file,
which can not be directly evaluated, thus loading it from remote site
using the
Hi Matej,
what about entities with lazy loaded associations that are not easily
detachable/re-attachable from/to their hibernate session? I was never
sure on how to do this, maybe dto is a healthier alternative despite
introducing a lot of duplication.
Anyway, I've done little tests with spring O
Hi!
How protected is Wicket against "JavaScript Hijacking", as described in this
paper?
http://www.fortifysoftware.com/servlet/downloads/public/JavaScript_Hijacking.pdf
http://www.fortifysoftware.com/servlet/downloads/public/JavaScript_Hijacking.pdf
Best Regards
Niels Bo
--
View this messag
It's not a good idea to use LoadableDetachableModel for entities that
you edit. Because they are detached after every request.
LoadableDetachableModel is best for View scenarios, when you need
fresh data on every request. In case you are editing entities, like
you do, load the entity only once, e.
In wicket 1.2.5, is not possible (at least I didn't manage to find a way) to
add AjaxIndicator image to a page for all Ajax requests made by its child
components.
Currently, the AbstractDefaultAjaxBehavior has a findIndicatorId() method
which is responsible to find the component id which should b
40 matches
Mail list logo
