We use the features (or profiles) to group a list of related modules
together based on the functions they provide. It provides an easy-to-use
dependency for our samples in maven. Then we can build distributions to
assemble a set of features into a downloadable archive.
The feature/profile is very lightweight (just a pom). We can create as many
features as we want. For the Tomcat distribution, it's probably not an
all-for-one thing. Depending on what functions the webapp wants to use, it
can contain various features. For example, if web services are needed, then
the distro has to contain binding.ws. The OSGi stuff can be potentially used
in the webapp too.
We can use the exclusion to exclude some of the stuff or define a new
feature/profile.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Monday, June 01, 2009 12:32 AM
To: <[email protected]>
Subject: Re: svn commit: r779869 -
/tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml
The problem is with the various webapp toolkits like myfaces and
stripes which get included with the tuscany runtime and try to
initialize themselves but the webapps don't have the correct
configuration so that results in spurious errors which make debugging
the tomcat integration harder, but also I think for now at least
(perhaps even always) we shouldn't embed client things like myfaces
and stripes with the tuscany runtime and it would be better to have
each webapp include those themselves if they need. Another issue is
that when using the features other unnecessary dependencies are
getting included like osgi jars.
To be honest I don't understand what the feature approach gives us
here and think its better and clearer and simpler to just use the
explicit dependencies so would really prefer we stick with that for
now.
...ant
On Fri, May 29, 2009 at 7:27 PM, Raymond Feng <[email protected]> wrote:
Can you tell us what modules are failing?
Thanks,
Raymond
--------------------------------------------------
From: <[email protected]>
Sent: Thursday, May 28, 2009 11:51 PM
To: <[email protected]>
Subject: svn commit: r779869 -
/tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml
Author: antelder
Date: Fri May 29 06:51:32 2009
New Revision: 779869
URL: http://svn.apache.org/viewvc?rev=779869&view=rev
Log:
Go back to eplicit dependencies as the features are dragging extra stuff
that doesnt work with the tomcat integration yet and is cauasing
failures
Modified:
tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml
Modified: tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml
URL:
http://svn.apache.org/viewvc/tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml?rev=779869&r1=779868&r2=779869&view=diff
==============================================================================
--- tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml (original)
+++ tuscany/java/sca/distribution/tomcat/tomcat-war/pom.xml Fri May 29
06:51:32 2009
@@ -48,25 +48,13 @@
</dependency>
<dependency>
<groupId>org.apache.tuscany.sca</groupId>
- <artifactId>tuscany-feature-webservice</artifactId>
+ <artifactId>tuscany-implementation-web-runtime</artifactId>
<version>2.0-SNAPSHOT</version>
- <type>pom</type>
- <exclusions>
- <exclusion>
- <groupId>org.apache.tuscany.sca</groupId>
- <artifactId>tuscany-host-jetty</artifactId>
- </exclusion>
- <exclusion>
- <groupId>org.apache.tuscany.sca</groupId>
- <artifactId>tuscany-host-tomcat</artifactId>
- </exclusion>
- </exclusions>
</dependency>
<dependency>
<groupId>org.apache.tuscany.sca</groupId>
- <artifactId>tuscany-feature-webapp</artifactId>
+ <artifactId>tuscany-binding-ws-axis2</artifactId>
<version>2.0-SNAPSHOT</version>
- <type>pom</type>
</dependency>
</dependencies>
