Abstract: Embodiments of the invention provide systems and methods for logging of messages in a development environment. More specifically, embodiments of the present invention provide dynamically adaptive logging of runtime messages generated by an application. These embodiments provide a way to handle the volume of information stored in the logs by dynamically changing the severity associated with generated messages based on previous code path execution. Embodiments can use a set of metrics to replace the usual static log level associated with the code by the developer. For example, such metrics can include but are not limited to a cost-based (storage volume on disk), an exception-based (weight increase in catch block), and/or a crowd-based (community can vote down noise). As a result, embodiments can provide more detailed information when the error is recurring for a particular user but without generating so much information as to make the log difficult to use.

Abstract: Embodiments of the invention provide systems and methods for logging of messages in a development environment. More specifically, embodiments of the present invention provide dynamically adaptive logging of runtime messages generated by an application. These embodiments provide a way to handle the volume of information stored in the logs by dynamically changing the severity associated with generated messages based on previous code path execution. Embodiments can use a set of metrics to replace the usual static log level associated with the code by the developer. For example, such metrics can include but are not limited to a cost-based (storage volume on disk), an exception-based (weight increase in catch block), and/or a crowd-based (community can vote down noise). As a result, embodiments can provide more detailed information when the error is recurring for a particular user but without generating so much information as to make the log difficult to use.

Abstract: Various techniques for providing product configuration as a Web Service are disclosed. One method involves receiving a Web Service signature requesting access to a product configuration session to configure a product and accessing information representing an instance of the product, in response to receipt of the Web Service signature. A responsive Web Service signature, containing information such as the price of the instance of the product, whether the instance of the product represents a valid configuration, and/or indicative of options available to further configure the product, can be returned to the application that requested access to the session. The requester can request multiple changes to the instance of the product, and validation of those changes can be delayed until after all of the changes have been applied (as opposed to each change being validated independently). A single configurator can handle requests received via multiple different sales channels.

Abstract: Various techniques for providing product versioning as a Web Service are disclosed. One method involves receiving a Web Service signature requesting access to a product model. In response to receipt of that Web Service signature, a product model that includes several versions of a product is accessed, and the current version of the product is selected from the product model. The product model can include future versions of he product that are not yet effective; such versions will not be selected as the current model prior to becoming effective. Information representing the current version can then be returned to the request in a second Web Service signature. A single object broker can respond to Web Service signatures requesting access to the product model from various different sales channels.

Abstract: Various systems and methods for integrating procedural logic with a stateless constraint engine are disclosed. One method involves accessing a first set of values generated by a stateless constraint engine based upon a first set of inputs and then accessing a second set of values generated by the stateless constraint engine subsequent to the first set of values and based upon a second set of inputs. The second set of values is validated based upon a procedural constraint. The procedural constraint can include a precondition and a postcondition. The precondition is dependent upon at least one value from the first set of values, and the postcondition is dependent upon at least one value from the second set of values.

Abstract: Various systems and methods for integrating procedural logic with a stateless constraint engine are disclosed. One method involves accessing a first set of values generated by a stateless constraint engine based upon a first set of inputs and then accessing a second set of values generated by the stateless constraint engine subsequent to the first set of values and based upon a second set of inputs. The second set of values is validated based upon a procedural constraint. The procedural constraint can include a precondition and a postcondition. The precondition is dependent upon at least one value from the first set of values, and the postcondition is dependent upon at least one value from the second set of values.

Abstract: Various systems and methods for integrating procedural logic with a stateless constraint engine are disclosed. One method involves accessing a first set of values generated by a stateless constraint engine based upon a first set of inputs and then accessing a second set of values generated by the stateless constraint engine subsequent to the first set of values and based upon a second set of inputs. The second set of values is validated based upon a procedural constraint. The procedural constraint can include a precondition and a postcondition. The precondition is dependent upon at least one value from the first set of values, and the postcondition is dependent upon at least one value from the second set of values.

Abstract: Various techniques for providing product configuration as a Web Service are disclosed. One method involves receiving a Web Service signature requesting access to a product configuration session to configure a product and accessing information representing an instance of the product, in response to receipt of the Web Service signature. A responsive Web Service signature, containing information such as the price of the instance of the product, whether the instance of the product represents a valid configuration, and/or indicative of options available to further configure the product, can be returned to the application that requested access to the session. The requester can request multiple changes to the instance of the product, and validation of those changes can be delayed until after all of the changes have been applied (as opposed to each change being validated independently). A single configurator can handle requests received via multiple different sales channels.

Abstract: Various techniques for providing product versioning as a Web Service are disclosed. One method involves receiving a Web Service signature requesting access to a product model. In response to receipt of that Web Service signature, a product model that includes several versions of a product is accessed, and the current version of the product is selected from the product model. The product model can include future versions of he product that are not yet effective; such versions will not be selected as the current model prior to becoming effective. Information representing the current version can then be returned to the request in a second Web Service signature. A single object broker can respond to Web Service signatures requesting access to the product model from various different sales channels.

Abstract: Various systems and methods for integrating procedural logic with a stateless constraint engine are disclosed. One method involves accessing a first set of values generated by a stateless constraint engine based upon a first set of inputs and then accessing a second set of values generated by the stateless constraint engine subsequent to the first set of values and based upon a second set of inputs. The second set of values is validated based upon a procedural constraint. The procedural constraint can include a precondition and a postcondition. The precondition is dependent upon at least one value from the first set of values, and the postcondition is dependent upon at least one value from the second set of values.