Thanks, everyone who contributed!
Is Wicket 1.4 still planned to be a Java 5 version of Wicket 1.3? How
far away is Wicket 1.4?
I have a small prototype application built using Wicket 1.2.6. I believe
that little prototype may soon graduate to a real application, and when
that happens I'd
Gwyn Evans wrote:
Does generification of the core make that much difference to a user of
the API? I've been focused on JDK 1.4, so didn't have a change to
look at Wicket 2 in practice.
Don't want to exaggerate, but once you start using Java 5 you don't want
to go back and you want all code
Chris Colman wrote:
The obvious benefit in such an approach is that your POJO model and the
services that you provide to implement business rules etc., remain
completely portable to different persistence engines - ie., no vendor
lock in.
well, i thought that was JPA was all about !?
No,
Hi,
I've not been able to follow the discussion on generics (simply too
much) but now that I've switched to 1.4-M3 I have a comment/question.
Generally I think wicket is going in the right direction regarding
generics...
Another (great) web application framework that I've used doesn't have
Sorry... I guess generics design has been discussed enough. /Anders
Igor Vaynberg wrote:
On Fri, Jul 18, 2008 at 4:52 AM, Anders Peterson wrote:
As it is now Component is not generified, but further down you introduce
generics to some components that you feel benefit from it. I think you
I used M2 and had no problem with it. When I heard talk about
decoupling the components and the models, for M3, I thought that
seemed a good idea.
Now I use M3. It works fine, but I think generics for components is
implemented upside down. I think M3 should have been M2 with generics
turned
My DropDownChoice always displays as if nothing is selected. Using it
works fine, but every time the page is (re)loaded the selection is reset.
wantOnSelectionChangedNotifications return true.
I have an older version of my app deployed (using an older version of
Wicket) that works as
) {
super.onSelectionChanged(newSelection);
...;
}
@Override
protected boolean wantOnSelectionChangedNotifications() {
return true;
}
});
Nothing strange... /Anders
Daan van Etten wrote:
On 17 sep 2008, at 14:55, Anders
there! /Anders
Anders Peterson wrote:
This is the code that creates the DropDownChoice:
myForm.add(new DropDownChoiceBLView(views,
this.getPortfolio().getViews(), new
ChoiceRendererBLView(toDisplayString)) {
@Override
protected void onSelectionChanged(BLView newSelection
Hi,
I'm using OnChangeAjaxBehavior with a TextField. The TextField is in a
table cell that is repeated using a ListView. When I change the value of
one of the TextFields more than one of the underlying models get updated
- the one that was supposed to be updated and all following in the list.
Here the code, html and Java fragments, for the tr. /Anders
Timo Rantalaiho wrote:
On Mon, 29 Sep 2008, Anders Peterson wrote:
I'm using OnChangeAjaxBehavior with a TextField. The TextField is in a
table cell that is repeated using a ListView. When I change the value of
one
Why can't all components always output that id? Or can't it be a global
option to turn it on/off for all components? Is there some situation
where you do not want that id? /Anders
Igor Vaynberg wrote:
like which ones?
-igor
On Fri, Oct 3, 2008 at 12:44 PM, Rob Sonke [EMAIL PROTECTED] wrote:
' was edited; therefore the refreshed components gets an
incorrect value. When/if I submit the form the usual (non ajax) way
everything is corrected.
/Anders
Anders Peterson wrote:
Here the code, html and Java fragments, for the tr. /Anders
Timo Rantalaiho wrote:
On Mon, 29 Sep 2008, Anders Peterson
What exactly does this stacktrace (below) mean?
In development, eclipse jetty, the application works fine. When
deployed (tomcat) the app cannot render login page (I suppose it can't
render anything).
/Anders
WicketMessage: Exception in rendering component: [MarkupContainer
[Component
Thank you, it was the security manager.
On Ubuntu Server it is turned on as a default. I turned it off by
editing the file /etc/default/tomcat6. Set TOMCAT6_SECURITY=no.
/Anders
On 11 maj 2009, at 10.24, Anders Peterson wrote:
What exactly does this stacktrace (below) mean
Hi,
Upgrading to wicket 1.5.1 from 1.4.18 my ajax updates stopped working.
I have a page with a form. Inside the form there is a repetition (ListView)
that among other things creates a text field for each item (ListItem). Each of
those text fields has an OnChangeAjaxBehavior set that should
, Anders Peterson wrote:
Hi,
Upgrading to wicket 1.5.1 from 1.4.18 my ajax updates stopped working.
I have a page with a form. Inside the form there is a repetition (ListView)
that among other things creates a text field for each item (ListItem). Each
of those text fields has
:marketWeight
But the HashMap containing parameter values ONLY contain this:
{instruments:0:marketWeight=[17.602]}
This results in me getting null as FormComponent input.
Anyone know what I've done wrong?
/Anders
On 2011-10-13 13:46, Anders Peterson wrote:
Here the (simplified) code that creates
, and it was in a
ListView so I had several of them.
I guess something related to replacing the name/id of a component changed from
1.4 to 1.5.
/Anders
On 2011-12-16 14:15, Anders Peterson wrote:
Hello again, I still have this problem... (been working on other things)
I've tracked
I have a related question. What should I do when the user logs out.
Currently I just set username to null and redirect to the original
login page. I feel I also should invalidate the session but that doesn't
work. Then I always end up with a Page Expired page. I'd like to
still end up with
login page, but get Page Expired.
/Anders
Martijn Dashorst wrote:
iirc:
setResponsePage(LoginPage.class);
setRedirect(true);
getSession().invalidate();
Martijn
On 1/13/08, Anders Peterson [EMAIL PROTECTED] wrote:
I have a related question. What should I do when the user logs out.
Currently I
conveniently invalidated.
Martijn
On 1/13/08, Anders Peterson [EMAIL PROTECTED] wrote:
Doesn't work for me...
I have a PageLink class with a onClick() method that looks like this:
public void onClick() {
super.onClick();
this.setRedirect(true);
this.getSession().invalidate
read my previous message closely you would have seen:
setResponsePage(LoginPage.class);
LoginPage.class instead of new LoginPage()
That generates the difference between a bookmarkable URL and a session
relative URL.
Martijn
On 1/13/08, Anders Peterson [EMAIL PROTECTED] wrote:
Then where do I
Anders Peterson wrote:
Is that the problem: Do I have to call
this.setResponsePage(LoginPage.class);
after
super.onClick();
?
Yes, that was it.
Thanks Martijn and Maurice!
/Anders
-
To unsubscribe, e-mail: [EMAIL
Hi,
I (sometimes) get a strange Exception. You can see the stacktrace in the
attached file.
The problem appears (sometimes) when I submit a form. Just displaying
data/pages is never a problem.
At first glance it seems I get a ClassCastException when doing
public static BLAppSession
That wasn't it. Just happened again... /Anders
Anders Peterson wrote:
No (don't know what it is).
I think maybe this problem was caused by the RunJettyRun plugin
picking up my wicket-1.3.0 jars that I had forgotten to delete from my
project. I did not reference those jars, but the files
, Feb 24, 2008 at 7:57 AM, Anders Peterson [EMAIL PROTECTED] wrote:
Hi,
I (sometimes) get a strange Exception. You can see the stacktrace in the
attached file.
The problem appears (sometimes) when I submit a form. Just displaying
data/pages is never a problem.
At first glance it seems I get
How far away is wicket with generics? /Anders
Martijn Dashorst wrote:
If you are depending on trunk and build your own Wicket versions,
please note that trunk is now Wicket 1.4 and will be used for the next
Wicket version.
If you wish to continue building 1.3 jars then switch your local
Hi,
I've got a problem when deploying my wicket application. I deploy to
Tomcat 5.5 on Linux.
The problem is that I get an OutOfMemoryError when viewing one
particular page. I can go straight from starting Tomcat to accessing
that page and get the error - there is no history. That kind of
Problem seems to be fixed...
I was building/deploying my application using wicket 1.3.3. Tomcat on
the deployment server had wicket-examples-1.3.0 installed. When I
removed that the problem disappeared.
/Anders
Anders Peterson wrote:
Hi,
I've got a problem when deploying my wicket
Eelco Hillenius wrote:
1) Generifying* Wicket
[x] Can best be done like currently in the 1.4 branch, where models
[x] Can best be done in a limited fashion, where we only generify
Both are acceptable to me
2) How strongly do you feel about your choice above?
[x] I definitively
31 matches
Mail list logo
