Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 53438 invoked from network); 25 Aug 2002 14:19:07 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Aug 2002 14:19:07 -0000 Received: (qmail 6628 invoked by uid 97); 25 Aug 2002 14:19:35 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 6572 invoked by uid 97); 25 Aug 2002 14:19:34 -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 6560 invoked by uid 98); 25 Aug 2002 14:19:34 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D68E746.2020907@apache.org> Date: Sun, 25 Aug 2002 16:18:46 +0200 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Avalon Developers List Subject: EOB References: <3D677832.20604@yahoo.com> <200208250354.42938.peter@apache.org> <3D67DE8C.6030901@apache.org> <3D68B067.7050102@yahoo.com> <3D68C1B4.3090807@apache.org> <3D68CE40.2020705@yahoo.com> <3D68D340.7000504@apache.org> <3D68D4D8.5090900@yahoo.com> <3D68DF6F.9020005@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stephen McConnell wrote: >>> >>> I can easily make plain components work in Phoenix, but as you have >>> seen with Merlin, viceversa is not painless. >>> Can Merlin use EOB? >> >> >> >> I dunno, I suggestd to Stephen that he tried it a couple of week ago :-) > > > > EOB includes BlockContext which means that additional meta-info is > required for these components to run inside Merlin. The solution to > this involves the following: > > * add .xtype descriptors to the EOB distribution (these contain the > information describing the depedencies that the EOB blocks have - > including the dependency on the Phoenix BlockContext interface and > Phoneix conterxt keys) > * use the patched version of cornerstone that I'm maintaining (the > patched version also includes the .xtype declarations in order to > solve the same issues and provide convinient deployment profiles for > some of the conterstone components) One point I forgot to mention is that EOB does not publish the components it provides under its manifest If you include a .xtype (i.e. additional info to handle context information) then you could declare this as follows: Name: net/sourceforge/eob/core/DefaultApplicationRepository Avalon: Type If your using blockinfo declarations Merlin will recognize the Phoenix pattern (but this will only work if you component does not reference Phoniex APIs). Name: net/sourceforge/eob/core/DefaultApplicationRepository Avalon-Block: true Cheers, Steve. -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@osm.net http://www.osm.net -- To unsubscribe, e-mail: For additional commands, e-mail: