"Richard S. Hall" <[EMAIL PROTECTED]> writes: > iPOJO is an evolution that uses byte code manipulation and > inspection to greatly simplify the programming model allowing true > POJO components with deferred service object creation, along with > other interesting features like dynamic service properties.
That all sounds good. I read the iPOJO Tutorial (.07), but that doesn't fully explain lifecycle and reference cardinality topics as addressed by DS, such as the static v. dynamic policy, and whether one can be notified when optional or multiple references come and go (a la the DS bind/unbind methods). In short, is there more documentation available? -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
