All,
I was a little too quick placing ASL2 headers in all the .java files in 2.0.
When looking trough 1.x I found some thirdparty code. I have therefore
looked through all java files which doesn't have a ASL2 header but something
else and the following came up:
On 11/16/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
These are public domain, taken from Doug Lea's concurrent utils. Sun
has adopted these for Java 1.5. So for 1.x they need to be there, 2.0
they could be removed in favor of the JDK provided
java.util.concurrent collections.
I don't know
yeah, but you forgot to put the appropriate first (and following) page param
to it:
/path/to/page2 - these are the prePageParams for me here, that i grab
each time i use a new one...
so you manually change your link to be at the mountpoint...
URLs are build like that: preParams / postParams
so you manually change your link to be at the mountpoint...
Where do you manually change it?
I was just pointing out that the 2 mount params must be in sync in wicket
else it doesn't work by default. If somebody makes a mistake an configures
it like i said
it goes wrong. The url will be
Hi,
I'm having a very annoying issue with ListView when used in a
form, with reuseItems set. Apply the attached patch to the
wicket-examples: it adds a link to remove an item in the list of
lines in the forminput example. Now start the patched examples
and go to
Hey guys,
I hope it is not too late to make some minor suggestions for 2.0. I'm sorry,
I noticed that you switched to apache mailing list too late...
1. Please remove 'null' and 'nullValid' properties from
wicket/Application.properties The names are too generic and used by Dropdown
controls.
2.
You can override keys in any component.
Please see here:
http://cwiki.apache.org/WICKET/i18n-and-resource-boundles.html
Alexei Sokolov wrote:
1. Please remove 'null' and 'nullValid' properties from
wicket/Application.properties The names are too generic and used by
Dropdown
controls.
So
That why it is dangerous to have the mount(string,coder)
method and
why it is removed in wicket 2.0 (and it will stay that way)
ok, basically this comes to: you never got it working/ dont
understand
it so stripped it...
what a stupid thing to say considering it was
On 11/16/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
what a stupid thing to say considering it was probably johan
that wrote that
part of the code in the first place. you wont be making any
friends here
saying things like these.
i replied to his statement - and if im on a black list
