A consistency enforcement system includes an XML object of an SOA-registry. The XML object includes a plurality of processing task XML elements that define a processing task to be performed the SOA. An updated XML object is received through an interface. The updated object includes at least one additional processing task XML element that defines at least one further processing task to be performed by the SOA. A validation unit is use to query the SOA-registry in order to obtain one or more predefined processing task identifiers. The validation unit matches a processing task identifier of the at least one additional processing task XML element of the updated XML object against the one or more predefined processing task identifiers obtained from the SOA-registry and approves or rejects the updated XML object (20′) depending on the result of the match.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A consistency enforcement system for at least one extensible markup language (XML) object that is stored in a service oriented architecture (SOA) registry, the at least one XML object including a plurality of processing task XML elements that each respectively define at least one processing task that is to be performed by at least one component of the SOA, the consistency enforcement system comprising: an interface configured to receive an updated XML object comprising at least one additional processing task XML element that defines at least one further processing task to be performed by components of the SOA, wherein the at least additional processing task XML element is not included in the at least one XML object that is stored in the SOA registry; and a validation unit configured to communicate with the SOA registry in order to obtain one or more predefined processing task identifiers, each one of the predefined processing task identifiers corresponding to a predetermined processing task, wherein the validation unit is further configured to determine a result based at least in part on comparing a processing task identifier of the at least one additional processing task XML element of the updated XML object against the one or more predefined processing task identifiers obtained from the SOA registry, the validation unit being further configured to either approve or reject the updated XML object based on the result, and wherein the validation unit is further configured to either (a) store the updated XML object in the SOA registry, or (b) replace the at least one XML object stored in the SOA registry, or (c) store the updated XML object in the SOA registry and replace the at least one XML object stored in the SOA registry, only when the result is an approval of the updated XML object.
2. The consistency enforcement system of claim 1 , wherein the validation unit is configured to reject the updated XML object when the result of the comparison of the processing task identifier of the at least one additional processing task XML element to at least one of the predefined processing task identifiers obtained from the SOA registry is not a match.
3. The consistency enforcement system of claim 1 , wherein the validation unit is configured to reject the updated XML object when the result of the comparison of the processing task identifier of the at least one additional processing task XML element to at least one of the predefined processing task identifiers obtained from the SOA registry is a match.
4. The consistency enforcement system of claim 1 , wherein the validation unit is configured to reject the updated XML object when the updated XML object comprises at least one termination step XML element not included in the at least one XML object stored in the SOA registry, the at least one termination step XML element defining an end point of a sequence of processing tasks performed by components of the SOA.
5. The consistency enforcement system of claim 1 , wherein the validation unit is configured to reject the updated XML object when the updated XML object includes at least one XML element type other than a processing task XML element type.
6. The consistency enforcement system of claim 1 , wherein the validation unit is configured to reject the updated XML object when the XML object stored in the SOA registry comprises at least one processing task XML element that is not included the at least one updated XML object.
7. The consistency enforcement system of claim 1 , wherein the at least one XML object stored in the SOA registry comprises at least one transition XML element, the at least one transition XML element referencing at least one source processing task XML element and at least one target processing task XML element in order to define a sequence between the corresponding processing task XML elements.
8. The consistency enforcement system of claim 7 , wherein the validation unit is configured to reject the updated XML object when the at least one additional processing task XML element of the at least one updated XML object is not located within the sequence defined by the at least one transition XML element.
9. The consistency enforcement system of claim 7 , wherein the validation unit is configured to reject the updated XML object when the updated XML object comprises at least one additional transition XML element defining a sequence of processing tasks that does not lead to a termination step XML element defined in the XML object stored in the SOA registry.
10. The consistency enforcement system of claim 7 , wherein the validation unit is configured to reject the updated XML object when the updated XML object comprises at least one additional transition XML element defining a sequence of processing tasks that does not lead to the at least one additional processing task XML element.
11. The consistency enforcement system of claim 1 , wherein the determined result of the validation unit is additionally based on validating at least one configuration property that the updated XML object depends upon.
12. The consistency enforcement system of claim 1 , wherein the one or more predefined processing task identifiers are included in a pre-existing taxomony that is defined in the SOA registry.
13. A method for enforcing the consistency of at least one extensible markup language (XML) object stored in a service oriented architecture (SOA) registry, the at least one XML object including a plurality of processing task XML elements that each respectively define at least one processing task that is to be performed by at least one component of the SOA, the method comprising: receiving an updated XML object comprising at least one additional processing task XML element that defines at least one further processing task to be performed by components of the SOA, wherein the at least additional processing task XML element is not included in the at least one XML object that is stored in the SOA registry; communicating with the SOA registry in order to obtain one or more predefined processing task identifiers, each one of the predefined processing task identifiers corresponding to a predetermined processing task; determining a result based at least in part on comparing a processing task identifier of the at least one additional processing task XML element of the updated XML object against the one or more predefined processing task identifiers obtained from the SOA registry; approving or rejecting the updated XML object based on the result; and when the result is an approval of the updated XML object, either (a) storing the updated XML object in the SOA registry, or (b) replacing the at least one XML object stored in the SOA registry, or (c) storing the updated XML object in the SOA registry and replacing the at least one XML object stored in the SOA registry.
14. A non-transitory computer readable storage medium storing computer readable instructions for enforcing the consistency of at least one extensible markup language (XML) object stored in a service oriented architecture (SOA) registry, the instructions causing at least one computer to at least: receive an updated XML object that includes at least one additional processing task XML element that defines at least one further processing task to be performed by components of the SOA, the at least additional processing task XML element not included in the at least one XML object that is stored in the SOA registry; retrieve one or more predefined processing task identifiers from the SOA registry, each one of the predefined processing task identifiers corresponding to a predetermined processing task; determine a result based at least in part on comparing a processing task identifier of the at least one additional processing task XML element of the updated XML object against the one or more predefined processing task identifiers obtained from the SOA registry; approve or reject the updated XML object based on the result; and either (a) store the updated XML object in the SOA registry, or (b) replace the at least one XML object stored in the SOA registry, or (c) store the updated XML object in the SOA registry and replace the at least one XML object stored in the SOA registry, when the result is an approval of the updated XML object.
15. The medium of claim 14 , wherein the one or more predefined processing task identifiers are included in a pre-existing taxomony that is defined in the SOA registry.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
July 21, 2009
May 8, 2012
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.