When jJOS Bytecode meets the BCNI, a virtual machine can always install a platform-specific, BCNI-compatible factory first, before calling the init class. Only one BCNI-compatible factory can be installed, with setFactory(). Factory.setFactory( new CustomFactory() ); For the latest binary and source distribution of jJOS bytecode, see also the JOSDistribution1e article on JOS Wiki. ----- It's a start. Other system-wide classes might be obtained though BCNI eventually. The static BCNI factory should be static, as in one object per virtual machine, rather than one object per class loader. ----- How is JOS CVS updated with jJOS bytecode w/ BCNI? I think all the bytecode should be organized in a bytecode directory, like this: JJOS/bytecode JJOS/bytecode/jos JJOS/bytecode/jos/host JJOS/bytecode/jos/host/driver JJOS/bytecode/jos/i386 JJOS/bytecode/jos/i386/driver JJOS/bytecode/jos/platform JJOS/bytecode/jos/platform/event JJOS/bytecode/jos/system JJOS/bytecode/jos/util JJOS/bytecode/org/jos/bcni1a There is no arch/host or arch/i386 directory needed to re-implement the jos.platform.driver package. Since the bytecode is no longer "common", it should not be called JJOS/common/bytecode. _______________________________________________ Kernel maillist - [EMAIL PROTECTED] http://jos.org/mailman/listinfo/kernel
