JA-SIG Day2: Developing with JSR 170

This is my notes. The official presentation slides will be at:

http://www.ja-sig.org/wiki/display/JCON/Denver+2007+presentations

Presentation PDF:
http://www.ja-sig.org/wiki/download/attachments/19378/JSR170Presentation.pdf?version=1

More info:
http://www.jcp.org/en/jsr/detail?id=170

JSR is a 'STANDARD' Content Repository API for JAVA

Other Standards:

1. ODMA/DMA
   Both dissolved prior to 2000
2. WebDAV
1. Managed by AIIM
2. is a standard for a protocol; NOT API!
3. iECM
1. managed by AIIM

Repositories with JCR179 Connectors

1. Jackrabbit
2. CRX
3. Alfresco - Level 1, Level 2 with support for transaction
4. eXo
5. Jeceira
6. ECM Documentum
7. BEA WebLogic Platfotm
8. Magnolia
9. jLibrary
10. JCRBrowser
    

JSR17o in details
Repository -> Workspaces -> tree of Items
A Item: a node (encapsulate the content structure) or a property (only be a leaf)

1. Level1 - Read Only
2. Level2 - Includes level 1 and adds ability to mutate (modify - add)
3. Optional features:
1. Transactions
2. Versioning
3. Observation
4. Locking
5. SQL Search
4. Simple Authenticartion

Some code demos ..

Know your content and design the Tree structure carefully.

Case study: Alfresco
= Excellent, full featured open source ent. le
= Some level of JSR 170 support exists
Issues
= Model2 deployment not supported due to serious JCR-RMI issues
= Many key optionals not implemented
= JCR query support not prod ready

Recommendations:

• Knowing your content
• Know how your selected CR threats your kinds of content
• First time designing tree structure for JCR?
• Allow time to make mistakes
• Prototype it to find mistakes
• Prefer deeper tree structure over wide tree structures

JSR283 - Content Repository API for JAVA version 2.