Hi,
Are you looking for mediation abilities that handle message level processing
agnostic to the business logic?
Let's assume that we have the following scenario:
1) There are multiple clients, such as ClientA and ClientB, that makes Web
Service calls.
2) A broker component (Broker) will receive all the SOAP messages and perform
mediations
3) The broker needs to dispatch to a Groovy class that provide the real service
implementation
Does ClientA and ClientB use the same WSDL interfaces?
Do you want to implement the Broker in Java?
Do you intend to wrap Groovy as SCA components?
I'm trying to better understand the usage requirements before we start to
explore some potential solutions.
Thanks,
Raymond
From: Wayne Keenan
Sent: Thursday, March 04, 2010 12:11 PM
To: user@tuscany.apache.org
Subject: Composite promotion of custom dispatch class
Hi,
In a few messaging stacks (e.g. XFire, Apache CXF, Apache Camel) it is
possible to route invocations on a SOAP endpoint to a generic handler if the
implementation class behind the interface contains a method with a signature
such as this fictional example:
class MyCustomRouter {
public Document handler(ExchangeInfo ex, Document request) {
String operationName = ex.getOperation();
// do some custome dispatch and build a SOAP response
return doc;
}
}
Is such a implementation.java promotion possible for Tuscany SCA composites?
As I wish to route all SOAP requests to a common Java component that does some
common setup and then dispatches to a Groovy class - in a way very different to
'implementation.script language="groovy"' provides.
Regards
Wayne
