You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2008/01/22 09:40:34 UTC
[jira] Created: (TAPESTRY-2071) Validators using Regexps shouldn't
use the pool-based PatternMatcher
Validators using Regexps shouldn't use the pool-based PatternMatcher
--------------------------------------------------------------------
Key: TAPESTRY-2071
URL: https://issues.apache.org/jira/browse/TAPESTRY-2071
Project: Tapestry
Issue Type: Bug
Components: Framework
Affects Versions: 4.1.3
Environment: any
Reporter: Marcus Schulte
Assignee: Marcus Schulte
Priority: Minor
Fix For: 4.1.4
PatternMatcher pools regular expression which makes sense when used as a member of (singleton-) services.
Validators on the other hand, are normally used as leight-weight beans not surviving a request cycle. Creating
a commons-pool for each of them doesn't seem right - and causes trouble when commons-pool breaks.
Thus validators should use java.util.regex.Pattern directly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Reopened: (TAPESTRY-2071) Validators using Regexps shouldn't
use the pool-based PatternMatcher
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte reopened TAPESTRY-2071:
--------------------------------------
missed ValidatorFactoryImpl, line 57
> Validators using Regexps shouldn't use the pool-based PatternMatcher
> --------------------------------------------------------------------
>
> Key: TAPESTRY-2071
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2071
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.3
> Environment: any
> Reporter: Marcus Schulte
> Assignee: Marcus Schulte
> Priority: Minor
> Fix For: 4.1.4
>
>
> PatternMatcher pools regular expression which makes sense when used as a member of (singleton-) services.
> Validators on the other hand, are normally used as leight-weight beans not surviving a request cycle. Creating
> a commons-pool for each of them doesn't seem right - and causes trouble when commons-pool breaks.
> Thus validators should use java.util.regex.Pattern directly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-2071) Validators using Regexps shouldn't
use the pool-based PatternMatcher
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte resolved TAPESTRY-2071.
--------------------------------------
Resolution: Fixed
> Validators using Regexps shouldn't use the pool-based PatternMatcher
> --------------------------------------------------------------------
>
> Key: TAPESTRY-2071
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2071
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.3
> Environment: any
> Reporter: Marcus Schulte
> Assignee: Marcus Schulte
> Priority: Minor
> Fix For: 4.1.4
>
>
> PatternMatcher pools regular expression which makes sense when used as a member of (singleton-) services.
> Validators on the other hand, are normally used as leight-weight beans not surviving a request cycle. Creating
> a commons-pool for each of them doesn't seem right - and causes trouble when commons-pool breaks.
> Thus validators should use java.util.regex.Pattern directly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-2071) Validators using Regexps shouldn't
use the pool-based PatternMatcher
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte resolved TAPESTRY-2071.
--------------------------------------
Resolution: Fixed
> Validators using Regexps shouldn't use the pool-based PatternMatcher
> --------------------------------------------------------------------
>
> Key: TAPESTRY-2071
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2071
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.3
> Environment: any
> Reporter: Marcus Schulte
> Assignee: Marcus Schulte
> Priority: Minor
> Fix For: 4.1.4
>
>
> PatternMatcher pools regular expression which makes sense when used as a member of (singleton-) services.
> Validators on the other hand, are normally used as leight-weight beans not surviving a request cycle. Creating
> a commons-pool for each of them doesn't seem right - and causes trouble when commons-pool breaks.
> Thus validators should use java.util.regex.Pattern directly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org