Empty url mapping prefix causes infinite loop in
DefaultViewHandlerSupport.handlePrefixMapping
--
Key: MYFACES-2891
URL:
[
https://issues.apache.org/jira/browse/MYFACES-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901762#action_12901762
]
Michal Dvorak commented on MYFACES-2891:
This happens probably only when using
[
https://issues.apache.org/jira/browse/MYFACES-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901762#action_12901762
]
Michal Dvorak edited comment on MYFACES-2891 at 8/24/10 4:06 AM:
+1
On Mon, Aug 23, 2010 at 10:46 PM, Leonardo Uribe lu4...@gmail.com wrote:
+1
2010/8/23 Leonardo Uribe lu4...@gmail.com
Hi,
I was running the needed tasks to get the version 1 release of Apache
MyFaces Site Skin.
This artifact is required to build the site of some myfaces projects.
I agree, that this should not block us from releasing the bits.
-Matthias
On Mon, Aug 23, 2010 at 11:53 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Ok. The idea in the future is integrate that work, but for now that is not a
stopper for a release.
The plan from my side for the next
+1
LieGrue,
strub
From: Jan-Kees van Andel jankeesvanan...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Tue, August 24, 2010 11:02:00 AM
Subject: Re: [VOTE] release for myfaces site skin v 1
+1
Looks good.
Regards,
Jan-Kees
2010/8/24 Matthias Wessendorf
+1
Regards,
Jakob
2010/8/24 Mark Struberg strub...@yahoo.de
+1
LieGrue,
strub
From: Jan-Kees van Andel jankeesvanan...@gmail.com
To: MyFaces Development dev@myfaces.apache.org
Sent: Tue, August 24, 2010 11:02:00 AM
Subject: Re: [VOTE] release for myfaces site skin v 1
+1
Hi folks!
With the new apache parent, we also got a new snapshots repository. We now face
the problem to have 2 apache-snapshots repositories which will not work without
overriding the maven metainfo of each other.
To work around those weird problems I usually have the following entry in my
Hi Mark,
+1
This means that we have to remove all snapshot-repo entries from our poms,
right?
Regards,
Jakob
2010/8/24 Mark Struberg strub...@yahoo.de
Hi folks!
With the new apache parent, we also got a new snapshots repository. We now
face
the problem to have 2 apache-snapshots
+1
But if they don't share the same repository id, if you happened to have both
snapshots repos in your POM file, the newer snapshot will be the one to be
picked, no?. So as long as you add the new snapshot repository with a new id
you should be safe. Of couse, to replace the old one would be
@Jakob: we should imo generally remove ALL repositories and
distributionManagement repo settings (repos, NOT the sites!). All we need for
doing a release is in apache-parent, and all other settings are most probably
problematic if not broken.
@Bruno: sadly the 2 repos both have the same id :(
[
https://issues.apache.org/jira/browse/MYFACES-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACES-2891.
Fix Version/s: 2.0.2-SNAPSHOT
Resolution: Fixed
I changed the algorithm so that
+1
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2010/8/24 Jakob Korherr jakob.korh...@gmail.com
+1
Regards,
Jakob
2010/8/24 Mark Struberg strub...@yahoo.de
+1
INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL applies for String only
---
Key: MYFACES-2892
URL: https://issues.apache.org/jira/browse/MYFACES-2892
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/MYFACES-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kočí updated MYFACES-2892:
-
Status: Patch Available (was: Open)
INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL applies
[
https://issues.apache.org/jira/browse/MYFACES-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr updated MYFACES-2886:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.2-SNAPSHOT
[
https://issues.apache.org/jira/browse/MYFACES-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901870#action_12901870
]
Matthias Weßendorf commented on MYFACES-2892:
-
thanks for the reminder - I
[
https://issues.apache.org/jira/browse/MYFACES-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-2839.
-
Assignee: Matthias Weßendorf
Fix Version/s: 2.0.2-SNAPSHOT
[
https://issues.apache.org/jira/browse/MYFACES-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated MYFACES-2892:
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.2-SNAPSHOT
Column of Trinidad table disappear
--
Key: EXTVAL-115
URL: https://issues.apache.org/jira/browse/EXTVAL-115
Project: MyFaces Extensions Validator
Issue Type: Bug
Affects Versions: 1.2.3
You're right, Gerhard. Furthermore we now have a spi package in impl (for
the JBoss integration) and I think this is the best place to put it. I will
open a JIRA issue, do some prototyping and provide a patch soon.
Regards,
Jakob
2010/8/13 Gerhard gerhard.petra...@gmail.com
the mentioned
[
https://issues.apache.org/jira/browse/TRINIDAD-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1884.
---
Fix Version/s: 1.2.15-core
Resolution: Fixed
Back port the Trinidad 2
[
https://issues.apache.org/jira/browse/TOBAGO-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901961#action_12901961
]
D. W. commented on TOBAGO-906:
--
Thanks for your quick reaction and apologies for my late reply
[
https://issues.apache.org/jira/browse/TOBAGO-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901961#action_12901961
]
D. W. edited comment on TOBAGO-906 at 8/24/10 12:51 PM:
Thanks for
Hi!
Not sure if this is covered in the spec, but wouldn't if be useful to parse for
the JSR-303 Size annotation [1] and use this value for the maxlength attribute
of h:inputText fields if nothing is manually specified in the xhtml?
LieGrue,
strub
Hi,
I tried it for my renderkit but unfortunately there is no (or I didn't
find) solution for scenario, where
value=#{bean.otherBean.constrainedProperty} and otherBean is null. In
such case you can only obtain constrains from declared type, not from
the real one.
But for simpler cases where
hi,
extval supports such features (see [1] - in this case you just have to
switch to the bv-module - the rest works automatically).
regards,
gerhard
[1] http://jsfcentral.com/articles/myfaces_extval_1.html
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in
27 matches
Mail list logo