Hi
Thanks to Tim for committing the 'blog sample'. This sample code makes
use of the blueprint and jndi modules at the moment. The persistence
layer is currently using JDBC - but it should be easy to move it to JPA
if/when that becomes available. The Web component uses the PAX Web
implementation.
I have a couple of questions about the sample:
1) To make it easy to test I have a blog-assembly project which gets all
the dependencies and puts them in a target directory. In the long term
having this as part of the default build might become a bit time
consuming. However - I have left it this way for now because I was
wondering if we could do some automated testing of the sample. Does this
seem reasonable?
2) The assembly currently the Equinox implementation of teh core OSGi
runtime. I could just have easily have used the Felix implementation
(actually more easily) but I think it's reasonable to expect samples to
work on both. I'm not sure how best to ensure this, a second assembly
project called called 'assembly-felix'?
3) As you may have noticed - this is a blog sample :-) I know this is a
long way off but ... would it be reasonable to have a target of using
this to host the Aries blog eventually? It would be nice to be using our
own code.
I will write tutorials and/or documentation which will appear on web
site over the next few weeks. In the interim - here are some very brief
instructions for running the code:
- Install and configure embedded Derby, see here for instructions:
http://db.apache.org/derby/papers/DerbyTut/install_software.html#derby
- Checkout and build the aries samples module
- cd samples/blog-sample/blog-assembly/target
- java org.apache.derby.tools.ij blogDB.sql
- java -jar osgi-3.5.0.v20090520.jar -console
- Point your web browser at
http://localhost:8080/org.apache.aries.samples.blog-servlet
(Don't get too excited - all you can do right now is create an author)
Zoe
