Simon Laws wrote:
On Jan 14, 2008 7:34 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
Have we decided to ship tuscany-host-jetty-1.1-incubating only (without
tuscany-host-tomcat-1.1-incubating) as the fix for TUSCANY-1954? If so, we
need to make sure that all of the ant scripts for modules that references
embedded tomcat should use embedded jetty instead.
Thanks,
Raymond
----- Original Message -----
From: "Simon Nash (JIRA)" <[email protected]>
To: <[email protected]>
Sent: Monday, January 14, 2008 3:56 AM
Subject: [jira] Commented: (TUSCANY-1963) callback-ws-client sample fails
with IndexOutOfBoundsException
(cut)
Hi
We are shipping all modules in the modules dir and the manifest jar but only
host-jetty in the all jar. I.e. host-tomcat, host-webapp, host-jms,
host-jms-activemq are omitted. A mistake on my part for RC1 meant that
host-tomcat was missing from the modules dir.
When we spoke about this earlier today I thought you said that host-tomcat
would be omitted from the manifest jar. If host-tomcat is named in the
manifest jar and is present in modules then I think both host-tomcat and
host-jetty will be available at runtime.
The majority of the ant scripts reference the manifest jar and hence pick up
jetty. The ones that don't are the generated build.xml files use for
generating war files and which reference explicit jars. These look ok so
far.
There were a few other ant scripts that explicitly referenced tomcat.
I am fixing these now (unless someone else has got to this before me).
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
