[jira] [Comment Edited] (XMLBEANS-490) XML tag is not created for [minOccurs=1 and nillable=false]
[ https://issues.apache.org/jira/browse/XMLBEANS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13460733#comment-13460733 ] Yuriy Glushanin edited comment on XMLBEANS-490 at 9/22/12 6:49 AM: --- Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message becouse of default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message becouse of default value for 'nillable' attribute is false. Could you tell me please: - Why first XML message does not contains notificationId tag? - Why second XML message contains notificationId tag marked as nillable? Thank you in advance, Yuriy. was (Author: yuriypalych): Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question because of it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message becouse of default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message becouse of default value for 'nillable' attribute is false. Could you tell me please: - Why first XML message does not contains notificationId tag? - Why second XML message contains
[jira] [Comment Edited] (XMLBEANS-490) XML tag is not created for [minOccurs=1 and nillable=false]
[ https://issues.apache.org/jira/browse/XMLBEANS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13460733#comment-13460733 ] Yuriy Glushanin edited comment on XMLBEANS-490 at 9/22/12 6:52 AM: --- Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why first XML message does not contains notificationId tag? - Why second XML message contains notificationId tag marked as nillable? Thank you in advance, Yuriy. was (Author: yuriypalych): Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message becouse of default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message becouse of default value for 'nillable' attribute is false. Could you tell me please: - Why first XML message does not contains notificationId tag? - Why second XML message contains notificationId tag marked
[jira] [Comment Edited] (XMLBEANS-490) XML tag is not created for [minOccurs=1 and nillable=false]
[ https://issues.apache.org/jira/browse/XMLBEANS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13460733#comment-13460733 ] Yuriy Glushanin edited comment on XMLBEANS-490 at 9/22/12 6:54 AM: --- Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why doesn't first XML message contain notificationId tag? - Why does second XML message contain notificationId tag marked as nillable? Thank you in advance, Yuriy. was (Author: yuriypalych): Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why does first XML message contain no notificationId tag? - Why does second XML message contain notificationId tag marked as
[jira] [Comment Edited] (XMLBEANS-490) XML tag is not created for [minOccurs=1 and nillable=false]
[ https://issues.apache.org/jira/browse/XMLBEANS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13460733#comment-13460733 ] Yuriy Glushanin edited comment on XMLBEANS-490 at 9/22/12 7:07 AM: --- Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why doesn't first XML message contain notificationId tag? - Why does second XML message contain notificationId tag marked as nillable? Thank you in advance, Yuriy. was (Author: yuriypalych): Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why doesn't first XML message contain notificationId tag? - Why does second XML message contain notificationId tag marked as nillable? Thank you in advance, Yuriy. XML tag is not created for [minOccurs=1 and nillable=false] --- Key: XMLBEANS-490 URL: https://issues.apache.org/jira/browse/XMLBEANS-490 Project: XMLBeans Issue Type: Bug Affects Versions: Version 2.3 Reporter: Yuriy
[jira] [Comment Edited] (XMLBEANS-490) XML tag is not created for [minOccurs=1 and nillable=false]
[ https://issues.apache.org/jira/browse/XMLBEANS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13460733#comment-13460733 ] Yuriy Glushanin edited comment on XMLBEANS-490 at 9/22/12 7:39 AM: --- Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why doesn't first XML message contain notificationId tag? - Why does second XML message contain notificationId tag marked as nillable? And main question - what should I do to create the following message: customerChangeNotificationRequest trackingInformation notificationId / /trackingInformation /customerChangeNotificationRequest Thank you in advance, Yuriy. was (Author: yuriypalych): Hi, Wing Yew Poon! Unfortunately, I am not able to provide java code for my initial question as it is a web service and we use maven to compile webservice stubs from WSDL/XSD, ets. But I have the same problem with other XSD and I can provide you with the information you need. My other XSD: xs:complexType name=CustomerChangeNotificationRequest xs:sequence xs:element name=trackingInformation minOccurs=0 xs:complexType xs:sequence xs:element name=notificationId type=xs:string / My first Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); System.out.println(document); First logs: customerChangeNotificationRequest trackingInformation/ /customerChangeNotificationRequest From my point of view, it is not valid XML message because default value for 'minOccurs' attribute is 1. I expect notificationId tag in the message. My second Java example: CustomerChangeNotificationRequestDocument document = CustomerChangeNotificationRequestDocument.Factory.newInstance(); CustomerChangeNotificationRequest request = document.addNewCustomerChangeNotificationRequest(); TrackingInformation trackingInformation = request.addNewTrackingInformation(); trackingInformation.setNotificationId(null); System.out.println(document); Second logs: customerChangeNotificationRequest trackingInformation notificationId xsi:nil=true/ /trackingInformation /customerChangeNotificationRequest It is also not valid XML message because default value for 'nillable' attribute is false. Could you tell me please: - Why doesn't first XML message contain notificationId tag? - Why does second XML message contain notificationId tag marked as nillable? Thank you in advance, Yuriy. XML tag is not created for [minOccurs=1 and nillable=false]