The exportActionListener now depends only on MyFaces APIs, and now it is
ready to move to MyFaces-common-components.
On Sat, Oct 25, 2008 at 4:11 AM, Hazem Saleh [EMAIL PROTECTED] wrote:
The vote has passed with the following results:
+1
Glauco P. Gomes
Grant Smith
Matthias Wessendorf
The vote has passed with the following results:
+1
Glauco P. Gomes
Grant Smith
Matthias Wessendorf
Gerhard Petracek
Mike
Leonardo
Volker
Andrew
Cagatay
So, we will have a (non-rendering) component module in myfaces-commons.
Thanks all!
On Wed, Oct 22, 2008 at 3:20 PM, Cagatay Civici [EMAIL
+1 to non rendering stuff only
On Wed, Oct 22, 2008 at 2:14 AM, Hazem Saleh [EMAIL PROTECTED] wrote:
OK. Let's then start empowering it ;).
On Wed, Oct 22, 2008 at 2:42 AM, Grant Smith [EMAIL PROTECTED] wrote:
So is the plan then to take ALL non-rendering components and listeners
from ALL
[ ] +1 - I agree.
[ ] +0 - I do not know.
[ ] -1 - I do not want to see components modules in commons, as we already
have component libraries like Tomahawk, Trinidad, Tobago.
--
Hazem Ahmed Saleh Ahmed
Author of (The Definitive Guide to Apache MyFaces and Facelets):
-1.
On Tue, Oct 21, 2008 at 7:16 PM, Hazem Saleh [EMAIL PROTECTED] wrote:
[ ] +1 - I agree.
[ ] +0 - I do not know.
[ ] -1 - I do not want to see components modules in commons, as we already
have component libraries like Tomahawk, Trinidad, Tobago.
--
Hazem Ahmed Saleh Ahmed
Author of
+1 only for components that doesn't render anything, like tr:iterator,
t:saveState, tr:fileDownloadActionListener, s:exporterActionListener,
s:valueChangeNotifier, etc.
Glauco P. Gomes
Hazem Saleh escreveu:
-1.
On Tue, Oct 21, 2008 at 7:16 PM, Hazem Saleh
[EMAIL PROTECTED] wrote:
[
-1
On Tue, Oct 21, 2008 at 10:36 AM, Glauco P. Gomes [EMAIL PROTECTED]
wrote:
+1 only for components that doesn't render anything, like tr:iterator,
t:saveState, tr:fileDownloadActionListener, s:exporterActionListener,
s:valueChangeNotifier, etc.
Glauco P. Gomes
Hazem Saleh escreveu:
these aren't components.
These are listeners and should go to commons
tr:fileDownloadActionListener, s:exporterActionListene
On Tue, Oct 21, 2008 at 7:36 PM, Glauco P. Gomes
[EMAIL PROTECTED] wrote:
+1 only for components that doesn't render anything, like tr:iterator,
t:saveState,
concerning the statement of matthias: +1
regards,
gerhard
2008/10/21 Matthias Wessendorf [EMAIL PROTECTED]
these aren't components.
These are listeners and should go to commons
tr:fileDownloadActionListener, s:exporterActionListene
On Tue, Oct 21, 2008 at 7:36 PM, Glauco P. Gomes
+1 only for components that don't render anything, like t:saveState
+1 only for listeners or tags that don't render anything.
On Tue, Oct 21, 2008 at 1:52 PM, Mike Kienenberger [EMAIL PROTECTED]wrote:
+1 only for components that don't render anything, like t:saveState
Hi,
2008/10/21 Matthias Wessendorf [EMAIL PROTECTED]:
these aren't components.
These are listeners and should go to commons
should we have a myfaces-commons-listeners? or what do you mean?
We should not create a submodule for every type of components.
But we should start having a submodule
+1 on Mike's reply
On Tue, Oct 21, 2008 at 12:52 PM, Mike Kienenberger [EMAIL PROTECTED] wrote:
+1 only for components that don't render anything, like t:saveState
So is the plan then to take ALL non-rendering components and listeners from
ALL myfaces subprojects and dump them in here ? If that is the case, then
+1. Having stuff scattered about unnecessarily because we didn't finish the
job would be an unacceptable situation. I would also propose calling the
OK. Let's then start empowering it ;).
On Wed, Oct 22, 2008 at 2:42 AM, Grant Smith [EMAIL PROTECTED] wrote:
So is the plan then to take ALL non-rendering components and listeners from
ALL myfaces subprojects and dump them in here ? If that is the case, then
+1. Having stuff scattered about
15 matches
Mail list logo
