Index Changes
Page Difference

Difference between version and version     

Back to Fuji EIP Split, or Fuji EIP Split Info


At line 23 added 10 lines.
! Examples
Split with inline configuration
\\
{{{
route do
from "batch-inbound"
split xpath ("/PurchaseOrder")
to "po-process"
end
}}}
At line 34 added 1 line.
__Note:__ ''I'm wondering if it would be more appropriate for the in-line configuration to be contained within 'do/end' blocks, similar to how broadcast is handled today. This may be a good general-purpose construct for scoping all IFL language features. Thoughts?''
At line 36 added 18 lines.
Split with external configuration
\\
{{{
route do
from "batch-inbound"
split xpath "po-split"
to "po-process"
}}}
{{{
> cat po-split.xml
/PurchaseOrder
}}}
! Misc.
* The IFL parser should not place any constraints on the type identifier in a split definition. This means that the value for type can only be verified at the time of service artifact generation.
* Known types to the parser/editor should provide contextual help in the form of syntax highlighting, code completion, etc. For the time being, this will be limited to xpath and regex types.
At line 60 added 3 lines.
! Other
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-14) was last changed on 21-Jul-09 09:42 AM, -0700 by MarkWhite