On Feb 6, 2008, at 1:50 AM, Alin Dreghiciu wrote: > "Facilitate OSGi developer, framework independent"
> 3. deploy: Well, Pax Runner. Make it suitable not only for development > but also for production use. e.g. ServiceMix4 goes OSGi. Shouldn't be > nice for them to allow users to pick the runtime framework? I would like to see a Pax Assembler that has the same advantages of Pax Runner but instead builds a directory or assembly that contains all the referenced/dependent bundles and scripts/configuration that will start them at startup. Then I could use Pax to build my app and then deploy as an entire application using the container of my choice. Right now as a developer I have to reproduce all of the work that PAX does to determine dependencies at assembly time. I would also like to see this extended to other enviroments like webstart or webapps. It would be nice to be able to have a single app and then say I want this to be a standalone app with felix underneath. I want to embed equinox in a war file or I want to run osgi in a webstart app. And other cases like embedded deployments would also be interesting. The last piece that would be nice to consider is native code building and bundling and how they would work in the above deployment scenarios. Thanks for all the hard work on PAX and I'm looking forward to seeing where it can go from here! Matt Brozowski ___________________________________________________________________________ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The OpenNMS Group, Inc. Fax: +1 503 961 7746 Email: [EMAIL PROTECTED] URL: http://www.opennms.com _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
