| sskarupa |
| Newbie |
|
| US |
|
|
| None Specified |
|
| Friday, December 30, 2005 |
| Friday, December 30, 2005 2:27:38 PM |
2
[0.01% of all post / 0.00 posts per day] |
|
I think I solved this one myself. Just need to stay away from the Schema/WSDL view and set the filetype for xsd and wsdl to always open in text view.
Still seems like a bug but as long as I can continue to work without it messing up my code I'm happy.
Steps to fix:
> Select Tools menu
> Select Options menuitem
> Select File types tab
> Select .xsd in the file type list box
> Select Text view option in the Default view section
> Click Apply button
> Click OK button
-Steve
|
I'm relatively new to XMLSpy but I am struggling with something that seems pretty fundemental.
In the Text view for a schema I have defined the following element:
Code:<xs:element name="GetInternalAccountById">
<xs:complexType>
<xs:sequence>
<xs:element name="internalAccountId" type="xs:long minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
I then save the document, close the document and then reopen. It automatically reopens in the Schema/WSDL view and because I perfer to work in the raw text I switch to the Text view.
In the Text view I see the following:
Code:<xs:element name="GetInternalAccountById">
<xs:complexType>
<xs:sequence>
<xs:element name="internalAccountId" type="xs:long"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Notice that the minOccurs and maxOccurs attributes are now removed... What is going on?
Note: this also happens for the name attribute of an input node in the bindings section of a WSDL too.
I am running XMLSpy Enterprise Edition Version 2005 rel. 3.
Any thoughts?
-Steve
For
|
|
