+1 for promoting to tomahawk now and perhaps moving stuff to commons
later. Now I need to read the commons proposal ...
sean
On 11/27/06, Manfred Geiler [EMAIL PROTECTED] wrote:
Yes, d'accord!
I agree with Zubin that these are two different pairs of shoes.
+1 for moving s:selectItems out of
Hi!
I'm planning to promote s:selectItems to tomahawk. Component satisfies
all of the requirements needed for promotion.
+1
Ciao,
Mario
+1
we already have been using this component in production for some time
without any issues
Manfred
On 11/26/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Hi,
I'm planning to promote s:selectItems to tomahawk. Component satisfies all
of the requirements needed for promotion.
Regards,
Cagatay
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons project, to enabel the use in
non tomahawk applications e.g. tobago. There is no renderer specific
stuff involed?
Regards,
Volker
2006/11/26, Cagatay Civici [EMAIL PROTECTED]:
Hi,
I'm
+1
and yes, Volker, no rendering specific stuff involved.
regards,
Martin
On 11/27/06, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons project, to enabel the use in
non tomahawk applications e.g.
+1
On 27/11/06, Martin Marinschek [EMAIL PROTECTED] wrote:
+1
and yes, Volker, no rendering specific stuff involved.
regards,
Martin
On 11/27/06, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
i didn't know this component before, looks very usefull.
I prefer to have this in the new commons
that would be great;
from what I got out of that commons thread is that they wanna have
*common utils* in that jar first. no response to the adding
validators/converters proposal so far.
Only Bernd had also something similar (security;fileupload,...)
-M
On 11/27/06, Volker Weber [EMAIL
Even if there is no renderer specific stuff involved, this goody is
quite component like. Particularly the tag definition is the thing
that makes it diffult to integrate into commons. We should not have
another TLD in commons with another recommended prefix (c ?!).
Wouldn't that be really
Why not having a commons-component library?
For converters and validators we neet also another TDL with another prefix.
I prefer to follow Bernds suggestion of having multiple commons artifacts.
Alternativly we can put all tag-components
(components/converters/validators/...?)
together into a
Hello Manfred,
i don't understand you. What is wrong to move all the common renderkit
stuff to a common package. This does't keep you to include this tag in
the tomahawk tld.
Here is my
+1 for moving to tomahawk
and
+1 for moving in a common whatever artifact.
and
+1 for starting a
Ok, now I do not understand anything anymore as well... :-)
Seems, like we got our wires crossed.
What is your exact proposal for the s:selectItems stuff. Moving it to
both tomahawk as well as commons means what?
Having a t:selectItems in tomahawk together with a
This are two related threads,
Cagatay wants to promote the component into tomahawk.
Some (at least me) want to have the component in a renderkid indepenend commons.
I don't like to put it now into tomahawk and next month (or so) from
tomahawk into the new commons.
If we decide to have
Yes, d'accord!
I agree with Zubin that these are two different pairs of shoes.
+1 for moving s:selectItems out of the tomahawk(!) sandbox to tomahawk core
Let's keep an eye on a future
alltogether-compatible-with-everything-components-set but do not not
mix up with the commons jsf utils package
Hi,
I'm planning to promote s:selectItems to tomahawk. Component satisfies all
of the requirements needed for promotion.
Regards,
Cagatay
http://myfaces.apache.org/sandbox/selectItems.html
+1 for that great component
On 11/26/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Hi,
I'm planning to promote s:selectItems to tomahawk. Component satisfies all
of the requirements needed for promotion.
Regards,
Cagatay
http://myfaces.apache.org/sandbox/selectItems.html
--
Matthias
15 matches
Mail list logo
