Extensible Controls for a Content Data Repository
First Claim
1. A system for providing extensible controls for a content data repository, the system comprising:
- a content repository including a plurality of nodes for maintaining data associated with specific data types;
an extensible control residing on a server, 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
at least one extended control interface associated with a specific data type, said extended control interface including one or more annotations, said annotations 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.
2 Assignments
0 Petitions
Accused Products
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.
-
Citations
20 Claims
-
1. A system for providing extensible controls for a content data repository, the system comprising:
-
a content repository including a plurality of nodes for maintaining data associated with specific data types;
an extensible control residing on a server, 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
at least one extended control interface associated with a specific data type, said extended control interface including one or more annotations, said annotations 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. 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 one or more data types;
providing an extensible control that includes a set of create, read, update and delete (CRUD) methods for performing specific operations within the content repository;
defining at least one interface that extends the extensible control, said interface including at least one method that is annotated with at least one annotation;
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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A computer readable 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 one or more data types;
provide an extensible control that includes a set of create, read, update and delete (CRUD) methods for performing specific operations within the content repository;
receive a definition of at least one interface that extends the extensible control, said interface including at least one method that is annotated with at least one annotation;
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.
-
Specification