System and method for providing SPI extensions for content management system

• US 7,953,734 B2
• Filed: 05/16/2006
• Issued: 05/31/2011
• Est. Priority Date: 09/26/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Roth, Steven Leslie, Zhou, Xiaojiang, McVeigh, Ryan Sean, Posner, Brad, Saarva, Tanya, Patadia, Jalpesh
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Casanova; Jorge A
• Application Number:
  US11/435,163
• Publication Number:
  US 20070083484A1
• Time in Patent Office: 1,841 Days
• Field of Search: 707/5, 707/10, 707/102, 707/104.1, 707/202, 707/999.005, 707/999.01, 707/999.102, 707/999.104, 707/999.202, 707/736, 707/781
• US Class Current: 707/736
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

In accordance with embodiments, there are provided mechanisms and methods for providing extensions to a Service Provider Interface (SPI) in a content management system. These mechanisms and methods for providing extensions to a Service Provider Interface (SPI) in a content management system can enable embodiments to integrate one or more of a plurality of content repositories into a virtual content repository (VCR) by mapping requests to access content received via a common Application Programming Interface (API) to at least one JSR-170 compliant repository and at least one SPI compliant repository. The ability of embodiments to provide so integrate disparate content repositories can enable one or more of navigation, CRUD operations (create, read, update, delete), versioning, workflows, and searching operations to operate on a plurality of repositories as though the plurality of repositories were one repository.

Claims

1. A method for extending a content management system, the method comprising:

connecting to a plurality of content repositories using a Service Provider Interface (SPI), wherein the plurality of content repositories includes a first content repository and a second content repository;

integrating the plurality of content repositories into a virtual content repository (VCR);

receiving a request to access content in both the first content repository and the second content repository from a client, via a common Application Programming Interface (API) associated with the VCR;

mapping the request to the first content repository and the second content repository correspondingly;

automatically using an XPath-based query for searching the first content repository and using an SQL-based query for searching the second content repository, wherein the first content repository returns a first result set for the XPath-based query and the second content repository returns a second result set for the SQL-based query, and wherein the first result set and the second result set are in two different format;

preparing the requested content based on a federation of the first result set for the XPath-based query from the first content repository and the second result set for the SQL-based query from the second content repository; and

providing the requested content to the client via the API.

2. The method of claim 1, further comprising:

relating structured content and unstructured content into a searchable corpus.

3. The method of claim 1, further comprising:

enabling at least one of navigation, CRUD (Create, Read, Update, Delete), versioning, workflows, and searching operations to operate on the plurality of repositories as though the plurality of repositories were one repository.

4. The method of claim 1, further comprising:

using a node cache to provide fast access to recently accessed nodes in the plurality of content repositories.

5. The method of claim 1, further comprising:

allowing a node in the plurality of content repositories to be any one of;

a hierarchy node that serves as containers for other nodes;

a content node that represents content and data; and

a schema node that is a placeholder for a schema which is a named collection of one or more property types associated with the content node.

6. The method of claim 1, further comprising:

allowing the client to interact with the VCR only through the API without a need to know which content repository contains the requested content.

7. The method of claim 1, further comprising:

accessing the first content repository via an adapter that facilitates a mapping of the request to different content repositories in the VCR.

8. The method of claim 1, further comprising:

associating both the first content repository and the second content repository with a transaction, wherein the first content repository uses a transient storage which is persisted when the transaction is committed, and the second content repository adapts an immediate persistence behavior that persists changes when any API method is called.

9. The method of claim 8, further comprising:

allowing the first content repository to persist the transient storage when a workspace API method is called, in order to simulate the immediate persistence behavior of the second content repository.

10. The method of claim 8, further comprising:

including workspace name in repository configuration for the first content repository, in order to add context to each path and make the path unique at the API level.

11. The method of claim 1, further comprising:

allowing the first content repository and the second content repository to use different security models, wherein the first content repository does not explicitly require context information for authorization when acquiring a session on a workspace, and wherein the second content repository explicitly requires context information for authorization.

12. The method of claim 1, further comprising:

allowing the first content repository and the second content repository to use different workspace models, wherein the first content repository allows multiple paths to a same node, and wherein the second content repository presumes a path to a node is unique.

13. A machine-readable medium storing one or more sequences of instructions for extending a content management system, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

connecting to a plurality of content repositories using a Service Provider Interface (SPI), wherein the plurality of content repositories includes a first content repository and a second content repository;

integrating the plurality of content repositories into a virtual content repository (VCR);

receiving a request to access content in both the first content repository and the second content repository from a client, via a common Application Programming Interface (API) associated with the VCR;

mapping the request to the first content repository and the second content repository correspondingly;

automatically using an XPath-based query for searching the first content repository and using an SQL-based query for searching the second content repository, wherein the first content repository returns a first result set for the XPath-based query and the second content repository returns a second result set for the SQL-based query, and wherein the first result set and the second result set are in two different format;

preparing the requested content based on a federation of the first result set for the XPath-based query from the first content repository and the second result set for the SQL-based query from the second content repository; and

providing the requested content to the client via the API.

14. The machine-readable medium as recited in claim 13, further carrying

instructions for carrying out the step of:

relating structured content and unstructured content into a searchable corpus.

15. The machine-readable medium as recited in claim 13, further carrying instructions for carrying out the step of:

enabling at least one of navigation, CRUD (Create, Read, Update, Delete), versioning, workflows, and searching operations to operate on the plurality of repositories as though the plurality of repositories were one repository.

16. An apparatus for extending a content management system, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

connecting to a plurality of content repositories using a Service Provider Interface (SPI), wherein the plurality of content repositories includes a first content repository and a second content repository;

integrating the plurality of content repositories into a virtual content repository (VCR);

receiving a request to access content in both the first content repository and the second content repository from a client, via a common Application Programming Interface (API) associated with the VCR;

mapping the request to the first content repository and the second content repository correspondingly;

automatically using an XPath-based query for searching the first content repository and using an SQL-based query for searching the second content repository, wherein the first content repository returns a first result set for the XPath-based query and the second content repository returns a second result set for the SQL-based query, and wherein the first result set and the second result set are in two different format;

preparing the requested content based on a federation of the first result set for the XPath-based query from the first content repository and the second result set for the SQL-based query from the second content repository; and

providing the requested content to the client via the API.