Re: Javascript conflict between x:tree2 and x:inputCalendar

pecifically, as I > reported on issue #MYFACES-743, I can't have x:tree2 with client-side > toggling and x:calendar with popup, because the treeNavClick javascript > function fails. > > Also, I noticed that the generated HTML body tag is malformed: > > > > (with a spa

Javascript conflict between x:tree2 and x:inputCalendar

Does anyone have any idea of what's happening with the javascript resources lately, that they seem to conflict with each other? Specifically, as I reported on issue #MYFACES-743, I can't have x:tree2 with client-side toggling and x:calendar with popup, because the treeNavClick javascrip

x:tree2 cookie exception and renewing the tree model [Scanned by ClamAV]

(Embedded image moved to file: pic28710.jpg) We are using x:tree2 in 2 webapplications. The clients are thrilled. But, … We really need some help with x:tree2. I don't know whether this is a bug in x:tree2, other whether it is our code. Some discussion might help. We use client

x:tree2 cookie exception and renewing the tree model We are using x:tree2 in 2 webapplications. The clients are thrilled. But, … We really need some help with x:tree2. I don't know whether this is a bug in x:tree2, other whether it is our code. Some discussion might help. We use client side navigation. 1) The tree model we use comes from a backing bean method: #{userH.treeModel}. The tree model is cached in a backing bean instance variable (it is a tree of instances of 4 different inner classes of the handler class). At a certain time, we call a stored procedure on the DB that adds some data, that represent nodes in the tree, from an action method. After the stored procedure, we refresh the cached data, before we end the action method. We debugged, and the new data is in the tree model. During render response, the getTreeModel method is called. But still the new nodes don't show up in the page. What are we missing? 2) We regularly get exceptions that have to do with parsing and the cookie. These exceptions are discussed in this list already, but I could not find any conclusive answer. With us, they "happen", after extensive use (impossible to debug), and after switching the user. I.e., the first user logs out, we log in as a second user, a completely new tree model is created in the beacking bean, we are directed to the page with the tree, and this gives the exception. To be able to solve these problems, a bit of explanation about the expected behavior would be nice, or someone talking us through the x:tree2 code, so that we can debug the problem ourself. We've done an effort, but as it is now, the code is a bit to dark for us to really understand what the intention is. We presume the x:tree2 code is caching the tree model somewhere, and that this is the cause of all these problems. But we didn't find where this cache might be, and how to reset it.

We are using x:tree2 in 2 webapplications. The clients are thrilled. But, … We really need some help with x:tree2. I don't know whether this is a bug in x:tree2, other whether it is our code. Some discussion might help. We use client side navigation. 1) The tree model we use comes f

Re: x:tree2 cookies exception

At 00:42 31/05/2005, you wrote: Every now and again, after extensive use, we get something like the following exception from x:tree2: 13:01:20,377 ERROR ApplyRequestValuesPhase:84 - Node with id 0:12. Failed to parse 0:12 java.lang.IllegalArgumentException: Node with id 0:12. Failed to parse

Re: x:tree2 - Example of Action Listener

ces Discussion" Sent: Monday, March 28, 2005 3:33 PM Subject: x:tree2 - Example of Action Listener Does anyone have any examples of the Action Listener for tree2? Regards, Roger Lee Internet communications are not secure and therefore NOTiFY does not accept legal responsibility for th

x:tree2 - Example of Action Listener

Does anyone have any examples of the Action Listener for tree2? Regards, Roger Lee Internet communications are not secure and therefore NOTiFY does not accept legal responsibility for the contents of this message. Although NOTiFY operates anti-virus programmes, it does not accept responsibility for

Re: x:tree2 problem - Fixed

ED]> To: "Roger Lee, NOTiFY" <[EMAIL PROTECTED]>; "MyFaces Discussion" Sent: Monday, March 28, 2005 2:34 PM Subject: Re: x:tree2 problem - Fixed Roger, I looked at the code that you sent me offlist. I'm glad you got everything working but your explanation of what solve

Re: x:tree2 problem - Fixed

an Schofield" <[EMAIL PROTECTED]> > To: "Roger Lee, NOTiFY" <[EMAIL PROTECTED]>; "MyFaces Discussion" > > Sent: Saturday, March 26, 2005 2:47 PM > Subject: Re: x:tree2 > > >I can't think of a reason why your tree wouldn't di

Re: x:tree2 problem - Fixed

r business reasons. - Original Message - From: "Sean Schofield" <[EMAIL PROTECTED]> To: "Roger Lee, NOTiFY" <[EMAIL PROTECTED]>; "MyFaces Discussion" Sent: Saturday, March 26, 2005 2:47 PM Subject: Re: x:tree2 I can't think of a reason why your

Re: x:tree2

onitored by NOTiFY for operational or > business reasons. > > - Original Message - > From: "Sean Schofield" <[EMAIL PROTECTED]> > To: "MyFaces Discussion" ; "Roger Lee, > NOTiFY" <[EMAIL PROTECTED]> > Sent: Friday, March 25, 2005 2

Re: x:tree2

monitored by NOTiFY for operational or business reasons. - Original Message - From: "Sean Schofield" <[EMAIL PROTECTED]> To: "MyFaces Discussion" ; "Roger Lee, NOTiFY" <[EMAIL PROTECTED]> Sent: Friday, March 25, 2005 2:08 PM Subject: Re: x:tree

Re: x:tree2

aces I am trying to use the x:tree2 > component. > > I have taken the backing class which I used with Web Galileo and converted > it to use TreeNode. > > The JSP gets called and my "breakpoints" are displayed in the JBoss console, > but no Tree is rendered or er

x:tree2

Using the example supplied with MyFaces I am trying to use the x:tree2 component. I have taken the backing class which I used with Web Galileo and converted it to use TreeNode. The JSP gets called and my "breakpoints" are displayed in the JBoss console, but no Tree is rendered