← Prev in month
← Prev in thread
Next in thread →
Next in month →
Proposed resolution to issue BINDINGS-68
Proposed resolution to remove the UPA error. The issue being that within the choice element we currently have one case with an optional destination and one with mandatory. Current schema for request is as follows, which shows that connectionFactory and activationSpec are mutually exclusive, destination is optional with activationSpec and mandatory with connectionFactory: <choice minOccurs="0" maxOccurs="1"> <sequence> <element name="destination" type="sca:JMSDestination"/> <element name="connectionFactory" type="sca:JMSConnectionFactory"/> </sequence> <sequence> <element name="destination" type="sca:JMSDestination" minOccurs="0"/> <element name="activationSpec" type="sca:JMSActivationSpec"/> </sequence> </choice> Proposal is to retain the mutual exclusivity of connectionFactory and activationSpec, but remove the destination from the choice and just make it optional, with the conformance statements making it mandatory for connectionFactory. So the proposal is to replace the above choice element in the binding.jms element schema in Appendix A with the following: <element name="destination" type="sca:JMSDestination" minOccurs="0"/> <choice minOccurs="0" maxOccurs="1"> <element name="connectionFactory" type="sca:JMSConnectionFactory"/> <element name="activationSpec" type="sca:JMSActivationSpec"/> </choice> No other updates to the document are proposed. Regards, Simon Simon Holdsworth STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898 Internet - Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
← Prev in month
← Prev in thread
Next in thread →
Next in month →