Re: Committing new contributed components [was: Re: [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders children only if there is a message for the specified component(s)]
I suppose that an example would make a good minimum requirement for the sandbox. regards, Martin On 3/31/06, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]> wrote: > On the other hand: How are users thought to use and test a new > sandbox-component if not at least a minimal amount of informations is > available. > Either javadoc (describing how to use) or a minimal (incomplete) xdoc > documentation might make since also for sandbox stuff... > > just my 2cents > Alexander > > > -Original Message- > > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 30, 2006 10:53 PM > > To: MyFaces Development > > Subject: Re: Committing new contributed components [was: Re: > > [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders > > children only if there is a message for the specified component(s)] > > > > I'm explicitly -1 on putting this restriction on new > > components in the sandbox. > > > > The sandbox is a playground, and this is what it is supposed to be. > > > > I am +1 on only allowing a component to get to tomahawk if all those > > requirements are met. > > > > And by the way, we should really start to vote on the > > schedule component > > > > regards, > > > > Martin > > > > On 3/30/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > > And Javadoc as well on the component. Examples, > > > Javadoc, tag documentation, etc. (And, if there > > > were a solid testing framework in place, unit tests > > > as well!) > > > > > > -- Adam > > > > > > > > > On 3/30/06, Jurgen Lust <[EMAIL PROTECTED]> wrote: > > > > +1 > > > > A component is useless if people don't know how to use it. > > > > > > > > Jurgen > > > > > > > > Mike Kienenberger schreef: > > > > On 3/30/06, Bruno Aranda (JIRA) wrote: > > > > > > > > > > > > Many thanks Mike! This component could be useful to many > > people. I have > > > > committed it into the sandbox. Could you prepare a > > documentation patch for > > > > the web site? > > > > > > > > I'd like to propose that we don't accept (ie, commit) any new > > > > components until such components have both an example and xdocs > > > > documentation as part of the patch. > > > > > > > > This should also be true of anything we ourselves put > > into the sandbox. > > > > > > > > > > > > > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Committing new contributed components [was: Re: [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders children only if there is a message for the specified component(s)]
That sounds reasonalbe. some small example to get an idea, what the component does is a good (minimum) requirement. -Matthias On 3/31/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > I suppose that an example would make a good minimum requirement for the > sandbox. > > regards, > > Martin > > On 3/31/06, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]> wrote: > > On the other hand: How are users thought to use and test a new > > sandbox-component if not at least a minimal amount of informations is > > available. > > Either javadoc (describing how to use) or a minimal (incomplete) xdoc > > documentation might make since also for sandbox stuff... > > > > just my 2cents > > Alexander > > > > > -Original Message- > > > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, March 30, 2006 10:53 PM > > > To: MyFaces Development > > > Subject: Re: Committing new contributed components [was: Re: > > > [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders > > > children only if there is a message for the specified component(s)] > > > > > > I'm explicitly -1 on putting this restriction on new > > > components in the sandbox. > > > > > > The sandbox is a playground, and this is what it is supposed to be. > > > > > > I am +1 on only allowing a component to get to tomahawk if all those > > > requirements are met. > > > > > > And by the way, we should really start to vote on the > > > schedule component > > > > > > regards, > > > > > > Martin > > > > > > On 3/30/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > > > And Javadoc as well on the component. Examples, > > > > Javadoc, tag documentation, etc. (And, if there > > > > were a solid testing framework in place, unit tests > > > > as well!) > > > > > > > > -- Adam > > > > > > > > > > > > On 3/30/06, Jurgen Lust <[EMAIL PROTECTED]> wrote: > > > > > +1 > > > > > A component is useless if people don't know how to use it. > > > > > > > > > > Jurgen > > > > > > > > > > Mike Kienenberger schreef: > > > > > On 3/30/06, Bruno Aranda (JIRA) wrote: > > > > > > > > > > > > > > > Many thanks Mike! This component could be useful to many > > > people. I have > > > > > committed it into the sandbox. Could you prepare a > > > documentation patch for > > > > > the web site? > > > > > > > > > > I'd like to propose that we don't accept (ie, commit) any new > > > > > components until such components have both an example and xdocs > > > > > documentation as part of the patch. > > > > > > > > > > This should also be true of anything we ourselves put > > > into the sandbox. > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > http://www.irian.at > > > > > > Your JSF powerhouse - > > > JSF Consulting, Development and > > > Courses in English and German > > > > > > Professional Support for Apache MyFaces > > > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > -- Matthias Wessendorf Zülpicher Wall 12, 239 50674 Köln http://www.wessendorf.net mwessendorf-at-gmail-dot-com
Re: Committing new contributed components [was: Re: [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders children only if there is a message for the specified component(s)]
Martin Marinschek schrieb: > I'm explicitly -1 on putting this restriction on new components in the > sandbox. > > The sandbox is a playground, and this is what it is supposed to be. > > I am +1 on only allowing a component to get to tomahawk if all those > requirements are met. > > And by the way, we should really start to vote on the schedule component > > regards, > > Martin > I agree with that, that a component has to have good docs before being promoted into the tomahawk, for the sandbox, I would leave out the requirements, because too much is in fluctuation there. Btw. regarding the sandbox, I see it as a huge problem that some vendors have started to integrate the sandbox as component set into their tools.
HTTP/GET support
Hi. I seem to remember that there were talk about adding support for HTTP/GET requests in MyFaces, but I can't find it in the archive. If so - how much work has been done in this area and what is missing ? If not - where do I start to look in the code ? And what issues should I consider. I've some spare cycles this month, so I may be able to help out with various tasks or getting the work started. I believe that HTTP/GET support is important, since web-crawler can't handle HTTP/POST and therefore JSF sites can't be indexed in the search engines (that is not good for business). If anybody has other information let me know. Best regards, Jesper P.S. Please, Cc: me since I'm not on the list (yet)
Re: [VOTE] Promote Schedule Component to tomahawk
On 3/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > I am 0 on this, but I feel it is worth mentioning that there are already > > components in tomahawk that don't work w/ the RI though. > > > 0 is a good choice on that ;-) First off, Schedule might run fine on the RI. I just doubt that it's been tested on the RI since I removed the unused import dependency a couple days ago. Maybe we can start by documenting each component as a) expected to work on RI b) never tested on RI c) will not work on RI We can add a new xdocs section for this. In fact, we should add into that section comments on other JSF refs (RI 1.1, RI 1.2), portlets, and facelets as these questions frequently come up for each component. Maybe some kind of grid so we can add others as necessary. I'm not much of a UI designer, but if no one else steps up, I'll see what I can do.
Re: Committing new contributed components [was: Re: [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders children only if there is a message for the specified component(s)]
On 3/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > That sounds reasonalbe. > some small example to get an idea, what the component does is a good > (minimum) requirement. > > -Matthias > > On 3/31/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > > I suppose that an example would make a good minimum requirement for the > > sandbox. My original proposal was an example and xdocs. If xdocs is too painful, what about an example and documentation (xdocs or wiki). I really think minimal documentation (what it does, how to configure it) need to be there for the component to be of use to anyone other than the contributor. And I think an example is the best way you'll "sell" the component to new users as well as prove that it works.
Re: Status of New Release
OK I created the branches and fixed the poms in preparation for release. I will try to get a release candidate ready shortly. Sean On 3/30/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > We use a snapshot as well, all fine for us. > > regards, > > Martin > > On 3/29/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > Hi! > > > So does anyone have any objections to my new branch creation? > > I am fine with it. We use a current snapshot in our production > > environment and it works. > > > > --- > > Mario > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
Re: Moving a file with svn under Windows.
I have tortoise svn but I use the command line for moving. svn move https://svn.apache.org/repos/asf/myfaces/trunk/foo/somefile.txt https://svn.apache.org/repos/asf/myfaces/trunk/bar/somefile.txt -m "log message here" If you get into trouble just stop where you are and post to the list. Myself or someone else familiar with SVN can bail you out. Sean On 3/29/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > I'm not sure why, but the history has always been preserved for me even > though it looks as though you are literally deleting and adding a different > file. This is how it is on projects here at my day job and w/ MyFaces repo ( > w/ Eclipse ). > > Dennis Byrne > > >-Original Message- > >From: Mike Kienenberger [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, March 29, 2006 08:10 PM > >To: 'MyFaces Development' > >Subject: Re: Moving a file with svn under Windows. > > > >On 3/29/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > >> If you drag it from one folder to another, right click on the folder you > >> dragged it to, and go to "team" -> "commit", it preserves history. > >> > >> I know, not very intuitive but it does work ;) > > > >I'm assuming you mean from Eclipse. > > > >That's what I did (dragged it from myfaces-impl to tomahawk-sandbox), > >but it still looks like it's going to do an add rather than a move. > > > >I wonder if the problem is because it changed projects. > > > >Or maybe it'll do the right thing even though it looks like an add. > >I suppose it's a trivial enough class (just a trivial subclass of > >FacesException) that it doesn't matter if history gets lost. > > > > >
[jira] Created: (TOMAHAWK-224) Making Ajax components work properly in dataTables
Making Ajax components work properly in dataTables -- Key: TOMAHAWK-224 URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 Project: MyFaces Tomahawk Type: Improvement Versions: 1.1.2-SNAPSHOT Reporter: Gerald Müllan Priority: Minor Fix For: 1.1.2-SNAPSHOT This patch solves the problem of seeking ajax components if they are located inside dataTables. Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TOMAHAWK-224) Making Ajax components work properly in dataTables
[ http://issues.apache.org/jira/browse/TOMAHAWK-224?page=all ] Gerald Müllan updated TOMAHAWK-224: --- > Making Ajax components work properly in dataTables > -- > > Key: TOMAHAWK-224 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 > Project: MyFaces Tomahawk > Type: Improvement > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > > This patch solves the problem of seeking ajax components if they are located > inside dataTables. > Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (TOMAHAWK-224) Making Ajax components work properly in dataTables
[ http://issues.apache.org/jira/browse/TOMAHAWK-224?page=all ] Martin Marinschek closed TOMAHAWK-224: -- Resolution: Fixed Assign To: Martin Marinschek Thanks Gerald for providing this patch. > Making Ajax components work properly in dataTables > -- > > Key: TOMAHAWK-224 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 > Project: MyFaces Tomahawk > Type: Improvement > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Assignee: Martin Marinschek > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: ajaxDecodePhaseListener.patch > > This patch solves the problem of seeking ajax components if they are located > inside dataTables. > Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Moving a file with svn under Windows.
Sean, What are you using for the command-line version of svn? Also, this was the commit message -- does it look right for a move? There was also a corresponding "remove" message. === Added: myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/ajax/api/ComponentNotFoundException.java - copied, changed from r389900, myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/ComponentNotFoundException.java === On 3/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > I have tortoise svn but I use the command line for moving. > > svn move https://svn.apache.org/repos/asf/myfaces/trunk/foo/somefile.txt > https://svn.apache.org/repos/asf/myfaces/trunk/bar/somefile.txt -m > "log message here" > > If you get into trouble just stop where you are and post to the list. > Myself or someone else familiar with SVN can bail you out. > > Sean > > On 3/29/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > > I'm not sure why, but the history has always been preserved for me even > > though it looks as though you are literally deleting and adding a different > > file. This is how it is on projects here at my day job and w/ MyFaces repo > > ( w/ Eclipse ). > > > > Dennis Byrne > > > > >-Original Message- > > >From: Mike Kienenberger [mailto:[EMAIL PROTECTED] > > >Sent: Wednesday, March 29, 2006 08:10 PM > > >To: 'MyFaces Development' > > >Subject: Re: Moving a file with svn under Windows. > > > > > >On 3/29/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > > >> If you drag it from one folder to another, right click on the folder you > > >> dragged it to, and go to "team" -> "commit", it preserves history. > > >> > > >> I know, not very intuitive but it does work ;) > > > > > >I'm assuming you mean from Eclipse. > > > > > >That's what I did (dragged it from myfaces-impl to tomahawk-sandbox), > > >but it still looks like it's going to do an add rather than a move. > > > > > >I wonder if the problem is because it changed projects. > > > > > >Or maybe it'll do the right thing even though it looks like an add. > > >I suppose it's a trivial enough class (just a trivial subclass of > > >FacesException) that it doesn't matter if history gets lost. > > > > > > > > > >
[jira] Created: (TOMAHAWK-225) New component TableSuggestAjax
New component TableSuggestAjax -- Key: TOMAHAWK-225 URL: http://issues.apache.org/jira/browse/TOMAHAWK-225 Project: MyFaces Tomahawk Type: New Feature Versions: 1.1.2-SNAPSHOT Reporter: Gerald Müllan Priority: Minor Fix For: 1.1.2-SNAPSHOT This patch takes the tablesuggest feature out of InputSuggestAjax component and creates a new comp TableSuggestAjax. It was a need because there were too few similarities between the two suggest possibilities, also as a matter of clarity for the page author. In order to achieve this, there is also a new base component SuggestAjax. All suggest ajax comps should extend it. Apart from that, there are some new features and improvements/fixes: - paginator now works as it should :) - if scrolling is enabled, it is now possible to move down the list with the arrow keys. (means the scrollbar goes with the keys automatically) - js code bloat in the renderer is reduced to a minimum - ie bleeds through bug completely solved - the component seems to be pretty stable now :) changes to InputSuggestAjax: - model update bug fixed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Committing new contributed components [was: Re: [jira] Closed: (TOMAHAWK-165) ifMessage tag that renders children only if there is a message for the specified component(s)]
>Btw. regarding the sandbox, I see it as a huge problem that some vendors >have started to integrate the sandbox as component set into their tools. Whoa, really? Which ones? That's going to be expensive for someone. Dennis Byrne
[jira] Updated: (TOMAHAWK-225) New component TableSuggestAjax
[ http://issues.apache.org/jira/browse/TOMAHAWK-225?page=all ] Gerald Müllan updated TOMAHAWK-225: --- > New component TableSuggestAjax > -- > > Key: TOMAHAWK-225 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-225 > Project: MyFaces Tomahawk > Type: New Feature > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: tableSuggest.patch > > This patch takes the tablesuggest feature out of InputSuggestAjax component > and creates a new comp TableSuggestAjax. > It was a need because there were too few similarities between the two suggest > possibilities, also as a matter of clarity for the page author. > In order to achieve this, there is also a new base component SuggestAjax. All > suggest ajax comps should extend it. > Apart from that, there are some new features and improvements/fixes: > - paginator now works as it should :) > - if scrolling is enabled, it is now possible to move down the list with the > arrow keys. (means the scrollbar goes with the keys automatically) > - js code bloat in the renderer is reduced to a minimum > - ie bleeds through bug completely solved > - the component seems to be pretty stable now :) > changes to InputSuggestAjax: > - model update bug fixed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (TOMAHAWK-225) New component TableSuggestAjax
[ http://issues.apache.org/jira/browse/TOMAHAWK-225?page=all ] Martin Marinschek closed TOMAHAWK-225: -- Resolution: Fixed Assign To: Martin Marinschek Thanks again Gerald for providing this patch. > New component TableSuggestAjax > -- > > Key: TOMAHAWK-225 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-225 > Project: MyFaces Tomahawk > Type: New Feature > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Assignee: Martin Marinschek > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: tableSuggest.patch > > This patch takes the tablesuggest feature out of InputSuggestAjax component > and creates a new comp TableSuggestAjax. > It was a need because there were too few similarities between the two suggest > possibilities, also as a matter of clarity for the page author. > In order to achieve this, there is also a new base component SuggestAjax. All > suggest ajax comps should extend it. > Apart from that, there are some new features and improvements/fixes: > - paginator now works as it should :) > - if scrolling is enabled, it is now possible to move down the list with the > arrow keys. (means the scrollbar goes with the keys automatically) > - js code bloat in the renderer is reduced to a minimum > - ie bleeds through bug completely solved > - the component seems to be pretty stable now :) > changes to InputSuggestAjax: > - model update bug fixed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
[ http://issues.apache.org/jira/browse/TOMAHAWK-224?page=comments#action_12372689 ] Mario Ivankovits commented on TOMAHAWK-224: --- This type of patch is very strange - and dangerous. It replaces the whole file instead of patching only the code in question. Looks like some sort of different white-space (tab, eol, ...) setting, no? > Making Ajax components work properly in dataTables > -- > > Key: TOMAHAWK-224 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 > Project: MyFaces Tomahawk > Type: Improvement > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Assignee: Martin Marinschek > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: ajaxDecodePhaseListener.patch > > This patch solves the problem of seeking ajax components if they are located > inside dataTables. > Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
Any way you guys could jump on the invokeOnComponent w/ Callbacks early from JSF 1.2 to get this system in place for all components now? >[ >http://issues.apache.org/jira/browse/TOMAHAWK-224?page=comments#action_12372689 > ] > >Mario Ivankovits commented on TOMAHAWK-224: >--- > >This type of patch is very strange - and dangerous. It replaces the whole file >instead of patching only the code in question. >Looks like some sort of different white-space (tab, eol, ...) setting, no? > >> Making Ajax components work properly in dataTables >> -- >> >> Key: TOMAHAWK-224 >> URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 >> Project: MyFaces Tomahawk >> Type: Improvement >> Versions: 1.1.2-SNAPSHOT >> Reporter: Gerald Müllan >> Assignee: Martin Marinschek >> Priority: Minor >> Fix For: 1.1.2-SNAPSHOT >> Attachments: ajaxDecodePhaseListener.patch >> >> This patch solves the problem of seeking ajax components if they are located >inside dataTables. >> Patch affects AjaxDecodePhaseListener. > >-- >This message is automatically generated by JIRA. >- >If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa >- >For more information on JIRA, see: > http://www.atlassian.com/software/jira >
Re: [jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Any way you guys could jump on the invokeOnComponent w/ Callbacks early from > JSF 1.2 to get this system in place for all components now? Hey Jacob. I think it's already in MyFaces. Have you tried it?
Editing xdocs in XMLMind
If anyone's interested, Henning (with some help from me) has gotten XMLMind configured so that it supports maven xdocs. I'm not entirely certain how to use it to create new document sections, but editing an existing document or starting from a myfaces xdoc template should make writing xdoc stuff easier! http://wiki.apache.org/jakarta-velocity/EditXdocs
Re: [jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
I haven't seen this in myfaces svn? http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/component/UIComponent.html#invokeOnComponent(javax.faces.context.FacesContext,%20java.lang.String,%20javax.faces.component.ContextCallback) >On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Any way you guys could jump on the invokeOnComponent w/ Callbacks early from >JSF 1.2 to get this system in place for all components now? > >Hey Jacob. > >I think it's already in MyFaces. Have you tried it?
Re: [jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
I guess I was confused. What Martin implemented was Tomahawk UIComponentPerspective.executeOn(). I guess the question is whether we can implement it directly on UIComponent in such a way as that we still pass the TCK. On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I haven't seen this in myfaces svn? > > http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/component/UIComponent.html#invokeOnComponent(javax.faces.context.FacesContext,%20java.lang.String,%20javax.faces.component.ContextCallback) > > > >On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> Any way you guys could jump on the invokeOnComponent w/ Callbacks early > >> from > >JSF 1.2 to get this system in place for all components now? > > > >Hey Jacob. > > > >I think it's already in MyFaces. Have you tried it? >
[jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
[ http://issues.apache.org/jira/browse/TOMAHAWK-224?page=comments#action_12372705 ] Gerald Müllan commented on TOMAHAWK-224: Hm..sorry, seems like i made some mistake when creating the patch. Martin hasn`t commited it till now, so i will have a look on it. > Making Ajax components work properly in dataTables > -- > > Key: TOMAHAWK-224 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 > Project: MyFaces Tomahawk > Type: Improvement > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Assignee: Martin Marinschek > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: ajaxDecodePhaseListener.patch > > This patch solves the problem of seeking ajax components if they are located > inside dataTables. > Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TOBAGO-50) Maven plugin repackaging
[ http://issues.apache.org/jira/browse/TOBAGO-50?page=all ] Bernd Bohmann resolved TOBAGO-50: - Resolution: Fixed change package name from org.apache.maven to org.apache.myfaces.maven > Maven plugin repackaging > > > Key: TOBAGO-50 > URL: http://issues.apache.org/jira/browse/TOBAGO-50 > Project: MyFaces Tobago > Type: Task > Reporter: Udo Schnurpfeil > Assignee: Bernd Bohmann > Fix For: 1.0.7 > > maven-apt-plugin currently contains "org.apache.maven" in the package name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
Jacob, have a look at UIComponentPerspective, implemented by Martin. This should be what you are looking for. cheers, Gerald On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I haven't seen this in myfaces svn? > > http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/component/UIComponent.html#invokeOnComponent(javax.faces.context.FacesContext,%20java.lang.String,%20javax.faces.component.ContextCallback) > > > >On 3/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> Any way you guys could jump on the invokeOnComponent w/ Callbacks early > >> from > >JSF 1.2 to get this system in place for all components now? > > > >Hey Jacob. > > > >I think it's already in MyFaces. Have you tried it? > -- Gerald Müllan Schelleingasse 2/11 1040 Vienna, Austria 0043 699 11772506 [EMAIL PROTECTED]
[jira] Commented: (TOMAHAWK-224) Making Ajax components work properly in dataTables
[ http://issues.apache.org/jira/browse/TOMAHAWK-224?page=comments#action_12372710 ] Dennis Byrne commented on TOMAHAWK-224: --- Gerald, This was happening to my patches using Eclipse 3.1 and Subclipse. I upgraded subclipse and it stopped. I forget the subclipse version number, hope this helps. > Making Ajax components work properly in dataTables > -- > > Key: TOMAHAWK-224 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-224 > Project: MyFaces Tomahawk > Type: Improvement > Versions: 1.1.2-SNAPSHOT > Reporter: Gerald Müllan > Assignee: Martin Marinschek > Priority: Minor > Fix For: 1.1.2-SNAPSHOT > Attachments: ajaxDecodePhaseListener.patch > > This patch solves the problem of seeking ajax components if they are located > inside dataTables. > Patch affects AjaxDecodePhaseListener. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Moving a file with svn under Windows.
> What are you using for the command-line version of svn? I'm using 'c:\Program Files\Subversion\bin' in my path. I think I had to install this separately form the subversion website. > Also, this was the commit message -- does it look right for a move? > There was also a corresponding "remove" message. > > === > Added: > > myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/ajax/api/ComponentNotFoundException.java > - copied, changed from r389900, > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/ComponentNotFoundException.java > === It looks like you moved this to the tomahawk proper. Is that what you wanted? If so then it looks right. The best way to check is to use your browser to checkout svn repo and see if things are where you want them. Just go to http://svn.apache.org/repos/asf/myfaces. I do this all the time when I'm moving lots of stuff around. Just remember, svn copy is to make a duplicate copy (like when you're branching or tagging.) svn move will move everything (history included.) Sean
Re: Moving a file with svn under Windows.
On 3/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > It looks like you moved this to the tomahawk proper. Is that what you > wanted? If so then it looks right. The best way to check is to use > your browser to checkout svn repo and see if things are where you want > them. Just go to http://svn.apache.org/repos/asf/myfaces. I do this > all the time when I'm moving lots of stuff around. Good point. I could have just went here and verified as well. Thanks for reminding me. http://svn.apache.org/viewcvs.cgi/myfaces/tomahawk/trunk/sandbox/core/src/main/java/org/apache/myfaces/custom/ajax/api/ComponentNotFoundException.java?rev=389957&view=log > Just remember, svn copy is to make a duplicate copy (like when you're > branching or tagging.) svn move will move everything (history > included.) Ok. So this was probably ok. It did a copy, then a delete. Same end result as a move even if it wasn't quite as clean. All the history appears to be preserved.
Re: Moving a file with svn under Windows.
Yes copy preserves the history as well so you are ok. Sean
Re: Editing xdocs in XMLMind
I've now "MyFaces-ized" the addon. I tried (cut-and-paste hackery) to make the css style of the page look like our web page -- not too terrible considering that I'm css-ignorant. I've also copied our component-template into the addon templates. So there's now a very easy process (once you install XMLMind and the addon) to edit xdocs! Get it here: http://wiki.apache.org/myfaces/EditXdocs [And yes, I misspelled Myfaces as Myface in the template name, but that's a fix for another day] On 3/31/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > If anyone's interested, Henning (with some help from me) has gotten > XMLMind configured so that it supports maven xdocs. I'm not entirely > certain how to use it to create new document sections, but editing an > existing document or starting from a myfaces xdoc template should make > writing xdoc stuff easier! > > http://wiki.apache.org/jakarta-velocity/EditXdocs >
[jira] Closed: (TOMAHAWK-223) Tree2 not working in Portlet Environment
[ http://issues.apache.org/jira/browse/TOMAHAWK-223?page=all ] Mike Kienenberger closed TOMAHAWK-223: -- Resolution: Invalid You're missing the JSP 2.0 classes. > Tree2 not working in Portlet Environment > > > Key: TOMAHAWK-223 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-223 > Project: MyFaces Tomahawk > Type: Bug > Components: Tree2 > Versions: 1.1.2-SNAPSHOT > Environment: IBM WebSphere Portal 5.1 > Reporter: pamarti > Priority: Blocker > > Works fine tomcat. Throwing > Nested Exception is java.lang.NoClassDefFoundError: > javax/servlet/jsp/el/ELException > at > org.apache.myfaces.renderkit.html.util.AddResourceFactory.getInstance(AddResourceFactory.java:187) > at > org.apache.myfaces.renderkit.html.util.AddResourceFactory.getInstance(AddResourceFactory.java:245) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.getImageUrl(HtmlTreeRenderer.java:571) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.getLayoutImage(HtmlTreeRenderer.java:553) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.renderTreeColumnChild(HtmlTreeRenderer.java:423) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.renderChildren(HtmlTreeRenderer.java:339) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.renderChildren(HtmlTreeRenderer.java:248) > at > org.apache.myfaces.custom.tree.renderkit.html.HtmlTreeRenderer.encodeEnd(HtmlTreeRenderer.java:106) > at > javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:726) > at org.apache.myfaces.custom.tree.HtmlTree.encodeEnd(HtmlTree.java:712) > at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:604) > at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:527) > at org.apache.jsp._TreeMenu._jspService(_TreeMenu.java:201) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOMAHAWK-226) After submit, backed bean date is one day before calendar selected day.
After submit, backed bean date is one day before calendar selected day. --- Key: TOMAHAWK-226 URL: http://issues.apache.org/jira/browse/TOMAHAWK-226 Project: MyFaces Tomahawk Type: Bug Components: Calendar Versions: 1.1.2-SNAPSHOT Environment: Linux FC5, Reporter: Bogdan Migail Sava -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Promote Schedule Component to tomahawk
+1 On Thu, 2006-03-30 at 23:06 +0200, Martin Marinschek wrote: I believe code quality, documentation, examples and support for the schedule component is good enough for it to be moved over to tomahawk. my +1 for this. regards, Martin
