if (parent instanceof IAlternateParentProvider)
{
this.parent = ((IAlternateParentProvider) parent).get*Alternate*Parent();
}
else
{
this.parent = parent;
}
Just a small typo ;-)
I like this one.
Martijn
On 9/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> While starting to removing
On 9/15/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> this is exactly the interface i described earlier in this thread, and yeah
> it will work for this usecase as well even though i explained another one.
>
> you just have to be careful to provide the page as the parent when the
> border componen
Thanks, the source code I checked in seems to be ok.
Juergen
On 9/15/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> if (parent instanceof IAlternateParentProvider)
> {
> this.parent = ((IAlternateParentProvider) parent).get*Alternate*Parent();
> }
> else
> {
> this.parent = parent;
> }
>
> J
it works for this _very_ simple usecase. some usecases ive hit recently that i wanted to implement but couldnt were a bit more complex and you really need to know more about what you are working on. now that i think about it, model is really not needed. i think getAlternateParent(Class clazz, Strin
Are you sure the border page use case and the ones you encountered are
similar in nature? I know we talked about re-parenting etc. but I
think it is different as we don't allow to re-parent, we just provide
an alternate parent to the components constructor and there is only
one point in time when t
What other types of components would you like to see? How would you all like to see the data stored?Would you like te see a relatively simple database or a content repository like the one described in the JSR-170?
Ted & Rick On 9/14/06, Nick Heudecker <[EMAIL PROTECTED]> wrote:
One project we did a
yes, i understand these are two different usecases, and we do need them both. the reparenting we can save for later or for another thread altogether. i have been thinking about this interface for a long time, here is a note i keep for myself in gmail
have some IParentLocator {
Component getTruePare
argh! i was laying down with my eyes closed thinking about this and couldnt fall asleep!i remember the usecase better nowbasically i had a section border for my bean panel. when a form component was added to the border i needed to insert a panel in between so the form component would have the appro
Sorry that it comes across as resistance, I tend to keep on asking
questions when I don't understand it. And when I don't understand it
than I'm probably a little bit resistance to change it.
Please correct me if I'm wrong but in your example Class c ==
this.getClass() (== BeanSection.class) and i
Oke thanks. We'll definitely look into that. Do you know if there are any implementation of the JSR-283? Because this is the most current version of the JCR specification.Ted
On 9/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 9/15/06, Ted Roeloffzen <[EMAIL PROTECTED]> wrote:> What other typ
Ted Roeloffzen wrote:
> Oke thanks. We'll definitely look into that.
> Do you know if there are any implementation of the JSR-283?
> Because this is the most current version of the JCR specification.
Isn't JSR 283 still under development? Anyhow, Jackrabbit will most
likely stay up to date as the
On 9/15/06, Ted Roeloffzen <[EMAIL PROTECTED]> wrote:
> What other types of components would you like to see?
> How would you all like to see the data stored?
> Would you like te see a relatively simple database or a content repository
> like the one described in the JSR-170?
>From what I read, us
Feature Requests item #1559384, was opened at 2006-09-15 15:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684978&aid=1559384&group_id=119783
Please note that this message will contain
Bugs item #1559387, was opened at 2006-09-15 16:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1559387&group_id=119783
Please note that this message will contain a full copy
On 9/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
Sorry that it comes across as resistance, I tend to keep on askingquestions when I don't understand it. And when I don't understand itthan I'm probably a little bit resistance to change it.i was just tired, it was way too far into the am :)
Hi,
Couple of days ago I've removed the disabling of component render check
from AjaxRequestTarget, as it seemed not to be necessary anymore
(Page#checkRendering(component) seemed to work well).
Now I came across a component that has children in wicket:head. The
render check fails, because hea
I guess. In the end it is still a debug tool, that should help track
down things instead of being in the way. Maybe Juergen has an opinions
about this?
Eelco
On 9/15/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Couple of days ago I've removed the disabling of component render check
> fro
> move IModel.getNestedModel() to IWrapModel.getNestedModel()
>
> rewrote/simplified some model classes (like CompoundPropertyModel) to
> implement IModel directly. a lot of our impls extended abstract
> implementations and yet overrode all the methods anyways, so i rewrote them
> to implement IMod
Hi,
When deploying a Wicket application in DEVELOPMENT mode with only
JARs in WEB-INF/lib (no WEB-INF/classes), and templates included
in JARs, the number of file descriptors increases steadily,
leading to an OS error: « Too many files open ».
When turning configuration to DEPLOYMENT,
Most of the display tag examples do not work anymore since the recent
(model or resolver?) changes. Also, my examples for the chapters I'm
working on for Wicket In Action is broken. I'm using a
PropertyListView, and the exception I'm getting is similar to the one
that wicket.examples.displaytag.Exa
I also ran into this problem.On 9/15/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
Hi,When deploying a Wicket application in DEVELOPMENT mode with onlyJARs in WEB-INF/lib (no WEB-INF/classes), and templates includedin JARs, the number of file descriptors increases steadily,
leading
Checked one fix in that solves some problems CompoundPropertyModel
had. Most of displaytag examples are still broken though, for various
reasons it seems.
Eelco
On 9/15/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Most of the display tag examples do not work anymore since the recent
> (model
22 matches
Mail list logo
