[GLASSFISH-17644] PaaS runtime should be extensible and should not be restricted to known service types Created: 04/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: iaas, paas-console, service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Bhavanishankar Assignee: Bhavanishankar
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

ALL


Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17645 virtualization layer should not be re... Sub-task Closed shreedhar_ganapathy  
Tags: ee7_cleanup_closed

 Description   

Neither the orchestrator nor the IMS layer should restrict themselves to known service types viz., JavaEE, MQ, LB, DB.

Also, the GlassFish SPE should consider dynamically integrating GlassFish service with any newly added service. For example, Java EE PaaS application might want to use a third party HA store. GlassFish SPE should provide mechanism to augment such additional services.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate components that will be impacted by this task.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.

Generated at Fri Sep 04 04:04:04 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.