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 Wick
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 rul
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
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);
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
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 l
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
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 _reall
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.
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, Eel
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:
>
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 = getSess
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
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 Ses
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 fundamenta
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
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
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 agai
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 fold
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 suggeste
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
-
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 w
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 FormComponentFeedbackBo
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
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
> 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 ca
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 the
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
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
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 telli
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-
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 pr
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
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 t
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
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 i
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 w
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();
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 <[EMA
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=
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)
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 th
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
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
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
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 th
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
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 messa
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://foru
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
> 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
suggest
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 ad
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
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 ;- ) si
> 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
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 reaso
56 matches
Mail list logo