seems there is a problem with how application.configure() works.if you call configure("deployment") from application.init() it doesnt really help, because a webapp.internalinit() runs before and already called configure("development") (if you did not speicfy deployment through
web.xml or system pr
Still, does the polling have that effect?
On 2/18/06, Andrew Lombardi <[EMAIL PROTECTED]> wrote:
> Yeah, I agree. I found the problem, in 1.2 versions, the servlet
> variable has been changed to "configuration:deployment/development"
> instead of "deployment:true/false".
>
> So I was checking in
Yeah, I agree. I found the problem, in 1.2 versions, the servlet
variable has been changed to "configuration:deployment/development"
instead of "deployment:true/false".
So I was checking in my base application class for deployment servlet
var, and calling configure("deployment") .. wasn't
Ok, I think this is the right fix (it's in HEAD now):
public final void onValidate(final FormComponent formComponent, final
String value)
{
// Check value only if form component is enabled
if (!formComponent.isEnabled())
{
Uh, another potential nastier problem is that you put in
disabled="disabled" there yourself either directly or with an
attribute modifier. In that case, the old code makes sense, though it
is not very generic. H... what should we do...
Eelco
On 2/18/06, Eelco Hillenius <[EMAIL PROTECTED]> wro
A potential, theoretic issue can be that isEnabled is based on an
algoritm in such a way that it was false during rendering, but true
now that the post back comes in. Or the other way around. But I think
that is too theoretical to worry about, and even if it would show up
sometime, somewhere for an
I just took a look, and the 'fix' that isInputNullable was wrong; it
was fixing the wrong problem in the first place. I removed that method
again, and RequiredValidator now looks like:
public final void onValidate(final FormComponent formComponent, final
String value)
{
That sounds pretty crazy. Did you turn off template reloading? That
would be the first thing to try, and actually wize in a production
environment anyway. /If/ that helps, we might have something that
should be done differently there.
Eelco
On 2/18/06, Andrew Lombardi <[EMAIL PROTECTED]> wrote:
When deploying one of our wicket-developed applications to our
production linux server, we've been seeing something very odd, maybe
someone can shed some light. This morning I awoke to error messages
in our Resin app server logs about "Too many open files". Checking
the max value, it was
Latest RequiredValidator only works for FormComponent.isInputNullable() that return true.So basically RequiredValidator no longer work for FormComponent like DropDownChoice .
I have one use case: the choices List may return zero size, and by
default, DropDownChoice will insert a Choose One... for
I think I got the problemfirst, the test I provided is wrong, the 2nd FormTester should instantiated withoutfill blank string on FormComponets, or it will overwrite all FormComponent's input. //
disable filling blank string for all FormComponents FormTester formTesterContinue = tester.newFormT
#1 is my vote too.
Regards,
Abdullah
--- Cameron Taggart <[EMAIL PROTECTED]> wrote:
> I vote for #1. I am already running Java 5 and it sounds like a 1.3
> release with the constructor change may delay work on Java 5.
>
> cheers,
> Cameron
>
> On 2/16/06, Eelco Hillenius <[EMAIL PROTECTED]> w
On Feb 16, 2006, at 5:33 PM, Eelco Hillenius wrote:
1. Give me the constructor change and the Java 5 functionality in one
pass (Wicket 2.0)
+1
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?
2/ +1 (separate releases).
./alex
--
.w( the_mindstorm )p.
On 2/17/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> This is a non-binding (the developers ultimately decide) call votes
> concerning whether we should fold the upcomming constructor changes
> with our move to Java 5 or n
+1 on option 1.On 2/18/06, Cameron Taggart <[EMAIL PROTECTED]> wrote:
I vote for #1. I am already running Java 5 and it sounds like a 1.3release with the constructor change may delay work on Java 5.cheers,CameronOn 2/16/06, Eelco Hillenius <
[EMAIL PROTECTED]> wrote:> Hi all,>> This is a non-bindi
I vote for #1. I am already running Java 5 and it sounds like a 1.3
release with the constructor change may delay work on Java 5.
cheers,
Cameron
On 2/16/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> This is a non-binding (the developers ultimately decide) call votes
> concerning
It looks like a namespace issue. We recently started using a kind of
namespace for various "resources" including url parameter. Reason:
avoiding issues due to users using wicket "preserved" names.
Juergen
On 2/18/06, Ingram Chen <[EMAIL PROTECTED]> wrote:
> I upgrade to latest CVS, but found beha
I upgrade to latest CVS, but found behavior of FormTester changed.below is small test case for wicket.util.tester.WicketTesterTest:public void testCreateBook_submit() throws Exception
{ MyMockApplication tester = new MyMockApplication(); tester.startPage(CreateBook.class); FormTester formT
also,the label will not be updated because its model is constant.to have it updated do thisnew Label("counter", new PropertyModel(this, "count")); and add a int getCount()also in the onclick handler remove these two lines, they are not necessary and will break your code:
RequestCycl
Always start with issuing clean first when working with maven. Like
'mvn clean install'.
Eelco
On 2/18/06, Mats Norén <[EMAIL PROTECTED]> wrote:
> Yes, I found the problem. Maven2 didn't pick up on the change to the
> src code. Weird.
>
>
> On 2/17/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
You should check your Wicket version. It looks like you compiled your
code against a different version of Wicket then what you include in
your webapp. Also check for double classpath entries.
Eelco
On 2/18/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> What may be wrong with these code
>
> pu
What may be wrong with these code
public class MyAjaxPage extends WebPage {
private int count = 0;
public MyAjaxPage(){
add(counter = new Label("counter", String.valueOf(count)));
add(new AjaxLink("ajlink") {public void onClick(AjaxRequestTarget target) { // Increme
2. Do the constructor change in a seperate release (Wicket 1.3) andput Java 5 in the next (Wicket 2.0)I would like to see the constructor change as soon as possible, as it is a bit of a thorn in the paw when using wicket. Watching the cvs commits, the rate of development on wicket is impressive. I'
I just asked for real world wicket-driven applications, because it surely
would make it much easier for me to understand how to do some things in wicket.
Thanks, Martijn, I'll try to download and take a look at it.
--
Tom
Ayodeji Aladejebi schrieb:
wat du u mean by real world driven?...wicket
we do it the other way around.just do this in youre example:[Form Code]
Form myform = new Form("myform", new CompoundPropertyModel(new Data()));
TextField txt = new TextField("myprop");
myform.add(txt);
[/Form Code]
myprop id is automaticaly mapped to youre model property mypropjohanOn 2/18/06, Ay
wat du u mean by real world driven?...wicket i believe is still evolving heavily and most applications being built on it are probably evolving along. So maybe it will take some (not-too-long) time before u see real-world projects spewing out from wicket.
On 2/18/06, Tom S. <[EMAIL PROTECTED
Tom,
Your question is hard to answer, as many companies that are developing
applications don't want you to take a look at their code.
Open source development takes a special type of person, one who is
willing to spend his/hers free, spare time to develop such
applications. This is a rather rare b
Since there wasn't any response at this question, I'll try it again:
Are there any real-world wicket-driven applications available for
investigation? Is there anybody trying to create something like a
issue-tracker or something similar?
Tom
--
What sort of application data is automatically stored in the wicketservlet's HttpSession (for simplicity, assume that models are not
detachable).First youre wicket session object (and everything you put in it when you subclass it) is stored in the session.Second are the pagemaps, the default one an
i am currently fixing this so that you can decide what the context path must beapplication.getApplicationSettings().setContextPath("")will set it to use the root (what you use from the outside)
johanOn 2/17/06, Al Maw <[EMAIL PROTECTED]> wrote:
Timo Stamm wrote:> I have a proxy server:>http://p
Hello,
Just another small suggestion as regarding future Java5 directions of Wicket.
I know Wicket generally may not be planning to use annotations but i just want to know the limitations of having stuff like this in some future Wicket version especially in the FormBindingToModel Situations.
Yes, I found the problem. Maven2 didn't pick up on the change to the
src code. Weird.
On 2/17/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> Somehow it seems that the code is a bit out of sync
> Or not compiled cleanly.
>
> Please make sure that you do compile everything from the start.
>
> If
32 matches
Mail list logo
