On Nov 22, 2007 2:21 PM, David Donohue <[EMAIL PROTECTED]> wrote: > Hello, and thanks for Pax! > Fascinating project, this Pax. I am new to Maven and Pax.
Thanks. But Maven is not the answer to your prayers. It has many other quirks that can be frustrating at times and occasionally stop you dead in your tracks. In the back of everyone's head there is this Utopian Build System, that solves all of this. First, also check non-advertised docs; http://www.ops4j.org/projects/pax/wicket > What steps do I have to take to add working Jetty + Pax Wicket Service > in my app? You will need the Pax Web bundle, the Pax Wicket bundle and write code according to the programming model in Pax Wicket. If you do that, it will be possible for you to upgrade parts of the application without taking down the entire system. Pax Wicket uses ContentSources and ContentAggregators to "wire" the Wicket UI together in a dynamic way. It means that you in runtime can actually move content from one page to another and many other tricks. Pax Wicket contains a simple example. > How do I write a bundle that makes use of the Pax Wicket services and > begins to build a plug-innable web application? 1. Get the ready-made parts, Pax Web and Pax Wicket. I think you need Config Admin service as well, which Pax doesn't have an implementation of. Should be able to use any one out there. Pax Logging will also be needed. 2. Understand Pax Runner, or if you prefer Pax Construct which will use Pax Runner automatically. This will make it easy to test your stuff on the 3 famous open source OSGi platforms, without getting caught up in each platform's quirks to get running, and how to install bundles in them. 3. Get the department store sample to run. 4. Plan your basic platform. You will need to define some useful 'extension points' and those are implemented as ContentAggregators. 5. Create your ContentSource plugins in separate bundles. Either their Activator wires them via the Config Admin service or use the Pax ConfMan propsloader to allow you to define the wiring in properties files. > What is the preferred way to package and deploy my project into a > runable, distributable application? I am not sure. Probably a zip file, containing your bundles, Pax Runner and a small script that uses Pax Runner to start the bundles. > Is there a way that I can use the plugin.xml file to declare extension > points and extensions, as I did in my Equinox prototype app? You could use extension points by installing a couple of bundles from Equinox. However, I wouldn't recommend it. It couples the bundles very tightly. Using "native OSGi" is probably a better idea. If you insist on simpler handling of components, then take a look at the Declarative Services spec in OSGi R4 Compendium. There are many other alternatives. Personally, I am not fond of anyone of them. Hope this helps. _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
