Index Changes

Difference between version and version     

Back to Fuji EIP Aggregate, or Fuji EIP Aggregate Info


At line 40 added 8 lines.
Aggregate with inline configuration
{{{
route do
from "multiple-in"
aggregate set {count=5}
to "single-out"
end
}}}
At line 49 added 8 lines.
Aggregate with external configuration
{{{
route do
from "multiple-in"
aggregate set "message-batch"
to "single-out"
end
}}}
At line 58 added 6 lines.
{{{
> cat message-batch/aggregate.properties
count=5
}}}
At line 65 added 12 lines.
Each aggregate type will have its own unique configuration requirements. The service artifact layer in Fuji will have a reasonable default behavior for all aggregate types. Individual aggregate types can override the default behavior by implementing the following contracts:
* Generation - the configuration generated from IFL for a given aggregate type. A facility must exist for discovering template service artifacts for a given aggregate type. This could be an SPI or a convention for resource location inside a bundle/jar file. For external configuration, a default implementation should be provided that results in an empty file with the aggregate configuration name used as the file name. Generation is not relevant for inline configuration.
* Validation - during the packaging phase of the application build, aggregate types will have an opportunity to validate configuration. This should be exposed as an SPI that a aggregate type provider can implement.
\\
The directory layout for generated configuration should be:
{{{
app-root/
aggregate/
{name}/
[configuration]
}}}
Where '{name}' is the named configuration provided in IFL.
At line 79 added 4 lines.
size
count
wait
order

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-16) was last changed on 02-Jun-09 02:04 AM, -0700 by Nikita