Simon Nash wrote:
Simon Laws wrote:
Hi Simon
I ran this over the weekend and the full app launcher works ok for me
with payment-java-policy and creditcard-payment-jaxb-policy in place
when run from Eclipse. Am struggling to get this to run from ant at
the moment so am looking into that.
What version of Tuscany did you run with?. There were some changes
that went into 1.x/1.6 to make this work.
Regards
Simon
I was using 1.5.1 with the ant build, in the hope that users would be
able to get this sample to run on a released version of Tuscany. I also
tried using 1.6-SNAPSHOT with the maven build (this is the Tuscany version
currently specified in the pom files) and I got the same failure. AFAICT
the 1.6-SNAPSHOT files that I am using were created on December 15, 2009.
Does this level have the fix that's needed to make this sample work?
I'm downloading the 1.6 branch now and I will try to a) build the 1.6
branch b) build the travel sample using my 1.6 build and c) run the
fullapp launcher in combination with my 1.6 build. I'll report back
with my results.
I tried this and the policy version of fullapp is working OK for me from a
maven build of the travel sample pulling in a developer build of the current
1.6 branch.
This also works for me with ant run and a binary distro built from the
1.6 branch, but I needed to rename one of the jars produced by the maven build
of the travel sample to get ant run to work (this might be the issue with
ant run that you are seeing). I renamed
launchers/common/target/scatours-launcher-common-1.0-SNAPSHOT.jar
to
launchers/common/target/scatours-launcher-common.jar
This difference between the output of the ant and maven builds is related
to TUSCANY-3422. It would be possible to change the ant scripts to recognize
the versioned filename for this jar produced by the maven build, but a better
approach might be to implement the restructure suggested in TUSCANY-3422.
Simon
Assuming I can get the fullapp scenario to work using a local 1.6 build,
the question still remains whether the travel sample should support the
latest Tuscany release or require a developer build as a prereq. As this
is supposed to be a user-oriented sample, my preference is for it to
support the latest Tuscany release "out of the box". If there are features
that need a developer build, I think these should be clearly flagged and
should require some explicit user action to include them.
Simon
