Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Use Configuration Admin for configuration in OSGi environments #1495

Closed
glassfishrobot opened this issue Apr 13, 2013 · 4 comments
Closed

Use Configuration Admin for configuration in OSGi environments #1495

glassfishrobot opened this issue Apr 13, 2013 · 4 comments
Assignees
@rlubke
Labels
p: Major t: Improvement

Comments

@glassfishrobot
Copy link

Configuration properties such as the port to listen on are now configured within the bundle itself, which is not flexible.
The standard way of providing configuration in OSGi is using Configuration Admin (part of the compendium spec). Grizzly should be configured this way as well.

Affected Versions

[2.3]
@glassfishrobot
Copy link
Author

Reported by pbakker

@glassfishrobot
Copy link
Author

@rlubke said:
Will look into this next week.

@glassfishrobot
Copy link
Author

This issue was imported from java.net JIRA GRIZZLY-1495

@rlubke rlubke removed the OSGi label May 9, 2017
@arinban arinban mentioned this issue Feb 3, 2018
Open
@glassfishrobot glassfishrobot mentioned this issue Feb 10, 2018
Closed
@glassfishrobot
Copy link
Author

Closing this as this issue is migrated to eclipse-ee4j/grizzly#1495

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rlubke rlubke

Labels
p: Major t: Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rlubke @glassfishrobot