Extensible controls for a content data repository

• US 7,805,459 B2
• Filed: 11/17/2006
• Issued: 09/28/2010
• Est. Priority Date: 11/17/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Polk, Ray
• Primary Examiner(s): Ali; Mohammad
• Assistant Examiner(s): Ruiz; Angelica
• Application Number:
  US11/561,343
• Publication Number:
  US 20070124326A1
• Time in Patent Office: 1,411 Days
• Field of Search: 707/103.R, 707/103.Y, 707/103.X, 707/103.Z, 707 1-206, 715/255
• US Class Current: 707/790
• CPC Class Codes: G06F 16/2448 for particular applications; for extensibility, e.g. user defined types
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An extensible control interface is provided to simplify access to the content management repository. Developers can write extension interfaces associated with new data types, where the extension interfaces extend the extensible control and are annotated with the control extension annotation. These new interfaces can specify the repository name and declare various methods annotated with annotations. Parameters of the various methods can also be annotated to supply needed information. Using an annotation process tool (APT), the developer can generate the bean and implementation classes and the methods can subsequently be called upon to perform operations on types in the repository. For example, the extensible control can take care of interacting with the type manager to perform the needed actions within the repository in order to create the new object classes and nodes. Object classes can be created on the first call, while node instances upon each call of the create method.

Claims

1. A system for providing extensible controls for a content data repository, the system comprising:

a content repository, residing on a server with one or more processors, including a plurality of nodes to maintain data associated with a plurality of specific data types, wherein each of the plurality of nodes contains data in one of the plurality of specific data types;

an extensible control residing on a server with one or more processors, said extensible control including an invoke method and a set of create, read, update and delete (CRUD) methods for performing specific operations within the content repository;

and a plurality of extended control interfaces, wherein each extended control interface is extended from an extensible control interface and is associated with one of the plurality of nodes in the content repository that contains data in one of the plurality of specific data types, said extended control interface including one or more annotations to specify properties of said node in the content repository, wherein the extensible control interface contains logic to map the one or more annotations in the extended control interface into the specific data type and perform one or more operations on a node in the content repository that contains data in the specific data type, said one or more operations being mapped to the CRUD methods on the extensible control such that for every annotated method call on the extended control interface, a corresponding CRUD method is invoked on the extensible control in order to perform an appropriate operation in the content repository, wherein one operation is to programmatically create or modify a specific data type within the content repository instead of changing a configuration file.

2. The system of claim 1 wherein the content repository further includes:

a type manager associated with the extensible control interface to perform operations associated with the content repository.

3. The system of claim 1 wherein each data type includes:

an object class and a node in the content repository, said node being associated with said object class.

4. The system of claim 1, further comprising:

an annotation processing tool (APT) and a Java compiler to process annotations within the extended control interface and to generate an implementation class and a bean that both implement the extensible control interface.

5. The system of claim 1 wherein each node within the repository is wrapped with a Java bean to specify the data type associated with the data contained by the node based on one of the extended control interface.

6. The system of claim 1, further comprising:

a generic control to encapsulate business logic and abstracting functionality away from the extensible control.

7. The system of claim 1 wherein each node within the repository further includes:

one or more properties that are comprised of a name and a value.

8. The system of claim 1 wherein said annotations in the extended control interface include at least one of method level annotations, parameter level annotations and class level annotations processed by an Annotation Processing tool.

9. The system of claim 8 wherein said annotations include one or more of:

create, delete, dynamic properties, find by, find by Id, Id, move, parent Id, property, property pair, repository info, search paths, sort order and update annotations.

19. The system of claim 1 wherein:

the extensible control interface contains one or more methods which correspond to annotations in each of the plurality of extended control interfaces, so that every method call on the extended control interface invokes a method in the extensible control interface to handle an interaction with the content repository.

20. The system of claim 4 wherein:

the APT and the compiler generate a bean that implements one of the plurality of extended control interfaces to interact with the content repository.

10. A method for providing extensible controls for a content data repository, the method comprising:

maintaining data in a plurality of nodes within a content repository, said data associated with a plurality of data types, wherein each of the plurality of nodes contains data in one of the plurality of data types;

providing an extensible control interface that includes a set of create, read, update and delete (CRUD) methods for performing specific operations within the content repository, wherein one operation is to programmatically create or modify a specific data type within the content repository instead of changing a configuration file;

defining an extended control interface that is extended from the extensible control interface and is associated with one of the plurality of nodes in the content repository that contains data in one of the plurality of data types, said extended control interface including one or more annotations to specify properties of said node in the content repository, wherein the extensible control interface contains logic to map the one or more annotations in the extended control interface into the specific data type and perform one or more operations on a node in the content repository that contains data in the specific data type;

invoking said method annotated with said annotation in the interface by a client application; and

mapping said method annotated with said annotation to at least one of said CRUD methods on the extensible control.

11. The method of claim 10 wherein the content repository further includes:

a type manager associated with the extensible control interface to perform operations associated with the content repository.

12. The method of claim 10 wherein each data type includes:

an object class and a node in the content repository, said node being associated with said object class.

13. The method of claim 10, further comprising:

processing said at least one annotation by an annotation processing tool and a Java compiler in order to generate an implementation class and a bean that both implement the extensible control interface.

14. The method of claim 10 wherein each node within the repository is wrapped with a Java bean to specify the data type associated with the data contained by the node based on one of the extended control interface.

15. The method of claim 10 wherein each node within the repository further includes:

one or more properties that are comprised of a name and a value.

16. The method of claim 10 wherein said annotations in the extended control interface include at least one of method level annotations, parameter level annotations and class level annotations processed by an Annotation Processing tool.

17. The method of claim 10 wherein said annotations include one or more of:

create, delete, dynamic properties, find by, find by Id, Id, move, parent Id, property, property pair, repository info, search paths, sort order and update annotations.

18. A computer readable storage medium having instructions stored thereon which when executed by one or more processors, cause a system to:

maintain data in a plurality of nodes within a content repository, said data associated with a plurality of data types, wherein each of the plurality of nodes contains data in one of the plurality of data types;

provide an extensible control interface that includes a set of create, read, update and delete (CRUD) methods for performing specific operations within the content repository, wherein one operation is to programmatically create or modify a specific data type within the content repository instead of changing a configuration file;

define an extended control interface that is extended from the extensible control interface and is associated with one of the plurality of nodes in the content repository that contains data in one of the plurality of data types, said extended control interface including one or more annotations to specify properties of said node in the content repository, wherein the extensible control interface contains logic to map the one or more annotations in the extended control interface into the specific data type and perform one or more operations on a node in the content repository that contains data in the specific data type;

invoke said method annotated with said annotation in the interface by a client application; and

map said method annotated with said annotation to at least one of said CRUD methods on the extensible control.