Re: Wiquery experiences
Ernesto, Hielke thanks a lot for your answers At the time I looked at wiquery, it was for some specific task. This task didn't include explorating whether a full blown jquery/wicket integration framework would fit our needs. This is quite a task on its own imho, and there the lack of documentation is a real issue. For example, questions I had which would involve quite some time to figure out: - does wiquery support being used from a wicket ajax request nicely? If so, is it part of its "intended aims" and thus made across all its wrappers or just some of the wrapper being properly done? How does it handle the case of wiquery dependent component made visible through an ajax request? => Hielke already provided some answers which I'm glad to have read, but it doesn't cover it all - ease to use with other librairies, like JSLibraries (and its CDN integration) ? - reliability now and in the future: what about eventual bug I would find, would they be easy to fix on my own? Does the code make enough sense to me? In there a proper community around to help in case ? What's the plan for currently supported jquery versions and the future? => Ernesto also provided some answers, which is good, thanks :) I hope you understand better the questions which arise and why it would take a while to figure them out just by looking at the code. That's where more documentation/tutorial/feedbacks would help, to make the discovery cost lower. as a side note, I was already bitten by being early adopting some new frameworks, so now I tend to be more carefull, esp. for stuff that are directly seen by the users... regards - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wiquery experiences
Hi Hielke Nice to be able to discuss with some wiquery commiter. Acutally, I was willing to use it some time ago but I found wiquery wasn't very good at selling itself. The wiki is pretty old and useless (http://code.google.com/p/wiquery/wiki/DocumentationHome?tm=6) and at the time I found no tutorial or example... Did it change in some way? I would still love to be able to have a better clue of it, since it looks intriguing, but I don't have enough time to do a proper investigation on how to use it... Regards 2011/4/7 Hielke Hoeve : > WiQuery *has* matured a lot. We are working hard in our late hours to > implement and test interfaces to all facets of jQuery and are getting ready > for Wicket 1.5. > > Bruno is right that for some purposes it is easy using only jQuery, simply > add the jQuery js files you want and write a script tag with the > document.onready function. But I am curious how one handles ajax added panels > with jQuery functionality on a page or components that consume data or jquery > enabled components that have jQuery options set based on business logic or > components that have their visibility set based on business logic. Once a > component is replaced by an ajax call the jQuery functionality is removed > from this component. Not to speak of being able to reuse numerous components > on numerous pages... I don't even want to begin to think about how to handle > jquery component options based on business data. > > Now I do agree that in some cases (which do not cover the ones I described > above) WiQuery is absolutely not useful and a simple static js file and > static jQuery initialization statement is good enough. Not every jQuery > component is worth converting to a WiQuery component. The ones that are worth > are often: > - components that are ajax enabled and/or; > - components that have their jQuery options depend on data or logic and/or; > - components that have their visibility or are enabled based on data or logic > and/or; > - components that are added by an ajax request and not at page load; > > > The reason I started working on the WiQuery project is because my company > creates enterprise administration applications where we have *a lot* of pages > with ajax replaced panels, autocomplete text fields, accordion panels, tabbed > panels, feedback popups... you name it we have it. > With WiQuery we create reusable components, define which resources this > component needs and what bit of jQuery it needs to initialize after the page > (or ajax response) has been loaded, and simple add them to the page. The page > is on a need to know basis, it will define the layout not boss all components > around... WiQuery checks which resources are loaded, removes duplicates, adds > the jQuery Core, jQuery UI and jQuery UI Theme. While managing multiple > projects with over 1000+ pages, this takes away quite a load off our > shoulders. > > Maarten says: > Writing what should be JavaScript in your wicket Java code is quite > out-of-place, and generally all you need to do is place your code where it > belongs, in a .js or your markup. > > I wonder if he ever really used WiQuery or even looked how it's used. Or for > that matter used jQuery. What you *don't* need to do with WiQuery is write js > code in your java classes and we recommend to put all js code in js files and > load them as a resource! To create a jQuery wicket component you: > - write your jQuery js file and the html file that comes with it; > - write the java code that you need to insert any application data, behaviors > or validators; > - let your component implement an interface (so WiQuery can detect it upon > creation) to define which js/css files you want to be added as a resource and > define the jQuery initialization statement with java code (which is > translated most often something like "document.onready(.);". > > > There are other libraries around that do about the same as WiQuery, and > perhaps better or faster, but my rant above is to clarify why the project > exists and why people are using it. And the best part of it is: you don't > have to use it... > > Regards, > > Hielke > > -Original Message- > From: Bruno Borges [mailto:bruno.bor...@gmail.com] > Sent: donderdag 7 april 2011 0:32 > To: users@wicket.apache.org > Cc: Maarten Billemont > Subject: Re: Wiquery experiences > > Most of the things you want to do with jQuery, you don't need a library for. > > I totally agree with Maarten > > > Bruno Borges > www.brunoborges.com.br > +55 21 76727099 > > "The glory of great men should always be measured by the means they have used > to acquire it." > - Francois de La Rochefoucauld > > > > On Wed, Apr 6, 2011 at 6:15 AM, Maarten Billemont wrote: > >> Unless WiQuery has matured a *lot* lately and the code has been >> cleaned up significantly, I can't recommend it, personally. >> >> Writing what should be JavaScript in your wicket Java code is quite >> out-of-plac
wicket ajax best practices ?
hi I've been quite heavily using ajax lately and, at the beginning, it appears to break often, getting "page not found 404" and others "channel busy - postponing". I'm mainly using modal windows, ajax links and ajax validating/submit behaviors. Recently, searching through the mailing list, I found that adding the doctype helped a lot. Precisely, I added : http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml";> Going further, I added the encoding on the first line : Then I used the w3c html validators to remove all the potential issues (found a few br lacking the closing /). I've now the feeling that it breaks less, but still I'm not sure I did all my best. So, at the end of the day, when using ajax in wicket, are they some good practices to follow ? What could I do to lower as far as possible all these 'page not found 404" and others "channel busy" on actions which 95% of the time work ? thanks in advance nono - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
how to avoid concurrent clic/submit on ajax links ?
hi when trying to push my ajax app to its limits, I spotted that I'm able to send 2 ajax requests but only have the display of the first one. Is there a way to avoid this kind of double clic ? to be precise, the pattern I use to reproduce easily this point is the following : - I click on a link having a warning (added through an AttributeModifier adding a confirm) - when the pop up is displayed, I put my cursor above another ajax link - i then press "enter" on my keyboard to have the pop up removed and, almost at the same time, clic with my mouse on the link I'm above - on the then rendered page, the displayed html doesn't take fully in account the result of my "return" key pressed (I've marked deleted an element of a tree : the element detail panel shows well "deleted" but the tree isn't showing it... as is the case usually). is there something to be done ? thanks in advance nono - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Example of ModalWindow misleading
done : https://issues.apache.org/jira/browse/WICKET-2295 nono 2009/5/28, Igor Vaynberg : > yes > > > -igor > > > On Thu, May 28, 2009 at 3:09 AM, Live Nono wrote: > > Should I open a jira for this ? > > > > > > > > 2009/5/21 Matej Knopp : > >> I think modal window example could be fixed by using > >> getPageReference() to pass page reference between pages instead of > >> page instance. > >> > >> -Matej > >> > >> On Wed, May 20, 2009 at 10:29 PM, Martin Makundi > >> wrote: > >>>> http://www.wicket-library.com/wicket-examples/ajax/modal-window.1 is > >>>> pretty misleading : passing components between components/page is > >>>> quite broken as can be seen in the past discussion on the mailing list > >>>> (serialization issue can arise and makes both sides using different > >>>> references of the same object "logically speaking"). > >>> > >>> True. > >>> > >>> I have found that the only safe way to pass references is via > >>> getSession().xxx so now all my (not all, but generally relevant ones) > >>> models are in session instead of being page-scoped. Not heavy models > >>> but selection models such that indicate what the user is operating on. > >>> > >>> However. Instead of changing the documentation, I would rather change > >>> the implementation such that the serialization would not break. > >>> > >>> The same offect, however, occurs if you have some other kind of pop-up > >>> window it would be nice to be able to continue using the > >>> underlying page in sync with the pop-up. > >>> > >>> > >>> > >>> ** > >>> Martin > >>> > >>>> > >>>> However, as it is in the example, I first used it considering that it > >>>> should be ok to do so. > >>>> > >>>> Could it be changed in some way ? > >>>> > >>>> On the bigger picture, I guess it raises again the issue of the > >>>> "recommended" way of communicating between the page and the modal > >>>> window, which currently doesn't exist (session, database...??). > >>>> However, this example is currently completely misleading, so even so > >>>> comments to explicit the issue would be welcomed. > >>>> > >>>> thanks again > >>>> nono > >>>> > >>>> - > >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>>> For additional commands, e-mail: users-h...@wicket.apache.org > >>>> > >>>> > >>> > >>> - > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>> For additional commands, e-mail: users-h...@wicket.apache.org > >>> > >>> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Example of ModalWindow misleading
Should I open a jira for this ? 2009/5/21 Matej Knopp : > I think modal window example could be fixed by using > getPageReference() to pass page reference between pages instead of > page instance. > > -Matej > > On Wed, May 20, 2009 at 10:29 PM, Martin Makundi > wrote: >>> http://www.wicket-library.com/wicket-examples/ajax/modal-window.1 is >>> pretty misleading : passing components between components/page is >>> quite broken as can be seen in the past discussion on the mailing list >>> (serialization issue can arise and makes both sides using different >>> references of the same object "logically speaking"). >> >> True. >> >> I have found that the only safe way to pass references is via >> getSession().xxx so now all my (not all, but generally relevant ones) >> models are in session instead of being page-scoped. Not heavy models >> but selection models such that indicate what the user is operating on. >> >> However. Instead of changing the documentation, I would rather change >> the implementation such that the serialization would not break. >> >> The same offect, however, occurs if you have some other kind of pop-up >> window it would be nice to be able to continue using the >> underlying page in sync with the pop-up. >> >> >> >> ** >> Martin >> >>> >>> However, as it is in the example, I first used it considering that it >>> should be ok to do so. >>> >>> Could it be changed in some way ? >>> >>> On the bigger picture, I guess it raises again the issue of the >>> "recommended" way of communicating between the page and the modal >>> window, which currently doesn't exist (session, database...??). >>> However, this example is currently completely misleading, so even so >>> comments to explicit the issue would be welcomed. >>> >>> thanks again >>> nono >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Example of ModalWindow misleading
Hi The example here : http://www.wicket-library.com/wicket-examples/ajax/modal-window.1 is pretty misleading : passing components between components/page is quite broken as can be seen in the past discussion on the mailing list (serialization issue can arise and makes both sides using different references of the same object "logically speaking"). However, as it is in the example, I first used it considering that it should be ok to do so. Could it be changed in some way ? On the bigger picture, I guess it raises again the issue of the "recommended" way of communicating between the page and the modal window, which currently doesn't exist (session, database...??). However, this example is currently completely misleading, so even so comments to explicit the issue would be welcomed. thanks again nono - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket 1.4 rc 2 : FileUpload name collision
Hi I just wanted to point out that there is currently two classes named FileUpload in wicket 1.4, one in org.apache.wicket.markup.html.form.upload and in the other in org.apache.wicket.util.upload. Could it be changed ? It would avoid some confusion and potential errors. thanks in advance nono - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: LinkTree breaks when using twice instances of Firefox (with Unexpected RuntimeException)
Thanks for your reply the jira is there https://issues.apache.org/jira/browse/WICKET-2233 bye 2009/4/19 Igor Vaynberg : > yes > > -igor > > On Sun, Apr 19, 2009 at 1:54 AM, Live Nono wrote: >> hi >> >> In case some one is interested, i found the solution : adding >> getPageSettings().setAutomaticMultiWindowSupport(true); solves the >> issue. >> >> I'm quite surprised though because the javadocs of this setting says >> it's enabled by default, which doesn't seem to be the case in fact. >> Should I open a jira issue for this ? >> >> bye >> nono >> >> >> >> >> 2009/4/18 Live Nono : >>> Hi >>> >>> I've just spotted the same behavior within the wicket examples page >>> itself, there : >>> http://www.wicket-library.com/wicket-examples/ajax/tree/simple.1 >>> >>> Open two tabs/windows of the same browser and then play with the tree >>> in one page and then the others, then it'll fail "internal error" it >>> says... >>> >>> In fact the state of the tree seems to be shared among the two pages : >>> do some changes on one page and then refresh the other page (with F5), >>> it'll have the state of the previous one. >>> >>> Is it an expected behavior for you ? If so, could someone tell me why >>> and if it's possible to avoid it ? >>> >>> thanks in advance >>> nono >>> >>> 2009/4/17, Live Nono : >>>> Hi >>>> >>>> I'm still working on this tree need and I've discovered this issue : >>>> - opening the page tree in Firefox (or Iceweasel in my ubuntu) >>>> - navigating the tree >>>> - opening the page tree in another tab or instance of firefox >>>> - navigating the tree in this second instance >>>> - when willing again to navigate in the first page, it breaks with an >>>> Unexpected RuntimeException >>>> >>>> However, browsing in 2 different browsers at the same time isn't an >>>> issue (at least with Iceweasel and epiphany, the gnome web browser). >>>> When using 2 epiphany (tabs or instances) at the same time, the issue >>>> is the same. >>>> >>>> My detailed config is Mozilla/5.0 (X11; U; Linux i686; en-US; >>>> rv:1.9.0.7) Gecko/2009032803 Iceweasel/3.0.6 (Debian-3.0.6-1) with >>>> iceweasel 3.0.6 and epiphany/gnome web browser 2.22.3 >>>> >>>> The page in question is heavy on the Ajax side, so perhaps it isn't >>>> directly TreeLink related. >>>> >>>> Am I missing something or... ? >>>> >>>> Thanks in advance >>>> nono >>>> >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: LinkTree breaks when using twice instances of Firefox (with Unexpected RuntimeException)
hi In case some one is interested, i found the solution : adding getPageSettings().setAutomaticMultiWindowSupport(true); solves the issue. I'm quite surprised though because the javadocs of this setting says it's enabled by default, which doesn't seem to be the case in fact. Should I open a jira issue for this ? bye nono 2009/4/18 Live Nono : > Hi > > I've just spotted the same behavior within the wicket examples page > itself, there : > http://www.wicket-library.com/wicket-examples/ajax/tree/simple.1 > > Open two tabs/windows of the same browser and then play with the tree > in one page and then the others, then it'll fail "internal error" it > says... > > In fact the state of the tree seems to be shared among the two pages : > do some changes on one page and then refresh the other page (with F5), > it'll have the state of the previous one. > > Is it an expected behavior for you ? If so, could someone tell me why > and if it's possible to avoid it ? > > thanks in advance > nono > > 2009/4/17, Live Nono : >> Hi >> >> I'm still working on this tree need and I've discovered this issue : >> - opening the page tree in Firefox (or Iceweasel in my ubuntu) >> - navigating the tree >> - opening the page tree in another tab or instance of firefox >> - navigating the tree in this second instance >> - when willing again to navigate in the first page, it breaks with an >> Unexpected RuntimeException >> >> However, browsing in 2 different browsers at the same time isn't an >> issue (at least with Iceweasel and epiphany, the gnome web browser). >> When using 2 epiphany (tabs or instances) at the same time, the issue >> is the same. >> >> My detailed config is Mozilla/5.0 (X11; U; Linux i686; en-US; >> rv:1.9.0.7) Gecko/2009032803 Iceweasel/3.0.6 (Debian-3.0.6-1) with >> iceweasel 3.0.6 and epiphany/gnome web browser 2.22.3 >> >> The page in question is heavy on the Ajax side, so perhaps it isn't >> directly TreeLink related. >> >> Am I missing something or... ? >> >> Thanks in advance >> nono >> > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: LinkTree breaks when using twice instances of Firefox (with Unexpected RuntimeException)
Hi I've just spotted the same behavior within the wicket examples page itself, there : http://www.wicket-library.com/wicket-examples/ajax/tree/simple.1 Open two tabs/windows of the same browser and then play with the tree in one page and then the others, then it'll fail "internal error" it says... In fact the state of the tree seems to be shared among the two pages : do some changes on one page and then refresh the other page (with F5), it'll have the state of the previous one. Is it an expected behavior for you ? If so, could someone tell me why and if it's possible to avoid it ? thanks in advance nono 2009/4/17, Live Nono : > Hi > > I'm still working on this tree need and I've discovered this issue : > - opening the page tree in Firefox (or Iceweasel in my ubuntu) > - navigating the tree > - opening the page tree in another tab or instance of firefox > - navigating the tree in this second instance > - when willing again to navigate in the first page, it breaks with an > Unexpected RuntimeException > > However, browsing in 2 different browsers at the same time isn't an > issue (at least with Iceweasel and epiphany, the gnome web browser). > When using 2 epiphany (tabs or instances) at the same time, the issue > is the same. > > My detailed config is Mozilla/5.0 (X11; U; Linux i686; en-US; > rv:1.9.0.7) Gecko/2009032803 Iceweasel/3.0.6 (Debian-3.0.6-1) with > iceweasel 3.0.6 and epiphany/gnome web browser 2.22.3 > > The page in question is heavy on the Ajax side, so perhaps it isn't > directly TreeLink related. > > Am I missing something or... ? > > Thanks in advance > nono > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
LinkTree breaks when using twice instances of Firefox (with Unexpected RuntimeException)
Hi I'm still working on this tree need and I've discovered this issue : - opening the page tree in Firefox (or Iceweasel in my ubuntu) - navigating the tree - opening the page tree in another tab or instance of firefox - navigating the tree in this second instance - when willing again to navigate in the first page, it breaks with an Unexpected RuntimeException However, browsing in 2 different browsers at the same time isn't an issue (at least with Iceweasel and epiphany, the gnome web browser). When using 2 epiphany (tabs or instances) at the same time, the issue is the same. My detailed config is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009032803 Iceweasel/3.0.6 (Debian-3.0.6-1) with iceweasel 3.0.6 and epiphany/gnome web browser 2.22.3 The page in question is heavy on the Ajax side, so perhaps it isn't directly TreeLink related. Am I missing something or... ? Thanks in advance nono Unexpected RuntimeException WicketMessage: Exception in rendering component: [Component id = content, page = myproject.web.EditTreePage, path = 11:tree:i:3:nodeComponent:contentLink:content.Label, isVisible = true, isVersioned = false] Root cause: java.lang.ClassCastException: javax.swing.tree.DefaultMutableTreeNode cannot be cast to java.lang.String at org.apache.wicket.util.convert.ConverterLocator$DefaultConverter.convertToString(ConverterLocator.java:127) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1653) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1625) at org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:115) at org.apache.wicket.Component.renderComponent(Component.java:2561) at org.apache.wicket.markup.html.WebComponent.onRender(WebComponent.java:62) at org.apache.wicket.Component.render(Component.java:2398) at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1377) at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1559) at org.apache.wicket.markup.html.link.AbstractLink.onComponentTagBody(AbstractLink.java:166) at org.apache.wicket.Component.renderComponent(Component.java:2561) at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1494) at org.apache.wicket.Component.render(Component.java:2398) at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1377) at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1559) at org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:658) at org.apache.wicket.markup.html.panel.Panel.onComponentTagBody(Panel.java:114) at org.apache.wicket.Component.renderComponent(Component.java:2561) at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1494) at org.apache.wicket.Component.render(Component.java:2398) at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1377) at org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1559) at org.apache.wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:1483) at org.apache.wicket.Component.renderComponent(Component.java:2561) at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1494) at org.apache.wicket.markup.html.tree.AbstractTree$TreeItem.onRender(AbstractTree.java:212) at org.apache.wicket.Component.render(Component.java:2398) at org.apache.wicket.Component.renderComponent(Component.java:2501) at org.apache.wicket.ajax.AjaxRequestTarget.respondComponent(AjaxRequestTarget.java:756) at org.apache.wicket.ajax.AjaxRequestTarget.respondComponents(AjaxRequestTarget.java:650) at org.apache.wicket.ajax.AjaxRequestTarget.respond(AjaxRequestTarget.java:562) at org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1175) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1246) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1347) at org.apache.wicket.RequestCycle.request(RequestCycle.java:497) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199) at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:87) at org.codesmell.jpsak.servlet.EntityManagerFilter.doFilter(EntityManagerFilter.java:40) at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:87) at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:181) at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:266) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:269) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:603) at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:721) at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:643) at java.lang.Thread.run(Thread.java:619) Complete stack: org.a
Re: LinkTree : when using a refreshing model, expanding/collapsing nodes not working anymore
hi
I didn't manage to sleep this night so I did a quickstart project with my
issue and then... realised how stupid I've been : when refreshing the tree I
loose the data about what to open/close, hence my issue.
I don't know yet the solution I'll follow, hesitating between informing the
user and refreshing the whole tree as soon as data behind change or keep
track of the tree state in some wrappers around my data.
Time'll tell, and hopefully my brain will be faster next time :)
Side node : I'm once again amazed by the flexibility of wicket. It's really
able to fit anyone needs.
The only "issue" with this tree, in my case, is that I find the code is a
bit clumsy. First I affect the data to the nodes (using recursion), and
then, when the linkTree is created, I assign some state to it according to
some specific nodes I've just added (like which one will be first the first
one, or to expand some nodes in order to have one pre selected), being kind
of required to keep track of them in between.
thanks again
nono
NB : I hope it doesn't seem like the mailing list is my teddy bear, even if
the fact is that I spend a lot of time before asking trying to figure out by
myself...
2009/4/15 Live Nono
> Small extra precision : using tree.getTreeState().expandAll()/collapseAll()
> works fine...
>
> 2009/4/15 Live Nono
>
> Hi
>>
>> I've another issue with the LinkTree.
>>
>> Up to recently, it was working all fine. I was creating the LinkTree this
>> way :
>> new LinkTree("tree", getTreeModel())
>>
>> But then I wanted the model to be refreshed at each request. I tried with
>> many refreshing models like for example new LinkTree("tree", new
>> LoadableTreeModel(rootId)) or new LinkTree("tree", new PropertyModel(this,
>> "TreeModel"))...
>>
>> However, each time, the expanding/collapsing behavior doesn't work
>> anymore. When I click on the + or - nothing happens.
>>
>> Any help regarding what to do/where to look is highly welcomed !
>>
>> thanks in advance
>> nono
>>
>
>
Re: LinkTree : when using a refreshing model, expanding/collapsing nodes not working anymore
Small extra precision : using tree.getTreeState().expandAll()/collapseAll()
works fine...
2009/4/15 Live Nono
> Hi
>
> I've another issue with the LinkTree.
>
> Up to recently, it was working all fine. I was creating the LinkTree this
> way :
> new LinkTree("tree", getTreeModel())
>
> But then I wanted the model to be refreshed at each request. I tried with
> many refreshing models like for example new LinkTree("tree", new
> LoadableTreeModel(rootId)) or new LinkTree("tree", new PropertyModel(this,
> "TreeModel"))...
>
> However, each time, the expanding/collapsing behavior doesn't work anymore.
> When I click on the + or - nothing happens.
>
> Any help regarding what to do/where to look is highly welcomed !
>
> thanks in advance
> nono
>
LinkTree : when using a refreshing model, expanding/collapsing nodes not working anymore
Hi
I've another issue with the LinkTree.
Up to recently, it was working all fine. I was creating the LinkTree this
way :
new LinkTree("tree", getTreeModel())
But then I wanted the model to be refreshed at each request. I tried with
many refreshing models like for example new LinkTree("tree", new
LoadableTreeModel(rootId)) or new LinkTree("tree", new PropertyModel(this,
"TreeModel"))...
However, each time, the expanding/collapsing behavior doesn't work anymore.
When I click on the + or - nothing happens.
Any help regarding what to do/where to look is highly welcomed !
thanks in advance
nono
Re: LinkTree : how to be notified on any node expansion ?
hi I've found the method onJunctionLinkClicked, it does the trick. thx 2009/4/15 Live Nono > Hi > > I'm using the LinkTree to display a tree with expand all/collapse all > links. > > I would like to do the following behaviors : > - expand all clicked : expand all link disabled > - any node selected or expanded : expand all link enabled > > The same goes for collapse all. > > I already manage to be inform of node selection, but not of node expansion. > Is there a way to do so ? > > Thanks in advance > live nono >
LinkTree : how to be notified on any node expansion ?
Hi I'm using the LinkTree to display a tree with expand all/collapse all links. I would like to do the following behaviors : - expand all clicked : expand all link disabled - any node selected or expanded : expand all link enabled The same goes for collapse all. I already manage to be inform of node selection, but not of node expansion. Is there a way to do so ? Thanks in advance live nono
