- This topic has 2 replies, 2 voices, and was last updated 16 years, 3 months ago by
nsoule.
-
AuthorPosts
-
nsouleMemberHello, I’m creating documentation within a node like below:
<wsdl:documentation>
for a wsdl. The documentation is written in sentence form. When I right click and select Source->Format the text in those comments seems to be formatted in a very odd way. Many words (short words included) end up on a line by themselves and all the lines seem to be of arbitrary length (I have the preference set at the default of 72 characters). Is there anything I can do to have this text format in a more visually acceptable way?
Also, in some circumstances I can select format multiple times in a row and get a different format each time.
Thank you.
-Nate
April 7, 2009 at 10:47 am #297296
Loyal WaterMemberNate,
Could you please paste a file here for us and list down the steps to help us reproduce this issue at our end. I’ll get this checked right away.April 10, 2009 at 10:04 am #297424
nsouleMemberHi Nipun. If you format the wsdl below once things look ok. If you then format it again it starts to put single words by themselves on a line. I’ve seen other cases where that incorrect formatting occurs on the first attempt. Thanks.
-Nate
<?xml version=”1.0″ encoding=”UTF-8″?>
<wsdl:definitions xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”
xmlns:tns=”http://www.example.org/NewWSDLFile/” xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/”
xmlns:xsd=”http://www.w3.org/2001/XMLSchema” name=”NewWSDLFile”
targetNamespace=”http://www.example.org/NewWSDLFile/”>
<wsdl:types>
<xsd:schema targetNamespace=”http://www.example.org/NewWSDLFile/”>
<xsd:element name=”NewOperation”>
<xsd:complexType>
<xsd:sequence>
<xsd:element name=”in” type=”xsd:string” />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name=”NewOperationResponse”>
<xsd:complexType>
<xsd:sequence>
<xsd:element name=”out” type=”xsd:string” />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name=”NewOperationRequest”>
<wsdl:part element=”tns:NewOperation” name=”parameters” />
</wsdl:message>
<wsdl:message name=”NewOperationResponse”>
<wsdl:part element=”tns:NewOperationResponse” name=”parameters” />
</wsdl:message>
<wsdl:portType name=”NewWSDLFile”>
<wsdl:operation name=”NewOperation”><wsdl:documentation>
This is some text. Text text text. Typing some text. More text. This is
is sample text to demonstrate issues with wrapping.
This is a 2nd line. To generate the line break I pressed Enter on the
keyboard. Text text text.
</wsdl:documentation>
<wsdl:input message=”tns:NewOperationRequest” />
<wsdl:output message=”tns:NewOperationResponse” />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name=”NewWSDLFileSOAP” type=”tns:NewWSDLFile”>
<soap:binding style=”document”
transport=”http://schemas.xmlsoap.org/soap/http” />
<wsdl:operation name=”NewOperation”>
<soap:operation soapAction=”http://www.example.org/NewWSDLFile/NewOperation” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name=”NewWSDLFile”>
<wsdl:port binding=”tns:NewWSDLFileSOAP” name=”NewWSDLFileSOAP”>
<soap:address location=”http://www.example.org/” />
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
AuthorPosts