Description: spelling fixes
Origin: vendor
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2016-05-29
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=114805
Bug: https://rt.cpan.org/Ticket/Display.html?id=114805
--- a/lib/SOAP/WSDL.pm
+++ b/lib/SOAP/WSDL.pm
@@ -668,7 +668,7 @@
=head2 Debugging / Tracing
While SOAP::Lite features a global tracing facility, SOAP::WSDL
-allows to switch tracing on/of on a per-object base.
+allows one to switch tracing on/of on a per-object base.
This has to be done in the SOAP client used by SOAP::WSDL - see
L<get_client|get_client> for an example and L<SOAP::WSDL::Client> for
@@ -737,7 +737,7 @@
=item * Serialization of hash refs does not work for ambiguous values
-If you have list elements with multiple occurences allowed, SOAP::WSDL
+If you have list elements with multiple occurrences allowed, SOAP::WSDL
has no means of finding out which variant you meant.
Passing in item => [1,2,3] could serialize to
@@ -811,7 +811,7 @@
Martin Kutter wrote:
-There are many people out there who fostered SOAP::WSDL's developement.
+There are many people out there who fostered SOAP::WSDL's development.
I would like to thank them all (and apologize to all those I have forgotten).
Giovanni S. Fois wrote a improved version of SOAP::WSDL (which eventually
@@ -838,7 +838,7 @@
testing. Thank you.
Noah Robin contributed lots of documentation fixes, and the mod_perl server,
-and eventually joined SOAP::WSDL's developement. Thanks.
+and eventually joined SOAP::WSDL's development. Thanks.
Mark Overmeer wrote XML::Compile::SOAP - competition is good for business.
--- a/lib/SOAP/WSDL/Expat/MessageParser.pm
+++ b/lib/SOAP/WSDL/Expat/MessageParser.pm
@@ -297,7 +297,7 @@
=head2 Skipping unwanted items
-Sometimes there's unneccessary information transported in SOAP messages.
+Sometimes there's unnecessary information transported in SOAP messages.
To skip XML nodes (including all child nodes), just edit the type map for
the message, set the type map entry to '__SKIP__', and comment out all
--- a/lib/SOAP/WSDL/Manual/CodeFirst.pod
+++ b/lib/SOAP/WSDL/Manual/CodeFirst.pod
@@ -71,7 +71,7 @@
Perl does not have the concept of interfaces. However, Moose provides Roles, which can be used for defining
interfaces.
-However, it's not really necessary to define a interface Interface (in the sense of a Jave interface) -
+However, it's not really necessary to define a interface Interface (in the sense of a Java interface) -
a interface class is sufficient.
Subroutine attributes could be used for providing additional information - attributes in perl are much like
--- a/lib/SOAP/WSDL/Manual/Cookbook.pod
+++ b/lib/SOAP/WSDL/Manual/Cookbook.pod
@@ -101,7 +101,7 @@
If you're talking to a Server using NTLMv2 exclusively, you will only the first line
in the debug output, and then an error.
-To explicitely enable NTLMv2, do the following in your client:
+To explicitly enable NTLMv2, do the following in your client:
use Authen::NTLM;
ntlmv2(1);
@@ -117,7 +117,7 @@
this is implementation specific (MIT or Heimdahl). See your Kerberos/GSSAPI
documentation for details.
-(Newer) Windows Web Services usually allow to use both the Negotiate (Kerberos)
+(Newer) Windows Web Services usually allow one to use both the Negotiate (Kerberos)
and NTLM authentication scheme.
=head3 Accessing HTTPS webservices protected by certificate authentication
@@ -156,7 +156,7 @@
How do I do this using SOAP::WSDL?
-A: The following steps are neccessary to achieve this result:
+A: The following steps are necessary to achieve this result:
First, you would need to write a new serializer, which is quite easy, as it
just creates the envelope and calls ->serialize_qualified() on $header and
@@ -214,7 +214,7 @@
=head2 Disabling strict XML processing in a CGI based server
-You have to set the deserializer in the transport class explicitely to
+You have to set the deserializer in the transport class explicitly to
a L<SOAP::WSDL::Deserializer|SOAP::WSDL::Deserializer> object with the
C<strict> option set to 0.
--- a/lib/SOAP/WSDL/Manual/FAQ.pod
+++ b/lib/SOAP/WSDL/Manual/FAQ.pod
@@ -64,7 +64,7 @@
Its SOAP message parser however, is not namespace sensitive but uses the
pre-shared information from the WSDL for looking up what each XML node means.
-SOAP::WSDL can parse SOAP messages including namespace informations up to the
+SOAP::WSDL can parse SOAP messages including namespace information up to the
point where equally named elements from different namespaces may appear at
the same position.
--- a/lib/SOAP/WSDL/Manual/Parser.pod
+++ b/lib/SOAP/WSDL/Manual/Parser.pod
@@ -75,7 +75,7 @@
=head3 Skipping unwanted items
-Sometimes there's unneccessary information transported in SOAP messages.
+Sometimes there's unnecessary information transported in SOAP messages.
To skip XML nodes (including all child nodes), just edit the type map for
the message and set the type map entry to '__SKIP__'.
--- a/lib/SOAP/WSDL/Manual/XSD.pod
+++ b/lib/SOAP/WSDL/Manual/XSD.pod
@@ -316,7 +316,7 @@
starting with "xml" (case-insensitive).
All XML attributes for a XML element are set- and retrievable via the method
-C<attr>. The name is chosen to allow mimicing SOAP::Lite's behaviour, which
+C<attr>. The name is chosen to allow mimicking SOAP::Lite's behaviour, which
allows setting a SOAP::Data object's attributes via C<attr>.
my $attrSet = $obj->attr();
@@ -424,7 +424,7 @@
=item * fractionDigits
-=item * lenght
+=item * length
=item * maxExclusive
--- a/lib/SOAP/WSDL/Manual/Glossary.pod
+++ b/lib/SOAP/WSDL/Manual/Glossary.pod
@@ -16,7 +16,7 @@
SOAP is a W3C recommendation. The latest version of the SOAP specification
may be found at L<http://www.w3.org/TR/soap/>.
-SOAP defines a protocoll for message exchange between applications.
+SOAP defines a protocol for message exchange between applications.
The most popular usage is to use SOAP for remote procedure calls (RPC).
While one of the constituting aspects of a web service is its
--- a/lib/SOAP/WSDL/Server/Simple.pm
+++ b/lib/SOAP/WSDL/Server/Simple.pm
@@ -129,7 +129,7 @@
=head1 DESCRIPTION
Lightweight SOAP server for use with HTTP::Server::Simple, mainly designed
-for testing purposes. It allows to set up a simple SOAP server without having
+for testing purposes. It allows one to set up a simple SOAP server without having
to configure CGI or mod_perl stuff.
SOAP::WSDL::Server::Simple is not recommended for production use.
--- a/lib/SOAP/WSDL/Manual/WS_I.pod
+++ b/lib/SOAP/WSDL/Manual/WS_I.pod
@@ -129,7 +129,7 @@
A fault is generated when an error occurs processing the message.
SOAP::WSDL::Deserializer::SOAP11 does not perform any additional processing
-after an error occured.
+after an error occurred.
=head2 R1029
@@ -429,7 +429,7 @@
The wsdl:import element imports the referenced WSDL definition.
-This is rather hard-wired and does not allow to specify a wsdl:import without
+This is rather hard-wired and does not allow one to specify a wsdl:import without
a resolvable location in SOAP::WSDL.
=head2 R4002
@@ -492,7 +492,7 @@
A DESCRIPTION MAY use any construct from XML Schema 1.0.
-SOAP::WSDL's WSDL parser doen not allow all contructs from XML Schema 1.0 to
+SOAP::WSDL's WSDL parser doen not allow all constructs from XML Schema 1.0 to
be used.
TODO become "minimal conformant".
--- a/example/lib/MyInterfaces/FullerData_x0020_Fortune_x0020_Cookie/FullerData_x0020_Fortune_x0020_CookieSoap.pm
+++ b/example/lib/MyInterfaces/FullerData_x0020_Fortune_x0020_Cookie/FullerData_x0020_Fortune_x0020_CookieSoap.pm
@@ -177,7 +177,7 @@
You may pass any combination of objects, hash and list refs to these
methods, as long as you meet the structure.
-List items (i.e. multiple occurences) are not displayed in the synopsis.
+List items (i.e. multiple occurrences) are not displayed in the synopsis.
You may generally pass a list ref of hash refs (or objects) instead of a hash
ref - this may result in invalid XML if used improperly, though. Note that
SOAP::WSDL always expects list references at maximum depth position.
--- a/lib/SOAP/WSDL/Deserializer/Hash.pm
+++ b/lib/SOAP/WSDL/Deserializer/Hash.pm
@@ -98,7 +98,7 @@
}
}
-List reference creation is triggered by the second occurance of an element.
+List reference creation is triggered by the second occurrence of an element.
XML Array types with one element only will not be represented as list
references.
--- a/lib/SOAP/WSDL/Generator/Template/XSD/Interface/POD/method_info.tt
+++ b/lib/SOAP/WSDL/Generator/Template/XSD/Interface/POD/method_info.tt
@@ -6,7 +6,7 @@
You may pass any combination of objects, hash and list refs to these
methods, as long as you meet the structure.
-List items (i.e. multiple occurences) are not displayed in the synopsis.
+List items (i.e. multiple occurrences) are not displayed in the synopsis.
You may generally pass a list ref of hash refs (or objects) instead of a hash
ref - this may result in invalid XML if used improperly, though. Note that
SOAP::WSDL always expects list references at maximum depth position.
--- a/lib/SOAP/WSDL/Generator/Template/XSD/complexType/POD/choice.tt
+++ b/lib/SOAP/WSDL/Generator/Template/XSD/complexType/POD/choice.tt
@@ -3,7 +3,7 @@
[%- IF complexType.get_name %] # [% XSD.create_xsd_name(complexType) %][% END %]
[%- indent = indent _ ' ' %]
[% indent %]# One of the following elements.
-[% indent %]# No occurance checks yet, so be sure to pass just one...
+[% indent %]# No occurrence checks yet, so be sure to pass just one...
[%- FOREACH element = complexType.get_element %]
[% indent %][% XSD.perl_var_name(XSD.element_name(element)) %] => [% INCLUDE element/POD/structure.tt -%]
[% END %]
--- a/lib/SOAP/WSDL/Generator/Visitor.pm
+++ b/lib/SOAP/WSDL/Generator/Visitor.pm
@@ -58,7 +58,7 @@
described by [GHJV1995].
A Visitor is an object implementing some behaviour for a fixed set of classes,
-whose implementation would otherwise need to be scattered accross those
+whose implementation would otherwise need to be scattered across those
classes' implementations.
Visitors are usually combined with Iterators for traversing either a list or
@@ -182,7 +182,7 @@
Both Type Classes and Interface Classes include documentation. Additional
documentation may be generated as a hint for programmers, or later for
-mimicing .NET's .asmx example pages.
+mimicking .NET's .asmx example pages.
=back
--- a/lib/SOAP/WSDL/Manual.pod
+++ b/lib/SOAP/WSDL/Manual.pod
@@ -178,7 +178,7 @@
);
The lines are hash key - value pairs. The keys are the XPath expressions
-without occurence numbers (like [1]) relative to the Body element.
+without occurrence numbers (like [1]) relative to the Body element.
Namespaces are ignored.
If you don't know about XPath: They are just the names of the XML tags,
--- a/lib/SOAP/WSDL/Transport/Test.pm
+++ b/lib/SOAP/WSDL/Transport/Test.pm
@@ -76,7 +76,7 @@
SOAP::WSDL::Transport::Test is a file-based test transport backend for
SOAP::WSDL.
-When SOAP::WSDL::Transport::Test is used as transport backend, the reponse is
+When SOAP::WSDL::Transport::Test is used as transport backend, the response is
read from a XML file and the request message is discarded. This is
particularly useful for testing SOAP::WSDL plugins.
--- a/lib/SOAP/WSDL/XSD/Typelib/Element.pm
+++ b/lib/SOAP/WSDL/XSD/Typelib/Element.pm
@@ -159,7 +159,7 @@
for the {http://www.w3.org/2001/XMLSchema-instance}nil="true" attribute
is hardcoded as 'xsi'.
-You should definitly provide your XML envelope generator with the same prefix
+You should definitely provide your XML envelope generator with the same prefix
namespace combination (Default for SOAP::WSDL::Envelope).
=back
--- a/bin/wsdl2perl.pl
+++ b/bin/wsdl2perl.pl
@@ -163,7 +163,7 @@
=head1 OPTIONS
- NAME SHORT DESCRITPION
+ NAME SHORT DESCRIPTION
----------------------------------------------------------------------------
prefix p Prefix for all generated classes. If you set "-p=Foo",
you will get "FooAttributes", "FooTypes",