Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 899595 (JBPAPP6-301)

Summary: OSGi Tech Preview Criteria
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Thomas Diesler <thomas.diesler>
Component: OSGiAssignee: Thomas Diesler <thomas.diesler>
Status: CLOSED EOL QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: dimitris, mark.little, smcgowan, thomas.diesler
Target Milestone: ---   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-301
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:46:37 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 899597, 899598, 899599, 899614    
Bug Blocks:    
Attachments:
Description Flags
OSGi.png none

Description Thomas Diesler 2011-11-22 17:03:19 UTC
project_key: JBPAPP6

Checklist to define the criteria for OSGi inclusion in EAP as tech preview

* Verify that it does not impact the EAP 6 schedule 
* QA test coverage review
* Check if we have any documentation holes and a plan to fill them
* Do a usability walk through as part of the Beta

Comment 1 Shelly McGowan 2011-11-22 17:17:38 UTC
Link: Added: This issue depends JBPAPP-7522


Comment 2 Thomas Diesler 2011-11-23 08:50:03 UTC
Link: Removed: This issue depends JBPAPP-7522 


Comment 3 Thomas Diesler 2011-11-23 08:50:27 UTC
Link: Added: This issue is a dependency of JBPAPP-7522


Comment 4 Shelly McGowan 2011-11-23 18:48:49 UTC
Raising priority to BLOCKER to get a firm decision on this.  

Comment 5 Mark Little 2011-12-08 14:36:15 UTC
I need confirmation from Trevor, Shelly and others that this has zero impact on the schedule.

Comment 6 Shelly McGowan 2011-12-14 21:49:29 UTC
OSGi presents no problems for productization if it remains in-line with the AS 7 distribution.  The impact occurs if we choose to remove it as well as present it to the user as a Tech Preview.  In the case of a Tech Preview, it is assumed (to be confirmed) that moving it to the "extras" directory would have to happen.  No change in the EAP build process will occur till there is final resolution on this.  Need to have Resolved by the first ER1 build which will be based of the AS 7.1.0.Final upstream release. 

Comment 7 Dimitris Andreadis 2012-01-09 17:07:58 UTC
Can you please take a look at [4], the set of supported functionality?

I believe we need to remove all the Jetty stuff from AS7 anyway:

Webconsole, provided by Felix (requires HttpService)
HttpService, provided by PaxWeb (runs on Jetty)
Webapp support, provided by PaxWeb (runs on Jetty)

or we should just get rid of all non-core OSGi bundles?


Comment 8 David Bosschaert 2012-01-10 07:41:43 UTC
I think it would be best to remove all non-core OSGi bundles from the distribution.
We can then describe, as part of the documentation, how the user can add this functionality if they need it.
This follows more the OSGi philosophy of only deploying what you need.

However, I would leave the ConfigAdmin service in the distro as it tightly integrates with the AS7 configuration, it's a fairly small component and most users will appreciate it being there. It doesn't depend on Jetty so this should not be a problem as far as I can see...

Comment 9 Thomas Diesler 2012-01-10 08:15:32 UTC
Link: Added: This issue depends AS7-3036


Comment 10 Paul Gier 2012-01-10 21:28:44 UTC
Link: Added: This issue relates to JBPAPP-7795


Comment 11 Shelly McGowan 2012-01-13 01:50:20 UTC
The management console exposes OSGi as a runtime operation.  If OSGi is removed, will there be an impact to the console functionality or is the availability of this subsystem dynamically detected?

Comment 12 Shelly McGowan 2012-01-13 01:50:20 UTC
Attachment: Added: OSGi.png


Comment 13 Shelly McGowan 2012-01-13 02:16:50 UTC
I removed OSGi subsystem.  OSGi remained in the console view as a runtime operation but it was a no-op.

Comment 14 Thomas Diesler 2012-01-13 08:00:11 UTC
This has also been mentioned in relation to AS7-3251. The expected behaviour is that the console does not show a management screen for a functionality that is not there. This is a general requirement that does not only apply to OSGi.

Comment 15 David Bosschaert 2012-01-13 09:25:59 UTC
I've created AS7-3300 for this.

Comment 16 Thomas Diesler 2012-01-17 08:21:18 UTC
Link: Added: This issue is related to AS7-3300


Comment 17 Thomas Diesler 2012-02-21 10:33:03 UTC
Release Notes Text: Added: Done


Comment 18 Anne-Louise Tangring 2012-11-05 13:23:06 UTC
Release Notes Text: Removed: Done 
Docs QE Status: Removed: NEW 


Comment 19 Josef Cacek 2012-11-20 14:24:32 UTC
reopening. subtasks are not complete.