Abstract: An XML schema defining elements representing different point of variability (POV) types for points of variability of a pattern is provided. The elements belong to an XML schema POV data-type substitution group that allows the POV types to be substituted for one another. A pattern author is allowed to add new or custom POV data types to the substitution group, thereby allowing the pattern author to extend the pattern meta model to include new POV data types. Once the desired POV data types are defined, the pattern author is allowed to generate an instance of the pattern that applies programmatic operations of the new or custom POV data types created and substituted by the end user to each respective system object.

Abstract: An XML schema defining elements representing different point of variability (POV) types for points of variability of a pattern is provided. The elements belong to an XML schema POV data-type substitution group that allows the POV types to be substituted for one another. A pattern author is allowed to add new or custom POV data types to the substitution group, thereby allowing the pattern author to extend the pattern meta model to include new POV data types. Once the desired POV data types are defined, the pattern author is allowed to generate an instance of the pattern that applies programmatic operations of the new or custom POV data types created and substituted by the end user to each respective system object.

Abstract: A method for capturing patterns and associated points of variability includes providing an XML schema defining elements representing different point of variability (POV) types for a pattern. The elements belong to an XML schema “substitution group” to enable the POV types to be substituted for one another. In selected embodiments, the method enables a pattern author to add new or custom POV types to the “substitution group,” thereby allowing the pattern author to extend the pattern meta model to include new POV types. Once the desired POV types are defined, the method enables the pattern author to generate an instance of the XML schema, defining the points of variability for a specific pattern, using the elements defined in the XML schema “substitution group.” A corresponding apparatus and computer program product are also disclosed and claimed herein.

Abstract: A method for capturing patterns and associated points of variability includes providing an XML schema defining elements representing different point of variability (POV) types for a pattern. The elements belong to an XML schema “substitution group” to enable the POV types to be substituted for one another. In selected embodiments, the method enables a pattern author to add new or custom POV types to the “substitution group,” thereby allowing the pattern author to extend the pattern meta model to include new POV types. Once the desired POV types are defined, the method enables the pattern author to generate an instance of the XML schema, defining the points of variability for a specific pattern, using the elements defined in the XML schema “substitution group.” A corresponding apparatus and computer program product are also disclosed and claimed herein.

Abstract: A method for capturing patterns and associated points of variability includes providing an XML schema defining elements representing different point of variability (POV) types for a pattern. The elements belong to an XML schema “substitution group” to enable the POV types to be substituted for one another. In selected embodiments, the method enables a pattern author to add new or custom POV types to the “substitution group,” thereby allowing the pattern author to extend the pattern meta model to include new POV types. Once the desired POV types are defined, the method enables the pattern author to generate an instance of the XML schema, defining the points of variability for a specific pattern, using the elements defined in the XML schema “substitution group.” A corresponding apparatus and computer program product are also disclosed and claimed herein.

Abstract: Developing and testing of message models includes receiving elements within a first side of an editor pane via a user interface. The elements define a logical structure of data for a message model. The development and testing also includes displaying a listing of physical properties applicable to the elements in a second side of the editor pane, and providing a movable bar between the first side of the editor pane and the second side of the editor pane. The development and testing further includes receiving a property from the listing of physical properties and associating the physical property with a corresponding one of the elements, such that selection of the element on the first side of the editor pane causes the property associated with the element to be displayed on the second side of the editor pane. The message model is created from received elements and associated physical properties.

Abstract: Developing and testing of message models includes receiving elements within a first side of an editor pane via a user interface. The elements define a logical structure of data for a message model. The development and testing also includes displaying a listing of physical properties applicable to the elements in a second side of the editor pane, and providing a movable bar between the first side of the editor pane and the second side of the editor pane. The development and testing further includes receiving a property from the listing of physical properties and associating the physical property with a corresponding one of the elements, such that selection of the element on the first side of the editor pane causes the property associated with the element to be displayed on the second side of the editor pane. The message model is created from received elements and associated physical properties.

Abstract: A method and apparatus for creating a schema definition from a language-specific metamodel of a data structure written in a legacy computer language involves walking through the nodes of the metamodel, and creating corresponding schema element objects in a schema tree that is serialized to create the schema definition. The creation of the schema element objects follows rules, and permits the definition of nested data structures having conjunctive-type and disjunctive-type membership.

