System and method for providing SPI extensions for content management system

• US 20070083484A1
• Filed: 05/16/2006
• Published: 04/12/2007
• Est. Priority Date: 09/26/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Zhou, Xiaojiang, Posner, Brad, Saarva, Tanya, Patadia, Jalpesh, Roth, Steven, McVeigh, Ryan
• Granted Patent: US 7,953,734 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 providing extensions to a Service Provider Interface (SPI) in a content management system in a content management system, the method comprising:

receiving a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository;

integrating each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository; and

managing content in the plurality of content repositories based upon the VCR.

2. The method of claim 1, wherein receiving a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository includes:

receiving at least one content repository relating structured content and unstructured content into a searchable corpus and complying with the JSR-170 specification and at least one content repository that does not comply with the JSR-170 specification.

3. The method of claim 1, wherein integrating each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository includes:

federating content within the at least one JSR-170 compliant repository and the at least one SPI compliant repository to make the data accessible via a single programming interface.

4. The method of claim 3, further comprising:

simulating immediate persistence behavior of the at least one SPI compliant repository for instances when a session is used, persisting session information before the API completes.

5. The method of claim 4, wherein simulating immediate persistence behavior of the at least one SPI compliant repository for instances when a session is used, persisting session information before the API completes includes:

using a JSR-170 workspace method when such method exists;

otherwise persisting immediately after performing an action.

6. The method of claim 3, further comprising:

using an XPath-based query language for searching the at least one JSR-170 compliant repository and using an SQL-based query language for searching the at least one SPI compliant repository.

7. The method of claim 1, wherein managing content in the plurality of content repositories based upon the VCR includes:

enabling at least one 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.

8. The method of claim 1, further comprising:

receiving a request to access content received via a common Application Programming Interface (API).

9. A machine-readable medium carrying one or more sequences of instructions for providing extensions to a Service Provider Interface (SPI) in a content management system in 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:

receiving a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository;

integrating each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository; and

managing content in the plurality of content repositories based upon the VCR.

10. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of receiving a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository include instructions for carrying out the step of:

receiving at least one content repository relating structured content and unstructured content into a searchable corpus and complying with the JSR-170 specification and at least one content repository that does not comply with the JSR-170 specification.

11. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of integrating each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository include instructions for carrying out the step of:

federating content within the at least one JSR-170 compliant repository and the at least one SPI compliant repository to make the data accessible via a single programming interface.

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

simulating immediate persistence behavior of the at least one SPI compliant repository for instances when a session is used, persisting session information before the API completes.

13. The machine-readable medium as recited in claim 12, wherein the instructions for carrying out the step of simulating immediate persistence behavior of the at least one SPI compliant repository for instances when a session is used, persisting session information before the API completes include instructions for carrying out the step of:

using a JSR-170 workspace method when such method exists; and

otherwise persisting immediately after performing an action.

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

using an XPath-based query language for searching the at least one JSR-170 compliant repository and using an SQL-based query language for searching the at least one SPI compliant repository.

15. The machine-readable medium as recited in claim 9, wherein the instructions for carrying out the step of managing content in the plurality of content repositories based upon the VCR include instructions for carrying out the step of:

enabling at least one 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.

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

receiving a request to access content received via a common Application Programming Interface (API).

17. An apparatus for providing extensions to a Service Provider Interface (SPI) in a content management system in 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;

receiving a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository;

integrating each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository; and

managing content in the plurality of content repositories based upon the VCR.

18. A transmission medium containing:

code to receive a plurality of content repositories, the plurality of content repositories including at least one JSR-170 compliant repository and at least one SPI compliant repository;

code to integrate each one of the 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 the at least one JSR-170 compliant repository and the at least one SPI compliant repository; and

code to manage content in the plurality of content repositories based upon the VCR.