I erroneously added jms message properties for jms message in wsdl binding as below:
    <binding name="CorrtestBinding" type="tns:CorrtestPortType">
        <jms:binding/>
        <wsdl:operation name="CorrtestOperation">
            <jms:operation destination="Queue1" destinationType="Queue"/>
            <wsdl:input name="input1">
                <jms:message messageType="TextMessage" textPart="part1"/>
                <jms:properties>
                        <jms:property part="IdProperty" type="long"
name="correlationId"></jms:property>
                </jms:properties>                  
            </wsdl:input>
        </wsdl:operation>
    </binding>

The validation did not complain. The above definition of input message is
incorrect, the correct definition of message property in binding should be as
below (jms properties to be child of jms message):
    <binding name="binding1" type="tns:CorrtestPortType1">
        <jms:binding/>
        <wsdl:operation name="CorrtestOperation">
            <jms:operation destination="Queue2"
destinationType="Queue"></jms:operation>
            <wsdl:input name="input1">
                <jms:message messageType="TextMessage" textPart="part1">
                    <jms:properties>
                        <jms:property part="IdProperty" type="long"
name="correlationId"></jms:property>
                    </jms:properties>                
                </jms:message>
            </wsdl:input>
        </wsdl:operation>
    </binding>

Please note that if the editor is used, it places the jms properties correctly
under the jms message element. 

Since the user could hand code the wsdl, the wsdl validation need to catch this
as error and report appropriately.