Bug 899599 (JBPAPP6-304)

thomas, can you elaborate on this?

This is to make sure that the OSGi tech preview in EAP is "usable". Naturally I would say this is the case, however we wanted to have a second opinion on this especially from the console perspective. If you don't know what to do with this (i.e. not sure what to test for) you can perhaps delegate to DavidB.

Ideally, we would like to see a short test plan (walk through) documented and associated with this issue. A jira comment should be sufficient. 

David, can you provide some kind of "tick list" that matches the use cases given? We can use it for testing the OSGI functionality manually and the QA team would need to create the corresponding selenium tests

Ok - here's a start.

Test OSGi Bundle deployment and runtime bundle management:
On the 'Runtime' page:
* Go to 'Runtime Operations->OSGi'
* The console should ask whether the OSGi subsystem needs to be activated, select yes. Then, after a few seconds, the list of bundles will appear.
* Deploy an OSGi Bundle (e.g. test TestOSGiBundle attached to this bug) via 'Deployments->Manage Deployments'
* Enable the deployment
** You should see 'Hello from an OSGi Bundle!' appear on the AS7 console.
* Go to 'Runtime Operations->OSGi'
Initially the new deployment is not visible as the table only has 8 rows and our testbundle is the 9th. 
* Reverse the sorting on Bundle ID by clicking on the header. You'll see bundle with the highest ID is our TestOSGiBundle.
* Click on the TestOSGiBundle row in the list and make sure that the Details pane is correctly filled with information. It should show:
{noformat}Version: 1.0.0
Start Level: 1
SymbolicName: TestOSGiBundle
Type: bundle
State: ACTIVE{noformat}
* Click the 'Stop' button on the bundle row.
** You should see 'Goodbye from an OSGi Bundle!' in the console
** The State column should be empty now and the state field in the details pane should say 'RESOLVED'.
* Go back to 'Deployments->Manage Deployments' and remove the TestOSGiBundle deployment.

Test capabilities configuration
On the 'Profile' page:
* Select 'OSGi->Framework' and go to the 'Capabilities' tab.
* Click 'Add' and enter org.projectodd.stilts with start level 2.
* Should appear now in the list.
Go back to the Runtime page:
* The stilts-stomplet-server-bundle should now be visible. Clicking on it should show Start Level 2. State should be INSTALLED.
* Now move the framework to start level 2 by clicking the Framework tab.
This causes the stilts bundle to be started, but unfortunately there is a resolution error. Thomas I attempted to add the org.jboss.netty module via capabilities, but that caused another error. Do you know what the issue is with netty?
* Open the standalone.xml file and see that the following line was added to the configuration:
{noformat}<capability name="org.projectodd.stilts" startlevel="2"/>{noformat}
* Remove the stilts bundle again by going back to the Capabilities tab and clicking remove.
** Console should say that it needs to be restarted, currently it doesn't (JBPAPP-8358).

Test framework properties
On the 'Profile' page:
* Select OSGi -> Framework and go to the 'Properties' tab.
* Remove the 'org.osgi.framework.startlevel.beginning' and add it again now with value 3. (BTW we used to have an edit button here, it would be more user-friendly to allow editing instead of delete-add)
** Console should say that it needs to be restarted, currently it doesn't (JBPAPP-8358).
* Check in the standalone.xml that it has the following configuration:
{noformat}
            <properties>
                <property name="org.osgi.framework.startlevel.beginning">
                    3
                </property>
            </properties>{noformat}
* Remove the check from the Lazy Activation configuration checkbox.
* Check in the standalone.xml that it has the following configuration:
{noformat}<subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="eager">{noformat}
* Restart the server and reopen the console.
On the 'Runtime' page
* Go to the 'Runtime Operations->OSGi' tab. Since the OSGi subsystem is eagerly started it should not ask to activate it. The list of bundles should appear instantly.
* Select the Framework tab. It should show start level 3 as the active start level.

Config Admin Service
On the 'Profile' page select 'Core->Config Admin Service'.
* Click 'Add' on top of the screen. Add a PID of org.foo.bar with mykey and myvalue as configuration values.
Add another config value: xkey, yval
* Check in the standalone.xml that it has the following configuration:
{noformat}
        <subsystem xmlns="urn:jboss:domain:configadmin:1.0">
            <configuration pid="org.foo.bar">
                <property name="mykey" value="myvalue"/>
                <property name="xkey" value="yval"/>
            </configuration>
        </subsystem>{noformat}

Attachment: Added: TestOSGiBundle_1.0.0.jar

Walkthrough provided.

Docs QE Status: Removed: NEW 

Verified - the walkthrough is provided. Closing.