[jira] [Created] (TOBAGO-1089) Examples: Update to Jetty 7 and cleanup
Examples: Update to Jetty 7 and cleanup --- Key: TOBAGO-1089 URL: https://issues.apache.org/jira/browse/TOBAGO-1089 Project: MyFaces Tobago Issue Type: Task Components: Demo Affects Versions: 1.5.2 Reporter: Udo Schnurpfeil Assignee: Udo Schnurpfeil Priority: Trivial The Maven configuration can be simplified. Configuring jetty in the example parent pom, so every example can use SSL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] release of myfaces core 2.1.6
My integration tests also pass +1 from my side. Werner Am 03.02.12 06:12, schrieb Leonardo Uribe: +1 2012/2/3 Leonardo Uribelu4...@gmail.com: Hi, I was running the needed tasks to get the 2.1.6 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.1.4 [1] 2. Maven artifact group org.apache.myfaces.core v2.1.6 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.1.6 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-180/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces216binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12319173
[jira] [Created] (MYFACES-3458) [perf] Store URL at class ResourceImpl
[perf] Store URL at class ResourceImpl
--
Key: MYFACES-3458
URL: https://issues.apache.org/jira/browse/MYFACES-3458
Project: MyFaces Core
Issue Type: Improvement
Affects Versions: 2.1.5, 2.1.3
Environment: Websphere Application Server v7
Windows 2003 Server
Double quad-core Intel Xeon CPU
Reporter: Jesús Pérez Alcaide (ISBAN)
Doing stress tests on a JSF application we have noticed some contention.
14% of the time that the threads are blocked is due to calls to
ClassLoader#getResource(String). Such calls comes from method
org.apache.myfaces.shared.resource.ResourceImpl#getUrl(). (see attached image)
Viewing the code of the method ResourceImpl#getURL(), it is always calculating
the URL of the resource through the ResourceLoader. This, in turn, ends up
calling the method ClassLoader#getResource(String).
public URL getURL()
{
return getResourceLoader().getResourceURL(_resourceMeta);
}
Since the resulting URL will not change during the life of the resource
instance, it could be stored in an instance variable and thus prevent
subsequent calls to this method end up calling the ClassLoader.
private URL _url;
public URL getURL()
{
if (_url == null) {
_url = getResourceLoader().getResourceURL(_resourceMeta);
}
return _url;
}
With this change applied we obtained a performance improvement between 14% and
119% of throughput, depending on the complexity of the rendered view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE] release of myfaces core 2.0.12
Hi, I was running the needed tasks to get the 2.0.12 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.12 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.12 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.12 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-181/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2012binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12319175
Re: [VOTE] release of myfaces core 2.0.12
+1 2012/2/3 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the 2.0.12 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.12 [1] 2. Maven artifact group org.apache.myfaces.core v2.0.12 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the 2.0.12 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-181/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2012binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600version=12319175
[jira] [Created] (TRINIDAD-2212) JDev plugin could use some improvements
JDev plugin could use some improvements --- Key: TRINIDAD-2212 URL: https://issues.apache.org/jira/browse/TRINIDAD-2212 Project: MyFaces Trinidad Issue Type: Improvement Components: Build Affects Versions: 2.0.7-plugins Environment: All Reporter: Bud Osterberg Priority: Minor There have been some improvements requested for the jdev:jdev plugin e.g. Allow the exclusion of certain projects from the workspace, allow specific naming of the context root or the workspace itself, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MYFACES-3459) RegexValidator does not provide label and pattern for first usage of RegexValidator.NOT_MATCHED
RegexValidator does not provide label and pattern for first usage of
RegexValidator.NOT_MATCHED
---
Key: MYFACES-3459
URL: https://issues.apache.org/jira/browse/MYFACES-3459
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.1.5
Environment: myfaces trunk
Reporter: Martin Kočí
Assignee: Martin Kočí
Priority: Trivial
RegexValidator uses javax.faces.validator.RegexValidator.NOT_MATCHED 2x:
javax.faces.validator.RegexValidator.NOT_MATCHED= the passed value is not a
String, or when the pattern does not match the passed value.
the first usage for if (value instanceof String) check does not provide args
for {0} {1} in message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3459) RegexValidator does not provide label and pattern for first usage of RegexValidator.NOT_MATCHED
[
https://issues.apache.org/jira/browse/MYFACES-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13200046#comment-13200046
]
Martin Kočí commented on MYFACES-3459:
--
few observations:
# java.util.regex.Pattern.matcher(CharSequence) support CharSequence and we can
easily support it too - change instanceof check to (value instanceof
CharSequence)
# this instanceof check indicates disagreement between local value (converted)
and type expected in validator - created '{1}: Validation Error: Value not
according to pattern ''{0}''' is not suitable for this (mojarra thows
CastClassExpception in the middle of validator and that is also not very proper)
# javax.faces.validator.RegexValidator.PATTERN_NOT_SET and
RegexValidator.MATCH_EXCEPTION are completely missing in .properties files - or
I can't find them
RegexValidator does not provide label and pattern for first usage of
RegexValidator.NOT_MATCHED
---
Key: MYFACES-3459
URL: https://issues.apache.org/jira/browse/MYFACES-3459
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.1.5
Environment: myfaces trunk
Reporter: Martin Kočí
Assignee: Martin Kočí
Priority: Trivial
RegexValidator uses javax.faces.validator.RegexValidator.NOT_MATCHED 2x:
javax.faces.validator.RegexValidator.NOT_MATCHED= the passed value is not a
String, or when the pattern does not match the passed value.
the first usage for if (value instanceof String) check does not provide
args for {0} {1} in message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
