Raymond Feng wrote:
Hi,
I suggest that we not expand too quickly into other bindings such as
RMI. Let's focus on getting your previous proposal (StockQuote,
AccountData services) implemented first.
Thanks,
Raymond
+1 to try to work through the actual scenario first.
When I brought up the scenario I was thinking about the following steps:
1. Copy the bigbank-* modules into new bigbank-secure-* modules.
2. Split the AccountData component into two components in two different
composites representing two divisions of the bank (checking and savings
accounts).
3. At this point I'm not sure that the calculator component is so
interesting for this scenario, as it was there to show integration of
different scripting languages, not very relevant here. It's probably
more interesting to invoke a CurrencyConverter Web service running on a
separate node simulating an external service.
4. Discuss on this list what kind of policies (authentication,
confidentiality, integrity) make sense to apply where in the bigbank
solution.
5. Author the policy related application and
configuration/deployment related artifacts in the bigbank modules; I'm
sure that many questions will arise and help understand usage patterns
and good practices for policies.
6. Go through the steps that an application developer, assembler,
deployer, system administrator needs to perform to put the bigbank
solution together; this is not a theoretical exercise as we'll actually
have to perform these steps ourselves, and work on what can be done to
our policy support to facilitate them.
7. Bring the pieces of the bigbank solution together, get it working end
to end and work through any relevant technical issues.
I'm guessing that questions like...
- how many definitions.xml files to we need?
- what do we write in them?
- where do we place them?
- can "intent=confidentiality" represent different types of
confidentiality mechanisms used for different types of exchanges?
- do we put policysets in the composites or definitions.xml
- how do we use appliesTo?
- and probably 50 more questions like that :)
... will pop up right in our face when we develop the scenario, backed
by a concrete use case which will help think through them.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
