Re: disabling of AjaxSubmitLink
Matej Knopp-2 wrote: > > It is already fixed in 1.3. > > -Matej > Thanks Matej. I explored the source of Wicket 1.3 and picked up the solution from there. wheleph -- View this message in context: http://www.nabble.com/disabling-of-AjaxSubmitLink-tf4712370.html#a13483161 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
For the AutoCompleteTextField I think it would make sense to never store the page and simply make respond(target) final so that the can not be changed. Does anyone really want to change the page state for every key press? If so then that would seem to be the exception rather than the rule. On 29 Oct 2007, at 18:11, Matej Knopp wrote: Problem is that we can't do this by default. The behavior may change the page / component and we can't detect it. Then people would start complaining why they changes aren't preserved. This could lead to bugs that are very hard to track. As I said, in the next version, we'll probably have more elegant way to prevent page serialization, however it will still be on- demand only, not by default. -Matej - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
Problem is that we can't do this by default. The behavior may change the
page / component and we can't detect it. Then people would start
complaining why they changes aren't preserved. This could lead to bugs
that are very hard to track.
As I said, in the next version, we'll probably have more elegant way to
prevent page serialization, however it will still be on-demand only, not
by default.
-Matej
John Patterson wrote / napísal(a):
I have just made the changes you suggested and it seems to work. I
added the metadata in response(target)
protected void respond(AjaxRequestTarget target)
{
super.respond(target);
RequestCycle.get().setMetaData(UNTOUCH_PAGE_KEY, Boolean.TRUE);
}
Perhaps this could be incorporated into the AutoUpdateBehaviour and the
metadata checked for somewhere in wicket core rather than my Page subclass.
John
On 29 Oct 2007, at 17:27, Matej Knopp wrote:
I doubt it would prevent the page from being serialized. Versioning
doesn't spot all changes to page (e.g. setting a property) so we can't
rely on it, therefore we serialize it on every request.
However, if you really want to get around the serialization for
certain cases, you need to call Session.untouch(page) before
Session.requestDetached() is called.
I think calling it from Page.onDetach() should work. So you can set a
request cycle metadata if you don't want the page to be serialized and
then check for the meta data in page.onDetach().
-Matej
Igor Vaynberg wrote / napísal(a):
autocomplete.setversioned(false) do it?
-igor
On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote:
Hi,
I am using the AutoCompleteTextField and can see that every keystroke
causes the entire page to be serialised and stored which seems a bit
excessive. Is there anyway to say that the page has not changed and
so don't store it?
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
I have just made the changes you suggested and it seems to work. I
added the metadata in response(target)
protected void respond(AjaxRequestTarget target)
{
super.respond(target);
RequestCycle.get().setMetaData(UNTOUCH_PAGE_KEY, Boolean.TRUE);
}
Perhaps this could be incorporated into the AutoUpdateBehaviour and
the metadata checked for somewhere in wicket core rather than my Page
subclass.
John
On 29 Oct 2007, at 17:27, Matej Knopp wrote:
I doubt it would prevent the page from being serialized. Versioning
doesn't spot all changes to page (e.g. setting a property) so we
can't rely on it, therefore we serialize it on every request.
However, if you really want to get around the serialization for
certain cases, you need to call Session.untouch(page) before
Session.requestDetached() is called.
I think calling it from Page.onDetach() should work. So you can set
a request cycle metadata if you don't want the page to be
serialized and then check for the meta data in page.onDetach().
-Matej
Igor Vaynberg wrote / napísal(a):
autocomplete.setversioned(false) do it?
-igor
On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote:
Hi,
I am using the AutoCompleteTextField and can see that every
keystroke
causes the entire page to be serialised and stored which seems a bit
excessive. Is there anyway to say that the page has not changed and
so don't store it?
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: updating components on Page from ModalWindow's internal Page's components
search the list for "updating images using ajax". It should give about
5-10 threads easily.
And this finds:
http://issues.apache.org/jira/browse/WICKET-939
Martijn
On 10/30/07, Kirk Israel <[EMAIL PROTECTED]> wrote:
> This might well be the problem.
> How do you explicitly postpend something to the URL of a Wicket Image?
> The URLs we've been using are autogenerated, and my Google mojo is
> failing me... it doesn't have anything to do with .forURL(), does it?
>
> On 10/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > Not sure if it is relevant, but to update images using ajax you need
> > to generate a unique URL by adding a timestamp or random number to it.
> >
> > Martijn
> >
> > On 10/29/07, Kirk Israel <[EMAIL PROTECTED]> wrote:
> > > I'm still having the fundamental problem of an Image refusing to
> > > update. (A coworker suggested that it might be that I wasn't (yet)
> > > updating the underlying model that the page was drawing from, which
> > > didn't "smell" like the problem to me, since I could see the
> > > component-based updating I thought I was doing, but I put in that
> > > change of updating the model, but still I can NOT get the image part
> > > of the page to update.) The Label subcomponent of the component is
> > > updating fine, but, the ImageComponent (a wrapper to a Wicket Image)
> > > seems as fix'd as the north star.
> > >
> > > I'm working with my own MediaComponent class. It has one of our
> > > ImageComponent, added thus:
> > > mImageComponent = new
> > > ImageComponent("mediaimage",mResource,pClassStyle);
> > > mImageComponent.setOutputMarkupId(true);
> > > add(mImageComponent);
> > >
> > > (the mResource here is our MMSDataResource which extends Wicket's
> > > DynamicImageResource )
> > >
> > > Then when it comes time to update w/ the MMSDataResource passed back
> > > from the ModalWindow, I do this:
> > > ImageComponent newImageComponent = new
> > > ImageComponent("mediaimage",mResource,mClassStyle);
> > > newImageComponent.setOutputMarkupId(true);
> > > mImageComponent.replaceWith(newImageComponent);
> > > mImageComponent = newImageComponent;
> > > pTarget.addComponent(MediaPanel.this);
> > >
> > > i can add a pTarget.addComponent(mImageComponent); to no avail; if I
> > > put it before the swap so the reference is to the "old"
> > > mImageComponent, it rightly complains, and doesn't make a difference
> > > coming later... I think adding the MediaPanel itself means the
> > > imageComponent inside of it gets redrawn via Ajax too.
> > >
> > > So I see that MMSDataResource's getImageData() is NOT being called by
> > > DynamicImageResource for the Ajax re-render. I see the whole
> > > MediaPanel getting redrawn in the Ajax debug window, but apparently
> > > the Image reference from ImageComponent is the same old thing.
> > >
> > > I know there are a few places in my group's code that I might be the
> > > actual source of the problem, but can anyone see if I'm doing
> > > something wrong? Can't you swap in a new subcomponent during an
> > > AjaxRequestTarget-driven update? Is there a likely culprit, or
> > > something else that needs to be explicitly added to the
> > > AjaxRequestTarget ?
> > >
> > > Thanks...
> > > Kirk
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Buy Wicket in Action: http://manning.com/dashorst
> > Apache Wicket 1.3.0-beta4 is released
> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
On 10/30/07, John Patterson <[EMAIL PROTECTED]> wrote:
>
>
> On 29 Oct 2007, at 17:37, Eelco Hillenius wrote:
> /
> Also, I was surprised to find that instances of image were stateful
> if I used the constructor Image(String, String) and I had to override
> the getStatelessHint.
yes that looks like a bug
because i you just give a path then this is called:
loadStaticImage(component.getModelObjectAsString());
that makes a ResourceReference
but in bind() we also create again the resource:
// Then dereference the resource
resource = resourceReference.getResource();
thats a bit weird why we do that there.
because the resource shouldn't be used if there is a resource reference,
because
the url to the shared resource is generated:
*
if* (resourceReference != *null*)
{
// Create URL to shared resource
url = RequestCycle.*get*().urlFor(resourceReference, resourceParameters);
}
i guess the:
*public* *final* *boolean* isStateless()
{
*return* resource == *null*;
}
could be reversed: return resourceReference != null
Re: AutoCompleteTextField excessive serialisation
Maybe for very specific ajax cases that could work
But most of the cases ajax updates state on the server side
that is then translated again to the client.
If there is anything for example that is replaced or created new a none
stateless page wouldnt work
because you can't recreate the exact same page
the auto complete could be the exception if the only thing that is its input
is the field itself.
johan
On 10/30/07, John Patterson <[EMAIL PROTECTED]> wrote:
>
> Nope. It looks like the logic to store the page is in
> SEcondLevelCacheSessionStore and it always stores pages that were
> 'touched' that are not stateless.
>
>
>if (!page.isPageStateless())
>{
>String sessionId = getSession().getId();
>if (sessionId != null)
>{
>getStore().storePage(sessionId,
> page);
>setLastPage(page);
>dirty();
>}
>}
>
> I think I need a BookmarkableBehaviorRequestTarget which doesn't seem
> to exist.
>
> It seems to me that AJAX behaviours could work with stateless pages
> and the back button if there was a behaviour equivalent of
> BookmarkableListenerInterfaceRequestTarget which would create the
> page if it did not exist and then call the behaviour.
>
> I was thinking about having a shot at it myself but can see all the
> places in the code that refer to
> BookmarkableListenerInterfaceRequestTarget and thought it would be
> better to leave it to someone who knows the code better.
>
> John
>
> On 29 Oct 2007, at 16:56, Igor Vaynberg wrote:
>
> > autocomplete.setversioned(false) do it?
> >
> > -igor
> >
> >
> > On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> I am using the AutoCompleteTextField and can see that every keystroke
> >> causes the entire page to be serialised and stored which seems a bit
> >> excessive. Is there anyway to say that the page has not changed and
> >> so don't store it?
> >>
> >> John
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
Re: AutoCompleteTextField excessive serialisation
On 29 Oct 2007, at 17:37, Eelco Hillenius wrote: Is this really just that component that causes the page to serialize? Sounds like a design flaw to me if that is the case... Eelco Definitely just that component causing the page to be marked stateful. An auto complete field is not _really_ stateful but the way it has been implemented using DefaultAjaxBehaviour which typically change the state of the page. Also, I was surprised to find that instances of image were stateful if I used the constructor Image(String, String) and I had to override the getStatelessHint.
Re: AutoCompleteTextField excessive serialisation
We serialize the page every time it's touched. And the page is touched every request. There is no easy way to determine whether a page jas changed during the request, so we just serialize it. Otherwise we would have to traverse the entire object tree and check every property for being changed. Kinda overkill, don't you think? In next version of wicket we should have this simplyfied, so that it is much easier to tell wicket not to serialize the page in cases when the page doesnt' change and the serialization would cause unnecessary overhead, such as some ajax polls or autocomplete requests. -Matej Eelco Hillenius wrote / napísal(a): On 10/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote: I doubt it would prevent the page from being serialized. Versioning doesn't spot all changes to page (e.g. setting a property) so we can't rely on it, therefore we serialize it on every request. However, if you really want to get around the serialization for certain cases, you need to call Session.untouch(page) before Session.requestDetached() is called. I think calling it from Page.onDetach() should work. So you can set a request cycle metadata if you don't want the page to be serialized and then check for the meta data in page.onDetach(). Is this really just that component that causes the page to serialize? Sounds like a design flaw to me if that is the case... Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
no we didn't do that at first, the last page wasn't serialized only when it didn't because the last page anymore but that had some problems for example. We have to serialize the page before another request makes a new version.. so every request we just have to snapshot it. johan On 10/30/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > On 10/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > I doubt it would prevent the page from being serialized. Versioning > > doesn't spot all changes to page (e.g. setting a property) so we can't > > rely on it, therefore we serialize it on every request. > > > > However, if you really want to get around the serialization for certain > > cases, you need to call Session.untouch(page) before > > Session.requestDetached() is called. > > > > I think calling it from Page.onDetach() should work. So you can set a > > request cycle metadata if you don't want the page to be serialized and > > then check for the meta data in page.onDetach(). > > Is this really just that component that causes the page to serialize? > Sounds like a design flaw to me if that is the case... > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: updating components on Page from ModalWindow's internal Page's components
This might well be the problem.
How do you explicitly postpend something to the URL of a Wicket Image?
The URLs we've been using are autogenerated, and my Google mojo is
failing me... it doesn't have anything to do with .forURL(), does it?
On 10/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Not sure if it is relevant, but to update images using ajax you need
> to generate a unique URL by adding a timestamp or random number to it.
>
> Martijn
>
> On 10/29/07, Kirk Israel <[EMAIL PROTECTED]> wrote:
> > I'm still having the fundamental problem of an Image refusing to
> > update. (A coworker suggested that it might be that I wasn't (yet)
> > updating the underlying model that the page was drawing from, which
> > didn't "smell" like the problem to me, since I could see the
> > component-based updating I thought I was doing, but I put in that
> > change of updating the model, but still I can NOT get the image part
> > of the page to update.) The Label subcomponent of the component is
> > updating fine, but, the ImageComponent (a wrapper to a Wicket Image)
> > seems as fix'd as the north star.
> >
> > I'm working with my own MediaComponent class. It has one of our
> > ImageComponent, added thus:
> > mImageComponent = new
> > ImageComponent("mediaimage",mResource,pClassStyle);
> > mImageComponent.setOutputMarkupId(true);
> > add(mImageComponent);
> >
> > (the mResource here is our MMSDataResource which extends Wicket's
> > DynamicImageResource )
> >
> > Then when it comes time to update w/ the MMSDataResource passed back
> > from the ModalWindow, I do this:
> > ImageComponent newImageComponent = new
> > ImageComponent("mediaimage",mResource,mClassStyle);
> > newImageComponent.setOutputMarkupId(true);
> > mImageComponent.replaceWith(newImageComponent);
> > mImageComponent = newImageComponent;
> > pTarget.addComponent(MediaPanel.this);
> >
> > i can add a pTarget.addComponent(mImageComponent); to no avail; if I
> > put it before the swap so the reference is to the "old"
> > mImageComponent, it rightly complains, and doesn't make a difference
> > coming later... I think adding the MediaPanel itself means the
> > imageComponent inside of it gets redrawn via Ajax too.
> >
> > So I see that MMSDataResource's getImageData() is NOT being called by
> > DynamicImageResource for the Ajax re-render. I see the whole
> > MediaPanel getting redrawn in the Ajax debug window, but apparently
> > the Image reference from ImageComponent is the same old thing.
> >
> > I know there are a few places in my group's code that I might be the
> > actual source of the problem, but can anyone see if I'm doing
> > something wrong? Can't you swap in a new subcomponent during an
> > AjaxRequestTarget-driven update? Is there a likely culprit, or
> > something else that needs to be explicitly added to the
> > AjaxRequestTarget ?
> >
> > Thanks...
> > Kirk
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
Nope. It looks like the logic to store the page is in
SEcondLevelCacheSessionStore and it always stores pages that were
'touched' that are not stateless.
if (!page.isPageStateless())
{
String sessionId = getSession().getId();
if (sessionId != null)
{
getStore().storePage(sessionId, page);
setLastPage(page);
dirty();
}
}
I think I need a BookmarkableBehaviorRequestTarget which doesn't seem
to exist.
It seems to me that AJAX behaviours could work with stateless pages
and the back button if there was a behaviour equivalent of
BookmarkableListenerInterfaceRequestTarget which would create the
page if it did not exist and then call the behaviour.
I was thinking about having a shot at it myself but can see all the
places in the code that refer to
BookmarkableListenerInterfaceRequestTarget and thought it would be
better to leave it to someone who knows the code better.
John
On 29 Oct 2007, at 16:56, Igor Vaynberg wrote:
autocomplete.setversioned(false) do it?
-igor
On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote:
Hi,
I am using the AutoCompleteTextField and can see that every keystroke
causes the entire page to be serialised and stored which seems a bit
excessive. Is there anyway to say that the page has not changed and
so don't store it?
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
On 10/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > I doubt it would prevent the page from being serialized. Versioning > doesn't spot all changes to page (e.g. setting a property) so we can't > rely on it, therefore we serialize it on every request. > > However, if you really want to get around the serialization for certain > cases, you need to call Session.untouch(page) before > Session.requestDetached() is called. > > I think calling it from Page.onDetach() should work. So you can set a > request cycle metadata if you don't want the page to be serialized and > then check for the meta data in page.onDetach(). Is this really just that component that causes the page to serialize? Sounds like a design flaw to me if that is the case... Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
I doubt it would prevent the page from being serialized. Versioning doesn't spot all changes to page (e.g. setting a property) so we can't rely on it, therefore we serialize it on every request. However, if you really want to get around the serialization for certain cases, you need to call Session.untouch(page) before Session.requestDetached() is called. I think calling it from Page.onDetach() should work. So you can set a request cycle metadata if you don't want the page to be serialized and then check for the meta data in page.onDetach(). -Matej Igor Vaynberg wrote / napísal(a): autocomplete.setversioned(false) do it? -igor On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote: Hi, I am using the AutoCompleteTextField and can see that every keystroke causes the entire page to be serialised and stored which seems a bit excessive. Is there anyway to say that the page has not changed and so don't store it? John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: updating components on Page from ModalWindow's internal Page's components
Are you sure that the newly added image has different src attribute
(e.g. adding a timestamp) than the old one? No-cache and no-store
headers on the image itself don't prevent the browser from caching
images on one page.
-Matej
Kirk Israel wrote / napísal(a):
I'm still having the fundamental problem of an Image refusing to
update. (A coworker suggested that it might be that I wasn't (yet)
updating the underlying model that the page was drawing from, which
didn't "smell" like the problem to me, since I could see the
component-based updating I thought I was doing, but I put in that
change of updating the model, but still I can NOT get the image part
of the page to update.) The Label subcomponent of the component is
updating fine, but, the ImageComponent (a wrapper to a Wicket Image)
seems as fix'd as the north star.
I'm working with my own MediaComponent class. It has one of our
ImageComponent, added thus:
mImageComponent = new ImageComponent("mediaimage",mResource,pClassStyle);
mImageComponent.setOutputMarkupId(true);
add(mImageComponent);
(the mResource here is our MMSDataResource which extends Wicket's
DynamicImageResource )
Then when it comes time to update w/ the MMSDataResource passed back
from the ModalWindow, I do this:
ImageComponent newImageComponent = new
ImageComponent("mediaimage",mResource,mClassStyle);
newImageComponent.setOutputMarkupId(true);
mImageComponent.replaceWith(newImageComponent);
mImageComponent = newImageComponent;
pTarget.addComponent(MediaPanel.this);
i can add a pTarget.addComponent(mImageComponent); to no avail; if I
put it before the swap so the reference is to the "old"
mImageComponent, it rightly complains, and doesn't make a difference
coming later... I think adding the MediaPanel itself means the
imageComponent inside of it gets redrawn via Ajax too.
So I see that MMSDataResource's getImageData() is NOT being called by
DynamicImageResource for the Ajax re-render. I see the whole
MediaPanel getting redrawn in the Ajax debug window, but apparently
the Image reference from ImageComponent is the same old thing.
I know there are a few places in my group's code that I might be the
actual source of the problem, but can anyone see if I'm doing
something wrong? Can't you swap in a new subcomponent during an
AjaxRequestTarget-driven update? Is there a likely culprit, or
something else that needs to be explicitly added to the
AjaxRequestTarget ?
Thanks...
Kirk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AutoCompleteTextField excessive serialisation
autocomplete.setversioned(false) do it? -igor On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote: > Hi, > > I am using the AutoCompleteTextField and can see that every keystroke > causes the entire page to be serialised and stored which seems a bit > excessive. Is there anyway to say that the page has not changed and > so don't store it? > > John > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disabling SecondLevelCache
Yes if you completely want to disable the writing to disk you could pass in an empty ipagestore implementation The back button would be lost then but if you have 1 ajax page site then that will be in memory. I do hope that the last rendered page is always the lastPage instance in the pagemap (and not by some accident another page that is used or created in the request) johan On 10/29/07, John Patterson <[EMAIL PROTECTED]> wrote: > > I would like to turn off the automatic serialising of pages to disk > but still keep one page in memory for AJAX operations. My pages are > bookmarkable so if the user uses the back button and the page does > not exist in the store it should be able to be re-created?and > placed in memory again to respond to AJAX calls. > > I can see that I can create my own SecondLevelCacheSession and pass > it an IPageStore. Do you just pass it null to disable serialising > pages? > > Cheers, > > John > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Disabling SecondLevelCache
I would like to turn off the automatic serialising of pages to disk but still keep one page in memory for AJAX operations. My pages are bookmarkable so if the user uses the back button and the page does not exist in the store it should be able to be re-created?and placed in memory again to respond to AJAX calls. I can see that I can create my own SecondLevelCacheSession and pass it an IPageStore. Do you just pass it null to disable serialising pages? Cheers, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Changing IDEs to eclipse
Okay its all working now, What was missing in that last bit is the proper configuration for the context.xml in the META-INF and web.xml in WEB-INF. I had to use tomcat 6.0 configuration xml. It took me a while to figure out taht the context.xml was suppsed to be in the webcontent/meta-inf folder. Great learning experiance, thanks for all your help guys, learnt a new thing today :) Johan Maasing-2 wrote: > > On 10/29/07, Ballist1c <[EMAIL PROTECTED]> wrote: >> >> >> However, i cant figure out how to get the thing to deploy on a web >> service. >> I have installed the tomcat plug in which has made it a breeze to start >> up >> the service from within Eclipse :) I cant seem to get the tomcat server >> to > > I configured the server using the JEE-eclipse built in server config > (just add a new tomcat server, point it to the tomcat directory). Then > it was simply a question of right clicking the server in the servers > view and add the project. Don't know how to do it in any other tomcat > plugin. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Changing-IDEs-to-eclipse-tf4695209.html#a13478688 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: updating components on Page from ModalWindow's internal Page's components
Not sure if it is relevant, but to update images using ajax you need
to generate a unique URL by adding a timestamp or random number to it.
Martijn
On 10/29/07, Kirk Israel <[EMAIL PROTECTED]> wrote:
> I'm still having the fundamental problem of an Image refusing to
> update. (A coworker suggested that it might be that I wasn't (yet)
> updating the underlying model that the page was drawing from, which
> didn't "smell" like the problem to me, since I could see the
> component-based updating I thought I was doing, but I put in that
> change of updating the model, but still I can NOT get the image part
> of the page to update.) The Label subcomponent of the component is
> updating fine, but, the ImageComponent (a wrapper to a Wicket Image)
> seems as fix'd as the north star.
>
> I'm working with my own MediaComponent class. It has one of our
> ImageComponent, added thus:
> mImageComponent = new
> ImageComponent("mediaimage",mResource,pClassStyle);
> mImageComponent.setOutputMarkupId(true);
> add(mImageComponent);
>
> (the mResource here is our MMSDataResource which extends Wicket's
> DynamicImageResource )
>
> Then when it comes time to update w/ the MMSDataResource passed back
> from the ModalWindow, I do this:
> ImageComponent newImageComponent = new
> ImageComponent("mediaimage",mResource,mClassStyle);
> newImageComponent.setOutputMarkupId(true);
> mImageComponent.replaceWith(newImageComponent);
> mImageComponent = newImageComponent;
> pTarget.addComponent(MediaPanel.this);
>
> i can add a pTarget.addComponent(mImageComponent); to no avail; if I
> put it before the swap so the reference is to the "old"
> mImageComponent, it rightly complains, and doesn't make a difference
> coming later... I think adding the MediaPanel itself means the
> imageComponent inside of it gets redrawn via Ajax too.
>
> So I see that MMSDataResource's getImageData() is NOT being called by
> DynamicImageResource for the Ajax re-render. I see the whole
> MediaPanel getting redrawn in the Ajax debug window, but apparently
> the Image reference from ImageComponent is the same old thing.
>
> I know there are a few places in my group's code that I might be the
> actual source of the problem, but can anyone see if I'm doing
> something wrong? Can't you swap in a new subcomponent during an
> AjaxRequestTarget-driven update? Is there a likely culprit, or
> something else that needs to be explicitly added to the
> AjaxRequestTarget ?
>
> Thanks...
> Kirk
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AutoCompleteTextField excessive serialisation
Hi, I am using the AutoCompleteTextField and can see that every keystroke causes the entire page to be serialised and stored which seems a bit excessive. Is there anyway to say that the page has not changed and so don't store it? John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: updating components on Page from ModalWindow's internal Page's components
I'm still having the fundamental problem of an Image refusing to
update. (A coworker suggested that it might be that I wasn't (yet)
updating the underlying model that the page was drawing from, which
didn't "smell" like the problem to me, since I could see the
component-based updating I thought I was doing, but I put in that
change of updating the model, but still I can NOT get the image part
of the page to update.) The Label subcomponent of the component is
updating fine, but, the ImageComponent (a wrapper to a Wicket Image)
seems as fix'd as the north star.
I'm working with my own MediaComponent class. It has one of our
ImageComponent, added thus:
mImageComponent = new ImageComponent("mediaimage",mResource,pClassStyle);
mImageComponent.setOutputMarkupId(true);
add(mImageComponent);
(the mResource here is our MMSDataResource which extends Wicket's
DynamicImageResource )
Then when it comes time to update w/ the MMSDataResource passed back
from the ModalWindow, I do this:
ImageComponent newImageComponent = new
ImageComponent("mediaimage",mResource,mClassStyle);
newImageComponent.setOutputMarkupId(true);
mImageComponent.replaceWith(newImageComponent);
mImageComponent = newImageComponent;
pTarget.addComponent(MediaPanel.this);
i can add a pTarget.addComponent(mImageComponent); to no avail; if I
put it before the swap so the reference is to the "old"
mImageComponent, it rightly complains, and doesn't make a difference
coming later... I think adding the MediaPanel itself means the
imageComponent inside of it gets redrawn via Ajax too.
So I see that MMSDataResource's getImageData() is NOT being called by
DynamicImageResource for the Ajax re-render. I see the whole
MediaPanel getting redrawn in the Ajax debug window, but apparently
the Image reference from ImageComponent is the same old thing.
I know there are a few places in my group's code that I might be the
actual source of the problem, but can anyone see if I'm doing
something wrong? Can't you swap in a new subcomponent during an
AjaxRequestTarget-driven update? Is there a likely culprit, or
something else that needs to be explicitly added to the
AjaxRequestTarget ?
Thanks...
Kirk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.3.0-beta4: updateFeedback() gone?
It is indeed a bug in FormComponentFeedbackBorder. Should be fixed soon though :) -Matej On 10/29/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > in 1.3.0-beta4, Page.renderPage() doesn't call the updateFeedback() on its > > children any more. Because of this change the FormComponentFeedbackBorder > > component fails to work. > > > > Is there a reason for this change? Do I have to call updateFeedback() now > > myself? What's the supposed place to do this? > > It should work without that, but if it doesn't, you found a bug. Could > you please open a JIRA issue for it? Also, it would be great to have a > unit test for these borders, so that it won't happen again. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Looks like the FormComponentFeedbackBorder is not fixed yet. Will fix today. -Matej On 10/29/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > 4) Pages are stateful now because of - > > http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396 > > Ah, I missed this. I fixed the example yesterday, thinking I missed a > deliberate change. But turns out it was a bug after all. Also here, we > need to have a test case. Anyone care to help with that? > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: EqualInputValidator inside WizardStep
Adding the validator to an embedded form worked! Thanks for your help, Igor!
Daniel
> -Original Message-
> From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 29, 2007 6:01 PM
> To: users@wicket.apache.org
> Subject: Re: EqualInputValidator inside WizardStep
>
> hrm, i think a good solution to this would be to create a fresh inner
> form for every new step. so the outer form contains the wizard
> buttons, and an inner form contains the user's panel.
>
> i think for now you can do that yourself, simply embed a form into
> your step's panel and add the validator to that, be sure to let us
> know if that works.
>
> eelco what do you think?
>
> -igor
>
>
> On 10/29/07, Daniel Kröger <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I need to check two TextFields for equality within a
> WizardStep, so i added
> > an EqualInputValidator to the Wizard's form inside the
> onBeforeRender()
> > method of the WizardStep:
> >
> > protected void onBeforeRender() {
> > super.onBeforeRender();
> >
> > final Form form = ((Wizard) getModelObject()).getForm();
> > form.add(new EqualInputValidator(emailField,
> emailConfirmationField));
> > }
> >
> > I think this was the wrong approach because now every other
> WizardStep is
> > complaining:
> >
> > "IFormValidator in form `orderWizard:form` depends on a
> component that has
> > been removed from the page or is no longer visible.
> Offending component id
> > `order.customer.email`."
> >
> > What is the right way to use an EqualInputValidator inside
> a WizardStep?
> >
> > Thanks in advance for your help!
> >
> > Best regards
> > Daniel
> >
> >
> >
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
> 4) Pages are stateful now because of - > http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396 Ah, I missed this. I fixed the example yesterday, thinking I missed a deliberate change. But turns out it was a bug after all. Also here, we need to have a test case. Anyone care to help with that? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Well, I have time on sunday to build the release. What do the other devs think? Frank On 10/29/07, Chris Lintz <[EMAIL PROTECTED]> wrote: > > > Any chance of getting a Beta5 out soon. As luck would have it, Beta4 to > say > the least has been frustrating for us. > > So far beta4 has caused these problems in our app (all stuff that worked > in > Beta3) > > 1) AJAXLink is broke when using the Crypted URL encoding strategy. > 2) StringResourceModel change on toString() method (this is fine, we > refactored and are now using getString() ) > 3) UpdateFeedback gone - > > http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html > 4) Pages are stateful now because of - > > http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396 > > Any chance of getting a Wicket beta5 out with at least the stateless page > fix? We have a high traffic site so the thought of generating some where > in the neighborhood of hundreds of thousands session IDs on disk for pages > as simple as a WebMarkupcontainer and a Label is very scary thought. > > > > > chris > -- > View this message in context: > http://www.nabble.com/Is-Beta5-coming-soon---Beta4-has-caused-these-issues-for-us-tf4713647.html#a13473915 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Changing IDEs to eclipse
On 10/29/07, Ballist1c <[EMAIL PROTECTED]> wrote: > > > However, i cant figure out how to get the thing to deploy on a web service. > I have installed the tomcat plug in which has made it a breeze to start up > the service from within Eclipse :) I cant seem to get the tomcat server to I configured the server using the JEE-eclipse built in server config (just add a new tomcat server, point it to the tomcat directory). Then it was simply a question of right clicking the server in the servers view and add the project. Don't know how to do it in any other tomcat plugin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is Beta5 coming soon? Beta4 has caused these issues for us....
Any chance of getting a Beta5 out soon. As luck would have it, Beta4 to say the least has been frustrating for us. So far beta4 has caused these problems in our app (all stuff that worked in Beta3) 1) AJAXLink is broke when using the Crypted URL encoding strategy. 2) StringResourceModel change on toString() method (this is fine, we refactored and are now using getString() ) 3) UpdateFeedback gone - http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html 4) Pages are stateful now because of - http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396 Any chance of getting a Wicket beta5 out with at least the stateless page fix? We have a high traffic site so the thought of generating some where in the neighborhood of hundreds of thousands session IDs on disk for pages as simple as a WebMarkupcontainer and a Label is very scary thought. chris -- View this message in context: http://www.nabble.com/Is-Beta5-coming-soon---Beta4-has-caused-these-issues-for-us-tf4713647.html#a13473915 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: enclosure and repeater
Thats odd, when I posted, the anchor tag inside the list item tag does not show up. skatz wrote: > > Is there a way to get an enclosure to work with a repeater. Perhaps I am > missing something, but I can't get: > > ... > > > # > > > > to work. What I get is an exception telling me there is no component > matching "item". > > -- View this message in context: http://www.nabble.com/enclosure-and-repeater-tf4713620.html#a13473829 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
enclosure and repeater
Is there a way to get an enclosure to work with a repeater. Perhaps I am missing something, but I can't get: ... to work. What I get is an exception telling me there is no component matching "item". -- View this message in context: http://www.nabble.com/enclosure-and-repeater-tf4713620.html#a13473822 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pickwick rss feeds
I just stumbled upon the wicketstuff pickwick project. http://wicketstuff.org/confluence/display/STUFFWIKI/Pickwick Just wondering if it's actively maintained, and if there'd be any interest in using the wicket-rss integration project for building the rss feeds. I maintain the wicketstuff-rome project and would be interested to hopefully improve *both* projects by integrating it with the pickwick app.
Re: How to manage multiple versions of data?
If you're going to have substantial amounts of data then you probably want to have a database that supports partioning, and then partition the data by the "live" column. - Scott On 10/29/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > usually this is done by supporting multiple rows with version and live > flags. the system always try to query objects that are marked live, so > instead of saying something like > > FROM User u WHERE u.name=? you would do FROM User u WHERE u.name=? AND > u.live=true > > this saves you from having to support what essentially are two sets of > the same tables in the same schema. > > this is also how soft deletes work, which is something you will > probably have to support if you want to support versioning properly... > > just some high level thoughts. > > -igor > > On 10/29/07, Tauren Mills <[EMAIL PROTECTED]> wrote: > > I have a wicket/hibernate/spring project that manages a set of live > > data. Users of the system view the live version of the data. > > Currently, administrative CRUD alters the live data as well. Changes > > by an admin are immediately reflected on the site to users. > > > > But a new set of features is going to require that administrators > > should be able to make updates and changes without affecting the live > > data. Once they are satisfied with the changes they have made, they > > can save/publish the "working data" to be "live data" on the site. > > > > The modification/editing of this data can take a fair amount of time, > > perhaps several days. Thus, I can't just put the working data into > > the session and then save it to the DB a few minutes later when the > > editing is done. The working data needs to be able to persist as well > > as the live data. > > > > Also, I'm reluctant to just make copies of all the data from the live > > version to the working version, because there are certain aspects of > > the live data that can be altered by the users. The users don't > > actually edit the basic data, but additional information is attached > > to the data as the user uses it. If the admin is editing data and it > > takes a few days, the copy of the data could get stale as users use > > it. Then I'd have data synchronization issues to deal with. > > > > I would google for patterns or techniques to deal with this type of > > situation, but I'm not sure what to even search for. Has anyone had > > to deal with anything similar? Any advice or suggestions? Or even > > keywords to search for? > > > > Thanks! > > Tauren > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Scott Swank reformed mathematician - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: EqualInputValidator inside WizardStep
hrm, i think a good solution to this would be to create a fresh inner
form for every new step. so the outer form contains the wizard
buttons, and an inner form contains the user's panel.
i think for now you can do that yourself, simply embed a form into
your step's panel and add the validator to that, be sure to let us
know if that works.
eelco what do you think?
-igor
On 10/29/07, Daniel Kröger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I need to check two TextFields for equality within a WizardStep, so i added
> an EqualInputValidator to the Wizard's form inside the onBeforeRender()
> method of the WizardStep:
>
> protected void onBeforeRender() {
> super.onBeforeRender();
>
> final Form form = ((Wizard) getModelObject()).getForm();
> form.add(new EqualInputValidator(emailField, emailConfirmationField));
> }
>
> I think this was the wrong approach because now every other WizardStep is
> complaining:
>
> "IFormValidator in form `orderWizard:form` depends on a component that has
> been removed from the page or is no longer visible. Offending component id
> `order.customer.email`."
>
> What is the right way to use an EqualInputValidator inside a WizardStep?
>
> Thanks in advance for your help!
>
> Best regards
> Daniel
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where do I get latest QuickStart Project?
we now have a maven archetype which is probably better to use, see quickstart page on wicket.apache.org -igor On 10/29/07, Francisco Diaz Trepat - gmail <[EMAIL PROTECTED]> wrote: > Is it the one on > http://sourceforge.net/project/showfiles.php?group_id=119783&package_id=166850 > > I use beta 4, do I download that one with version 1.2.6 and replace > references? > > > thanks, > > f(t) > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Repeaters' use of WebMarkupContainer question
correct
-igor
On 10/29/07, Scott Swank <[EMAIL PROTECTED]> wrote:
> I believe that instead of
>
>webmarkupcontainer container=new ...
>
> you meant
>
>webmarkupcontainer item=new ...
>
> - Scott
>
> On 10/27/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> > direct children of a repeater inherit the markup, so you can do
> > something like this:
> >
> >
> >
> > repeatingview repeater=new repeatingview("repeater");
> > for (int i=0;i<10;i++) {
> > Link link=new Link(repeater.newchildid()) { };
> > repeater.add(link);
> > link.add(new label("label", ""+i));
> > }
> >
> > this works fine when a repeater only contains one direct child per
> > iteration - the link we added does not have "siblings"
> >
> > but now lets say inside repeater you want two siblings
> >
> > > wicket:id="textfield" type="text"/>
> >
> > so each item has two siblings - a label and a textfield. so what do we
> > add to a repeater? it has to be something that can be attached to a
> > div tag, has no behavior, yet can contain any number of components -
> > best thing that fits is a WebMarkupContainer.
> >
> > so our code is like this:
> >
> > repeatingview repeater=new repeatingview("repeater");
> > for (int i=0;i<10;i++) {
> > webmarkupcontainer container=new
> > webmarkupcontainer(repeater.newchildid());
> > repeater.add(item);
> > item.add(new label("label", "text field "+i));
> > item.add(new textfield("textfield"));
> > }
> >
> > hope this helps...
> >
> > -igor
> >
> >
> > On 10/27/07, skatz <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi,
> > >
> > > Could someone give me some insight into the use of WebMarkupContainers
> > > with
> > > repeaters. In particular, I was wondering how come there does not need to
> > > be markup that has the id of the interposed WebMarkupContainer? (Also, a
> > > pointer to the code, if it exists, where repeaters do special handing of
> > > their direct children.)
> > >
> > > Here is a code snippet from the examples:
> > >
> > > ...
> > >
> > > RepeatingView repeating = new RepeatingView("repeating");
> > > add(repeating);
> > >
> > > int index = 0;
> > > while (contacts.hasNext())
> > > {
> > > WebMarkupContainer item = new
> > > WebMarkupContainer(repeating.newChildId());
> > > repeating.add(item);
> > > Contact contact = (Contact)contacts.next();
> > >
> > > item.add(new ActionPanel("actions", new
> > > DetachableContactModel(contact)));
> > > item.add(new Label("contactid",
> > > String.valueOf(contact.getId(;
> > > item.add(new Label("firstname", contact.getFirstName()));
> > > item.add(new Label("lastname", contact.getLastName()));
> > > item.add(new Label("homephone", contact.getHomePhone()));
> > > item.add(new Label("cellphone", contact.getCellPhone()));
> > > ...
> > >
> > > How come the markup parser doesn't get upset that there is no component
> > > with
> > > the wicket:id=repeating.newChildId()?
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://www.nabble.com/Repeaters%27-use-of-WebMarkupContainer-question-tf4704749.html#a13448018
> > > Sent from the Wicket - User mailing list archive at Nabble.com.
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Scott Swank
> reformed mathematician
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to manage multiple versions of data?
usually this is done by supporting multiple rows with version and live flags. the system always try to query objects that are marked live, so instead of saying something like FROM User u WHERE u.name=? you would do FROM User u WHERE u.name=? AND u.live=true this saves you from having to support what essentially are two sets of the same tables in the same schema. this is also how soft deletes work, which is something you will probably have to support if you want to support versioning properly... just some high level thoughts. -igor On 10/29/07, Tauren Mills <[EMAIL PROTECTED]> wrote: > I have a wicket/hibernate/spring project that manages a set of live > data. Users of the system view the live version of the data. > Currently, administrative CRUD alters the live data as well. Changes > by an admin are immediately reflected on the site to users. > > But a new set of features is going to require that administrators > should be able to make updates and changes without affecting the live > data. Once they are satisfied with the changes they have made, they > can save/publish the "working data" to be "live data" on the site. > > The modification/editing of this data can take a fair amount of time, > perhaps several days. Thus, I can't just put the working data into > the session and then save it to the DB a few minutes later when the > editing is done. The working data needs to be able to persist as well > as the live data. > > Also, I'm reluctant to just make copies of all the data from the live > version to the working version, because there are certain aspects of > the live data that can be altered by the users. The users don't > actually edit the basic data, but additional information is attached > to the data as the user uses it. If the admin is editing data and it > takes a few days, the copy of the data could get stale as users use > it. Then I'd have data synchronization issues to deal with. > > I would google for patterns or techniques to deal with this type of > situation, but I'm not sure what to even search for. Has anyone had > to deal with anything similar? Any advice or suggestions? Or even > keywords to search for? > > Thanks! > Tauren > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
EqualInputValidator inside WizardStep
Hi,
I need to check two TextFields for equality within a WizardStep, so i added
an EqualInputValidator to the Wizard's form inside the onBeforeRender()
method of the WizardStep:
protected void onBeforeRender() {
super.onBeforeRender();
final Form form = ((Wizard) getModelObject()).getForm();
form.add(new EqualInputValidator(emailField, emailConfirmationField));
}
I think this was the wrong approach because now every other WizardStep is
complaining:
"IFormValidator in form `orderWizard:form` depends on a component that has
been removed from the page or is no longer visible. Offending component id
`order.customer.email`."
What is the right way to use an EqualInputValidator inside a WizardStep?
Thanks in advance for your help!
Best regards
Daniel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: conditionally including a div
for flash messages you actually need to do getsession().info("foo") so
it lasts across requests :)
-igor
On 10/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> flash messages:
>
> info("foo");
>
> add(new FeedbackPanel("feedbackpanel"));
>
>
>
> Martijn
>
>
> On 10/29/07, Brill Pappin <[EMAIL PROTECTED]> wrote:
> > I'm porting an app written in Ruby on Rails as a spike on how Wicket works.
> > I've run into an issue I'm not sure how to handle.
> >
> > I have the case of a message box near the top of the screen that's in a
> > conditional block... here is the ruby code to demonstrate:
> > <% if @flash[:notice] %>
> > <%= @flash[:notice] %>
> > <% end %>
> >
> > (fyi, flash in this context is not Flash, but a "flash message")
> >
> > I get the part of wicket were I can attach a component to the div element,
> > but what I really want is the div to not be there if it's not needed.
> > Is there any way to actually remove the div if I don't need it in the
> > content?
> > Is there a "non-html" wicket tag I haven't found yet for adding a
> > placeholder instead of the div?
> >
> > - Brill Pappin
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-beta4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Repeaters' use of WebMarkupContainer question
I believe that instead of
webmarkupcontainer container=new ...
you meant
webmarkupcontainer item=new ...
- Scott
On 10/27/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> direct children of a repeater inherit the markup, so you can do
> something like this:
>
>
>
> repeatingview repeater=new repeatingview("repeater");
> for (int i=0;i<10;i++) {
> Link link=new Link(repeater.newchildid()) { };
> repeater.add(link);
> link.add(new label("label", ""+i));
> }
>
> this works fine when a repeater only contains one direct child per
> iteration - the link we added does not have "siblings"
>
> but now lets say inside repeater you want two siblings
>
> wicket:id="textfield" type="text"/>
>
> so each item has two siblings - a label and a textfield. so what do we
> add to a repeater? it has to be something that can be attached to a
> div tag, has no behavior, yet can contain any number of components -
> best thing that fits is a WebMarkupContainer.
>
> so our code is like this:
>
> repeatingview repeater=new repeatingview("repeater");
> for (int i=0;i<10;i++) {
> webmarkupcontainer container=new webmarkupcontainer(repeater.newchildid());
> repeater.add(item);
> item.add(new label("label", "text field "+i));
> item.add(new textfield("textfield"));
> }
>
> hope this helps...
>
> -igor
>
>
> On 10/27/07, skatz <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > Could someone give me some insight into the use of WebMarkupContainers with
> > repeaters. In particular, I was wondering how come there does not need to
> > be markup that has the id of the interposed WebMarkupContainer? (Also, a
> > pointer to the code, if it exists, where repeaters do special handing of
> > their direct children.)
> >
> > Here is a code snippet from the examples:
> >
> > ...
> >
> > RepeatingView repeating = new RepeatingView("repeating");
> > add(repeating);
> >
> > int index = 0;
> > while (contacts.hasNext())
> > {
> > WebMarkupContainer item = new
> > WebMarkupContainer(repeating.newChildId());
> > repeating.add(item);
> > Contact contact = (Contact)contacts.next();
> >
> > item.add(new ActionPanel("actions", new
> > DetachableContactModel(contact)));
> > item.add(new Label("contactid",
> > String.valueOf(contact.getId(;
> > item.add(new Label("firstname", contact.getFirstName()));
> > item.add(new Label("lastname", contact.getLastName()));
> > item.add(new Label("homephone", contact.getHomePhone()));
> > item.add(new Label("cellphone", contact.getCellPhone()));
> > ...
> >
> > How come the markup parser doesn't get upset that there is no component with
> > the wicket:id=repeating.newChildId()?
> >
> >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Repeaters%27-use-of-WebMarkupContainer-question-tf4704749.html#a13448018
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Scott Swank
reformed mathematician
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Where do I get latest QuickStart Project?
Is it the one on http://sourceforge.net/project/showfiles.php?group_id=119783&package_id=166850 I use beta 4, do I download that one with version 1.2.6 and replace references? thanks, f(t)
Re: disabling of AjaxSubmitLink
It is already fixed in 1.3. -Matej On 10/29/07, wheleph <[EMAIL PROTECTED]> wrote: > > Hello everyone! > > I use Wicket 1.2.6 and when I try to disable AjaxSubmitLink via > link.setEnabled(false) call it really doesn't react on clicks but it still > looks like a regular link in browser. I mean that in resulting markup it's > represented by element. But similar disabledLink substitutes > element with and thus looks like a plain text. > > Thus the current behavior of disabled AjaxSubmitLink is not consistent with > Link's. Shouldn't it be corrected it the futher versions of Wicket? > > wheleph > -- > View this message in context: > http://www.nabble.com/disabling-of-AjaxSubmitLink-tf4712370.html#a13469788 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
disabling of AjaxSubmitLink
Hello everyone! I use Wicket 1.2.6 and when I try to disable AjaxSubmitLink via link.setEnabled(false) call it really doesn't react on clicks but it still looks like a regular link in browser. I mean that in resulting markup it's represented by element. But similar disabledLink substitutes element with and thus looks like a plain text. Thus the current behavior of disabled AjaxSubmitLink is not consistent with Link's. Shouldn't it be corrected it the futher versions of Wicket? wheleph -- View this message in context: http://www.nabble.com/disabling-of-AjaxSubmitLink-tf4712370.html#a13469788 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to manage multiple versions of data?
I would also try searching for auditing persistent objects. There should be a few pages on the Hibernate wiki about it. -- Nick Heudecker Professional Wicket Training & Consulting http://www.systemmobile.com Eventful - Intelligent Event Management http://www.eventfulhq.com
Re: Portlet howto
I've tried to localize this.
It looks like the generated url s not correct.
this is the source for the ajax link example
href="#" onclick="var
wcall=wicketAjaxGet('http://localhost:8080/web/guest/admin?p_p_id=AjaxApplication&p_p_action=1&p_p_col_id=column-1&p_p_col_count=1&;',null,null,
function() {return Wicket.$$(this)}.bind(this));return !wcall;" ...
notice the 'p_p_id=AjaxApplication' while this should be:
'p_p_id=AjaxApplication_WAR_wicketexamples'
I'm trying to find where the this javascript fragment URL is generated in
wicket because the normal, non ajax links do point to the correct location:
href="http://localhost:8080/web/guest/admin?p_p_id=AjaxApplication_WAR_wicketexamples&p_p_action=1&p_p_state=normal&p_p_mode=view.
Can someone point me in the right direction?
Thijs
Thijs wrote:
>
> Hello Charly,
>
> Have you got any answer from Liferay jet?
> We could put this in an issue in the Liferay support system. Or post a
> message on the forum.
>
> I tried something very ugly I implemented encodeRedirectURL as encodeURL
> is implemented. (copied the code) This prevents the nullpointer of
> showing up. But then I get this message:
>
> 13:08:40,375 WARN [PortletLocalServiceImpl:138] Portlet not found for 1
> AjaxApplication
>
> Which probably is logical :)
> I'll try and dig some further.
>
> Thijs
>
>
>
>
>
> Charles CHAHBAZIAN wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi Ate,
>>
>> Ate Douma a écrit :
>> Charly
>> wrote:
>>
>> Hello,
>>
>> I have the beginning of a solution !
>>
>>
>> Cool !
>>
>>
>> My code is based on Liferay's struts support
>> with some adaptations.
>>
>>
>> At this time, Guestbook portlet sample is ok, and I've made a
>> modification in wicket to get Navomatic and other bookmarkablePage
>> working.
>>
>>
>> The main point is that Liferay want a new HttpServletRequest (from
>> theirs object) in ServletContextProvider implementation of
>> ServletContextProvider and we must copy the request's parameters from
>> the original request to the new one.
>>
>>
>> Weird, but I guess it is something Liferay specific.
>>
>>
>> You're right. Because if I keep the same HttpServletRequest, I have a
>> ClassCastException later because Liferay use these specific objects...
>>
>> I translate also the "_wu"
>> (WicketPortlet.WICKET_URL_PORTLET_PARAMETER) parameter into differents
>> parameters
>>
>>
>> Why?
>>
>> The WicketPortlet dispatches to the servlet/filter using this url, so
>> the underlying web container (e.g. catalina) should already provide the
>> query string parameters as request parameters (as required by the
>> servlet spec).
>>
>>
>>
>> You can have a look to my 3 classes at the end of this mail.
>>
>>
>> I notice that you don't set the provided Map portletArg arguments on
>> the created PortletURLImpl in createResourceURL method.
>>
>> You probably should...
>>
>>
>> I tried that solution first. In that case, the url looks like that :
>> http://localhost:8080/user/joebloggs/3?p_p_id=NavomaticApplication_WAR_wicketexamples&p_p_action=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1&_NavomaticApplication_WAR_wicketexamples__wuview=%2Fnavomatic%2F%3Fwicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2
>>
>>
>> But the WebRequestCodingStrategy (at line : 518) use the
>> request.getParameter() and on my debug sessions i saw that the
>> portletArgs i've put in the PortletURLImpl parameters are available in
>> the queryString but not in the parameters of the request ... (looks
>> strange for me too, it seems to be a liferay's bug)
>>
>>
>>
>>
>> I've got a problem for all bookmarkablePage, because the argument are
>> encoded by Wicket, and Liferay encode it second time.
>>
>>
>> Liferay shouldn't be doing that: you should get back the parameters
>> previously set on a PortletURL exactly the same.
>>
>> Seems like a Liferay bug to me.
>>
>>
>> About that question, as you can see in the sample url I've put, we have
>>
>> wicket%3AbookmarkablePage%3D%253Aorg.apache.wicket.examples.navomatic.Page2
>> you can see that the there are 2 encoding :
>> 1) wicket set the parameter from
>> ":org.apache.wicket.examples.navomatic.Page2" to
>> "%3Aorg.apache.wicket.examples.navomatic.Page2"
>> 2) Liferay encode the "%" character to "%25"
>>
>> When Liferay get back the Encoded parameter, the "%25" is set into "%"
>> but no Wicket Code transform back the "%3A" to ":"
>>
>> Note : Wicket Encoding is done by :
>> org.apache.wicket.request.target.coding.WebRequestEncoder : line 86
>> escapedValue = URLEncoder.encode(escapedValue,
>> application.getRequestCycleSettings().getResponseRequestEncoding());
>> and I can't find a decode for this level in Wicket's code.
>>
>>
>> The parameter received is like
>> "%3Aorg.apache.wicket.examples.navomatic.Page2". So I add a call to
>> decode function
Re: recommend a CMS to integrate w/our wicket-based webapp?
It's possible to develop some cool stuff with Magnolia, just by loading wicket apps inside Iframes. It's not the best solution, but it will probably give you a quick start. :) regards -- Bruno Borges blog.brunoborges.com.br +55 1185657739 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld On 10/29/07, Frank Meiser <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm currently working on an integration of wicket as TemplateRenderer into > the Magnolia CMS (http://magnolia.info) > Currently it is just a prove of concept. Is there any interest? > > Regards, > Frank > > Quoting Erik van Oosten <[EMAIL PROTECTED]>: > > > Hi Nikita, > > > > Regarding option 1: there are a few public CMS components for Wicket. > > Just search the list (Nabble is perfect) for CMS, component and Cronos. > > > > Regards, > >Erik. > > > > > > dukehoops wrote: > >> Hi, > >> > >> We're developing our (social networking ;- ) site using wicket talking > to > >> our Spring-managed services layer. We're going to need to provide > content > >> management features for our internal users (admins, moderators, > marketers) > >> and I'm exploring possible solutions. I realize we can build our > >> own CMS but I wonder whether any of the existing > >> (mature) systems would play nicely with a wicket based app. I see > >> pages on our site being divided into three groups: 1. dynamic pages > >> composed and rendered by wicket (ex: user profile page) > >> 2. static pages composed and rendered by some CMS (say opencms, joomla > or > >> whatever else) (ex: faq, legal section, static promo) > >> 3. hybrid pages: a wicket page that someone "includes" a cms-managed > module. > >> (ex: marketing wants to add and mange a promo area to user profile > pages) > >> > >> What I'd like to avoid is to have the CMS dictate the way our dynamic > >> (wicket-based) pages are built. > >> > >> Have you added a pre-made CMS to your wicket-based webapp? Or, in other > >> words, do you have a site where pages divide into the above 3 > catogories? > If > >> so, could you please share with CMS did you choose and how did you > >> integrate? > >> > >> thanks > >> -nikita > >> > > > > -- > > Erik van Oosten > > http://2008.rubyenrails.nl/ > > http://day-to-day-stuff.blogspot.com/ > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: recommend a CMS to integrate w/our wicket-based webapp?
Hi, I'm currently working on an integration of wicket as TemplateRenderer into the Magnolia CMS (http://magnolia.info) Currently it is just a prove of concept. Is there any interest? Regards, Frank Quoting Erik van Oosten <[EMAIL PROTECTED]>: > Hi Nikita, > > Regarding option 1: there are a few public CMS components for Wicket. > Just search the list (Nabble is perfect) for CMS, component and Cronos. > > Regards, >Erik. > > > dukehoops wrote: >> Hi, >> >> We're developing our (social networking ;- ) site using wicket talking to >> our Spring-managed services layer. We're going to need to provide content >> management features for our internal users (admins, moderators, marketers) >> and I'm exploring possible solutions. I realize we can build our >> own CMS but I wonder whether any of the existing >> (mature) systems would play nicely with a wicket based app. I see >> pages on our site being divided into three groups: 1. dynamic pages >> composed and rendered by wicket (ex: user profile page) >> 2. static pages composed and rendered by some CMS (say opencms, joomla or >> whatever else) (ex: faq, legal section, static promo) >> 3. hybrid pages: a wicket page that someone "includes" a cms-managed module. >> (ex: marketing wants to add and mange a promo area to user profile pages) >> >> What I'd like to avoid is to have the CMS dictate the way our dynamic >> (wicket-based) pages are built. >> >> Have you added a pre-made CMS to your wicket-based webapp? Or, in other >> words, do you have a site where pages divide into the above 3 catogories? If >> so, could you please share with CMS did you choose and how did you >> integrate? >> >> thanks >> -nikita >> > > -- > Erik van Oosten > http://2008.rubyenrails.nl/ > http://day-to-day-stuff.blogspot.com/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
Re: conditionally including a div
flash messages:
info("foo");
add(new FeedbackPanel("feedbackpanel"));
Martijn
On 10/29/07, Brill Pappin <[EMAIL PROTECTED]> wrote:
> I'm porting an app written in Ruby on Rails as a spike on how Wicket works.
> I've run into an issue I'm not sure how to handle.
>
> I have the case of a message box near the top of the screen that's in a
> conditional block... here is the ruby code to demonstrate:
> <% if @flash[:notice] %>
> <%= @flash[:notice] %>
> <% end %>
>
> (fyi, flash in this context is not Flash, but a "flash message")
>
> I get the part of wicket were I can attach a component to the div element,
> but what I really want is the div to not be there if it's not needed.
> Is there any way to actually remove the div if I don't need it in the
> content?
> Is there a "non-html" wicket tag I haven't found yet for adding a
> placeholder instead of the div?
>
> - Brill Pappin
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: OT: API to calculate distances from zip code
Sean and Matt, Thanks for the advice! You're suggestions got me going in the right direction... As this small scale project is using MySQL, I discovered it supports some GIS features as well. In case anyone else is looking to do something similar, this thread is particularly useful: http://forums.mysql.com/read.php?23,3868,3868#msg-3868 Tauren On 10/27/07, Matt Jensen <[EMAIL PROTECTED]> wrote: > > If you want to implement this for yourself, you need to start with two > pieces: a database of zip code data including latitude/longitude, and > (to make things as simple as possible) an OpenGIS extension package for > your database. This gives you the ability to index on > latitude/longitude and do quick lookups using a "distance" function in > the WHERE clause of your query. The implementation for PostgreSQL is > called PostGIS (http://www.postgis.org); if you're using some other > database then you will have to find the equivalent extension on your > own. I wouldn't be surprised if some high end databases have this > functionality built in. > > Zip code databases are available from about a million different > sources. I was most pleased with the offering from > http://www.zipcodeworld.com, but I'm sure that I did not investigate > them all. In my experience, the data is a bit shoddy in all of these > collections. You may not have problems with that until you try to > combine it with something like gazetteer data. In about 2,000 cases, > that becomes a nightmare. If you can avoid that...do! > > I have an SQL INSERT script which was generated off of the September > topical gazetteer and zip code databases, but with everything pulled in > I believe it weighs in at something like 40MB. :-/ > > Tauren Mills wrote: > > I apologize for this being off topic, but I have a feeling some of you > > might have some ideas for me. > > > > I'd like to implement a feature that will search for all physical > > locations in my database that are within a radius of a zip code. In > > other words, the user enters a zip code and selects a distance from a > > drop down list (5 mi, 10 mi, 25 mi, 50 mi, etc.) and a list of all > > locations within that distance of the zip code will be displayed. You > > can see something similar to this at: > > http://www.restaurant.com/ > > > > Are there any web services out there that would simplify this task? I > > have been looking at the Google Geocoding API > > (http://www.google.com/apis/maps/documentation/services.html), but am > > not sure how much it will help. I could geocode locations as they are > > added to my database and store the lat/long, but I get fuzzy on how to > > proceed from there. Somehow my SQL query (using hibernate) would need > > to do some computation to see if the lat/long stored in the DB is > > within the specified radius from the lat/long of the specified zip > > code. > > > > I guess I mostly want to hear from others if this would be the way > > they would do it, or if there is some other way that would work better > > or be simpler. > > > > Thanks! > > Tauren > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to manage multiple versions of data?
On 10/29/07, Tauren Mills <[EMAIL PROTECTED]> wrote: > I have a wicket/hibernate/spring project that manages a set of live > data. Users of the system view the live version of the data. > Currently, administrative CRUD alters the live data as well. Changes > by an admin are immediately reflected on the site to users. > > But a new set of features is going to require that administrators > should be able to make updates and changes without affecting the live > data. Once they are satisfied with the changes they have made, they > can save/publish the "working data" to be "live data" on the site. > > The modification/editing of this data can take a fair amount of time, > perhaps several days. Thus, I can't just put the working data into > the session and then save it to the DB a few minutes later when the > editing is done. The working data needs to be able to persist as well > as the live data. > > Also, I'm reluctant to just make copies of all the data from the live > version to the working version, because there are certain aspects of > the live data that can be altered by the users. The users don't > actually edit the basic data, but additional information is attached > to the data as the user uses it. If the admin is editing data and it > takes a few days, the copy of the data could get stale as users use > it. Then I'd have data synchronization issues to deal with. > > I would google for patterns or techniques to deal with this type of > situation, but I'm not sure what to even search for. Has anyone had > to deal with anything similar? Any advice or suggestions? Or even > keywords to search for? No real experience with this myself, but start with 'long transactions'? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: recommend a CMS to integrate w/our wicket-based webapp?
> You wish :( > On jetspeed based portals maybee. I haven't really tried it in there. > However in the biggest opensource portal Liferay it's not really working. > (See http://www.nabble.com/Portlet-howto-tf4587073.html) I have no real experience with it I'm afraid. Maybe Ate has some good suggestions? I hear he is a CMS/ Portlet beast. ;-) What about Jahia (http://www.jahia.org)? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Confirmation message after form submit
On Thu, 25 Oct 2007 11:33:57 +0100 "Dipu Seminlal" <[EMAIL PROTECTED]> wrote: > yes a modal window, I see, I'll go with this solution.. Many thanks to everyone who answered :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to manage multiple versions of data?
I have a wicket/hibernate/spring project that manages a set of live data. Users of the system view the live version of the data. Currently, administrative CRUD alters the live data as well. Changes by an admin are immediately reflected on the site to users. But a new set of features is going to require that administrators should be able to make updates and changes without affecting the live data. Once they are satisfied with the changes they have made, they can save/publish the "working data" to be "live data" on the site. The modification/editing of this data can take a fair amount of time, perhaps several days. Thus, I can't just put the working data into the session and then save it to the DB a few minutes later when the editing is done. The working data needs to be able to persist as well as the live data. Also, I'm reluctant to just make copies of all the data from the live version to the working version, because there are certain aspects of the live data that can be altered by the users. The users don't actually edit the basic data, but additional information is attached to the data as the user uses it. If the admin is editing data and it takes a few days, the copy of the data could get stale as users use it. Then I'd have data synchronization issues to deal with. I would google for patterns or techniques to deal with this type of situation, but I'm not sure what to even search for. Has anyone had to deal with anything similar? Any advice or suggestions? Or even keywords to search for? Thanks! Tauren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: recommend a CMS to integrate w/our wicket-based webapp?
You wish :( On jetspeed based portals maybee. I haven't really tried it in there. However in the biggest opensource portal Liferay it's not really working. (See http://www.nabble.com/Portlet-howto-tf4587073.html) Thijs Eelco Hillenius wrote: > >> We're developing our (social networking ;- ) site using wicket talking to >> our Spring-managed services layer. We're going to need to provide content >> management features for our internal users (admins, moderators, >> marketers) >> and I'm exploring possible solutions. >> >> I realize we can build our own CMS but I wonder whether any of the >> existing >> (mature) systems would play nicely with a wicket based app. > > I have no experience with this myself. If I would look for an existing > one, I would probably look for a CMS that supports JSR-168 (portlets). > From Wicket beta3 onwards, Wicket pages should work fluently in such > environments. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/recommend-a-CMS-to-integrate-w-our-wicket-based-webapp--tf4704210.html#a13463355 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.3.0-beta4: updateFeedback() gone?
> in 1.3.0-beta4, Page.renderPage() doesn't call the updateFeedback() on its > children any more. Because of this change the FormComponentFeedbackBorder > component fails to work. > > Is there a reason for this change? Do I have to call updateFeedback() now > myself? What's the supposed place to do this? It should work without that, but if it doesn't, you found a bug. Could you please open a JIRA issue for it? Also, it would be great to have a unit test for these borders, so that it won't happen again. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.3.0-beta4: updateFeedback() gone?
Hi, browsing the JIRA I found WICKET-836 (which originally addressed a different problem), but I think that the call to updateFeedback() was removed because of this issue. At the end of WICKET-836 it was said that the original issue was caused by wrong usage. So I wonder if there is still a reason for removing the updateFeedback() call in Page.renderPage(). As said, FormComponentFeedbackBorder doesn't work any more because of this change. regards, Oliver -- View this message in context: http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html#a13463170 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
