Issue Details (XML | Word | Printable)

Key: MULE-3848
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Andrew Perepelytsya
Reporter: Andrew Perepelytsya
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

Groovy expression evaluator isn't listed in allowed values list in xsd

Created: 17/Oct/08 10:25 AM   Updated: 17/Oct/08 12:37 PM
Component/s: Core: Configuration
Affects Version/s: None
Fix Version/s: 2.0 ITR9, 2.1.1

Time Tracking:
Not Specified

Labels: expressions groovy filters
User impact: Low
Effort points: 0
Affects Docs: Yes



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Andrew Perepelytsya added a comment - 17/Oct/08 10:32 AM
Ross, could you please comment?

Taking a closer look, it is in fact listed for generic evaluators, but not for expressionFilter evaluators. Then, there's a big discrepancy in the list contents for those:

Here's the expressionAttributes/evaluator list:

<xsd:restriction base="substitutableName">
                    <xsd:enumeration value="groovy"/>
                    <xsd:enumeration value="header"/>
                    <xsd:enumeration value="headers"/>
                    <xsd:enumeration value="headers-list"/>
                    <xsd:enumeration value="attachment"/>
                    <xsd:enumeration value="attachments"/>
                    <xsd:enumeration value="attachments-list"/>
                    <xsd:enumeration value="message"/>
                    <xsd:enumeration value="map-payload"/>
                    <xsd:enumeration value="payload"/>
                    <xsd:enumeration value="xpath"/>
                    <xsd:enumeration value="jxpath"/>
                    <xsd:enumeration value="bean"/>
                    <xsd:enumeration value="ognl"/>
                    <xsd:enumeration value="function"/>
                    <xsd:enumeration value="custom"/>
                </xsd:restriction>

and expression-filter/expressionFilterType/evaluator for comparison:

<xsd:simpleType>
                        <xsd:restriction base="substitutableName">
                            <xsd:enumeration value="header"/>
                            <xsd:enumeration value="payload-type"/>
                            <xsd:enumeration value="exception-type"/>
                            <xsd:enumeration value="wildcard"/>
                            <xsd:enumeration value="regex"/>
                            <xsd:enumeration value="ognl"/>
                            <xsd:enumeration value="xpath"/>
                            <xsd:enumeration value="jxpath"/>
                            <xsd:enumeration value="bean"/>
                            <xsd:enumeration value="custom"/>
                        </xsd:restriction>
                    </xsd:simpleType>

Ross Mason added a comment - 17/Oct/08 10:35 AM
Hmmm, good catch, this is a screw up. We need to add this back in. Can we do it for this release?

Ross Mason added a comment - 17/Oct/08 12:04 PM
that would be good. This change would not de-stabilize the release.

Ross Mason added a comment - 17/Oct/08 12:13 PM
I believe this can be merges safely since its just another option in a n enumeration