+0
regards,
gerhard
2008/10/21 Leonardo Uribe [EMAIL PROTECTED]
+1
regards
Leonardo Uribe
On Mon, Oct 20, 2008 at 7:47 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi,
I was running the needed tasks to get the 1.0.2 release of Apache
MyFaces Builder Plugin out.
This artifacts
InputDate should only set the date fields when it is in date mode
-
Key: TOMAHAWK-1361
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1361
Project: MyFaces Tomahawk
Issue
[
https://issues.apache.org/jira/browse/TOMAHAWK-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cagatay Civici resolved TOMAHAWK-1361.
--
Resolution: Fixed
Fix Version/s: 1.1.8-SNAPSHOT
InputDate should only set
Optimize org.apache.myfaces.trinidadinternal.share.url.EncoderUtilsto use less
CPU time
---
Key: TRINIDAD-1275
URL: https://issues.apache.org/jira/browse/TRINIDAD-1275
ViewController does not invoke initView on new instance of same view
Key: ORCHESTRA-30
URL: https://issues.apache.org/jira/browse/ORCHESTRA-30
Project: MyFaces Orchestra
[
https://issues.apache.org/jira/browse/TOMAHAWK-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12641398#action_12641398
]
Jon Harley commented on TOMAHAWK-3:
---
I agree that this component should work with any
No warning/error reported when fetching bean from conversation marked as
invalidated
Key: ORCHESTRA-31
URL: https://issues.apache.org/jira/browse/ORCHESTRA-31
[
https://issues.apache.org/jira/browse/TRINIDAD-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Kao updated TRINIDAD-195:
-
Status: Patch Available (was: Open)
Two requests at the same time throw an exception when
any more ideas?
On Tue, Oct 14, 2008 at 5:39 PM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
2008/10/14 Hazem Saleh [EMAIL PROTECTED]:
I think that If commons should include components, then these components
should be independent + have no UI.
+1 for those myfaces-commons-components
i suggest to start a vote concerning myfaces-commons-components.
regards,
gerhard
2008/10/21 Hazem Saleh [EMAIL PROTECTED]
any more ideas?
On Tue, Oct 14, 2008 at 5:39 PM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
2008/10/14 Hazem Saleh [EMAIL PROTECTED]:
I think that If commons
The only way I could see myfaces-commons-components being useful is if ALL
components are migrated to it that are common to Tomahawk, Tobago, and
Trinidad. Is that the plan ? If it becomes yet another bucket of components,
I am against it.
On Tue, Oct 21, 2008 at 9:46 AM, Gerhard Petracek
[EMAIL
+1
On Tue, Oct 21, 2008 at 8:59 AM, Udo Schnurpfeil [EMAIL PROTECTED] wrote:
here is my
+1
I've deployed the demo 1.0.20:
http://tobago.atanion.net/tobago-example-demo/
Regards
Udo
Bernd Bohmann schrieb:
Hello,
I would like to release Tobago 1.0.20
For a detail list please
+0 sorry no time to learn how to test this.
On Tue, Oct 21, 2008 at 9:25 AM, Hazem Saleh [EMAIL PROTECTED] wrote:
+1.
On Tue, Oct 21, 2008 at 2:47 AM, Leonardo Uribe [EMAIL PROTECTED] wrote:
+1
regards
Leonardo Uribe
On Mon, Oct 20, 2008 at 7:47 PM, Leonardo Uribe [EMAIL PROTECTED]
I totally agree with Grant!
On Tue, Oct 21, 2008 at 6:53 PM, Grant Smith [EMAIL PROTECTED] wrote:
The only way I could see myfaces-commons-components being useful is if ALL
components are migrated to it that are common to Tomahawk, Tobago, and
Trinidad. Is that the plan ? If it becomes yet
Ooops that sounded ungrateful. It's a wonderful plugin, and I appreciate the
hard work gone into it, but I honestly have no time to test :(
On Tue, Oct 21, 2008 at 9:56 AM, Grant Smith [EMAIL PROTECTED] wrote:
+0 sorry no time to learn how to test this.
On Tue, Oct 21, 2008 at 9:25 AM, Hazem
i'm not in favour or against it, because i haven't thought about it so far.
i just mentioned that we need a vote (since there were no arguments against
it).
regards,
gerhard
2008/10/21 Grant Smith [EMAIL PROTECTED]
The only way I could see myfaces-commons-components being useful is if ALL
+1
Hazem Saleh schrieb:
I totally agree with Grant!
On Tue, Oct 21, 2008 at 6:53 PM, Grant Smith [EMAIL PROTECTED] wrote:
The only way I could see myfaces-commons-components being useful is if ALL
components are migrated to it that are common to Tomahawk, Tobago, and
Trinidad. Is that
[ ] +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
Sorry, I forgot the word [VOTE] in the subject.
Scott O'Bryan wrote:
Hi,
I'm trying to release the MyFaces Portlet Bridge Master
1.0.0-alpha-3. This release was created in order to support the
latest JSR-301 Public Review so that it may be tested by developers
during the review process.
+1
Scott O'Bryan wrote:
Sorry, I forgot the word [VOTE] in the subject.
Scott O'Bryan wrote:
Hi,
I'm trying to release the MyFaces Portlet Bridge Master
1.0.0-alpha-3. This release was created in order to support the
latest JSR-301 Public Review so that it may be tested by developers
+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,
+1 on what volker said.
Which is adding *helpers* like actionListener tags, or no-UI stuff
-M
On Tue, Oct 14, 2008 at 5:39 PM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
2008/10/14 Hazem Saleh [EMAIL PROTECTED]:
I think that If commons should include components, then these components
should
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
Hi all -
I was wondering if one of the Trinidad committees could take a look at
trinidad-1262 (https://issues.apache.org/jira/browse/TRINIDAD-1262)? It
needs to be reviewed and committed.
Thanks
Anita
+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
looks good so far.
I just wonder if this:
+ Locale locale = getLocale();
+ if (null == locale)
+ {
+RequestContext reqContext = RequestContext.getCurrentInstance();
+if (reqContext != null)
+{
+ locale = reqContext.getFormattingLocale();
+}
[
https://issues.apache.org/jira/browse/TOMAHAWK-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph ONeil updated TOMAHAWK-616:
--
Status: Patch Available (was: Open)
Datatable AutoSort and Facelets Bug
What do you mean by the demo app stops running? Does it run at all?
If so how far do you get before you run into the problem? The error
message you are seeing is written into the log, right? If so, all this
is telling you is that Myfaces is running in a configuration where it
writes the
On Tue, Oct 21, 2008 at 4:50 PM, michael freedman
[EMAIL PROTECTED] wrote:
What do you mean by the demo app stops running? Does it run at all? If
so how far do you get before you run into the problem? The error message
you are seeing is written into the log, right? If so, all this is
On Tue, Oct 21, 2008 at 5:18 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Tue, Oct 21, 2008 at 4:50 PM, michael freedman
[EMAIL PROTECTED] wrote:
What do you mean by the demo app stops running? Does it run at all?
If so how far do you get before you run into the problem? The error
[
https://issues.apache.org/jira/browse/TRINIDAD-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1274.
---
Resolution: Fixed
Fix Version/s: 1.2.8-plugins
The maven faces plug-in
Hey Leo, this could be related to the state-saving issue with MyFaces
that I posted to the dev list about a month ago. I havn't had time to
fix it (or even write a JIRA ticket) but, essentially, there are times
that MyFaces does not generate a state-saving token when maybe it
should. On the
When you say the state isn't restored when you click a button or link
can you be more specific? there are two views -- the first view asks
you to enter your name. Is the problem on navigating from this page?
I.e. the second view doesn't say hello name. Or is there a problem
when you hit
The main thing to note here is that this message is always written to
the log when running this Myfaces config (for all your browsers) and
hence is non-indicative of the problem. FYI -- we can't determine that
its correct (for all cases) that we didn't find the Token which is why
we write a
+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
On Tue, Oct 21, 2008 at 6:13 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
The problem only happens when server state saving is used. On client side
state saving everything works well.
I'll try add the params to faces-config.xml and see what happens.
Checking myfaces core 1.2.x code, class
Leonardo,
Right. This was the problem discovered last release. The behavior your
seeing is actually expected (it was CHANGED to do what it does because
it USED to throw an exception). What Mike discovered was that, although
there is really no need to tokenize server-side and JS state
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
44 matches
Mail list logo
