Hi,
I know this may not be the best place to ask my questions but since I'm
evaluating ServiceMix I thought I at least should ask.
The involved components are:
- HTTP-bindings with a propriatary protocol based on S/MIME.
- Content Based Routing based on messageheader combined with lookup of
endpoints from local or global directory (LDAP v3)
- The delivery of messages are either async. or synchronous based on
message header.
Typical async-scenario
======================
A client issues a HTTP-post to the BC (like the HTTP-binding example in
SM). The content of the message is a multipart/mixed.
The first part of the message is always text/xml and contains the header
information used to determine how to process the message.
The messages can be signed/encrypted but the header part is always
unsigned/unencrypted.
Based on a property in the header of the first mime-part the request is
either async. or sync.
In this case we pretend that we have an async case.
Before returning an HTTP-result to the client the label must be
validated against a DTD.
I've got a couple of different approaches on how to solve this with
ServiceMix:
- build a complete solution based on application framework XXX and
deploy and bootstrap within SM.
- build the different BC:s (HTTP-client / HTTP-binding) and the
RS-Async, RS-Sync as SE in ServiceMix and use the Spring-support for
building services used for LDAP-lookup, Logging etc.
Do you have any suggestions on how to approach the problem?
How granular should one be when designing services in ServiceMix if you
want a system as performant as possible?
By looking at JBI I'm trying to deduce which MEP to use for the sync and
async messaging in my case.
Best regards,
Mats
