avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Phoenix minimal size
Date Thu, 08 May 2003 18:42:13 GMT

Peter, Leo, David - Thanks all that will help in this.
We are prepared to put in a fair amount of work, as the choice is to redo from 
scratch, which neither of us developers believe in.


On Wednesday 07 May 2003 11:03 am, Leo Simons wrote:
> Niclas Hedhman wrote:
> > I am evaluating to drop Phoenix into an embedded environment, since it
> > does exactly what I need, but I don't have plenty of memory to fool
> > around with. The idea is to replace Xerces with a small XML parser and
> > strip out all the deprecated code amd code that will not be used as well.
> >
> > Looking at the dist/lib directory of Phoenix, I see a total of 3MB+, of
> > which Xalan/Xerces is a very large contributor.
> >
> > Them aside, how much of the remaining JARs are required for Phoenix
> > itself to run? I assume all is not required.
> you can loose a lot of stuff. Browse the source code for NullXXX.java or
> NoopXXX.java. Add those to kernel.xml instead of defaults. You can
> disable JMX this way, for example, and remove most of the stuff in
> components/manager. Several other classes can go, too, like the
> beanshell kernel, containerkit/demo, etc. You can probably also disable
> most monitoring and instrumentation. You might be able to replace the
> launcher/CLIMain stuff with something simpler and more barebone.
> > What is the jing.jar and isolax.jar, since they are also rather large,
> > and seems to be from somewhere else.
> they're used for configuration management IIRC. I think there's a Noop
> version of that.
> looking at the current cvs (find -name *.jar), some stuff which you
> probably want to remove
> xerces & xalan (replaced by something minimal, that is)
> altrmi
> excalibur-cli
> excalibur-instrument-manager
> isorelax
> jing
> cli
> log4j
> mx4j
> qdox
> which might enable you to get close to a 1mb total of jars for a
> functional phoenix. You might be able to get a little smaller than that,
> but this is not something phoenix was really designed or optimized for,
> so it'd be more work.
> good luck, and please let us know the results :D
> cheers!
> - Leo
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message