[
https://issues.apache.org/jira/browse/TRINIDAD-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1659:
-
Resolution: Fixed
Fix Version/s: 2.0.0-plugins
Assignee:
http://svn.apache.org/viewvc?view=revisionrevision=891581
On Thu, Dec 17, 2009 at 8:16 AM, Matthias Wessendorf mat...@apache.org wrote:
good catch :-) Will submit your patch later 2day.
-M
On Thu, Dec 17, 2009 at 1:07 AM, Pavitra Subramaniam
pavitra.subraman...@oracle.com wrote:
Hi,
I
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791870#action_12791870
]
Ashish Jain commented on MYFACES-1820:
--
How is that this problem can be recreated??
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791871#action_12791871
]
Ashish Jain commented on MYFACES-1820:
--
Any idea on a sample application will be
get rid of oracle.application.environment system property
---
Key: TRINIDAD-1661
URL: https://issues.apache.org/jira/browse/TRINIDAD-1661
Project: MyFaces Trinidad
Issue Type: Bug
Create centralized util that reads configuration parameters (from web.xml)
--
Key: TRINIDAD-1662
URL: https://issues.apache.org/jira/browse/TRINIDAD-1662
Project: MyFaces
[
https://issues.apache.org/jira/browse/TRINIDAD-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791943#action_12791943
]
Matthias Weßendorf commented on TRINIDAD-1662:
--
see also
Hi,
this parameter ([1]) is currently marked as INTERNAL and the source
says temporary.
Question is now, if we can't get rid of it in the near future, should
we make it API ?
Or are there some plans to remove this parameter ?
Thanks,
Matthias
[1]
I will ignore the temporary
org.apache.myfaces.trinidadinternal.ENABLE_PPR_OPTIMIZATION
parameter, until we know more.
See here:
http://markmail.org/message/dqgeqwkzdwjkrhgm
-Matthias
On Tue, Dec 8, 2009 at 5:56 PM, Matthias Wessendorf mat...@apache.org wrote:
[
https://issues.apache.org/jira/browse/TRINIDAD-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791962#action_12791962
]
Matthias Weßendorf commented on TRINIDAD-1662:
--
IMO this should be done
[
https://issues.apache.org/jira/browse/TRINIDAD-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791966#action_12791966
]
Matthias Weßendorf commented on TRINIDAD-1662:
--
CHECK_TIMESTAMP_PARAM as
The CHECK_STATE_SERIALIZATION parameter is evaluated (via System
Property) in the static constructor of the StateUtils class;
Not sure if we really should move this behavior over to the ProjectStage API.
Any thoughts ?
The class is here:
I had another question regarding the CHECK_STATE_SERIALIZATION
parameter (check dev@)
patch for the other items is attached to:
https://issues.apache.org/jira/browse/TRINIDAD-1652
Also, check:
https://issues.apache.org/jira/browse/TRINIDAD-1661
https://issues.apache.org/jira/browse/TRINIDAD-1662
create documentation for new ProjectStage behavior
--
Key: TRINIDAD-1663
URL: https://issues.apache.org/jira/browse/TRINIDAD-1663
Project: MyFaces Trinidad
Issue Type: Sub-task
Affects
FYI
cool news!
-- Forwarded message --
From: Gurkan Erdogdu gurkanerdo...@yahoo.com
Date: Thu, Dec 17, 2009 at 5:29 PM
Subject: Apache OpenWebBeans Has Graduated
To: gene...@incubator.apache.org
Hi;
We have just received confirmation that the Board has established Apache
Hello Andrew,
I like your proposal.
+1 on doing so!
-Matthias
On Wed, Dec 16, 2009 at 11:26 PM, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
Currently the trinidad examples (trinidad-demo and trinidad-blank)
use JSP and JSPX. Just turning facelets on for JSPX files isn't going
to
+1 from me too.
Max
Matthias Wessendorf wrote:
Hello Andrew,
I like your proposal.
+1 on doing so!
-Matthias
On Wed, Dec 16, 2009 at 11:26 PM, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
Currently the trinidad examples (trinidad-demo and trinidad-blank)
use JSP and
Matthias Wessendorf said the following On 12/17/2009 6:45 AM PT:
Hi,
this parameter ([1]) is currently marked as INTERNAL and the source
says temporary.
Question is now, if we can't get rid of it in the near future, should
we make it API ?
Or are there some plans to remove this parameter ?
On Thu, Dec 17, 2009 at 6:55 PM, Blake Sullivan
blake.sulli...@oracle.com wrote:
Matthias Wessendorf said the following On 12/17/2009 6:45 AM PT:
Hi,
this parameter ([1]) is currently marked as INTERNAL and the source
says temporary.
Question is now, if we can't get rid of it in the near
This is partly a performance issue. I assume that the security checks
would keep us from calling System.setProperty(). Actually, the fastest
solution might be to initialize a static variable off of the system
property and the ProjectStage, assuming that we don't have to run in a
system where
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792071#action_12792071
]
Simon Kitching commented on MYFACES-1820:
-
For FacesContext subclasses, this
Thanks for committing the changes!
And thanks too for the really sweet thank you card from you and Anja!
Hope you got something nice for yourselves...
Happy Holidays!
- Pavitra
Matthias Weßendorf (JIRA) wrote: On 12/17/2009 12:34 AM PT:
[
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792073#action_12792073
]
Simon Kitching commented on MYFACES-1820:
-
This problem was noticed during the
Hey Guys,
I'm working on a preliminary version of the portlet-bridge for
JSF2.0.. Looking at the current R.I. implementations, it appears as if
I'm going to have to come up with my own implementations for the
ViewDeclairationLanguage's for the bridge. Although the R.I. is laid
out so that
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792126#action_12792126
]
Ashish Jain commented on MYFACES-1820:
--
HI Simon, Thanks for your generous reply. I
Hi
Thanks to all people who vote.
We have 3 +1
Werner Punz
Gerhard Petracek
Leonardo Uribe
So we can continue with the necessary steps to release myfaces orchestra
1.4.
regards,
Leonardo Uribe
[
https://issues.apache.org/jira/browse/MYFACES-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792138#action_12792138
]
Leonardo Uribe commented on MYFACES-1820:
-
Just as a side note, the latest code
Cool, you're working on this. Just a week ago I was stuck with
the current portal - JSF2.0 problem. Are you doing portal 1.0 -
JSF 2.0 or portal 2.0 - JSF 2.0?
I not yet clear about why the bridge needs to care about the
VDL. I thought it would suffice to brige the portal lifecyle
phases and
Hi,
I'm working off the Trinidad trunk. When I tested my project against
the trinidad-2.0.x branch, I noticed that certain new APIs are missing.
Is there a plan to merge the new changes from trunk into the 2.0 branch?
Fyi, I'm running into this issue with the following APIs on the
It's going to be JSF 2.0/Portal 2.0. I'm not sure if the JCP is going
to look at a Portal 1.0 Spec for JSF 2.0. The leanings on the current
EG's were that they were not. Portal 1.0 has some pretty major issues
in dealing with AJAX and whatnot so such a specification would be
problematic.
[
https://issues.apache.org/jira/browse/MYFACES-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792192#action_12792192
]
Jakob Korherr commented on MYFACES-2454:
I came up with the following solution
Hi,
I am currently working on the Exception handling mechanism of MyFaces 2.0
and I was thinking how we should provide backwards compatibility to the
situation in 1.2.
I came up with the following solution for the backwards compatibility:
- org.apache.myfaces.ERROR_HANDLING will be dismissed by
[
https://issues.apache.org/jira/browse/MYFACES-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-2460.
-
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Assignee: Leonardo Uribe
Find a way to do not use ELExpressions on jsf.js for getProjectStage
Key: MYFACES-2464
URL: https://issues.apache.org/jira/browse/MYFACES-2464
Project: MyFaces Core
Issue
[
https://issues.apache.org/jira/browse/MYFACES-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792229#action_12792229
]
Jakob Korherr commented on MYFACES-2464:
what if we store two implementations of
Hi
I think you're right. Makes sense deprecate/remove
org.apache.myfaces.ERROR_HANDLING. The standard solution to error handling
takes precedence over myfaces hack.
regards
Leonardo Uribe
2009/12/17 Jakob Korherr jakob.korh...@gmail.com
Hi,
I am currently working on the Exception handling
[
https://issues.apache.org/jira/browse/MYFACES-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792235#action_12792235
]
Leonardo Uribe commented on MYFACES-2464:
-
Really in that case we need four, one
[
https://issues.apache.org/jira/browse/MYFACES-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792239#action_12792239
]
Leonardo Uribe commented on MYFACES-2464:
-
Looking on google I found a link:
[
https://issues.apache.org/jira/browse/MYFACES-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792243#action_12792243
]
Jakob Korherr commented on MYFACES-2464:
Actually, I was also thinking of that.
On Thu, Dec 17, 2009 at 11:42 PM, Scott O'Bryan darkar...@gmail.com wrote:
It's going to be JSF 2.0/Portal 2.0. I'm not sure if the JCP is going to
look at a Portal 1.0 Spec for JSF 2.0. The leanings on the current EG's
were that they were not. Portal 1.0 has some pretty major issues in
40 matches
Mail list logo
