Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 41580 invoked from network); 25 Jan 2002 22:07:54 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Jan 2002 22:07:54 -0000 Received: (qmail 9952 invoked by uid 97); 25 Jan 2002 22:07:52 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 9876 invoked by uid 97); 25 Jan 2002 22:07:51 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 9803 invoked from network); 25 Jan 2002 22:07:51 -0000 Message-Id: <200201252207.g0PM7n418309@mail012.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Avalon Developers List" Subject: Re: Visibility of assembly.xml in deployed applications Date: Sat, 26 Jan 2002 08:47:45 +1100 X-Mailer: KMail [version 1.3.2] References: <60098A15DB40D511B69F00508B8B84BFD7DDA3@hoth.whitehill.net> In-Reply-To: <60098A15DB40D511B69F00508B8B84BFD7DDA3@hoth.whitehill.net> X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 24 Jan 2002 02:02, Fred Yeomans wrote: > Some time back when I first started looking at Phoenix, the assembly.xml > file was visible after a SAR was deployed. After the deployment file > structure was changed, however, this ceased to be the case. I am curious as > to the reasons behind this? > > The reason I ask is that my application consists of a number of blocks > which communicate either directly, via RMI, or via JMS message queues. This > allows the blocks to reside in the same or different JVMs, or on different > machines. The JMS interface is implemented by blocks which serve as > proxies, making it so that a client block does not need to know whether it > is talking directly to the server block, or to the JMS queue. I was able to > change the deployment structure without "redeploying" by editing the > assembly.xml file. I have reverted this to the old behaviour and it will now extract assembly.xml. The original reason for not extracting it was because we wanted to try out an experimental idea that would not extract SARs at all if not needed. So you should grab a nightly build or download from CVS to get this functionality again. -- Cheers, Pete *------------------------------------------------------* | "Computers are useless. They can only give you | | answers." - Pablo Picasso | *------------------------------------------------------* -- To unsubscribe, e-mail: For additional commands, e-mail: