tag:blogger.com,1999:blog-20358640.post6467694675345091712..comments2023-12-28T08:54:07.007-08:00Comments on Eclipse Communication Framework: Remote Services without OSGi bundlesScott Lewishttp://www.blogger.com/profile/15783631237186844143noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-20358640.post-80906342956758100822018-01-05T14:40:04.926-08:002018-01-05T14:40:04.926-08:00Hi eu4,
encapsulation, information hiding, and se...Hi eu4,<br /><br />encapsulation, information hiding, and separation of concerns (modularity) are enforced by the OSGI bundle layer. This provides the tools for scaling up system complexity, and I disagree with you that this doesn't scale. Of course for any large system (particularly a multi-process/distributed system) it's going to require more than just OSGI-provided modularity. That's why OSGI provides additional concepts, such as OSGi services, dynamic composition, subsystems, standardized services, versioning, and others. Even still, if these mechanisms are used poorly (e.g. one bundle/no modularity, no separation of concerns, etc), or not at all then it seems to me that scaling will be limited by complexity.<br /><br />In other words, I think that OSGi provides a number of very useful mechanisms for building solutions that scale, but I don't see how any technology could force people to use those mechanisms appropriately.Scott Lewishttps://www.blogger.com/profile/15783631237186844143noreply@blogger.comtag:blogger.com,1999:blog-20358640.post-20751798974659618192018-01-05T10:17:54.923-08:002018-01-05T10:17:54.923-08:00You have described how the problem of accessing th...You have described how the problem of accessing the internal state of the components is solved (though, in fact, the OOP paradigm solves it just fine). But you haven't described how the problem of growing complexity of the project is solved by OSGi (new components are added, new arrows appear - obviously, this doesn't scale, even given that the internal state of the component is nicely encapsulated). Does OSGi provide a solution to that? Thanks.<br />eu4 console commandshttp://eu4consolecommands.com/noreply@blogger.comtag:blogger.com,1999:blog-20358640.post-72457737297835438222018-01-01T09:44:30.359-08:002018-01-01T09:44:30.359-08:00This appears to be the output from a framework tha...This appears to be the output from a framework that has a bundle agenda.service.simple with a requirement for org.apache.dm version >= 4.4 and < 5.0.0.Scott Lewishttps://www.blogger.com/profile/15783631237186844143noreply@blogger.comtag:blogger.com,1999:blog-20358640.post-63537560936131438372018-01-01T04:58:16.610-08:002018-01-01T04:58:16.610-08:00nable to resolve 2.0: missing requirement [2.0] os...nable to resolve 2.0: missing requirement [2.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.felix.dm)(version>=4.4.0)(!(version>=5.0.0)))<br />, agenda.service.simple-0.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle agenda.service.simple [3]: Unable to resolve 3.0: missing requirement [3.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.felix.dm)(version>=4.4.0)(!(version>=5.0.0)))ark adobe ramphttp://arkconsolecommands.com/1006-2/noreply@blogger.com