On Wed, May 7, 2008 at 11:39 AM, ant elder <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, May 7, 2008 at 11:29 AM, Simon Laws <[EMAIL PROTECTED]>
> wrote:
>
> <snip>
>
>
>>> This is not quite what we need in the Tomcat case. I shouldn't need to
>>> write
>>> a NodeX.composite file for each webapp as we can say each webapp is a
>>> node,
>>> use the webapp name for the node name, and use the webapps
>>> meta-inf/sca-deployables or sca-contribution.xml to get all the
>>> composites.
>>>
>>> So i guess what i want is for the TuscanyStandardHost to start up an
>>> inial
>>
>>
>> What's the "TuscanyStandardHost"? Does that exist yet?
>>
>
> Its the Tuscany implementation of the Tomcat StandardHost which is what
> gets control when Tomcat starts up and can cerate whatever domains and nodes
> are necessary for the webapps. There is an old one in the runtime-tomcat
> module but i'm right now trying to rewrite it to use all this new domain
> stuff.
>
> ...ant
>
>
I've committed the updates i had for the TuscanyHost in r654467 its still
using just the old "standalone" SCADomain but it enables you to run SCA
webapps without any Tuscany stuff in the web.xml or webapp lib directory.
You point a Tomcat install at a Tuscany binary distribution install with two
updates to the Tomcat configuration:
- in tomcat conf/catalina.properties add the Tuscany Distro lib directory to
the common.loader path, eg:
common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar,/tuscany-sca-2.0-incubating-SNAPSHOT/lib/*.jar
- in tomcat conf/server.xml add the TuscanyHost class name to the localhost
definition, eg:
<Host name="localhost" appBase="webapps"
className="org.apache.tuscany.sca.runtime.tomcat.TuscanyHost"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
Ideally we'd update org.apache.tuscany.sca.runtime.tomcat.TuscanyHost to use
the new distributed domain stuff, but Ive not been able to make much
progress with getting that to work, I'll start a new thread about that.
...ant
