I'll refactor the two creditcard-payment contributions to reflect the fact
that different technologies are used.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <[email protected]>
Sent: Thursday, February 12, 2009 12:33 AM
To: <[email protected]>
Subject: Re: Travel sample directory structure reorganization
Raymond Feng wrote:
The creditcardpayment-contribution was initially added by me to test the
payment component and it uses JAXB databinding. The one in chapter-09
uses SDO databinding which matches the draft in the book.
Should we remove creditcardpayment-contribution or should we keep both
versions to demonstrate the flexibility of switching databinding?
+1 for keeping both versions. The book could mention both versions
even if only one of them actually appears within the book itself.
If we do this, it would be good to use names like
creditcardpayment-sdo-contribution and creditcardpayment-jaxb-contribution
to make it clear which version is which.
Is any other code using the JAXB version? I am wondering why it
is part of shared-contributions.
Simon
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <[email protected]>
Sent: Wednesday, February 11, 2009 1:50 AM
To: <[email protected]>
Subject: Re: Travel sample directory structure reorganization
Raymond Feng wrote:
A quick update: I just added a creditcard-payment-contribution for
chapter 09 to demonstrate the SDO version of CreditCardPayment
implementation.
It's a bit confusing having creditcard-payment-contribution
in chapter-09 and creditcardpayment-contribution in
shared-contributions.
Are these intended to be the same thing? If not, could one of
them be renamed?
Simon
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <[email protected]>
Sent: Monday, February 09, 2009 3:53 PM
To: <[email protected]>
Subject: Travel sample directory structure reorganization
I have reorganized the directory structure in sandbox/travelsample
so that the code structure is the same as for the rest of Tuscany:
src/main/java/xxx Java code for package xxx
src/main/resources other files: composite, WSDL, BPEL, HTML, CSS,
XSD
src/main/resources/META-INF sca-contribution.xml
src/main/webapp chapter 8 already had this
src/test/java/xxx test Java code for package xxx
src/test/resources other test files: composite, etc.
I am able to do a complete top-level build from the travelsample
directory. (I needed to comment out a few lines for this.)
It is possible that there could be one or two small fix-ups
still needed (e.g., in some pom files).
I have also changed all the dependency pom version numbers to 1.4.
I'm planning a few more changes soon:
Use 1.0-SNAPSHOT instead of 1.4 for the travelsample version number
Change maven repo artifact names to travelsample-xxxx
Fix up the ant scripts that run the node launchers
Change the "scatours" package names to "com.tuscanyscatours"
(I'll hold off on this for a day or two to give people a chance
to consider this and maybe make other suggestions... or offer
to help :-)
Simon
