Re: OptionalValidator - Required validator - compound components
Hi,Yes, tree traversing won't work in case of a datatable. I always think required attribute is a mistake, it should be a validator instead.Cagatay,On 6/18/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: After looking more at the source code for the optional validatorframework, it doesn't look to me like it will support data tables,trees and other complex comonents that render children multiple times.It walks the component tree looking for required components, but it will never check rows of a data table for example as it won't iteratethe rows, only the components once. Don't suppose there is a wayaround this. I have no idea why JSF has the required attribute insteadof a required validator. Is this true, or did I miss something?-Andrew
Tomahawk Schedule
Ave! I'm a beginner and I'm with problems on start to use the Tomahawk Schedule component. Has somebody a war file example with some initial code, or template to help me? Tnks.-- May the Source be with you
Re: AUTO_SCROLL Kills Command Links
or: create an issue and upload a "sample war file" On 6/17/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: Can some of you post a directory listing of WEB-INF/lib ? A snippet of all jsf related context params would help as well. Dennis Byrne >-Original Message- >From: Hailong Zhang [mailto:[EMAIL PROTECTED] >Sent: Sunday, June 18, 2006 01:11 AM >To: 'MyFaces Discussion' >Subject: Re: AUTO_SCROLL Kills Command Links > >Hi Dennis, >I have this problem too. My environment is Windows XP sp2, >Firefox1.5.0.4, JDK 1.5.0_06-b05. MyFaces 1.1.3 & Tomahawk 1.1.3, > >2006/6/18, Dennis Byrne <[EMAIL PROTECTED]>: >> >> I still can't reproduce this - using the simple examples web application >> (myfaces distribution). I tried w/ trunk and with MyFaces 1.1.3 and >> Tomahawk 1.1.3 . getScrolling() renders when the >> org.apache.myfaces.AUTO_SCROLL context parameter is set to true and >> getScrolling() dows not render when the org.apache.myfaces.AUTO_SCROLLcontext parameter is set to false. In both cases and the outputLink >> elements on the home page work. >> >> @Mike - An example of the org.apache.myfaces.AUTO_SCROLL context param, w/ >> a few lines of documentation, is in web.xml of the simple examples >> application. >> >> So ... what is it about your dev environments that is different? It is >> probably something simple. >> >> Dennis Byrne >> >> >> >-Original Message- >> >From: Jim the Standing Bear [mailto:[EMAIL PROTECTED] >> >Sent: Saturday, June 17, 2006 03:09 PM >> >To: 'MyFaces Discussion' >> >Subject: Re: AUTO_SCROLL Kills Command Links >> > >> >It is a problem with the JavaScript function getScrolling(). Somehow it >> >doesn't get generated. This goes true not for commandlinks, but also >> other >> >stuff. One way to workaround is to run with an earlier version of the >> >myFaces, and look at the rendered html/javascript source code from the >> web >> >browser. Copy down the function getScolling()... then insert this >> function >> >in your .jsp file, and then compile and run with the newer version of >> >tomahawk. that way, the JS function will be there. >> > >> >On 6/17/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> >> >> >> Thx Dennis. >> >> >> >> If you use the Tomahawk jar from the 1.1.1 example app, the command >> links >> >> work. >> >> >> >> I am not a Java Script guru, but the java script that is generated is >> >> definitely different between >> >> the current 1.1.3 jar and the 1.1.1 jar; if you compare the two you >> might >> >> see the answer. >> >> >> >> Also, I can't seem to find my reference for configuring AUTO_SCROLL in >> >> general. Searching the >> >> Wiki does not help and there's lots of noise in Google. Can you please >> >> forward a reference link? >> >> >> >> Mike >> >> >> >> >> >> --- Dennis Byrne <[EMAIL PROTECTED]> wrote: >> >> >> >> > Hey guys. >> >> > >> >> > The dev team recognizes the problem and I promise it will be >> fixed. Any >> >> pointers from the user >> >> > community will help. >> >> > >> >> > Dennis Byrne >> >> > >> >> > >-Original Message- >> >> > >From: Enrique Medina [mailto:[EMAIL PROTECTED] >> >> > >Sent: Saturday, June 17, 2006 02:11 AM >> >> > >To: 'MyFaces Discussion' >> >> > >Subject: Re: AUTO_SCROLL Kills Command Links >> >> > > >> >> > >Me too :-( >> >> > > >> >> > >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote: >> >> > >> >> >> > >> I have also brought this issue up before, still have it with >> >> 1.1.4Snapshot. >> >> > >> >> >> > >> >> >> > >> >> >> > >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> >> > >> > >> >> > >> > This issue has been brought up in multiple posts to this list. >> >> > >> > >> >> > >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and >> >> greatest >> >> > >> > for both). >> >> > >> > >> >> > >> > When I configure AUTO_SCROLL to true, the command links do not >> >> function. >> >> > >> > >> >> > >> > >> >> > >> > Mike >> >> > >> > >> >> > >> > __ >> >> > >> > Do You Yahoo!? >> >> > >> > Tired of spam? Yahoo! Mail has the best spam protection around >> >> > >> > http://mail.yahoo.com >> >> > >> > >> >> > >> >> >> > >> >> >> > > >> >> > >> >> > >> >> > >> >> >> >> >> >> __ >> >> Do You Yahoo!? >> >> Tired of spam? Yahoo! Mail has the best spam protection around >> >> http://mail.yahoo.com >> >> >> > >> > >> > >> >-- >> >-- >> >Standing Bear Has Spoken >> >-- >> > >> >> >> > -- Matthias Wessendorf Aechterhoek 18 48282 Emsdetten blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: AUTO_SCROLL Kills Command Links
Can some of you post a directory listing of WEB-INF/lib ? A snippet of all jsf related context params would help as well. Dennis Byrne >-Original Message- >From: Hailong Zhang [mailto:[EMAIL PROTECTED] >Sent: Sunday, June 18, 2006 01:11 AM >To: 'MyFaces Discussion' >Subject: Re: AUTO_SCROLL Kills Command Links > >Hi Dennis, >I have this problem too. My environment is Windows XP sp2, >Firefox1.5.0.4, JDK 1.5.0_06-b05. MyFaces 1.1.3 & Tomahawk 1.1.3, > >2006/6/18, Dennis Byrne <[EMAIL PROTECTED]>: >> >> I still can't reproduce this - using the simple examples web application >> (myfaces distribution). I tried w/ trunk and with MyFaces 1.1.3 and >> Tomahawk 1.1.3 . getScrolling() renders when the >> org.apache.myfaces.AUTO_SCROLL context parameter is set to true and >> getScrolling() dows not render when the >> org.apache.myfaces.AUTO_SCROLLcontext parameter is set to false. In both >> cases and the outputLink >> elements on the home page work. >> >> @Mike - An example of the org.apache.myfaces.AUTO_SCROLL context param, w/ >> a few lines of documentation, is in web.xml of the simple examples >> application. >> >> So ... what is it about your dev environments that is different? It is >> probably something simple. >> >> Dennis Byrne >> >> >> >-Original Message- >> >From: Jim the Standing Bear [mailto:[EMAIL PROTECTED] >> >Sent: Saturday, June 17, 2006 03:09 PM >> >To: 'MyFaces Discussion' >> >Subject: Re: AUTO_SCROLL Kills Command Links >> > >> >It is a problem with the JavaScript function getScrolling(). Somehow it >> >doesn't get generated. This goes true not for commandlinks, but also >> other >> >stuff. One way to workaround is to run with an earlier version of the >> >myFaces, and look at the rendered html/javascript source code from the >> web >> >browser. Copy down the function getScolling()... then insert this >> function >> >in your .jsp file, and then compile and run with the newer version of >> >tomahawk. that way, the JS function will be there. >> > >> >On 6/17/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> >> >> >> Thx Dennis. >> >> >> >> If you use the Tomahawk jar from the 1.1.1 example app, the command >> links >> >> work. >> >> >> >> I am not a Java Script guru, but the java script that is generated is >> >> definitely different between >> >> the current 1.1.3 jar and the 1.1.1 jar; if you compare the two you >> might >> >> see the answer. >> >> >> >> Also, I can't seem to find my reference for configuring AUTO_SCROLL in >> >> general. Searching the >> >> Wiki does not help and there's lots of noise in Google. Can you please >> >> forward a reference link? >> >> >> >> Mike >> >> >> >> >> >> --- Dennis Byrne <[EMAIL PROTECTED]> wrote: >> >> >> >> > Hey guys. >> >> > >> >> > The dev team recognizes the problem and I promise it will be >> fixed. Any >> >> pointers from the user >> >> > community will help. >> >> > >> >> > Dennis Byrne >> >> > >> >> > >-Original Message- >> >> > >From: Enrique Medina [mailto:[EMAIL PROTECTED] >> >> > >Sent: Saturday, June 17, 2006 02:11 AM >> >> > >To: 'MyFaces Discussion' >> >> > >Subject: Re: AUTO_SCROLL Kills Command Links >> >> > > >> >> > >Me too :-( >> >> > > >> >> > >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote: >> >> > >> >> >> > >> I have also brought this issue up before, still have it with >> >> 1.1.4Snapshot. >> >> > >> >> >> > >> >> >> > >> >> >> > >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> >> > >> > >> >> > >> > This issue has been brought up in multiple posts to this list. >> >> > >> > >> >> > >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and >> >> greatest >> >> > >> > for both). >> >> > >> > >> >> > >> > When I configure AUTO_SCROLL to true, the command links do not >> >> function. >> >> > >> > >> >> > >> > >> >> > >> > Mike >> >> > >> > >> >> > >> > __ >> >> > >> > Do You Yahoo!? >> >> > >> > Tired of spam? Yahoo! Mail has the best spam protection around >> >> > >> > http://mail.yahoo.com >> >> > >> > >> >> > >> >> >> > >> >> >> > > >> >> > >> >> > >> >> > >> >> >> >> >> >> __ >> >> Do You Yahoo!? >> >> Tired of spam? Yahoo! Mail has the best spam protection around >> >> http://mail.yahoo.com >> >> >> > >> > >> > >> >-- >> >-- >> >Standing Bear Has Spoken >> >-- >> > >> >> >> >
Re: AUTO_SCROLL Kills Command Links
Hi Dennis, I have this problem too. My environment is Windows XP sp2, Firefox1.5.0.4, JDK 1.5.0_06-b05. MyFaces 1.1.3 & Tomahawk 1.1.3,2006/6/18, Dennis Byrne < [EMAIL PROTECTED]>:I still can't reproduce this - using the simple examples web application (myfaces distribution). I tried w/ trunk and with MyFaces 1.1.3 and Tomahawk 1.1.3 . getScrolling() renders when the org.apache.myfaces.AUTO_SCROLL context parameter is set to true and getScrolling() dows not render when the org.apache.myfaces.AUTO_SCROLL context parameter is set to false. In both cases and the outputLink elements on the home page work. @Mike - An example of the org.apache.myfaces.AUTO_SCROLL context param, w/ a few lines of documentation, is in web.xml of the simple examples application.So ... what is it about your dev environments that is different? It is probably something simple. Dennis Byrne>-Original Message->From: Jim the Standing Bear [mailto:[EMAIL PROTECTED]]>Sent: Saturday, June 17, 2006 03:09 PM >To: 'MyFaces Discussion'>Subject: Re: AUTO_SCROLL Kills Command Links>>It is a problem with the _javascript_ function getScrolling(). Somehow it>doesn't get generated. This goes true not for commandlinks, but also other >stuff. One way to workaround is to run with an earlier version of the>myFaces, and look at the rendered html/_javascript_ source code from the web>browser. Copy down the function getScolling()... then insert this function >in your .jsp file, and then compile and run with the newer version of>tomahawk. that way, the JS function will be there.>>On 6/17/06, Mike Duffy <[EMAIL PROTECTED] > wrote: Thx Dennis. If you use the Tomahawk jar from the 1.1.1 example app, the command links>> work. I am not a _javascript_ guru, but the _javascript_ that is generated is >> definitely different between>> the current 1.1.3 jar and the 1.1.1 jar; if you compare the two you might>> see the answer. Also, I can't seem to find my reference for configuring AUTO_SCROLL in >> general. Searching the>> Wiki does not help and there's lots of noise in Google. Can you please>> forward a reference link? Mike>> --- Dennis Byrne < [EMAIL PROTECTED]> wrote: > Hey guys.>> >>> > The dev team recognizes the problem and I promise it will be fixed. Any>> pointers from the user >> > community will help.>> >>> > Dennis Byrne>> >>> > >-Original Message->> > >From: Enrique Medina [mailto: [EMAIL PROTECTED]]>> > >Sent: Saturday, June 17, 2006 02:11 AM>> > >To: 'MyFaces Discussion'>> > >Subject: Re: AUTO_SCROLL Kills Command Links>> > > >> > >Me too :-(>> > >>> > >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote:>> > > >> I have also brought this issue up before, still have it with >> 1.1.4Snapshot.>> > > > > >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED] > wrote:>> > >> >>> > >> > This issue has been brought up in multiple posts to this list.>> > >> >>> > >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and>> greatest>> > >> > for both).>> > >> >>> > >> > When I configure AUTO_SCROLL to true, the command links do not >> function.>> > >> >>> > >> >>> > >> > Mike>> > >> >>> > >> > __ >> > >> > Do You Yahoo!?>> > >> > Tired of spam? Yahoo! Mail has the best spam protection around>> > >> > http://mail.yahoo.com >> > >> >>> > > > >>> >>> >>> >>> __ >> Do You Yahoo!?>> Tired of spam? Yahoo! Mail has the best spam protection around>> http://mail.yahoo.com>>-- >-->Standing Bear Has Spoken>-->
Understanding the lifecycle and complex components like UIData
I was trying to determine how I could maybe "fix" the problem of having data tables lose their submitted values when there are validation errors or when the action is immediate, and I am not sure how the UIInput components actually work in the UIData. What I saw: The UI Data runs all of the decode/validation/updates for each of its child components, but during each of it's phases. However, UIInput components set their values from the local value they get from the decode phase. If each component is evaluated one time for each row, this local value would be invalid. How do UIInput components get their correct values inside these complex controls (what didn't I see in the code)? Thanks, Andrew
Re: Deleting Nodes/Branch from Tree
Rows state is by row index not row ID unfortunately (I sumbitted an issue on this). As a result you will have that issue. Best thing you can do is write a custom tree state object for your model or manually expand/collapse the paths when you add/remove nodes. BTW - You shouln't have to rebuild the branch, but simply remove the nodes you need to (unless you really need to rebuild the nodes for some reason). -Andrew On 6/17/06, Hughes, Stan <[EMAIL PROTECTED]> wrote: This may seem counter-productive to some, but, I need to be able to dynamically delete and rebuild a tree structure. The thing is, I need the data to always be real-time… So, given the tree following: A | A1 |A1.1 B How do I, when the user clicks the A node, delete everything beneath it so that I can rebuild it? I have tried various things, but, nothing seems to work. The only way I can see to do it is, HtmlTree tree = (HtmlTree) component; selectedNode = (TreeNodeBase) tree.getNode(); selectedNode.getChildren().removeAll(selectedNode.getChildren()); But, this does not work. When the tree is rebuilt, the nodes seem to keep the state of the node that previously occupied that position. Here is what happens: if the user selects A, then selects A1 (to expand them), and then collapses A by selecting it again, everything looks normal. But if he then selects A to expand it (again), the code is supposed to delete everything below A and rebuild the first level below A (like lazy loading). This appears to work also, but, A1, though it has been deleted and newly created, has the state of being expanded – forcing you to select it twice to expand it… Is there some way to COMPLETELY remove everything below a node? Or, is my description not clear enough of what is going on? Thanks for any help…
OptionalValidator - Required validator - compound components
After looking more at the source code for the optional validator framework, it doesn't look to me like it will support data tables, trees and other complex comonents that render children multiple times. It walks the component tree looking for required components, but it will never check rows of a data table for example as it won't iterate the rows, only the components once. Don't suppose there is a way around this. I have no idea why JSF has the required attribute instead of a required validator. Is this true, or did I miss something? -Andrew
Re: Does SubForm do anything?
Well, that (below) almost worked. I let me add the row (with that dummy subform at the bottom of the page), but unfortunately the data table rows still lost their values since they were not validated. The optional validator would be idea except for that it only works with validator IDs and not validator tags. Perhaps I can look more at that code and find a way to do it. -Andrew On 6/15/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: My problem is that I would have to put a subForm around every input component, since the only parent component that I could wrap multiple elements contains the commandLink that I wouldn't want to trigger the validations from. Can a link in a subform NOT validate the sub for it is in? IOW is this possible? Clicking on the link should not include helperForm - is this true? -Andrew On 6/15/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > Andrew- > > you may take a look at [1]. > This example uses two component's and the > when you are outside of > any subform. When you click the first button (Show current values of > Person) - on a empty form_page - you'll get validations messages for > "First name" and "last name". > > For the second button (Show current values of Vehicle) you'll only get > the validation messages for "Type" and "Make". > > The example has no "global" input component (like yours). > > > -Matthias > > [1] http://www.irian.at/myfaces-sandbox/subForm.jsf > > On 6/15/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > Andrew, > > > > I don't know the subform sandbox component specifically > > (just the Trinidad component that partly inspired it); but I > > suspect that components that are outside of any subform > > will always process. Components that are in a subform > > other than the one that was submitted will not. > > > > -- Adam > > > > > > On 6/13/06, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > > I attempted to use the subForm sandbox component with absolutely no luck. > > > > > > I had a page like: > > > > > > > > > > > > > > >> > maximum="30"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > When I click the command link, I get validation errors from the input > > > text outside of the subform. Correct me if I am wrong, but I thought > > > the whole point of the subform was to stop validation and updating > > > outside of that component. > > > > > > What am I doing wrong? > > > > > > Tomahawk 1.1.2 > > > Sandbox snapshot 2006-05-13 > > > > > > Thanks, > > > Andrew > > > > > > > > -- > Matthias Wessendorf > Aechterhoek 18 > 48282 Emsdetten > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
Deleting Nodes/Branch from Tree
This may seem counter-productive to some, but, I need to be able to dynamically delete and rebuild a tree structure. The thing is, I need the data to always be real-time… So, given the tree following: A | A1 | A1.1 B How do I, when the user clicks the A node, delete everything beneath it so that I can rebuild it? I have tried various things, but, nothing seems to work. The only way I can see to do it is, HtmlTree tree = (HtmlTree) component; selectedNode = (TreeNodeBase) tree.getNode(); selectedNode.getChildren().removeAll(selectedNode.getChildren()); But, this does not work. When the tree is rebuilt, the nodes seem to keep the state of the node that previously occupied that position. Here is what happens: if the user selects A, then selects A1 (to expand them), and then collapses A by selecting it again, everything looks normal. But if he then selects A to expand it (again), the code is supposed to delete everything below A and rebuild the first level below A (like lazy loading). This appears to work also, but, A1, though it has been deleted and newly created, has the state of being expanded – forcing you to select it twice to expand it… Is there some way to COMPLETELY remove everything below a node? Or, is my description not clear enough of what is going on? Thanks for any help…
Re: AUTO_SCROLL Kills Command Links
I still can't reproduce this - using the simple examples web application (myfaces distribution). I tried w/ trunk and with MyFaces 1.1.3 and Tomahawk 1.1.3 . getScrolling() renders when the org.apache.myfaces.AUTO_SCROLL context parameter is set to true and getScrolling() dows not render when the org.apache.myfaces.AUTO_SCROLL context parameter is set to false. In both cases and the outputLink elements on the home page work. @Mike - An example of the org.apache.myfaces.AUTO_SCROLL context param, w/ a few lines of documentation, is in web.xml of the simple examples application. So ... what is it about your dev environments that is different? It is probably something simple. Dennis Byrne >-Original Message- >From: Jim the Standing Bear [mailto:[EMAIL PROTECTED] >Sent: Saturday, June 17, 2006 03:09 PM >To: 'MyFaces Discussion' >Subject: Re: AUTO_SCROLL Kills Command Links > >It is a problem with the JavaScript function getScrolling(). Somehow it >doesn't get generated. This goes true not for commandlinks, but also other >stuff. One way to workaround is to run with an earlier version of the >myFaces, and look at the rendered html/javascript source code from the web >browser. Copy down the function getScolling()... then insert this function >in your .jsp file, and then compile and run with the newer version of >tomahawk. that way, the JS function will be there. > >On 6/17/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> >> Thx Dennis. >> >> If you use the Tomahawk jar from the 1.1.1 example app, the command links >> work. >> >> I am not a Java Script guru, but the java script that is generated is >> definitely different between >> the current 1.1.3 jar and the 1.1.1 jar; if you compare the two you might >> see the answer. >> >> Also, I can't seem to find my reference for configuring AUTO_SCROLL in >> general. Searching the >> Wiki does not help and there's lots of noise in Google. Can you please >> forward a reference link? >> >> Mike >> >> >> --- Dennis Byrne <[EMAIL PROTECTED]> wrote: >> >> > Hey guys. >> > >> > The dev team recognizes the problem and I promise it will be fixed. Any >> pointers from the user >> > community will help. >> > >> > Dennis Byrne >> > >> > >-Original Message- >> > >From: Enrique Medina [mailto:[EMAIL PROTECTED] >> > >Sent: Saturday, June 17, 2006 02:11 AM >> > >To: 'MyFaces Discussion' >> > >Subject: Re: AUTO_SCROLL Kills Command Links >> > > >> > >Me too :-( >> > > >> > >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote: >> > >> >> > >> I have also brought this issue up before, still have it with >> 1.1.4Snapshot. >> > >> >> > >> >> > >> >> > >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED]> wrote: >> > >> > >> > >> > This issue has been brought up in multiple posts to this list. >> > >> > >> > >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and >> greatest >> > >> > for both). >> > >> > >> > >> > When I configure AUTO_SCROLL to true, the command links do not >> function. >> > >> > >> > >> > >> > >> > Mike >> > >> > >> > >> > __ >> > >> > Do You Yahoo!? >> > >> > Tired of spam? Yahoo! Mail has the best spam protection around >> > >> > http://mail.yahoo.com >> > >> > >> > >> >> > >> >> > > >> > >> > >> > >> >> >> __ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam protection around >> http://mail.yahoo.com >> > > > >-- >-- >Standing Bear Has Spoken >-- >
Re: AUTO_SCROLL Kills Command Links
It is a problem with the _javascript_ function getScrolling(). Somehow it doesn't get generated. This goes true not for commandlinks, but also other stuff. One way to workaround is to run with an earlier version of the myFaces, and look at the rendered html/_javascript_ source code from the web browser. Copy down the function getScolling()... then insert this function in your .jsp file, and then compile and run with the newer version of tomahawk. that way, the JS function will be there. On 6/17/06, Mike Duffy <[EMAIL PROTECTED]> wrote: Thx Dennis.If you use the Tomahawk jar from the 1.1.1 example app, the command links work. I am not a _javascript_ guru, but the _javascript_ that is generated is definitely different betweenthe current 1.1.3 jar and the 1.1.1 jar; if you compare the two you might see the answer.Also, I can't seem to find my reference for configuring AUTO_SCROLL in general. Searching the Wiki does not help and there's lots of noise in Google. Can you please forward a reference link?Mike--- Dennis Byrne <[EMAIL PROTECTED]> wrote: > Hey guys.>> The dev team recognizes the problem and I promise it will be fixed. Any pointers from the user> community will help.>> Dennis Byrne>> >-Original Message- > >From: Enrique Medina [mailto:[EMAIL PROTECTED]]> >Sent: Saturday, June 17, 2006 02:11 AM> >To: 'MyFaces Discussion'> >Subject: Re: AUTO_SCROLL Kills Command Links > >> >Me too :-(> >> >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote:> >>> >> I have also brought this issue up before, still have it with 1.1.4Snapshot.> >>> >>> >>> >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED]> wrote:> >> >> >> > This issue has been brought up in multiple posts to this list. > >> >> >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and greatest> >> > for both).> >> >> >> > When I configure AUTO_SCROLL to true, the command links do not function. > >> >> >> >> >> > Mike> >> >> >> > __> >> > Do You Yahoo!?> >> > Tired of spam? Yahoo! Mail has the best spam protection around > >> > http://mail.yahoo.com> >> >> >>> >>> __ Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com-- -- Standing Bear Has Spoken--
Re: AUTO_SCROLL Kills Command Links
Thx Dennis. If you use the Tomahawk jar from the 1.1.1 example app, the command links work. I am not a Java Script guru, but the java script that is generated is definitely different between the current 1.1.3 jar and the 1.1.1 jar; if you compare the two you might see the answer. Also, I can't seem to find my reference for configuring AUTO_SCROLL in general. Searching the Wiki does not help and there's lots of noise in Google. Can you please forward a reference link? Mike --- Dennis Byrne <[EMAIL PROTECTED]> wrote: > Hey guys. > > The dev team recognizes the problem and I promise it will be fixed. Any > pointers from the user > community will help. > > Dennis Byrne > > >-Original Message- > >From: Enrique Medina [mailto:[EMAIL PROTECTED] > >Sent: Saturday, June 17, 2006 02:11 AM > >To: 'MyFaces Discussion' > >Subject: Re: AUTO_SCROLL Kills Command Links > > > >Me too :-( > > > >On 6/16/06, Raj Rajendran <[EMAIL PROTECTED]> wrote: > >> > >> I have also brought this issue up before, still have it with 1.1.4Snapshot. > >> > >> > >> > >> On 6/16/06, Mike Duffy <[EMAIL PROTECTED]> wrote: > >> > > >> > This issue has been brought up in multiple posts to this list. > >> > > >> > I am using MyFaces Core 1.1.3 and Tomahawk 1.1.3 (latest and greatest > >> > for both). > >> > > >> > When I configure AUTO_SCROLL to true, the command links do not function. > >> > > >> > > >> > Mike > >> > > >> > __ > >> > Do You Yahoo!? > >> > Tired of spam? Yahoo! Mail has the best spam protection around > >> > http://mail.yahoo.com > >> > > >> > >> > > > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: myFaces Schedule entry clicked
When you click an entry with the left button, the id of the entry you clicked is put in a hidden input field, and the form that contains the schedule is submitted. The href of an entry is indeed "#", which is the same as in the commandLink for example. Are you saying that you get redirected to another page when clicking the entry? If so, it could be that you specified an action in you schedule tag.Jurgen2006/6/16, koRo < [EMAIL PROTECTED]>:Hallo, I hope someone can help me with the schedule component. I use myFaces and Tomahawk 1.1.4 Snapshot. I can add entries to the schedule in my pagelike descibed in the Tomahawk 1.1.4 examples. I can select the entry byusing the right mouse button, but everytime I click on an entry with the left button, I got redirected to /myAppDir/#.There seems to be a problem with the rendered href=""> '_idJsp24:_idJsp26','16621171118264607757920408448610');" _javascript_ Function. I hope, someone can help me, I'm despaired.--View this message in context: http://www.nabble.com/myFaces-Schedule-entry-clicked-t1798196.html#a4900238 Sent from the MyFaces - Users forum at Nabble.com.
Re: InputSuggest (non-AJAX)
I spent a few hours playing with the source code but didn't get very far. I guess I'm still too much of a novice in understanding the ins an outs to have a positive impact, though I did get a taste for maven which is pretty darn cool. Do you know of any other taglibs out there that function as inputSuggest was intended? By the way, you guys do an awesome job with tomahawk. Super useful stuff, even for the newbies! Dennis Sean Schofield wrote: > We kind of stopped work on it because it runs into trouble on IE with > large data sets (renders really slow.) I don't have a need for a > suggest control at the moment so I'm no longer working on it. I'll > probably try to help with the ajax version when I get enough time > again. > > Why not try modifying the existing source code so that you can make it > work the way you want? It might be a good opportunity to learn more > about JSF and open source in general. Just dive right in and you'll > be suprised how fast you will be able to fix things yourself! > > > Sean > > On 6/17/06, Dennis Gesker <[EMAIL PROTECTED]> wrote: >> Are there any plans for moving the non-AJAX inputSuggest from the >> sandbox into tomahawk? I gave the latest snapshot a try and this control >> is so close to being exactly what I need but there are properties that >> can't seem to be set (size, etc.). >> >> If there are no plans to promote this control could someone recommend >> another non-AJAX inputSuggest control? >> >> Dennis >> >> >> -- Dennis R. Gesker email: [EMAIL PROTECTED] gpg key: 0xEFA10A51
Re: InputSuggest (non-AJAX)
I don't know. There was no discussion about this component yet. If there are no plans to promote this control could someone recommend another non-AJAX inputSuggest control? Why not staying with the sandbox, when it fits your needs? Also it is allowed to *included* the source of the control to your own component library. Apache 2.0 license allows you to do so. -Matthias Dennis -- Matthias Wessendorf Aechterhoek 18 48282 Emsdetten blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: InputSuggest (non-AJAX)
We kind of stopped work on it because it runs into trouble on IE with large data sets (renders really slow.) I don't have a need for a suggest control at the moment so I'm no longer working on it. I'll probably try to help with the ajax version when I get enough time again. Why not try modifying the existing source code so that you can make it work the way you want? It might be a good opportunity to learn more about JSF and open source in general. Just dive right in and you'll be suprised how fast you will be able to fix things yourself! Sean On 6/17/06, Dennis Gesker <[EMAIL PROTECTED]> wrote: Are there any plans for moving the non-AJAX inputSuggest from the sandbox into tomahawk? I gave the latest snapshot a try and this control is so close to being exactly what I need but there are properties that can't seem to be set (size, etc.). If there are no plans to promote this control could someone recommend another non-AJAX inputSuggest control? Dennis
InputSuggest (non-AJAX)
Are there any plans for moving the non-AJAX inputSuggest from the sandbox into tomahawk? I gave the latest snapshot a try and this control is so close to being exactly what I need but there are properties that can't seem to be set (size, etc.). If there are no plans to promote this control could someone recommend another non-AJAX inputSuggest control? Dennis
Re: javax.faces.STATE_SAVING_METHOD doesn't work for form submting
Actually I am not using facelets, but in my case I believe the problem is that my component is embedded within a tabbedPanel -- View this message in context: http://www.nabble.com/javax.faces.STATE_SAVING_METHOD-doesn%27t-work-for-form-submting-t1679622.html#a4913792 Sent from the MyFaces - Users forum at Nabble.com.
Re: javax.faces.STATE_SAVING_METHOD doesn't work for form submting
This problem affect developers that uses facelets and can be solved by upgrading to a newer version of facelets.2006/6/16, pokkie <[EMAIL PROTECTED] >:I am experiencing exactly the same problem. Have you found a solution by any chance?--View this message in context: http://www.nabble.com/javax.faces.STATE_SAVING_METHOD-doesn%27t-work-for-form-submting-t1679622.html#a4910408 Sent from the MyFaces - Users forum at Nabble.com.-- Yours truly (Atenciosamente),Rogério
