As for the docs, I think they really are outdated if the following is any indication:
$ pwd
/Users/gnormington/dev/eclipse/org.eclipse.gemini.blueprint/docs/src/docbkx
[localhost:docbkx master]$ ack update-strategy
reference/compendium/compendium.xml
195: one can configure <literal>managed-properties</literal> element to receive configuration updates through the <literal>update-strategy</literal>
231: <osgix:managed-properties persistent-id="labX" update-strategy="container-managed"/>
236: <osgix:managed-properties persistent-id="labY" update-strategy="bean-managed" update-method="updateCallback"/>
252: <entry><literal>update-strategy</literal></entry>
381: <entry>update-strategy</entry>
418: update-strategy="bean-managed"
469: Finally, due to the specified <literal>update-strategy</literal>, any updates executed to each CM configuration will cause the
Would you be able to provide a correction to the docs as a separate patch which you could then base the patch for the new docs upon?
Regards,
Glyn
Hi Glyn
I've started looking into the documentation sources and found them a little bit outdated. It seems that the managed-service-factory is described as it was in schema spring-osgi-compendium-1.2.xsd while even in the latest release (1.0.2) the latest version is spring-osgi-compendium-2.0.xsd or gemini-blueprint-compendium-1.0.xsd. One of the differences is that update-strategy attribute in managed-service-factory which is mentioned in the documentation was replaced by autowire-on-update attribute in the latest schema. Moreover, I've checked that the online documentation and the documentation which ships with 1.0.2 release has the same outdated information. As my new attribute's behavior somehow depends on autowire-on-update I need it to be present in the docs :) Could you please check whether the docs are really outdated or am I missing something?
_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev