Hi Jamie,

I followed your guide and I think it's great :).

Below are some minor comments:

1. You could base your Maven assembly descriptor on the ones that are
avilable in the Apache Felix project. This would eliminate the need to
change the existing sections of config.properties and
startup.properties. See:
http://svn.apache.org/viewvc/karaf/trunk/assembly/src/main/descriptors/unix-bin.xml?revision=958856&view=markup

2. Unfortunately, the released version of Apache Aries
(0.1-incubating) uses Derby DB with disk storage. This complicates
your quide a bit. The version of samples that is available in the
trunk uses in-memory DB. I think that it would make sense to update
your guide when a new version of Aries is released.

3. Warnings related to namespace handlers are ok. All shell commands
are initialized eventually by the Blueprint Extender.

4. Maybe you could also provide a package with a fully working
solution? It would be really useful for those wanting to take the
shortest path possible. :)

Best regards,
  Bartek

2010/7/4 Valentin Mahrwald <[email protected]>:
> Very nice!
>
> I followed it all the way through and except for a small race condition 
> between the blog datasource service registration and the jpa extender 
> creating the EntityManager everything worked like a charm. I am not quite 
> sure what the right fix for the race condition is, I am not sure tweaking 
> start orders would be necessarily any more reliable.
>
> One thought would be that making the references to the sample files 
> hyperlinks would make it a bit more consumable ;)
>
> Thanks for posting this.
>
> Valentin
>
> On 29 Jun 2010, at 21:46, jamie campbell wrote:
>
>> Valentin, Bartoz,
>>
>> Thanks for your helpful comments.  I got things working (I think) and wrote 
>> up a tutorial based on the adventure, at 
>> http://parit.ca/documentation/tutorials/apache/aries/openjpa-karaf-aries-derby-blog-sample
>>  .. it's an unformatted plain text monstrosity, but, hopefully has some 
>> useful information for folks to reference in future.
>>
>> Part of what it includes is a shell command implementing bundle.  I got kind 
>> of stuck on what namespace to use for it.  I didn't want to use 
>> org.apache.aries.samples.blog because that would imply that it was apache 
>> endorsed.  And I didn't want to use a namespace that was too obscure to 
>> clearly connect to the fact that it DOES provide functionality for that 
>> namespace.  So I went with org.parit.aries.samples.blog.  If that namespace 
>> is still too close for comfort, I can take another try at a different name, 
>> and am open to suggestions :)
>>
>> -Jamie
>
>

Reply via email to