You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Scott Kurz <sk...@gmail.com> on 2011/06/23 17:54:05 UTC
where to put a (2.x) two-Contribution test of binding-sca-runtime?
Quick question:
I noticed a bug on the path used by binding-sca-runtime when doing a
cross-classloader (e.g. cross-Contribution) copy.
Not sure how important it is to people to keep the tests structured
relatively simply...
I'm thinking I'll add the test to the binding-sca-runtime module and
just check-in a couple contribution JARs as source, since that's
easier to me than trying to build/copy/package things in two JARs.
(I see some modules e.g. 'contribution' checking in JARs as source).
Kind of ugly not to have the Java as source though...
Does anyone have a better suggestion on where to add a test for this case?
Thanks,
Scott
Re: where to put a (2.x) two-Contribution test of binding-sca-runtime?
Posted by Simon Laws <si...@googlemail.com>.
On Thu, Jun 23, 2011 at 4:54 PM, Scott Kurz <sk...@gmail.com> wrote:
> Quick question:
>
> I noticed a bug on the path used by binding-sca-runtime when doing a
> cross-classloader (e.g. cross-Contribution) copy.
>
> Not sure how important it is to people to keep the tests structured
> relatively simply...
>
> I'm thinking I'll add the test to the binding-sca-runtime module and
> just check-in a couple contribution JARs as source, since that's
> easier to me than trying to build/copy/package things in two JARs.
> (I see some modules e.g. 'contribution' checking in JARs as source).
>
> Kind of ugly not to have the Java as source though...
>
> Does anyone have a better suggestion on where to add a test for this case?
>
> Thanks,
> Scott
>
We do have examples where contribution jars are held in svn but
generally they are built from modules that are elsewhere in svn. It's
useful in case we need to rebuild the contributions. Is that the case
here? Is the source somewhere in svn?
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: where to put a (2.x) two-Contribution test of binding-sca-runtime?
Posted by ant elder <an...@gmail.com>.
Its fine to have a contribution jar added to the binding-sca-runtime
module but the source for any Java classes in there MUST be available
somewhere in the Tuscany SVN. So if its not using classes from an
existing sample or test then you'll need to make one. Its fine if the
contribution has something like extra or modified .composite, wsdl,
xsd or other human readable files as it easy enough to look in the
contribution jar to view or update those, but thats too hard .class
files.
...ant
On Thu, Jun 23, 2011 at 4:54 PM, Scott Kurz <sk...@gmail.com> wrote:
> Quick question:
>
> I noticed a bug on the path used by binding-sca-runtime when doing a
> cross-classloader (e.g. cross-Contribution) copy.
>
> Not sure how important it is to people to keep the tests structured
> relatively simply...
>
> I'm thinking I'll add the test to the binding-sca-runtime module and
> just check-in a couple contribution JARs as source, since that's
> easier to me than trying to build/copy/package things in two JARs.
> (I see some modules e.g. 'contribution' checking in JARs as source).
>
> Kind of ugly not to have the Java as source though...
>
> Does anyone have a better suggestion on where to add a test for this case?
>
> Thanks,
> Scott
>
Re: where to put a (2.x) two-Contribution test of binding-sca-runtime?
Posted by Mike Edwards <mi...@gmail.com>.
Scott,
I think that it is best if you put the sources of the Contributions into some separate modules that
are built separately to create Contribution ZIPs that are then used as dependencies by the tests.
This is effectively what we do in the OASIS testcases, where there are loads of Contribution ZIPs
that are then used by the testcases thenmselves.
You must be able to see how the Contributions are built from sources - and be able to change the
Contributions in the case where errors or updates need dealing with.
This may even be desirable from a test perspective in that sharing of contributions between
different testcases may be possible, reducing the overall pile of materials - this too is done in
the OASIS tests and makes a big impact on the number of artifacts required, especially in the
Assembly testcases.
Yours, Mike.
PS. Don't feel inhibited to beg steal or borrow any of the OASIS materials. They can be freely
reused and contain some entertaining artifacts at the level of both Composites and Implementations.
On 23/06/2011 16:54, Scott Kurz wrote:
> Quick question:
>
> I noticed a bug on the path used by binding-sca-runtime when doing a
> cross-classloader (e.g. cross-Contribution) copy.
>
> Not sure how important it is to people to keep the tests structured
> relatively simply...
>
> I'm thinking I'll add the test to the binding-sca-runtime module and
> just check-in a couple contribution JARs as source, since that's
> easier to me than trying to build/copy/package things in two JARs.
> (I see some modules e.g. 'contribution' checking in JARs as source).
>
> Kind of ugly not to have the Java as source though...
>
> Does anyone have a better suggestion on where to add a test for this case?
>
> Thanks,
> Scott
>