Re: Possible use of maven-faces-plugin for myfaces 1.2

2006-10-30 Thread Matthias Wessendorf
technical spoken yes, somehow. but ... this all is snapshot/incubator. hard to get a release of myface 1.1.6 (or so) out with that stuff. -M On 10/30/06, Martin Marinschek [EMAIL PROTECTED] wrote: Hey Bruno, great stuff! Can we add this to the MyFaces-build somehow? I wonder how we will

Re: Possible use of maven-faces-plugin for myfaces 1.2

2006-10-30 Thread Bruno Aranda
Well, I was aiming at myfaces 1.2, but when all this works, I will add the generators for myfaces 1.1 too. How to include the dependency on the plugin in the myfaces 1.2 branch? Maybe we can deploy the plugin somewhere, or we will have to build the plugin locally by hand when working on 1.2 for a

Re: Possible use of maven-faces-plugin for myfaces 1.2

2006-10-30 Thread Matthias Wessendorf
we can publish the plugin to the m2-incubator-repo the myfaces12 pom points to that that's fine. Also I don't expect myfaces12 ready (tested against TCK, bla bla ) this year, so we can try to release a trinidad_pluings_jsf_12 thing... -M On 10/30/06, Bruno Aranda [EMAIL PROTECTED] wrote:

Re: generics on property-class/ xml element ?

2006-10-30 Thread Matthias Wessendorf
Hello Adam, regarding the setString I think it is not working on default, becasue the JspTaglibMojo... I would require to add something like resolvableTypes.put(java.lang.String[], StringArray); for a SetString into that. (and modify the *set mechanism* inside the mojo for that *propType*

Re: panelBox and simple skin

2006-10-30 Thread Adam Winer
I agree... though this is confusing... I can't think of anything better, though. Do we have a Wiki page yet for skinning? This'd be a good thing to throw up there. -- Adam On 10/30/06, Simon Lessard [EMAIL PROTECTED] wrote: Hello all, There was a post this morning about a skin selector

Re: panelBox and simple skin

2006-10-30 Thread Simon Lessard
Yes we got one. I'll add the issue a bit later tonight. On 10/30/06, Adam Winer [EMAIL PROTECTED] wrote: I agree... though this is confusing... I can't think of anything better, though. Do we have a Wiki page yet for skinning? This'd be a good thing to throw up there. -- Adam On

Re: api cleanup for UIXCollection

2006-10-30 Thread Matthias Wessendorf
just saw that. thx! On 10/29/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote: uploaded a patch http://issues.apache.org/jira/browse/ADFFACES-270 On 10/25/06, Simon Lessard [EMAIL PROTECTED] wrote: +1 as well, when I first saw that method I thought about money. On 10/25/06, Adam Winer [EMAIL

Re: TreeTable focusRowKey

2006-10-30 Thread venkata guddanti
On 10/30/06, Kamran Kashanian [EMAIL PROTECTED] wrote: In UIXTreeTable the focusRowKey attribute specifies the rowKey of the currently focused row. In the renderer, the row with the focusRowKey is rendered as the root node of the TreeTable and a focus path is rendered above the TreeTable. When

Re: Re: TreeTable focusRowKey

2006-10-30 Thread Adam Winer
Question 2 would be what we should do if the focusRowKey is null? If we simply removed the defaulting code altogether, what would go wrong, and where? -- Adam On 10/30/06, venkata guddanti [EMAIL PROTECTED] wrote: On 10/30/06, Kamran Kashanian [EMAIL PROTECTED] wrote: In UIXTreeTable the

Bug with read-only, required fields.

2006-10-30 Thread Simon Lessard
Hello all, I just found out that if you use an inputText with readOnly and required set to true, validation will always fail, even if there's data in the underlying bean. Anyone heard about this before? Regards, ~ Simon

Re: Bug with read-only, required fields.

2006-10-30 Thread Adam Winer
Yeah, I'm with Gab here - you should never hit validation at all. -- Adam On 10/30/06, Gabrielle Crawford [EMAIL PROTECTED] wrote: Really? I thought the renderer checks wasSubmitted which checks for readOnly and disabled. SubmittedValue should then be set to null, and in UIXEditableValue's

Re: Bug with read-only, required fields.

2006-10-30 Thread Simon Lessard
Yep I could reproduce with with that simple page any bean with a default value will work : ?xml version='1.0' encoding='windows-1252'? jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0 xmlns:f=http://java.sun.com/jsf/core; xmlns:tr=http://myfaces.apache.org/trinidad;

Re: Re: TreeTable focusRowKey

2006-10-30 Thread Arjuna Wijeyekoon
+1 to moving the defaulting code to the renderer. However, the renderer must call setFocusRowKey on the component with the default value, so that decode/validate/update will work correctly. if the focusRowKey is null upon postback, it could cause errors during decode. --arjuna On 10/30/06, Adam

Re: Re: Re: TreeTable focusRowKey

2006-10-30 Thread Adam Winer
On 10/30/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote: +1 to moving the defaulting code to the renderer. However, the renderer must call setFocusRowKey on the component with the default value, so that decode/validate/update will work correctly. if the focusRowKey is null upon postback, it

Re: Bug with read-only, required fields.

2006-10-30 Thread Matthias Wessendorf
I committed the changed template by accident, when I was looking into the Trinidad side of MYFACES-1467. I went into the source code repo during my changes on the client side tasks... I do a revert on that, but still we need to look at that (form the MyFaces side) However, Thomas run the TCK

Re: Bug with read-only, required fields.

2006-10-30 Thread Matthias Wessendorf
Hey David, can you follow that thread, regarding the man-in-the-middle-tool issue ? http://mail-archives.apache.org/mod_mbox/incubator-adffaces-dev/200610.mbox/ajax/[EMAIL PROTECTED] Thanks, Matt On 10/30/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: I committed the changed template by