2007/3/30, Toscano [EMAIL PROTECTED]:
countries = new DropDownChoice (country,
new Model() {
public List getObject() {
return getCountries();
}
}, getCountries(),
new
can you show us your code?
...
ah, sorry. this is the code i take it. just not in response to my
original post (at least on nabble).
There is possibly an even simpler solution using onAttach - overriding
it in WebPage:
onAttach()
{
commonInit();
init();
}
public void init()
{
That was whý I suggested that we could have another constructor that took an
Ichoicerender. There are tons of places in other wicket core components that
supply a constructor that takes the ichoicerender.
SO I think it should be ok? I would really like that ichoicerenderer would be
supported
I think one of your answer can be found in this thread...
http://www.nabble.com/XHTML-ContentType-problem-tf3362030.html#a9352755
On 3/29/07, Johannes Schneider [EMAIL PROTECTED] wrote:
Hi,
I am new to Wicket and want to use XHTML and validate the files. I use
IntelliJ Idea but I could not
I've got a simple option class (as i've seen in examples)p/
public class Option {
String key;
String value;
public String getKey() {
return key;
}
public void setKey(String key) {
this.key = key;
}
public
the ddc will try to set the Option on the model object.
public class Foo {
Option option;
}
form = new Form(form, new CompoundPropertyModel(new Foo()));
form.add(new DropDownChoice(option, imageList, new ChoiceRenderer(...));
This instructs Wicket to bind the value of the ddc to the option
radio and check do not take an ichoicerenderer because they do not need it.
they do not traverse over a list of choices and try to look one up, they
have the choice attached directly to them via imodel.
-igor
On 3/30/07, Nino Wael [EMAIL PROTECTED] wrote:
That was whý I suggested that we
/**
* Whether this component's onSelectionChanged event handler should
called
* using javascript if the selection changes. If true, a roundtrip will
be
* generated with each selection change, resulting in the model being
* updated (of just this component) and onSelectionChanged
Right now, if I have a localized property file (e.g. Welcome_de.properties),
it seems I must have all resource keys defined in it.
I would prefer to have the localizer be smart enough to fallback to the
default properties file (e.g. Welcome.properties) if a property is not
present in the
Does anyone have any good recommendations for how I get started with second
level session storage in Wicket 1.2, via persistence to disk, for (1) old
page versions and (2) entire sessions when session expires? We can't move to
1.3 or 2.0, so I'm trying to get an understanding of what my options
second level store involved some pretty heavy refactoring of the internals
afaik, so i dont think you will get it working under 1.2
-igor
On 3/30/07, dukejansen [EMAIL PROTECTED] wrote:
Does anyone have any good recommendations for how I get started with
second
level session storage in
I just checkout the branches/wicket-1.x.
After I create the jar file with mvn -Dmaven.test.skip=true package
and attach the library, jetty always return these exception:
org.mortbay.util.MultiException[java.lang.ClassNotFoundException:
wicket.protocol.http.WicketFilter]
at
Thanks Igor.
That's what I was doing but I didn't manage to grab my feedback borders.
It's now done like this :
target.addComponent(formComponent.getParent());
Cheers
ZedroS
On 3/28/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
use a visitor to visit all form component feedback borders and add
Not even just writing my own session store that hides the complexity of the
persistence? Or is that the point your making, that doing so would be
difficult/impossible based on the Wicket 1.2 code?
I feel like I've read about 1.2 having ability to do it, just not easily. Am
I mistaken?
Hello,
I am getting 'Stack Overflow' error from the browser while selecting Date
from Date picker UI. Please help.
Thanks,
sraj
samyem wrote:
So far so good. It got rid of the issues with stack overflow and the other
previous issues has not surfaced.
Thanks,
Samyem
Matej Knopp
i think a lot of internal api changed to allow for this to work well. for
example pagemap is now an interface, its not in 1.2. things like that. feel
free to give it a go though, i didnt do that refactor so im not 100% sure of
what im talking about here :)
-igor
On 3/30/07, dukejansen [EMAIL
What version of Wicket are you using? And if it is not the latest
1.2.x or 1.3, please upgrade.
Eelco
Hello,
I am getting 'Stack Overflow' error from the browser while selecting Date
from Date picker UI. Please help.
Thanks,
sraj
1.2.3.
Thanks,
Shyla
Eelco Hillenius wrote:
What version of Wicket are you using? And if it is not the latest
1.2.x or 1.3, please upgrade.
Eelco
Hello,
I am getting 'Stack Overflow' error from the browser while selecting
Date
from Date picker UI. Please help.
Thanks,
I would recommend using 1.3. Some people of the team (including me)
are using 1.3 for a project that needs to be live bigtime medio July.
So, 1.3 has to be good enough to run production systems by then (and
in fact we're running a production server with a 1.3 snapshot right
now and that works
Yeah, please upgrade to a new version. You can download them here:
http://sourceforge.net/project/showfiles.php?group_id=119783package_id=130482
or you can get the latest snapshot from here:
http://wicketstuff.org/maven/repository/wicket/wicket/1.2-SNAPSHOT/
We want to do a 1.2.6 release soon if
Thank you! I will do that. Also, I changed my mode in web.xml to DEPLOYMENT.
-Shyla
Eelco Hillenius wrote:
Yeah, please upgrade to a new version. You can download them here:
http://sourceforge.net/project/showfiles.php?group_id=119783package_id=130482
or you can get the latest snapshot
Try mvn clean first.
Eelco
On 3/30/07, Chan Man Kam [EMAIL PROTECTED] wrote:
I just checkout the branches/wicket-1.x.
After I create the jar file with mvn -Dmaven.test.skip=true package
and attach the library, jetty always return these exception:
Yeah, and the concept of a session store is new to 1.3 too. If you
want to do something like that in 1.2 you should start with a custom
session, and patch the setAttribute/ getAttribute methods for your
needs. With a bit of creativity you should be able to come a long way,
but the refactorings of
I don't know... you might be better off just creating your own
components here. But I'd also like to know the opinions of other
developers here...
Eelco
On 3/30/07, Nino Wael [EMAIL PROTECTED] wrote:
That was whý I suggested that we could have another constructor that took an
Ichoicerender.
It already does work like that.
http://cwiki.apache.org/WICKET/i18n-and-resource-bundles.html
Regards,
Erik.
dukejansen wrote:
Right now, if I have a localized property file (e.g. Welcome_de.properties),
it seems I must have all resource keys defined in it.
I would prefer to have the
The same exception occurred.
Man Kam.
Eelco Hillenius wrote:
Try mvn clean first.
Eelco
On 3/30/07, Chan Man Kam [EMAIL PROTECTED] wrote:
I just checkout the branches/wicket-1.x.
After I create the jar file with mvn -Dmaven.test.skip=true package
and attach the library, jetty always
Hi everyone!
I read on the devel list that you're voting about merging the fix to issue
wicket-371 into 1.2.6. It would really help me if you did. It would fix a
problem in the app I'm developing, which currently requires a workaround.
The context: I'm using statefull non-singleton beans,
Hi all,
I need to show errors for form fields next to the fields themselves. I have
tried with FormComponentFeedbackIndicator/Border, which just worked fine,
but the fact is that I need to affect the background of both the field and
its error message (for example, turning it to red) while these
If you use borders, you can wrap the form components with elements for
which you set the class or style attribute, and you can do this with
CSS, right?
Eelco
On 3/30/07, Carlos Pita [EMAIL PROTECTED] wrote:
Hi all,
I need to show errors for form fields next to the fields themselves. I have
Yes I would indeed also go for 1.3. I use it in one live system now. The
trick right now is just to think before upgrading to latest snapshot all the
time. I'm using a version from before the big backports (Model) from around
18. march and I'm not going to upgrade again until the dust has settled
Not sure if I understand you. Precisely what I want to do is to wrap the
components (field+feedback... even the label) as you say, but depending on
the feedback status I would need to: (i) show/hide the wrapper border or
(ii) change its style attribute. I would like to do this programmatically,
pseudocode
class myfeedbackborder extends formcomponentfeedbackborder {
public void onComponentTag(tag) {
if (!getfeedbackmessages().isempty()) {
tag.put(class,error);
}
}
}
div.error input { background-color:red;}
-igor
On 3/30/07, Carlos Pita [EMAIL PROTECTED] wrote:
Not
Thanks :). Every time I think I really catch up with how powerful wicket is,
you show me I'm wrong.
On 3/30/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
pseudocode
class myfeedbackborder extends formcomponentfeedbackborder {
public void onComponentTag(tag) {
if
I too am working on a system which must go live to a large user base early to
mid July.
What kind of confidence can I have that 1.3 be stable enough by then? Are we
talking 95%, 75%, or 50%?
I need some of the 1.3 functionality but once I commit to move to 1.3 I'm
not going to have time to go
On 3/30/07, dukejansen [EMAIL PROTECTED] wrote:
I too am working on a system which must go live to a large user base early to
mid July.
What kind of confidence can I have that 1.3 be stable enough by then? Are we
talking 95%, 75%, or 50%?
95% or more.
I need some of the 1.3 functionality
Okay, here's my opinion:
People have been using Wicket for years now and this is the first bug
of this type I have heard of. I am very reluctant attempt any sort of
generic framework-level fix to the semantics of Java object
construction
(regardless of how anyone feels about the practices
On 3/30/07, Chris Colman [EMAIL PROTECTED] wrote:
Java objects construct the way that they do and we use Java object
constructors because we like that simplicity. Your bug is reported
and
will be fixed.
Any time schedule for that?
the fix is in svn
-igor
37 matches
Mail list logo
