Hi,
here is a (complete?) list of all Trinidad configuration parameters:
* System Properties ( = System.getProperty()):
org.apache.myfaces.trinidad.CHECK_STATE_SERIALIZATION
documentation is here:
http://issues.apache.org/jira/browse/TRINIDAD-1245
Make _ErrorPageWriter public to allow re-use of default functionality
-
Key: MYFACES-2441
URL: https://issues.apache.org/jira/browse/MYFACES-2441
Project: MyFaces Core
Hello,
well, of course you could as well just pass the proxy, it would work.
The difference is just that in my version the proxy actually will never
be called, i.e. there's definitely no performance impact. It's just as
I've mentioned a workaround for the not-null-check in the constructor of
[
https://issues.apache.org/jira/browse/TRINIDAD-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784715#action_12784715
]
Matthias Weßendorf commented on TRINIDAD-1650:
--
code will live in
add support for empty field validation and BeanValidation API
---
Key: TRINIDAD-1650
URL: https://issues.apache.org/jira/browse/TRINIDAD-1650
Project: MyFaces Trinidad
Issue Type:
[
https://issues.apache.org/jira/browse/MYFACES-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784731#action_12784731
]
Jakob Korherr commented on MYFACES-2441:
I'm afraid the _ErrorPageWriter cannot
Hi,
I created a quick wiki page for to cover our research:
http://wiki.apache.org/myfaces/Trinidad_goes_ProjectStage
-Matthias
On Wed, Dec 2, 2009 at 10:49 AM, Bruno Aranda brunoara...@gmail.com wrote:
Hi,
I do agree. The list looks fine to me, and yes, we should allow the users to
[
https://issues.apache.org/jira/browse/TRINIDAD-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784760#action_12784760
]
Markus Döring commented on TRINIDAD-1327:
-
I had a look into the issue and could
Hi,
I had a look at the issue
https://issues.apache.org/jira/browse/TRINIDAD-1327
and added a comment, maybe someone deeper into this code could have another
look at it because I think this is a major issue.
Regards
Markus
FYI
http://markmail.org/message/kbnb2imqdohkra7f
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Max Starets píše v Út 01. 12. 2009 v 20:42 -0500:
Gabrielle,
I think the main advantage of using application view cache is that state
saving/view root caching is done once for a particular page
within an application (that only applies to pages displayed in response
to a GET request).
Hi we could resolve that yesterday offline, I am in the middle of an
overhaul of the codebase, so I am reluctant to commit some quick fixes
now, the pom.xml needs to be upgraded to the latest stable
of myfaces (since the snapshots seem to be obviously older in shared
than what the project
Hi,
does trinidad reload both JSP and facelets views if
org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION=true?
For facelets based views there is a new JSF 2.0 param
javax.faces.FACELETS_REFRESH_PERIOD (-1 = never reload, 0=always, 1,2,
3,.. - check interval) but it's relation to project stage
[
https://issues.apache.org/jira/browse/TRINIDAD-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784805#action_12784805
]
Markus Döring commented on TRINIDAD-1327:
-
Found an slightly better workaround:
Hi,
I think the best way would be that the init parameters have stage related
standard values (actually that what Matthias suggested), for example:
If we are in ProjectStage.Production the standard value of
org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION is false, otherwise
it is true.
yep, that's what I was saying
On Wed, Dec 2, 2009 at 3:04 PM, Jakob Korherr jakob.korh...@gmail.com wrote:
Hi,
I think the best way would be that the init parameters have stage related
standard values (actually that what Matthias suggested), for example:
If we are in ProjectStage.Production
Problem when using MyFaces with Spring DM within an OSGi environment
Key: MYFACES-2442
URL: https://issues.apache.org/jira/browse/MYFACES-2442
Project: MyFaces Core
Issue
all serializable classes should have serialversionuids
--
Key: TRINIDAD-1651
URL: https://issues.apache.org/jira/browse/TRINIDAD-1651
Project: MyFaces Trinidad
Issue Type: Improvement
Hi
Just for curiosity, Is there any plans for a tobago and jsf 2.0?
regards,
Leonardo Uribe
[
https://issues.apache.org/jira/browse/TRINIDAD-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1651.
--
Resolution: Fixed
Fix Version/s: 1.2.13-core
all serializable
[
https://issues.apache.org/jira/browse/TRINIDAD-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784934#action_12784934
]
Matthias Weßendorf commented on TRINIDAD-1651:
--
some of them have already
Use JSF ProjectState API for some configuration parameters
--
Key: TRINIDAD-1652
URL: https://issues.apache.org/jira/browse/TRINIDAD-1652
Project: MyFaces Trinidad
Issue Type: New
Ok,
I added some value suggestions to those guys that we identified to fit
into the ProjectStage API:
-org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT
* Production = FALSE
* other stages = TRUE
-org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION
* Production = FALSE
* other stages = TRUE
[
https://issues.apache.org/jira/browse/TRINIDAD-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784959#action_12784959
]
Matthias Weßendorf commented on TRINIDAD-1601:
--
also, the JavaDoc (and
Hi,
my question was not clear probably, so I try to reformulate it:
- Trindad has param CHECK_FILE_MODIFICATION
- JSF 2.0 has param FACELETS_REFRESH_PERIOD
- javax.faces.ProjectStage is a general parameter at higher level of
abstraction than previous two
- FACELETS_REFRESH_PERIOD vs.
Matthias Wessendorf wrote: On 12/2/2009 10:43 AM PT:
Ok,
I added some value suggestions to those guys that we identified to fit
into the ProjectStage API:
-org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT
* Production = FALSE
* other stages = TRUE
+1. although I think if a user were to
Hi,
I have provided a patch which fixes issue 1649
https://issues.apache.org/jira/browse/TRINIDAD-1649. The fix is to
update the Trinidad ResponseWriter classes to override the new APIs
added to javax.faces.context.ResponseWriter in JSF2.0. I am working on a
project that uses the JSF 2.0
On Wed, Dec 2, 2009 at 8:32 PM, Martin Koci martin.k...@aura.cz wrote:
Hi,
my question was not clear probably, so I try to reformulate it:
- Trindad has param CHECK_FILE_MODIFICATION
- JSF 2.0 has param FACELETS_REFRESH_PERIOD
- javax.faces.ProjectStage is a general parameter at higher
On Wed, Dec 2, 2009 at 8:52 PM, Pavitra Subramaniam
pavitra.subraman...@oracle.com wrote:
Matthias Wessendorf wrote: On 12/2/2009 10:43 AM PT:
Ok,
I added some value suggestions to those guys that we identified to fit
into the ProjectStage API:
[
https://issues.apache.org/jira/browse/MYFACES-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Concini resolved MYFACES-2434.
--
Resolution: Fixed
Thanks to Bernhard Huemer for help in coming up with the final
org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable to parse
web.xml
---
Key: MYFACES-2443
URL: https://issues.apache.org/jira/browse/MYFACES-2443
[
https://issues.apache.org/jira/browse/MYFACES-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-2443.
-
Resolution: Invalid
please use the user list to ask questions on myfaces. this
[
https://issues.apache.org/jira/browse/TRINIDAD-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1650.
--
Resolution: Fixed
Fix Version/s: 2.0.0-core
add support for empty
is there anyone that is planing to do some stuff for JSF 2.0 and Tomahawk ?
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
34 matches
Mail list logo