i don't have a windows machine to test it but: "What could Pax Runner be doing after the framework starts ": nothing. Its just about _preparing_ everything (downloading bundles/framework itself, write the platform specfic config file) and then it starts the framework by launch a sub process (System.exec). This _might_ confuse the daemon tool perhaps.
Can you proof this with a standalone java app that instantiates another process using System.exec ? (perhaps something "long running" like your browser, or whatever) Tell me/us what you think/experience. Toni On 30.07.2008, at 22:15, Craig Walls wrote: > What could Pax Runner be doing after the framework starts _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
