[DOCU-326] Using a JNDI data source Created: 03/Oct/12  Updated: 31/Dec/14  Resolved: 31/Dec/14

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Ruth Stocks
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

The Magnolia JNDI module is effectively superseded by Jackrabbit's native JNDI support. Edit the module document:

  • Explain when and why you should consider using a JNDI data source. The rationale is missing from the article.
  • Recommend Jackrabbit's own JDNI support as the first option, Magnolia's JNDI module as the second. Add an info box to say the JNDI module does not work with Magnolia 4.5 or later. Watch MGNLJNDI-6.
  • Test the Jackrabbit JNDI configuration on the demo-project. Document the configuration steps. If no Magnolia specific configuration is needed, linking to Jackrabbit documentation may be adequate.


 Comments   
Comment by Antti Hietala [ 03/Oct/12 ]

Related info in http://wiki.magnolia-cms.com/display/WIKI/Database-Only+Repositories+with+JNDI+Datasources

Comment by Magnolia International [ 11/Oct/12 ]

Antti, I see you linked to MGNLJNDI-6, but that is completely unrelated.
The MGNLJNDI module's purpose is to help exposing the repository so it can be addressed (retrieved, found, discovered, named) via JNDI. The focus of DOCU-326 (this issue) is about JDNI Datasources, i.e database connection information that is named/retrieved via JNDI. (JNDI stands for Java Naming and Directory Interface and its purpose is simply to propose interfaces to expose/find/access arbitrary objects by name.) - JNDI is merely the mechanism by which the application (Magnolia/Jackrabbit) and the container (Tomcat) can communicate and exchange the object (the DataSource).

Comment by Ruth Stocks [ 31/Dec/14 ]

Module is not 4.5 or 5.0 compatible - removed both module pages

Generated at Mon Feb 12 01:08:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.