> > OSGi *is* tricky to get right, that much is true. > > But... You need the right tools to get there, and it would seem that Spring > simply doesn't have what it takes, that's hardly OSGi's fault though!
I don't know.. it's easy to blame the framework but then, does the framework make things easy to get right? Is the framework fragile, does it fail easily or not lend it's self to guiding people on how to use it? These are very subtle questions. You know, the Spring crowd has some of the most brilliant minds in the industry. Rod was committed to OSGi very early on. I'd say if those guys can't get it right what hope do the rest of us have (wait a minute, didn't Dick use this argument in another thread in which I called him out???). > > Have a talk from OSGi & Eclipse specialist Neil Bartlett at JavaWUG, it's > rather good. He explains matters more clearly than I could: > http://skillsmatter.com/podcast/java-jee/scala-modules No voice. The wrong code checks for null but then does nothing with it. So the code is wrong 'cos it should throw the null pointer exception, same with type safety, handle it or throw it. that is the throw don't catch mantra.. no? ok, we can nit pick at the code but without voice I'm hard pressed to guess at the OSGi message here. Kirk -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
