> From: Andrzej Jan Taramina [mailto:[EMAIL PROTECTED]] > > I was wondering how suitable Avalon (and possibly Phoenix) > might be for use > on embedded Java processors?
Avalon Framework is very low weight, and it can work in just about any environment. However, most of our more functional containers are not friendly to the Embedded environment. That said, we have an eye on the embedded arena for Avalon 5. > These environments typically have rather severe memory footprint and > processor speed contraints, and may be missing other key > functionality (eg. > dynamic classloading can be problematic, without disk storage). As long as the JAR can remain in memory, we can access the classes that way. I think we have a "virtual" file system API somewhere. > Would it be possible to pare down Avalon and/or Phoenix to > run in such > environments? Is there any prior work in this area? Caveats? Effort? We would probably have to start with Tweety (in Excalibur) and add in what you need. In Avalon 5, we will be able to create a container that works in the embedded arena. Most likely, all logging would be turned off, since as you say disk access is an issue and logging is of dubious benefit on a PDA. Using a NullLogger will disable all logging. > Much appreciate any advice/insight the group can offer on the > feasibility of > such a project... It is feasible, but it depends on how much funcationality you need. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
