That discussion will not happen any time soon, first java 7 must be
released.. Then i guess 2+ or 3+ years will pass before java 7 is
widely used.
So i guess we can plan that discussion around 2011..
On 7/16/08, Ricky [EMAIL PROTECTED] wrote:
orginally said by Martijn:
We don't say that, but
Hi Timo,
thanks for your reply.
Anyway, if your intent to only validate when the textfield
loses focus? If it would be OK to validate on each keypress,
you could try using OnChangeAjaxBehavior in the TextField.
We are doing validation via Ajax, so we decided to not to validate on each
Extend one of the defaultcolumns, like propertycolumn, and override
onpopulateitem.
Something like this:
public void populateItem(Item item, String componentId, IModel model)
{
item.add(new Label(componentId, createLabelModel(model))
{
I've written some code that allow spring to validate objects for me using the
org.springframework.validation.Validator interface.
I've also got some code that maps the ValidationErrors back to wicket
fields.
The spring validators take an entire object rather than field by field. My
question
thanks for the pointers..
Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hi Guys
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez
Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with around 1
million
users, and a lot more over time. What could be great optimizing
points?
Daan van Etten wrote:
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great
On 16 jul 2008, at 09:54, Nino Saturnino Martinez Vazquez Wael wrote:
Daan van Etten wrote:
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez
Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with
It is exactly the opposite: keeping state serverside increases
performance. It makes it more expensive to scale out, but that is
about it.
Keeping state readily available at the server ensures you don't have
to send it across the wire, or have to reconstruct it at the server.
It consumes memory,
Hi Martijn,
On 16 jul 2008, at 10:19, Martijn Dashorst wrote:
It is exactly the opposite: keeping state serverside increases
performance. It makes it more expensive to scale out, but that is
about it.
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many
For wicket keeping server state gives you more performance, except maybe the
serialization penalty which is an overhead.
But if you have enough memory for your clients (the expense to scale out) it
is way faster
If you use bookmarkable/stateless pages then everything has to be
constructed on the
Hi Ned,
Here my 2 cents,
If you look at the Form.process method you'll see that only after
validating the model object is updated. There is no hook that you can
use to get a callback after the model object is updated. The only way
I see is to override the process method itself (which is not
Hi,
A quick mail to many thanks to the Wicket community for all it's support
in helping us to launch a new social news and bookmarking site,
www.roo10.com .
In addition to saying that the framework itself was fun and easy to work
with, a few comments on our experience of using Wicket to
IMHO whether state at the client helps hugely depends on the amount of
pages the user works with.
If the user hardly ever leaves that one single page, keeping state on
the client will help performance, provided the server does not need to
keep a copy of (all) that state. The latter deviates
Hi,
i wont create an application base with Qwicket examples.
I port all in maven2 project with eclipse, but when i run in eclipse
application i recived this exceptio:
STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
INFO - /geosdiSystem - Loading Spring root
Thanks Lars,
That's the same *conclusion* I had come to :)
I'll have to override process I think (provided thats what's setting the
form elements back to the backing model).
The validators and the domain objects live in a module that has no wicket
dependencies, and I am not in a position to be
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many clients, so I'd love to learn why it gives higher
performance at the server.
What is this data juggling you talk of? If you use
you have wicket 1.2 code somewhere on the classpath. Remove all
non-wicket 1.3 libraries from your application.
wicket.Initializer is no more.
Martijn
On Wed, Jul 16, 2008 at 11:26 AM, Francesco Izzi
[EMAIL PROTECTED] wrote:
Hi,
i wont create an application base with Qwicket examples.
I
On 16 jul 2008, at 11:34, Martijn Dashorst wrote:
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many clients, so I'd love to learn why it gives
higher
performance at the server.
Hi,
Everybody think happy thoughts, flowers, waterfalls, idle servers :-)
On Wed, Jul 16, 2008 at 11:34 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
In my opinion it depends on your use case, but in high-load
Hi
After starting my local Webpshere Application Server (6.1.0.15), running my
wicket application (1.3.4) in development mode, the ModificationWatcher
appears to devour memory, until eventually I get out of memory exceptions
(when my latest exception occured, my wicket instance was using 1.7GB
Hi everybody,
I have a strange problem when I use a AutoCompleteTextField. This component
works well, indeed it suggests words, but when I pass on a word to select
it, the page is scrolling down.
To be more unequivocal, look at the screenshot :
http://www.nabble.com/file/p18486597/totoyz5.jpg
Hello,
I am using wicket tree with swing DefaultMutableTreeNode.
In render node, i am writing the tree headers labels.
protected String renderNode(TreeNode node) {
TreeItem item = (TreeItem) ((DefaultMutableTreeNode)
node).getUserObject();
return item.getName();
So you mean every static image in my HTML will have to be converted to code
Basically we are having problems using any of the encoding strategies
because all of our background images and inline CSS images disappear
can this URL rewriting for resources be made to work with inline images
On Mon,
wicket has special support for that:
if (urlConnection instanceof JarURLConnection)
{
JarURLConnection jarUrlConnection =
(JarURLConnection)urlConnection;
URL jarFileUrl = jarUrlConnection.getJarFileURL();
In the Wicket Examples, there is an Editable TreeTable:
http://www.wicket-library.com/wicket-examples/
Then click ajax, then click Tree and Tree Table, then click the
Editable tree table link.
But using the TreeTable is more complex than using the ListView, and we
don't need the Tree structure -
Fabien D. schrieb:
I have a strange problem when I use a AutoCompleteTextField. This component
works well, indeed it suggests words, but when I pass on a word to select
it, the page is scrolling down.
do you use 1.3.4.?
cu uwe
--
THOMAS DAILY GmbH
Adlerstraße 19
79098 Freiburg
Deutschland
T
I have the same problem with 1.3.4.
I met this behavior when my page has a scrolbar. If there is no scrolbar,
there is no problem.
This is come from Wicket? CSS?...
Fabien D. wrote:
no 1.3.3, i will try with 1.3.4.
Uwe Schäfer wrote:
Fabien D. schrieb:
I have a strange problem
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
Million users per week/ month/ year/ decade? ;-)
Answer these questions for yourself:
1) On average, how many concurrent sessions will there be
The trick is based on a hidden iframe, like the following:
iframe id=upload_target wicket:id=upload_target name=upload_target
style=width:0px;height:0px;border:0 /iframe
form wicket:id=form0 target=upload_target
div id=upload-field-handler style=position: absolute; z-index: 100;
display: none
Daan van Etten wrote:
Yeah I know, problem are that our application are ajax heavy, and
stateless and ajax does not cope well I've heard..
Maybe not within Wicket, I know too little of Wicket to draw a valid
conclusion on that. But it is definitely possible.
Look for example at the
you will have to at least use wicket's type conversion validators
unless your beans only have string properties.
-igor
On Wed, Jul 16, 2008 at 2:30 AM, Ned Collyer [EMAIL PROTECTED] wrote:
Thanks Lars,
That's the same *conclusion* I had come to :)
I'll have to override process I think
Can't answser the Wicket side, but consider:
a) Swing is not thread-safe
b) it is often better to code your own TreeNode as a bridge to the
underlying reality (Wicket's models?); rather than using
DefaultMutableTreeNode, which is a full-blown model in itself
--
Michael Allan
Thanks for your mail:)
Eelco Hillenius wrote:
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
Million users per week/ month/ year/ decade? ;-)
We actually discussed this today:)
Answer
On Wed, Jul 16, 2008 at 8:00 PM, Michael Allan [EMAIL PROTECTED] wrote:
1. The user can seamlessly click into the application from external
sites, and click back out again.
1 a. A Web client is good for demonstrating a new application,
because it's convenient for casual users, who
I converted our project to 1.4 as an experiment. It's quite large (257 source
files). It was a bit tedious changing xxxModel to xxDefaultModel, etc, but
it wasn't too bad. I haven't fixed all the warnings though.
I think the design will benefit us and the conversion will be worth it. We
use this
this is actually a perfect example where generifying Component broke
down in 1.4m2. dataview does not use its model, it uses the
dataprovider which it stores as a field. so right now you can just say
new DataViewFoo and it will expect IDataProviderFoo and you are
free to attach any type of model
Hi,
In my resource file, I need a property expression to display the
toString() value of my model object. I've discovered that using ${}
works, but it seems like a bad hack to me. What's the correct way of
doing this?
Regards,
I ported all our projects to 1.4-m3 (from 1.4-m2).
It was quite large - about 500 source files. Everything
worked out nicely.
I can say, that I am very happy with actual generics style.
I think, that this is how generics should be applied in Wicket.
Good work!
Thanks to the Wicket team yet
Yep, cool. Thanks Igor.
Will see how I go :)
igor.vaynberg wrote:
you will have to at least use wicket's type conversion validators
unless your beans only have string properties.
-igor
--
View this message in context:
Your reason is a special instance of a much more general reason. Web
applications are much easier to deal with from a deployment perspective than
desktop applications. Also, there are firewall and security issues surrounding
access to central data repositories that web applications handle
Hello,
I successfully implement wicket-push in our wicket application...i just used
the example in the wicket-stuff...with the default configuration...i just
checked out and run it...then customized for our needs...
i think the mininum requirement is jetty 6.1.4 to run it
and it even run on
So this is how i solved it - basically preserving wickets functionality as
much as I could, and only changing it in the event i have a spring
validator.
on my AbstractForm i did the following:
public void setSpringValidator(Validator validator) {
this.validator = validator;
}
43 matches
Mail list logo
