hi,
i talked with ed about this topic and he opened [1].
imo we should implement a solution including a spi. it would be easier to
specify the mechanism based on our implementation.
furthermore, a spi would allow to implement a myfaces-core2 specific add-on
for libs like codi.
regards,
gerhard
+1
2011/5/10 Mark Struberg strub...@yahoo.de:
puh, finally found the 2 hours to verify the release.
+1
* tested with 2 real world projects
* signature verified
* sha1 + md5 ok
* source distribution builds
* rat check ok
LieGrue,
strub
--- On Mon, 5/9/11, Werner Punz
+1
On Wed, May 11, 2011 at 10:02 AM, Leonardo Uribe lu4...@gmail.com wrote:
+1
2011/5/10 Mark Struberg strub...@yahoo.de:
puh, finally found the 2 hours to verify the release.
+1
* tested with 2 real world projects
* signature verified
* sha1 + md5 ok
* source distribution
Hi why not introduce a url param as view window/tag token and
then basically hook the map history in the session onto this token if given.
We could use codi window id for that token. If present we can handle
multiple maps per session if not then we run within the old scheme.
Outside of codi you
hi werner,
it's the other way round - a jsf impl is able to do way more in a portable
way (as soon as it is in the spec) than codi.
what we should prototype (imo):
- window-id
- request token
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses
[
https://issues.apache.org/jira/browse/TRINIDAD-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031902#comment-13031902
]
Max Starets commented on TRINIDAD-2100:
---
The basic idea of the patch is to
[
https://issues.apache.org/jira/browse/MYFACES-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031929#comment-13031929
]
Martin Kočí commented on MYFACES-3134:
--
I think that suspicious lines:
if
+1 for specific parameter (in one project I build view dynamically from
DB and want this ids check)
Gerhard Petracek píše v St 11. 05. 2011 v 07:52 +0200:
hi,
i would combine it - +1 for a myfaces specific parameter which gets
evaluated in case of project-stage production.
regards,
[
https://issues.apache.org/jira/browse/MYFACES-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031945#comment-13031945
]
Martin Kočí commented on MYFACES-3130:
--
mail topic: [core] performance: use indices
[
https://issues.apache.org/jira/browse/MYFACES-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031963#comment-13031963
]
Leonardo Uribe commented on MYFACES-3134:
-
Note JspStateManagerImpl will be
Hi
Working on this stuff I have found a problem with our current
ResponseStateManager implementation. The spec javadoc says this:
... ResponseStateManager is the helper class to StateManager that
knows the specific rendering technology being used to generate the
response. It is a singleton
[
https://issues.apache.org/jira/browse/MYFACES-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032006#comment-13032006
]
Matt Benson commented on MYFACES-3132:
--
I think the problem that was caused by this
Correct spelling errors in HtmlResponseStateManager exception messages
--
Key: MYFACES-3135
URL: https://issues.apache.org/jira/browse/MYFACES-3135
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/MYFACES-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson updated MYFACES-3135:
-
Status: Patch Available (was: Open)
Correct spelling errors in HtmlResponseStateManager
[perf] review UIComponentBase.getRendererType
--
Key: MYFACES-3136
URL: https://issues.apache.org/jira/browse/MYFACES-3136
Project: MyFaces Core
Issue Type: Improvement
Components:
Align ResponseStateManager implementation with the spec
---
Key: MYFACES-3137
URL: https://issues.apache.org/jira/browse/MYFACES-3137
Project: MyFaces Core
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/MYFACES-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3137.
-
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.6
Align
Simplify ResponseStateManager implementation code
-
Key: MYFACES-3138
URL: https://issues.apache.org/jira/browse/MYFACES-3138
Project: MyFaces Core
Issue Type: Sub-task
Components:
[
https://issues.apache.org/jira/browse/MYFACES-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe resolved MYFACES-3138.
-
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.6
Simplify
hi leo,
@window-id:
we have a window(-id) concept e.g. in trinidad, icefaces, cdi (at least a
conversation-id which should be specific to a window), codi,... . so we
again have incompatibilities (esp. in case of dialogs,...) which can't be
solved by just wrapping something. - adding the concept
20 matches
Mail list logo
