Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-13 Thread Scott O'Bryan
Yeah, this is a complex issue. And trinidad doesn't do it right either. Here is what I was going to do for Trinidad (in my copious amounts of spare time). :) Each Portlet would have a root element. When a form is submitted via ppr, the view state for each javax.faces.ViewState under that

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Leonardo Uribe
On Wed, Jun 11, 2008 at 11:24 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote: I want to know if any developer has a reason to avoid render this id, and if no objections I'll commit this change in 72 hours (doing this s:inputSuggestAjax and s:tableSuggestAjax could work with trinidad

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread [EMAIL PROTECTED]
Leonardo Uribe schrieb: On Wed, Jun 11, 2008 at 11:24 PM, Matthias Wessendorf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I want to know if any developer has a reason to avoid render this id, and if no objections I'll commit this change in 72 hours (doing this

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Leonardo Uribe
On Thu, Jun 12, 2008 at 8:51 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Leonardo Uribe schrieb: On Wed, Jun 11, 2008 at 11:24 PM, Matthias Wessendorf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I want to know if any developer has a reason to avoid render this

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Matthias Wessendorf
On Thu, Jun 12, 2008 at 7:02 AM, Leonardo Uribe [EMAIL PROTECTED] wrote: On Thu, Jun 12, 2008 at 8:51 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Leonardo Uribe schrieb: On Wed, Jun 11, 2008 at 11:24 PM, Matthias Wessendorf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Leonardo Uribe
On Thu, Jun 12, 2008 at 9:27 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote: On Thu, Jun 12, 2008 at 7:02 AM, Leonardo Uribe [EMAIL PROTECTED] wrote: On Thu, Jun 12, 2008 at 8:51 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Leonardo Uribe schrieb: On Wed, Jun 11, 2008

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread [EMAIL PROTECTED]
Matthias Wessendorf schrieb: On Thu, Jun 12, 2008 at 7:02 AM, Leonardo Uribe [EMAIL PROTECTED] wrote: On Thu, Jun 12, 2008 at 8:51 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Leonardo Uribe schrieb: On Wed, Jun 11, 2008 at 11:24 PM, Matthias Wessendorf [EMAIL PROTECTED]

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Mario Ivankovits
Hi! why not getElementsByName[0] ? Well, in general document.getElementById is both faster and more elegant. So in this case, rendering this component with id=clientId seems reasonable. Hmm..but it is possible that there are multiple view state fields in the page, one per form.

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread [EMAIL PROTECTED]
Mario Ivankovits schrieb: Hi! why not getElementsByName[0] ? Well, in general document.getElementById is both faster and more elegant. So in this case, rendering this component with id=clientId seems reasonable. Hmm..but it is possible that there are multiple view state

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Mario Ivankovits
Hi! And also ensure that every ViewState will be replaced and not only the first [0] one. When you do have multiple JSF forms (which is valid) each ViewState needs to be replaced. Yes, but only when they came from the same view! I don't know much about JSF portal bridge stuff. Can this

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Mario Ivankovits
Hi! I ignore what happens when use multiple jsf portlets in the same page, or when the page is using multiple forms on the same page (normal submits should work on both environmets, but ajaxified components?). With I ignore you mean you will not replace the ViewState for each form having a

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-12 Thread Leonardo Uribe
On Fri, Jun 13, 2008 at 12:07 AM, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! I ignore what happens when use multiple jsf portlets in the same page, or when the page is using multiple forms on the same page (normal submits should work on both environmets, but ajaxified components?).

[trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-11 Thread Leonardo Uribe
Hi Checking some tomahawk stuff I have noted that when I'm using trinidad (any version 1.1 and 1.2) at the end of the form the hidden field that stores or references the state: input type=hidden name=javax.faces.ViewState never render its id=javax.faces.ViewState as myfaces and jsf ri does.

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-11 Thread Leonardo Uribe
I made a mistake copy paste the code of writeState. Actually looks like this: public void writeState( FacesContext context, StateManager.SerializedView serializedView) throws IOException { ResponseWriter rw = context.getResponseWriter(); rw.startElement(input, null);

Re: [trinidad] Why input type=hidden name=javax.faces.ViewState ... does not render its id?

2008-06-11 Thread Matthias Wessendorf
I want to know if any developer has a reason to avoid render this id, and if no objections I'll commit this change in 72 hours (doing this s:inputSuggestAjax and s:tableSuggestAjax could work with trinidad and/or facelets and solve TOMAHAWK-1157). so, I guess I am not 100% getting your mail.