You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Mike Edwards <mi...@gmail.com> on 2008/12/05 22:06:43 UTC
Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca:
distribution/core/pom.xml modules/pom.xml
Raymond Feng wrote:
> Hi,
>
> I added host-http to get the implementation-node-runtime compiled. I
> agree with you that we should probably refactor the web application part
> out of implementation-node-runtime.
>
> I'm starting to clean up the interface models. The interface-wsdl-???
> modules have quite a lot references to the base interface module. I
> added the interface-wsdl-??? to take advantage of the Eclipse
> refactoring capability. On the other hand, interface.wsdl is part of the
> SCA assembly model. I think it would be nice to bring it up for the
> first milestone of 2.0 release as Luciano has proposed. I'll give more
> details in that thread.
>
> Thanks,
> Raymond
>
Folks,
I've been doing some work quietly to get the Web services related modules working in Trunk
- not putting them into any main build or anything, but enough to get the following running:
<interface-wsdl/>
<binding.ws/>
My reason for doing this is that I am building a testcase suite for the OASIS Specifications and I
need to drive them via an interoperable binding (ie binding.sca will not do...).
This has involved the following modules:
binding-ws
binding-ws-axis2
binding-ws-wsdlgen
binding-ws-xml
databinding-axiom
databinding-jaxb-axiom
node-impl
policy
policy-security
policy-xml
policy-xml-ws
xsd-xml
So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies and OSGi MANIFEST files,
but in a few cases, the 2.0 APIs are different from the 1.x APIs and some changes are needed - this
often affects testcases more than mainline module code. One lesson from this is that I think we
should consider creating a tests-utils module to contain some of the sequences that tests seem to
need commonly - and to hide the testcase code from changes in the base platform.
Yours, Mike.
Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Raymond Feng <en...@gmail.com>.
It's great to know that you are bringing up the binding.ws for 2.x. Would
you like to add these additional modules under a profile in modules/pom.xml?
This way, we can try to build and load them into Eclipse to see the
progress. A few of us have been attacking the OSGi puzzles for a while and
I'm definitely willing to help.
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <mi...@gmail.com>
Sent: Friday, December 05, 2008 1:06 PM
To: <de...@tuscany.apache.org>
Subject: Activities in Trunk - was: svn commit: r723136 - in
/tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
> Raymond Feng wrote:
>> Hi,
>> I added host-http to get the implementation-node-runtime compiled. I
>> agree with you that we should probably refactor the web application part
>> out of implementation-node-runtime.
>> I'm starting to clean up the interface models. The interface-wsdl-???
>> modules have quite a lot references to the base interface module. I added
>> the interface-wsdl-??? to take advantage of the Eclipse refactoring
>> capability. On the other hand, interface.wsdl is part of the SCA assembly
>> model. I think it would be nice to bring it up for the first milestone of
>> 2.0 release as Luciano has proposed. I'll give more details in that
>> thread.
>> Thanks,
>> Raymond
>>
> Folks,
>
> I've been doing some work quietly to get the Web services related modules
> working in Trunk
> - not putting them into any main build or anything, but enough to get the
> following running:
>
> <interface-wsdl/>
> <binding.ws/>
>
> My reason for doing this is that I am building a testcase suite for the
> OASIS Specifications and I need to drive them via an interoperable binding
> (ie binding.sca will not do...).
>
> This has involved the following modules:
>
> binding-ws
> binding-ws-axis2
> binding-ws-wsdlgen
> binding-ws-xml
>
> databinding-axiom
> databinding-jaxb-axiom
>
> node-impl
>
> policy
> policy-security
> policy-xml
> policy-xml-ws
>
> xsd-xml
>
> So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies
> and OSGi MANIFEST files, but in a few cases, the 2.0 APIs are different
> from the 1.x APIs and some changes are needed - this often affects
> testcases more than mainline module code. One lesson from this is that I
> think we should consider creating a tests-utils module to contain some of
> the sequences that tests seem to need commonly - and to hide the testcase
> code from changes in the base platform.
>
>
> Yours, Mike.
Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I have fixed most of the compilation errors and OSGi access violations for
the binding.ws related modules. The changes were committed under r724568.
There is only access violation left: EndpointReferenceImpl.
Description Resource Path Location Type
Access restriction: The constructor EndpointReferenceImpl(String) is not
accessible due to restriction on required project tuscany-coreAxis2ServiceProvider.java tuscany-binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2 line716 Java Problem
Access restriction: The type EndpointReferenceImpl is not accessible due to
restriction on required project tuscany-core Axis2ServiceProvider.javatuscany-binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2 line83 Java Problem
EndpointReferenceImpl is not from the SPI package. We need to use a factory
such as RuntimeAssemblyFactory to create the EndpointReference instead of
directly referencing the implementation class.
I also added a maven profile named "ws" to contain the extra binding.ws
related modules. You can run mvn -Peclipse,ws to include these projects into
Eclipse. See r724614.
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <mi...@gmail.com>
Sent: Friday, December 05, 2008 1:06 PM
To: <de...@tuscany.apache.org>
Subject: Activities in Trunk - was: svn commit: r723136 - in
/tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
> Raymond Feng wrote:
>> Hi,
>> I added host-http to get the implementation-node-runtime compiled. I
>> agree with you that we should probably refactor the web application part
>> out of implementation-node-runtime.
>> I'm starting to clean up the interface models. The interface-wsdl-???
>> modules have quite a lot references to the base interface module. I added
>> the interface-wsdl-??? to take advantage of the Eclipse refactoring
>> capability. On the other hand, interface.wsdl is part of the SCA assembly
>> model. I think it would be nice to bring it up for the first milestone of
>> 2.0 release as Luciano has proposed. I'll give more details in that
>> thread.
>> Thanks,
>> Raymond
>>
> Folks,
>
> I've been doing some work quietly to get the Web services related modules
> working in Trunk
> - not putting them into any main build or anything, but enough to get the
> following running:
>
> <interface-wsdl/>
> <binding.ws/>
>
> My reason for doing this is that I am building a testcase suite for the
> OASIS Specifications and I need to drive them via an interoperable binding
> (ie binding.sca will not do...).
>
> This has involved the following modules:
>
> binding-ws
> binding-ws-axis2
> binding-ws-wsdlgen
> binding-ws-xml
>
> databinding-axiom
> databinding-jaxb-axiom
>
> node-impl
>
> policy
> policy-security
> policy-xml
> policy-xml-ws
>
> xsd-xml
>
> So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies
> and OSGi MANIFEST files, but in a few cases, the 2.0 APIs are different
> from the 1.x APIs and some changes are needed - this often affects
> testcases more than mainline module code. One lesson from this is that I
> think we should consider creating a tests-utils module to contain some of
> the sequences that tests seem to need commonly - and to hide the testcase
> code from changes in the base platform.
>
>
> Yours, Mike.
Re: Testcase templates? was: Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by ant elder <an...@gmail.com>.
A simple easy way to create a started node, what a great idea ;)
Would be good to add something like this to the API instead of needing a
helper. Maybe we could consider the current node APIs more of an SPI and
create an easy to use client API.
...ant
On Wed, Dec 10, 2008 at 1:48 AM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> It might be a good idea to define a set of templates to shield the test
> cases from the environment-specific node configuration and lifecycle. This
> way, the test cases can be simpler and it's possible to run them with
> different environment (JSE or OSGi) by switching the base.
>
> We could define two modules tuscany-test and tuscany-test-equinox to host
> the base test cases. Other itests can add them as test dependencies in
> pom.xml.
>
> The following code is something I tried locally. But I have some issues
> getting the @BeforeClass and @AfterClass version going as JUNIT tries to run
> these methods even before the static initializer of a class is called.
>
> Thanks,
> Raymond
>
> /**
> * Base Node API based test case
> */
> public abstract class NodeTestCase {
> protected final Logger logger = Logger.getLogger(getClass().getName());
> protected String compositeResource;
> protected Node node;
>
> protected NodeTestCase(String compositeResource) {
> super();
> this.compositeResource = compositeResource;
> }
>
> @Before
> public void setUp() throws Exception {
> try {
> String location =
> ContributionLocationHelper.getContributionLocation(compositeResource);
> Contribution contribution = new Contribution(location, location);
> NodeFactory factory = NodeFactory.newInstance();
> node = factory.createNode(compositeResource, contribution);
> node.start();
> } catch (Exception e) {
> logger.log(Level.SEVERE, e.getMessage(), e);
> throw e;
> }
> }
>
> @After
> public void tearDown() throws Exception {
> if (node != null) {
> node.stop();
> }
> }
> }
>
> --------------------------------------------------
> From: "Mike Edwards" <mi...@gmail.com>
> Sent: Friday, December 05, 2008 1:06 PM
> To: <de...@tuscany.apache.org>
> Subject: Activities in Trunk - was: svn commit: r723136 - in
> /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
>
> [[SNIP]]
>
>
>> So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies
>> and OSGi MANIFEST files, but in a few cases, the 2.0 APIs are different from
>> the 1.x APIs and some changes are needed - this often affects testcases more
>> than mainline module code. One lesson from this is that I think we should
>> consider creating a tests-utils module to contain some of the sequences that
>> tests seem to need commonly - and to hide the testcase code from changes in
>> the base platform.
>>
>>
>> Yours, Mike.
>>
>
>
Testcase templates? was: Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Raymond Feng <en...@gmail.com>.
Hi,
It might be a good idea to define a set of templates to shield the test
cases from the environment-specific node configuration and lifecycle. This
way, the test cases can be simpler and it's possible to run them with
different environment (JSE or OSGi) by switching the base.
We could define two modules tuscany-test and tuscany-test-equinox to host
the base test cases. Other itests can add them as test dependencies in
pom.xml.
The following code is something I tried locally. But I have some issues
getting the @BeforeClass and @AfterClass version going as JUNIT tries to run
these methods even before the static initializer of a class is called.
Thanks,
Raymond
/**
* Base Node API based test case
*/
public abstract class NodeTestCase {
protected final Logger logger = Logger.getLogger(getClass().getName());
protected String compositeResource;
protected Node node;
protected NodeTestCase(String compositeResource) {
super();
this.compositeResource = compositeResource;
}
@Before
public void setUp() throws Exception {
try {
String location =
ContributionLocationHelper.getContributionLocation(compositeResource);
Contribution contribution = new Contribution(location,
location);
NodeFactory factory = NodeFactory.newInstance();
node = factory.createNode(compositeResource, contribution);
node.start();
} catch (Exception e) {
logger.log(Level.SEVERE, e.getMessage(), e);
throw e;
}
}
@After
public void tearDown() throws Exception {
if (node != null) {
node.stop();
}
}
}
--------------------------------------------------
From: "Mike Edwards" <mi...@gmail.com>
Sent: Friday, December 05, 2008 1:06 PM
To: <de...@tuscany.apache.org>
Subject: Activities in Trunk - was: svn commit: r723136 - in
/tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
[[SNIP]]
>
> So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies
> and OSGi MANIFEST files, but in a few cases, the 2.0 APIs are different
> from the 1.x APIs and some changes are needed - this often affects
> testcases more than mainline module code. One lesson from this is that I
> think we should consider creating a tests-utils module to contain some of
> the sequences that tests seem to need commonly - and to hide the testcase
> code from changes in the base platform.
>
>
> Yours, Mike.
Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Giorgio Zoppi <gi...@gmail.com>.
2008/12/5 Luciano Resende <lu...@gmail.com>:
> You are still in both trunks [1][2], we might make use of contrib [3]
> folders during release time
>
> [1] https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/demos/workpool-distributed/
> [2] https://svn.apache.org/repos/asf/tuscany/java/sca/demos/workpool-distributed/
> [3] https://svn.apache.org/repos/asf/tuscany/java/sca/contrib/
That's perfect.
Cheers,
Giorgi.
--
Quiero ser el rayo de sol que cada día te despierta
para hacerte respirar y vivir en me.
"Favola -Moda".
Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Luciano Resende <lu...@gmail.com>.
You are still in both trunks [1][2], we might make use of contrib [3]
folders during release time
[1] https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/demos/workpool-distributed/
[2] https://svn.apache.org/repos/asf/tuscany/java/sca/demos/workpool-distributed/
[3] https://svn.apache.org/repos/asf/tuscany/java/sca/contrib/
On Fri, Dec 5, 2008 at 1:25 PM, Giorgio Zoppi <gi...@apache.org> wrote:
> I see that you're cleaning up the trunk, I kindly request that you
> leave me in the trunk, my old
> workpool-distributed demo, because afaik is still in working progress,
> but i've no other mirror, so
> before cleaning up that code simply ask :). I'd help out but i'm in
> progress to relocate myself abroad from Italy, for now nothing sure.
> Cheers,
> Girogio.
>
> --
> Quiero ser el rayo de sol que cada día te despierta
> para hacerte respirar y vivir en me.
> "Favola -Moda".
>
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
Re: Activities in Trunk - was: svn commit: r723136 - in /tuscany/java/sca: distribution/core/pom.xml modules/pom.xml
Posted by Giorgio Zoppi <gi...@apache.org>.
I see that you're cleaning up the trunk, I kindly request that you
leave me in the trunk, my old
workpool-distributed demo, because afaik is still in working progress,
but i've no other mirror, so
before cleaning up that code simply ask :). I'd help out but i'm in
progress to relocate myself abroad from Italy, for now nothing sure.
Cheers,
Girogio.
--
Quiero ser el rayo de sol que cada día te despierta
para hacerte respirar y vivir en me.
"Favola -Moda".