Hi All,
For the advanced version of the required label add-on, I would like to have
some initialisation parameters in web.xml so that the developer could
customize the add-on.
To my knowledge, there isn't any add-on for the moment that have such
initialisation parameters. So I would like to
hi rudy,
+1 for thinking about a suggested name convention.
@ #2: imo it's confusing for people to see an org.apache.* prefix outside an
apache project.
@ #3: you don't lose the information that it is related to extval, because
it's part of the package name.
what's about the suggestion that
hi @ all,
i've started to move some parts to our new (c)wiki.
however, imo we should just move the information which is important for
users.
that means we should continue to use the moinmoin wiki just for information
related to our dev-team (e.g. our reports, release wiki pages, drafts,...).
so
All,
I've got a bug that one of our testers found where we behave differently
from the RI. Let me lay out the situation and the two options I have
come up with for solutions. This applies to at least the 1.2.x and
2.0.x releases.
The application has a simple logout.jsp that we get to via a
Hi Mike,
2) do something in the form renderer to indicate that the state needs to be
saved, maybe setting a request attribute that can be checked in saveView to
determine whether to actually save state or just return null.
I would lean towards option 2 - I don´t see how the saved state would
[
https://issues.apache.org/jira/browse/TRINIDAD-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Starets updated TRINIDAD-1827:
--
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.0.3-core
What about ajax and http get which perse do not post a form in all cases
but can post data back into the lifecycle?
OK,http get is handled, but still there is ajax which can trigger
a post without a form.
Werner
Am 11.06.10 16:13, schrieb Martin Marinschek:
Hi Mike,
2) do something in
Hi
In theory, if there is no form there is no state saved, so the ajax received
will not have the state and no postback could be sent. Ok, if the view state
is saved in some different way by other alternate ajax component, the point
in common is that any component that writes the state should
The Apache MyFaces team is pleased to announce the release of MyFaces
Core 1.1.8.
MyFaces Core is a JavaServer(tm) Faces 1.1 implementation as specified
by JSR-127. MyFaces Core has passed Sun's JSR-127 TCK and is 100%
compliant with the JSR-127 specification.
Please note this release also
The Apache MyFaces team is pleased to announce the release of MyFaces
Core 1.2.9.
MyFaces Core is a JavaServer(tm) Faces 1.2 implementation as specified
by JSR-252. MyFaces Core has passed Sun's JSR-252 TCK and is 100%
compliant with the JSR-252 specification.
Please note this release also
Leo,
So I just did a little digging through the facelets code, and it looks
like in the facelets case, we already are doing something similar to
what you are proposing. ViewHandlerImpl's writeState method looks like
it only gets called by the encodeEnd on HtmlFormRendererBase. So I
think
Hi,
Yes, great idea, Gerhard.
+1 on that from me!
Regards,
Jakob
2010/6/11 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
i've started to move some parts to our new (c)wiki.
however, imo we should just move the information which is important for
users.
that means we should
[
https://issues.apache.org/jira/browse/MYFACES-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877913#action_12877913
]
Jakob Korherr commented on MYFACES-2739:
Hi Martin and Leo,
Yes this is
Hi,
I was running the needed tasks to get the 2.0.1 release of Apache
MyFaces core out.
The artifacts passed all TCK tests.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared v4.0.2 [1]
2. Maven artifact group
+1
2010/6/11 Leonardo Uribe lu4...@gmail.com
Hi,
I was running the needed tasks to get the 2.0.1 release of Apache
MyFaces core out.
The artifacts passed all TCK tests.
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.shared
[
https://issues.apache.org/jira/browse/MYFACES-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877927#action_12877927
]
Leonardo Uribe commented on MYFACES-2739:
-
Hi Jakob
I think for now we can let
+1
Werner
Am 11.06.10 21:07, schrieb Leonardo Uribe:
+1
2010/6/11 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com
Hi,
I was running the needed tasks to get the 2.0.1 release of Apache
MyFaces core out.
The artifacts passed all TCK tests.
Please note that this
+1
Am 11.06.10 20:34, schrieb Jakob Korherr:
Hi,
Yes, great idea, Gerhard.
+1 on that from me!
Regards,
Jakob
2010/6/11 Gerhard Petracek gerhard.petra...@gmail.com
mailto:gerhard.petra...@gmail.com
hi @ all,
i've started to move some parts to our new (c)wiki.
however, imo we
[
https://issues.apache.org/jira/browse/MYFACES-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877936#action_12877936
]
Nick Belaevski commented on MYFACES-2638:
-
Investigating the reasons of unit
[
https://issues.apache.org/jira/browse/MYFACES-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877936#action_12877936
]
Nick Belaevski edited comment on MYFACES-2638 at 6/11/10 3:42 PM:
[
https://issues.apache.org/jira/browse/MYFACES-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877970#action_12877970
]
Leonardo Uribe commented on MYFACES-2638:
-
Yes, you're right. I tested it and
[
https://issues.apache.org/jira/browse/MYFACES-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877976#action_12877976
]
Nick Belaevski commented on MYFACES-2638:
-
Leonardo,
Thank you for the fix :)
create a public api for zipping the page state
--
Key: TRINIDAD-1829
URL: https://issues.apache.org/jira/browse/TRINIDAD-1829
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/TRINIDAD-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12878107#action_12878107
]
Gabrielle Crawford commented on TRINIDAD-1829:
--
The current name of the
Hi
Just one small note, I regenerate all artifacts to include a small fix in
MYFACES-2638. It is just move one line of code, so it does not affect
anything, but I did all tests again, so we can continue the vote as is.
regards,
Leonardo Uribe
2010/6/11 Werner Punz werner.p...@gmail.com
+1
Hi,
We added a context param a while back to turn on zipping the page state,
the param was internal, but would like to make it public, please see:
https://issues.apache.org/jira/browse/TRINIDAD-1829
The current name of the param is
org.apache.myfaces.trinidadinternal.COMPRESS_VIEW_STATE
The
+1. Very good idea.
On Fri, Jun 11, 2010 at 12:10 PM, Gerhard Petracek
gerhard.petra...@gmail.com wrote:
hi @ all,
i've started to move some parts to our new (c)wiki.
however, imo we should just move the information which is important for
users.
that means we should continue to use the
UIXHierarchy.visitHierarchy() has a bad if statement
Key: TRINIDAD-1830
URL: https://issues.apache.org/jira/browse/TRINIDAD-1830
Project: MyFaces Trinidad
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/TRINIDAD-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Cooper resolved TRINIDAD-1830.
---
Fix Version/s: 1.2.14-core
2.0.0.2-core
Resolution: Fixed
29 matches
Mail list logo