Abstract: A method for capturing patterns and associated points of variability includes providing an XML schema defining elements representing different point of variability (POV) types for a pattern. The elements belong to an XML schema “substitution group” to enable the POV types to be substituted for one another. In selected embodiments, the method enables a pattern author to add new or custom POV types to the “substitution group,” thereby allowing the pattern author to extend the pattern meta model to include new POV types. Once the desired POV types are defined, the method enables the pattern author to generate an instance of the XML schema, defining the points of variability for a specific pattern, using the elements defined in the XML schema “substitution group.” A corresponding apparatus and computer program product are also disclosed and claimed herein.

Abstract: A method for synchronizing data files, the method comprising: within a messaging utility, associating a Web Service Definition Language (WSDL) definition with a data file, the association made by a passive reference between the WSDL definition to the data file; creating a reference table identifying WSDL files and referenced data files; determining if the WSDL file has changed, if the WSDL file has changed then: determining if a reference to a data file exists in the changed WSDL file; adding an entry in the reference table associating the WSDL file and the data file; launching a component of a builder application to build the data file; and determining if any additional references to data files exist in the changed WSDL file; determining if the data file has changed, if the data file has changed then: determining if the changed data file is referenced by a WSDL file by examining the reference table; if the changed data file exists in the reference table, then launching a component of the builder application

Abstract: A method and apparatus for creating a schema definition from a language-specific metamodel of a data structure written in a legacy computer language involves walking through the nodes of the metamodel, and creating corresponding schema element objects in a schema tree that is serialized to create the schema definition. The creation of the schema element objects follows rules, and permits the definition of nested data structures having conjunctive-type and disjunctive-type membership.

Abstract: A meta-model for creating models of alternative physical representations of logically equivalent entities, such as alternative wire format representations of logically equivalent messages, includes a logical meta-model and a physical meta-model. The logical meta-model provides logical entity component classes for creating a logical model which describes, in a platform and programming language neutral manner (e.g. as an XML schema), the logical structure of the modeled entity as a hierarchy of logical entity components. The physical meta-model provides classes for creating a physical model which describes the alternative physical representations. The physical meta-model includes Base Classes representative of generic physical representations of the logical entity components, with “correspondence associations” being defined between the Base Classes and corresponding logical entity component classes.

Abstract: A method and apparatus for creating a schema definition from a language-specific metamodel of a data structure written in a legacy computer language involves walking through the nodes of the metamodel, and creating corresponding schema element objects in a schema tree that is serialized to create the schema definition. The creation of the schema element objects follows rules, and permits the definition of nested data structures having conjunctive-type and disjunctive-type membership.

Abstract: A method for synchronizing data files, the method comprising: within a messaging utility, associating a Web Service Definition Language (WSDL) definition with a data file, the association made by a passive reference between the WSDL definition to the data file; creating a reference table identifying WSDL files and referenced data files; determining if the WSDL file has changed, if the WSDL file has changed then: determining if a reference to a data file exists in the changed WSDL file; adding an entry in the reference table associating the WSDL file and the data file; launching a component of a builder application to build the data file; and determining if any additional references to data files exist in the changed WSDL file; determining if the data file has changed, if the data file has changed then: determining if the changed data file is referenced by a WSDL file by examining the reference table; if the changed data file exists in the reference table, then launching a component of the builder application

Abstract: A meta-model for creating models of alternative physical representations of logically equivalent entities, such as alternative wire format representations of logically equivalent messages, includes a logical meta-model and a physical meta-model. The logical meta-model provides logical entity component classes for creating a logical model which describes, in a platform and programming language neutral manner (e.g. as an XML schema), the logical structure of the modeled entity as a hierarchy of logical entity components. The physical meta-model provides classes for creating a physical model which describes the alternative physical representations. The physical meta-model includes Base Classes representative of generic physical representations of the logical entity components, with “correspondence associations” being defined between the Base Classes and corresponding logical entity component classes.

Abstract: A method and apparatus for creating a schema definition from a language-specific metamodel of a data structure written in a legacy computer language involves walking through the nodes of the metamodel, and creating corresponding schema element objects in a schema tree that is serialized to create the schema definition. The creation of the schema element objects follows rules, and permits the definition of nested data structures having conjunctive-type and disjunctive-type membership.