[JUDDI-206] Implement save_subscription method of API

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0beta
• Assignee: Jeff Faath
• Reporter: Kurt T Stam
• Created: 18/Mar/09 18:22
• Updated: 01/Jun/09 02:02
• Resolved: 10/Apr/09 01:20

Description

A publisher can make subscription information to later retrieve registry data based on the subscription. Notes:

• Subscriptions are identified by a unique key. This key can be provided by the publisher (must have owning key generator) or be generated by the system. Validation should ensure that no entities use a proposed key (and vice versa, saving entities should now check the subscription keys for clashes).

• bindingKey and notificationInterval values are used for asynchronous notification.

• the subscription filter input contains a collection of find_* and get_* xml messages that will be used to query the registry to get results. how should these be stored? As text blobs or serialized objects?

• Read section 5.5.8 of spec for more information