Hi,
I have compiled the wicket sources and when I try to start tomcat, I get the error "Error loading previous sessions" and an invalidClassException. While this goes away if I use the same version of JDK for my build and tomcat (I believe this has to do with the serialVersionUID. could someon
ahhh that one ;)That is not needed for a alpha version if you ask me. Because it is really an internal thing.I will work on it the comming weeks (maybe together with eelco of JL when i am in seattle)johan
On 9/26/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i mean the serialization thing where you
i mean the serialization thing where you walk the model object and create a property map so that we can have working model object sharing.-IgorOn 9/26/06,
Johan Compagner <[EMAIL PROTECTED]> wrote:
do remind me, what is that model walking thing?I did fix a few things. But what things are now still
do remind me, what is that model walking thing?I did fix a few things. But what things are now still open things? You did move the getNestedModel right?And get rid of the stack of property models?Or do you mean with model walking the thing to get the "real" model?
johanOn 9/26/06, Igor Vaynberg <[E
do you think you will have the new model walking thing done soon? would be nice to have that in the alpha and let it get lots of exposure.-IgorOn 9/26/06,
Johan Compagner <[EMAIL PROTECTED]> wrote:
Yes put an alpha as soon as possible out of the doorThings change after that but that is the idea.jo
Yes put an alpha as soon as possible out of the doorThings change after that but that is the idea.johanOn 9/26/06, Igor Vaynberg <
[EMAIL PROTECTED]> wrote:after juergen and i (but mostly juergen) figure out this border+ialternateparent thing i think all the major functionalities will be there.
-Ig
after juergen and i (but mostly juergen) figure out this border+ialternateparent thing i think all the major functionalities will be there.-IgorOn 9/26/06,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hey devs,When are we going to put our first 'official' alphas/ betas out?Eelco-
Hey devs,
When are we going to put our first 'official' alphas/ betas out?
Eelco
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on
I don't mind, but what would be the best way of doing this?
Currently, component#renderHead is in charge of deciding whether to
render header or not. Is this also the place of marking header
components as rendered even though they have not been really rendered?
I'm not sure, doesn't seem so to
If we do that we can as well as remove the flag completely, because it
would rendere it useless then.
The flags purpose is to prevent writing header contribution to ajax
response for components, whose header contribution has already been made
(so that we reduce the size of ajax response).
The
Not sure. Why not reset the flag of all children at the beginning of
each render cycle. I remember we did that some time before.
Juergen
On 9/26/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> On 9/26/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> > There's a problem with panel that have component
Ahh, I should have read it more carefully. But I still don't like to
basically disable all tests for children of containers.
Can't we either mark them as being rendered if the flag is true or
change the use check in a way that it only ignores head child if
head-flag is true.
Juergen
On 9/26/06,
On 9/26/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> There's a problem with panel that have components in wicket:head and are
> rendered using ajax.
>
> The problem is that first time, the wicket:head is rendered. But any
> subsequent call to component.renderHead() is ignored, because the head
> ha
On Tue, 2006-09-26 at 00:04 -0700, Igor Vaynberg wrote:
> what we need is to come up with a form submission lifecycle listener
> interface that
> FormComponent will implement and other components can implement.
>
> maybe something like
>
> IFormListener {
> void validate();
> void updateModel();
-1 for adding this to the core, this is a pretty big hack imho. all this just to get the updatemodel() callback.i say this is a hack because the thing itself is not really a form component, it doesnt support validators itself because it never has input.
what we need is to come up with a form submis
Does this feel right?
new Model(defaultMinimumValue())
What happens if the model object changes? How do you propagate the new
value to form components?
-Matej
Janne Hietamäki wrote:
> This mail is originally from wicket-user, but I reply here to get
> more attention.
>
> This looks pretty el
16 matches
Mail list logo
