[
https://issues.apache.org/jira/browse/EXTVAL-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142205#comment-13142205
]
Rudy De Busscher commented on EXTVAL-137:
-----------------------------------------
There exists in many cases a workaround to define an appropiate InvocationOrder
annotation on your custom NameMapper so that it is tried as the first
NameMapper.
@InvocationOrder(value = 1)
> Deregistering a class from the NameMapperFactory results in unsupported
> operation on CopyOnWriteArrayList
> ---------------------------------------------------------------------------------------------------------
>
> Key: EXTVAL-137
> URL: https://issues.apache.org/jira/browse/EXTVAL-137
> Project: MyFaces Extensions Validator
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.4, 2.0.4
> Reporter: Rudy De Busscher
> Assignee: Rudy De Busscher
> Priority: Minor
>
> If you wan't to deregister a NameMapper from the Factory class, so that it
> isn't used in your application, you get an exception because (some) factories
> use a CopyOnWriteArrayList List implementation.
> For example
> ClassMappingFactory factory =
> ExtValContext.getContext().getFactoryFinder()
> .getFactory(FactoryNames.STORAGE_MANAGER_FACTORY,
> ClassMappingFactory.class);
> NameMapperAwareFactory nameMapperFactory = (NameMapperAwareFactory)
> factory.create(ProcessedInformationStorage.class);
> nameMapperFactory.deny(ProcessedInformationStorageNameMapper.class);
> // Code omitted to add the custom nameMapper
--
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
