"Steven E. Harris" <[EMAIL PROTECTED]> writes:
> <!--<ipojoMetadata>metadata.xml</ipojoMetadata>-->
Ah, that has to be
<iPOJOMetadata>metadata.xml</iPOJOMetadata>
^^^^ ^^^^
Now, I'm trying to understand how to arrange for iPOJO to provide a
ManagedServiceFactory on my behalf. The "How to use iPOJO factories"
document¹ says:
How to use the ManagedServiceFactory to create instances
The principle of the ManagedServiceFactory is the same as the iPOJO
Factory Service. To have further information on it, read the OSGi R4
Compendium - Configuration Admin chapter.
There's earlier discussion of the "factory" attribute on the iPOJO
"component" element. If I have a class "Foo" that I want to be exposed
as the component type for a factory to create, is the following
sufficient?
<?xml version="1.0" encoding="UTF-8"?>
<iPOJO>
<component className="Foo" factory="foo.factory"/>
</iPOJO>
Also, I noticed that the iPOJO plugin creates directives by inspecting
class "Foo" above, and mentioning its various member variables and
their types. If I don't want these fields to be manipulated by iPOJO,
can I do anything to disable this behavior. Actually, I'm not really
sure what iPOJO is going to do with that member-related information;
I'm just fearing the worst.
Footnotes:
¹ http://cwiki.apache.org/FELIX/how-to-use-ipojo-factories.html
--
Steven E. Harris
