Jeff McAffer wrote:
I think it is crucial that bundles run out of the box and not require
you to chase other bundles to get it to work. This first level
experience is
quite important. Just doubling the number of bundles because you might
have
to stop a bundle does not like the right trade off to me.
In the OSGi build, all the implementations care the interfaces they
implement
so they always run out of the box so setup is simplified.
It is important to simplify consumption. Agreed. However, personally I
don't find this to be a motivating argument here. In our experience writing
large OSGi-based systems it is relatively rare that a bundle implementation
is self-contained so putting the API with the impl still does not give you
just one bundle you can install and run.
Instead I would prefer to see people use a comprehensive provisioning
mechanism (insert shameless plug for p2)
chuckle :)
rather than sacrifice architecture
or flexibility. This is not to say that putting API with impl is wrong,
just that the "out of the box" argument does not work for me.
I think there's another issue that even a comprehensive provisioning
mechanism (also like that used in newton ;) ) can't solve and that's
when the export-uses graph gets so tangled that it's impossible to
resolve all bundles in the jvm at the same time. Thankfully this problem
raises its head /very/ infrequently - I've never found it yet in any
practical situation but always worth knowing about the beasties that can
be found out in the deep ocean.
If each developer /tries/ to limit the amount of graph they couple their
client code to it helps reduce the risk of getting to tangled up in the
reafs just out side of port.
(Must be the end of the day again, I'm rambling)
Regards,
Dave
Jeff
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________________________________
This email has been scanned by both Message Labs and Paremus internal systems
for viruses and inappropriate attachments. Email suspected of carrying a virus
payload or inappropriate attachment will not be delivered to you, and the
sender will receive an appropriate warning notice.
_______________________________________________________________________
_______________________________________________________________________
Paremus Limited. Registered in England
No. 4181472
Registered Office: 22-24 Broad Street, Wokingham, Berks RG40 1BA
Postal Address: 107-111 Fleet Street, London, EC4A 2AB
The information transmitted is intended only for the person(s) or entity to
which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.
If you received this in error, please contact the sender and delete the
material from any computer.
_______________________________________________________________________
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
