Accessing a non-relational store with a container-managed persistence bean via a web service function

1. A storage medium encoded with instructions, wherein the instructions when executed comprise:

receiving a key parameter from a container-managed persistent bean;

determining whether the container-managed persistent bean is associated with a non-relational data store, wherein the determining whether the container-managed persistent bean is associated with the non-relational data store is further based on deployment description extension settings specified by a bean assembler, wherein the determining whether the container-managed persistent bean is associated with the non-relational data store further comprises determining whether the container-managed persistent bean is marked as non-relational, wherein a method in the container-managed persistent bean causes invocation of a persistent helper method in a persistence manager, and wherein the persistent helper method in the persistence manager performs the determining;

if the container-managed persistent bean is not associated with the non-relational data store, inserting the key parameter into a prepared statement and communicating the key parameter to a relational data store; and

if the container-managed persistent bean is associated with the non-relational data store, creating a web service input message with the key parameter and invoking a web service function with the web service input message, wherein the web service function communicates the web service input message to the non-relational data store, wherein the invoking further comprises invoking the web service function with the web service input message without using an interface to the non-relational data store.

2. The storage medium of claim 1 , wherein the method in the container-managed persistent bean comprises a create method, wherein the create method is passed the key parameter by a client, and wherein the create method creates an instance of the container-managed persistent bean.

3. The storage medium of claim 2 , wherein the key parameter specifies an instance of a primary key class that the client desires to use.

4. The storage medium of claim 1 , wherein the key parameter is associated with a command to create data in the non-relational data store.

5. The storage medium of claim 1 , wherein the key parameter is associated with a command to retrieve data from the non-relational data store.

6. The storage medium of claim 1 , wherein the key parameter is associated with a command to update data in the non-relational data store.

7. The storage medium of claim 1 , wherein the key parameter is associated with a command to delete data from the non-relational data store.

8. The storage medium of claim 1 , wherein the method in the container-managed persistent bean comprises a remove method, wherein the remove method is passed the key parameter by a client, and wherein the remove method creates an instance of the container-managed persistent bean.

9. A server comprising:

a processor; and

a storage device connected to the processor, wherein the storage device is encoded with instructions, and wherein the instructions when executed on the processor comprise:

receiving a key parameter from a container-managed persistent bean,

determining whether the container-managed persistent bean is associated with a non-relational data store, wherein the determining whether the container-managed persistent bean is associated with the non-relational data store is further based on deployment description extension settings specified by a bean assembler, wherein the determining whether the container-managed persistent bean is associated with the non-relational data store further comprises determining whether the container-managed persistent bean is marked as non-relational, wherein a method in the container-managed persistent bean causes invocation of a persistent helper method in a persistence manager, and wherein the persistent helper method in the persistence manager performs the determining,

if the container-managed persistent bean is not associated with the non-relational data store, inserting the key parameter into a prepared statement and communicating the key parameter to a relational data store, and

if the container-managed persistent bean is associated with the non-relational data store, creating a web service input message with the key parameter and invoking a web service function with the web service input message, wherein the web service function communicates the web service input message to the non-relational data store, wherein the invoking further comprises invoking the web service function with the web service input message without using an interface to the non-relational data store.

10. The server of claim 9 , wherein the method in the container-managed persistent bean comprises a create method, wherein the create method is passed the key parameter by a client, and wherein the create method creates an instance of the container-managed persistent bean.

11. The server of claim 10 , wherein the key parameter specifies an instance of a primary key class that the client desires to use.

12. The server of claim 9 , wherein the key parameter is associated with a command to create data in the non-relational data store.

13. The server of claim 9 , wherein the key parameter is associated with a command to retrieve data from the non-relational data store.

14. The server of claim 9 , wherein the key parameter is associated with a command to update data in the non-relational data store.

15. The server of claim 9 , wherein the key parameter is associated with a command to delete data from the non-relational data store.

16. The server of claim 9 , wherein the method in the container-managed persistent bean comprises a remove method, wherein the remove method is passed the key parameter by a client, and wherein the remove method creates an instance of the container-managed persistent bean.