[snip]

> I you are willing to be a guinea pig ... errr I mean tester ...

Oink, Oink ...
yep I'll try it out.


> I can upload the classes and tack on a basic script to launch it
> like this. However I can't guarentee it works ;)
>
> For a long term solution it would be best to wait for Leos JMX
> manager to get a good client (hint hint) and then we could safely
> and securely manage the servers that way.
>
> > - also, a while ago we
> > mentioned the potential for non-expanded sar files - anything changing
> > that impacts these two areas ?
>
> It is about a 20 line change.


What .. write code!!
You know I don't do anything as concrete as that!


> Essentially you goto DefaultSarDeployer and remove expand() function and
> reimplement
>
> URL[] getClassPath( final File file )
>
> to create URLs of the form
>
> jar:file:/path/to/my.sar!/blocks/foo.bar
> rather than
> file:/path/to/my/blocks/foo.bar
>
> If it is a feature you want then I will try to do it next time I get the
> chance. The main reason I haven't done it is because some server rely on
> things being expanded to filesystem and I wasn't sure how to
> handle this. I thought about adding an optional ant script to do "install"
> things or maybe some other descriptor. Really not sure atm.

The main objective I have is to keep end-user fingers away from things they
don't need to know about.  The perfect scenario is to be able to execute the
phases you mentioned earlier:

  installing:

    1. extract only the files that need to be exposed in the file system
       for (a) configuration files (b) system resources
       possibly involving a plugged-in expander

    2. establish a valid default configuration (possibly involving the
       launching of a plugged-in human interface/plug-in validation
       class - i.e. the validation class could be declared in the bar
       config)

  deployment:

    1. enable the declaration of the external controller (through
       configuration setting - so that I can easily integrate control
       over a block lifecycle independently of the block developer -
       i.e. without going to the code)
       - could be JMX
       - could be a dedicated combined Phoenix lifecycle
         interceptor/event-listener

Enough of my wish-list - back to other stuff !

Cheers, Steve.


> Cheers,
>
> Pete
>
> *-----------------------------------------------------*
> | "Faced with the choice between changing one's mind, |
> | and proving that there is no need to do so - almost |
> | everyone gets busy on the proof."                   |
> |              - John Kenneth Galbraith               |
> *-----------------------------------------------------*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to