Thank all of you for the feedback.
More comments inline.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, October 08, 2007 12:28 PM
Subject: Re: A demo application to showcase our XML integration story
Raymond Feng wrote:
Hi,
I put together a demo application to showcase our XML integration story.
The business scenario is derived from the bigbank demo and the main
function is to calculate the total value (using a selected currency) of a
customer who has checking/saving/stock accounts.
At this moment, I add three different sources to provide XML data.
1) A live feed to retrieve the exchange rate (binding.feed) and use XPath
to exact the rate for a given currency. I have to use Rome API to convert
the feed as our feed binding produces Feed objects.
2) The account data for a customer is loaded from a XML file. (We can use
implementation.data once Sebastien's proposal is implemented).
3) A live Web Service invocation to get the quotes for a list of symbols.
Only XMLStreamReader is used as the input and output. (binding.ws)
4) The calculation of the total value is implemented using XQuery to join
the XML data from 2 and 3. (implementation.xquery)
The demo application is checked in under r581755. I hope we can use it as
a test-bed to further drive our XML integration story. Please feel free
to chime in with your ideas, for example, add implementation.data or
implementation.das, or implementation.bpel.
Thanks,
Raymond
A few comments:
- This looks pretty good!
- CustomerAsset looks like the AccountService from the Java Bigbank demo,
if it's the same thing then it should be named AccountService to avoid any
confusion and make the comparison easier.
+1. I renamed it to AccountService.
- I think we should try to remove all Java code from the demo and try to
implement CustomerAsset (or AccountService) as a BPEL process or an XQuery
function.
Ant was proposing to have a java script component :-). I'm open.
and a question:
- What would it take to return Account summary complex documents from the
AccountService instead of just a number? Can we do this without having to
generate any code?
We could try to return the AccountReport (w/ a list account summaries). If
we don't want to code-gen, then we could use DOM, AXIOM or even
XMLStreamReader. Or we could use XQuery or XSLT to produce HTML.
I'm wondering if code-gen is always a bad thing. On one hand, it complicates
the story a bit, but on the other hand, it demonstrates that application
developers have the freedom of choices if they prefer strong-typed
representation of XML infoset.
(I'd like to do change the Java Bigbank demo to return account summaries
as well, like the original Bigbank scenario described in the original spec
docs)
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
