Hi David On 05/15/2012 08:41 AM, David Bosschaert wrote: > Hi Thomas, > > I made the OSGi subsystem section in AS7 point to JBOSGI > documentation wiki as it contained pretty much all of the > documentation needed. > > I had a look at the JBOSGI docs at > https://docs.jboss.org/author/display/JBOSGI/JBoss+OSGi+Home and had > a few thoughts, just thought I'd run them by you before changing > anything... > > * The Getting Started page focuses on the JBOSGi installer and > obtaining JBoss OSGi that way. I think it should focus on pure AS7 > where it mention that the AS7 installer can be used to obtain extra > functionality, but I think people should realize that no additional > download is needed to obtain JBoss OSGI... We expect to have a faster release cycle than AS7. In future the jbosgi installer can be used to update the osgi components in a given AS7 community release. We would update our binaries but not any of the AS/integration code. The jbosgi examples demonstrate/document the scope of supported functionality, which is the second aspect of an jbosgi release. The third is a snapshot of documentation. > > * The bundle deployment section on the getting started page needs > updating yes > > * The CLI documentation needs to be added, do you agree that this can > be added somewhere in the Application Server Integration section? yes that'd be the right place. ConfigAdmin coverage is missing too. > > I am happy to make these changes but wanted to get your opinion first... That'd be awesome. cheers > > Cheers, > > David

Here some feedback ... > Capabilities refer to bundles or modules available in the AS 7 product repository. The capability name is an abstract identifier for some functional capability. We currently support module identifiers (i.e. a pointer to some bundle or module available in the AS 7 product repository) and maven coordinates (i.e. a maven artifact identifier availbale in the public jboss nexus repository) Otherwise great - thanks cheers -thomas PS: great flowers ;-) On 05/16/2012 01:49 PM, David Bosschaert wrote: > I've added some content here: > > http://docs.jboss.org/author/display/JBOSGI/Command+Line+Interface+Console > and here: > http://docs.jboss.org/author/display/JBOSGI/Management+Console > > I also updated > http://docs.jboss.org/author/display/JBOSGI/Getting+Started > to explain the difference between the AS7 and project distribution > and updated the bundle deployment section in there. > > I made some minor changes to > > http://docs.jboss.org/author/display/JBOSGI/Application+Server+Integration > > Cheers, > > David > > On 15/05/2012 09:28, Thomas Diesler wrote: >> Hi David >> >> On 05/15/2012 08:41 AM, David Bosschaert wrote: >>> Hi Thomas, >>> >>> I made the OSGi subsystem section in AS7 point to JBOSGI >>> documentation wiki as it contained pretty much all of the >>> documentation needed. >>> >>> I had a look at the JBOSGI docs at >>> https://docs.jboss.org/author/display/JBOSGI/JBoss+OSGi+Home and >>> had a few thoughts, just thought I'd run them by you before >>> changing anything... >>> >>> * The Getting Started page focuses on the JBOSGi installer and >>> obtaining JBoss OSGi that way. I think it should focus on pure AS7 >>> where it mention that the AS7 installer can be used to obtain extra >>> functionality, but I think people should realize that no additional >>> download is needed to obtain JBoss OSGI... >> We expect to have a faster release cycle than AS7. In future the >> jbosgi installer can be used to update the osgi components in a >> given AS7 community release. We would update our binaries but not >> any of the AS/integration code. The jbosgi examples >> demonstrate/document the scope of supported functionality, which is >> the second aspect of an jbosgi release. The third is a snapshot of >> documentation. >>> >>> * The bundle deployment section on the getting started page needs >>> updating >> yes >>> >>> * The CLI documentation needs to be added, do you agree that this >>> can be added somewhere in the Application Server Integration section? >> yes that'd be the right place. ConfigAdmin coverage is missing too. >>> >>> I am happy to make these changes but wanted to get your opinion >>> first... >> That'd be awesome. >> >> cheers >>> >>> Cheers, >>> >>> David >> >