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/10/14 02:39:31 UTC

[jira] Created: (EXTVAL-65) execution order

execution order
---------------

                 Key: EXTVAL-65
                 URL: https://issues.apache.org/jira/browse/EXTVAL-65
             Project: MyFaces Extensions Validator
          Issue Type: New Feature
          Components: Core
    Affects Versions: 1.1.2, 1.1.1, 1.2.2, 1.2.1
            Reporter: Gerhard Petracek
            Priority: Minor


for some artifacts it makes sense to define the order of execution when it comes to add-ons which have to extend extval in a very special way. that allows to force an execution order independent of the registration order.

@ExecutionOrder ... marks an artifact with a given order
@ExecutionOrderSupport... marks interfaces (instances of classes implementing these interfaces will be sorted)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (EXTVAL-65) invocation order mechanism

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/EXTVAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved EXTVAL-65.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.3-SNAPSHOT
                   2.0.3-SNAPSHOT
                   1.2.3-SNAPSHOT

> invocation order mechanism
> --------------------------
>
>                 Key: EXTVAL-65
>                 URL: https://issues.apache.org/jira/browse/EXTVAL-65
>             Project: MyFaces Extensions Validator
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.1, 1.2.2, 1.1.1, 1.1.2
>            Reporter: Gerhard Petracek
>            Priority: Minor
>             Fix For: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> for some artifacts it makes sense to define the order of execution when it comes to add-ons which have to extend extval in a very special way. that allows to force an execution order independent of the registration order.
> @InvocationOrder ... marks an artifact with a given order
> @InvocationOrderSupport... marks interfaces (instances of classes implementing these interfaces will be sorted internally)
> suggested ranges:
> negative values for very special cases
> 0-49 for custom artifacts which should have the highest priority
> 50-99 for add-ons which provide artifacts which should have a higher priority than the default artifacts
> 100-999
> 1000+ for custom artifacts
> a priority should be unique within one artifact-type - that means:
> if a name-mapper has priority 100, it's ok that an exception-interceptor also has priority 100.
> but a 2nd name-mapper shouldn't have priority 100 (if so - the order depends on the registration order)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.