Hi and thanks for response. > >>> would normally be added to the SAR-INF/lib directory and your application redeployed
In this case I have to teach a customer how to build sar... Requires a lot of documentation... What are the options of adding new block (in jar) file to already deployed Phoenix application. I see the following choices: 1. add it to phoenix/lib - this will not always work 2. look for some location where this jar can be found (e.g. inside SAR-INF etc). Other ideas? > p.s. There is nothing to stop you putting in place a block that does > active loading of pluggable components. Can not say anything before I've tried this, but as I see it, this way new components will not be phoenix blocks any more and it will not be possible to manage them via assembly.xml and config.xml. Andrei ----- Original Message ----- From: "Stephen McConnell" <[EMAIL PROTECTED]> To: "Avalon-Phoenix Developers List" <[email protected]> Sent: Wednesday, June 12, 2002 1:30 AM Subject: Re: How to add new blocks (jars) to existing phoenix application (sar) > > > Stephen McConnell wrote: > > > > > > > Nicola Ken Barozzi wrote: > > > >> > >> > >> Stephen McConnell wrote: > >> > >>> > >>> > >>> Andrei Ivanov wrote: > >>> > >>>> Hi, > >>>> suppose I have Phoenix application in sar file. Suppose someone > >>>> else can > >>>> write new block for my application (and add it by modifying > >>>> assembly.xml and > >>>> config.xml) > >>>> The question is: how this new block (extra jar) can be included into > >>>> existing application (if not in sar, where new block can be placed > >>>> under > >>>> SAR-INF or under phoenix-lib, latter imho is not good)? > >>>> > >>>> Andrei > >>>> > >>> > >>> The new block (preumably packaged as a jar file) would normally be > >>> added to the SAR-INF/lib directory and your application redeployed > >>> as a new .sar file containing the additional .jar file. > >> > >> > >> > >> Which is not really plug 'n pray... > >> > >> If I want to augment the running .sar without messing with it? > >> IE: any proposals? > > > > > > > > Ohh ... hot blocks! > > Not available in the current Phoenix version - but very desirable. > > Someone was talking/working on that recently - could be a good idea to > > check the Phoenix mail archive. I can't remember who it was but I'm > > sure it was sometime in the last 4-6 weeks. > > > > Cheers, Steve. > > > p.s. There is nothing to stop you putting in place a block that does > active loading of pluggable components. > > SJM > > -- > > Stephen J. McConnell > > OSM SARL > digital products for a global economy > mailto:[EMAIL PROTECTED] > http://www.osm.net > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
