On Friday 27 April 2007 20:13, Aggelos Mpimpoudis wrote: > So, what is a common practice for reusing existing jars?
As always, one need to know what one is doing. In this case; Beware of SISO principle. S**t in, s**t out. In other words, un-examined 3rd party libraries will sooner or later not do what you expect in an OSGi environment, since the library is probably 'buggy' in many areas which isn't noticed, hence not fixed, in other environments. I have for long been a strong opponent to "Programming by Coincidence" which is the current, long-running trend in our industry. "Let's see if it works..." is a lot more common than "What does the spec say?", and when the specs do exist, they are often too extensive to be complete, hence few corner cases are covered and one need to do the "Let's see if it works...". Worst is when those findings are then used to build new models (and sometimes specs) on top of it. I love OSGi, because the specs are fairly small (each one), developed over a long time, so there are less corner cases, and interoperability is high, not perfect, at least not yet... ;o) And what I fear is that the strong influx of new technologies that OSGi will end up being part of and/or supporting through various mechanisms (SOA/WS, JMX, JMS, and so on), will dilute the quality seen here so far ... Cheers Niclas _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
