You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2009/07/14 17:45:14 UTC
[jira] Resolved: (EXTVAL-49) pluggable named storages and storage
management
[ https://issues.apache.org/jira/browse/EXTVAL-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved EXTVAL-49.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.3-SNAPSHOT
2.0.3-SNAPSHOT
1.2.3-SNAPSHOT
> pluggable named storages and storage management
> -----------------------------------------------
>
> Key: EXTVAL-49
> URL: https://issues.apache.org/jira/browse/EXTVAL-49
> Project: MyFaces Extensions Validator
> Issue Type: New Feature
> Components: Bean Validation, Core, Property Validation
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Priority: Minor
> Fix For: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> the bv integration uses a request scoped storage for groups. the basic concept might be also useful for add-ons or custom validation modules.
> this mechanism allows to reuse existing implementations. to avoid collisions a storage name is used to allowed multiple storages of the same type.
> the generic implementation isn't aware of the concrete storage type. so it's possible to register custom storage types and implementations.
> the mapping between the storage type and the storage implementation is up to the storage manager implementation.
> (the default implementation reuses the name-mapping principle.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.