| Summary: | Integrate with OSGi JNDI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Gemini.Web | Reporter: | Violeta Georgieva <milesg78> | ||||
| Component: | unknown | Assignee: | Violeta Georgieva <milesg78> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | glyn.normington | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 2.1.0.M01 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 328174 | ||||||
| Bug Blocks: | 361173 | ||||||
| Attachments: |
|
||||||
|
Description
Violeta Georgieva
Is it a requirement that Gemini Web does not have a hard dependency on OSGi JNDI or Gemini Naming? I think it should be. (In reply to comment #1) > Is it a requirement that Gemini Web does not have a hard dependency on OSGi > JNDI or Gemini Naming? I think it should be. It will not depend neither on OSGi JNDI nor on Gemini Naming. GW will expose services with the corresponding interfaces: - javax.naming.spi.InitialContextFactoryBuilder - javax.naming.spi.ObjectFactoryBuilder - javax.naming.spi.ObjectFactory Patch will be attached so we can comment on it. Perfect. Thanks. Created attachment 205386 [details] Patch proposal The interesting part is: if (OSGI_NAMING_ENABLED.equals(useNaming)) { - //TODO Integration with OSGi JNDI will be covered in - //https://bugs.eclipse.org/bugs/show_bug.cgi?id=361144 + registerInitialContextFactory(); + registerJavaURLContextFactory(); + registerObjectFactoryBuilder(); } Comment on attachment 205386 [details]
Patch proposal
Looks ok to me.
Change is tested, committed and pushed. Commit ID: 683e8e18b2464fb429fbf4f96cef4660177ee273 |