wsdlpull-discussion — Discussion related to the WSDL parser

[Wsdlpull-discussion] installation questions: libcurl

[Stéphane C. <ste...@gm...>]

Looking to install wsdlpull on Ubuntu 10.10.  I do have curl installed, but
running wsdlpull's "./configure" reports:

checking for getopt_long... yes
checking for curl_easy_init in -lcurl... no
configure: WARNING: curl is needed for HTTP GET/POST
configure: creating ./config.status
config.status: creating Makefile

Trying to run wsdlpull from the command-line results in:

    libcurl needs to be installed to proceed with invocation
    Try using the -g option to just print the soap message

Anyone happen to know what else I'm missing?  This is the version of curl I
have:

$ dpkg -l | grep curl
ii  curl
7.19.7-1ubuntu1                                 Get a file from an HTTP,
HTTPS or FTP server
ii  gnupg-curl
1.4.10-2ubuntu1                                 GNU privacy guard - a free
PGP replacement (
ii  libcurl3
7.19.7-1ubuntu1                                 Multi-protocol file transfer
library (OpenSS
ii  libcurl3-gnutls
7.19.7-1ubuntu1                                 Multi-protocol file transfer
library (GnuTLS
ii  libwww-curl-perl
4.11-1                                          Perl bindings to libcurl
ii  python-pycurl                        7.19.0-3

Thanks for any hints.

Stéphane

[Wsdlpull-discussion] Restrict validation in SchemaValidator class

[Marek D. <mar...@gm...>]

Hi,
There is a problem in our client with response validation. We did research
and we are almost sure that schema validator should pass response like this
<tag attribute="" />, but unfortunately we have found code in
SchemaValidator.cpp file:

874 /*  875 Check for the correctness of each attribute  876 */  877 string
> attVal = xpp->getAttributeValue("", at->getName());  878 if (attVal.empty
> ())  879 {  880 if (at->isRequired())  881 error("Required attribute \"" +
> at->getName() +  882 "\" missing or empty",xpp);  883
>  884 else  885 continue;  886 }

If you have any information about such restrict validation could you give us
a note? All links we looked says that empty strings fits even for required
attributes.

-- 
z pozdrowieniami
Marek Daniluk

[Wsdlpull-discussion] xml validation against wsdl file

[Gilles B. <gil...@gm...>]

Hi,

I want to catch xml and validate it with a wsdl file but i'm starting in web
services development and i don't understand very well the code. I don't know
if this library can do that and if it's possible, how.

Thanks for your attention

[Wsdlpull-discussion] Parsing WSDL

[Jacob P. <Jac...@fo...>]

Hello

I'm having problems parsing loads of Web Services while others work fine.

Problem is that no operations are found.

I have attached a WSDL file containing just one function. Visual Studio and SOAPUI can parse this WSDL file, but not WSDLPull.

Simple example code:

	WsdlInvoker invoker(wsdlstream);
	int numberOfOperations = invoker.getOperations(operations);

Operations count returned equals 0.

Not that I know the WSDL specification nor the WSDLPull sourcecode, I found the following when debugging a little:

- The constructor never calls init(wParser_) because no element has status set. No idea if this is normal or not.
- Operations seems only to be read in init which explains why count is 0.

So question is;

Is there a bug in WSDLPull or am missing something in my example, to be able to parse the remaining WSDLfiles?

Other example is the WSDL file for Microsoft Exchange which does not work either, but for Microsoft SharePoint it works fine.

NB! WSDLPull was not compiled with CURL since I only need the parsing of WSDL not invoking any methods. Hopefully this is not why some fails?


Thanks for any pointers!

Best regards,
Jacob Pedersen

[Wsdlpull-discussion] error Unable to locate file /usr/local/share/wsdlpull/soap.xsd

[Danette C. <dc...@gc...>]

I get this error even though I am at root.  I test and the file is exactly
where it should be.  Help..

 

Danette Cross

GCS Research

Senior Geospatial Developer

115 South 4th Street West

Missoula, Montana 59801

Office 406-541-3261

Direct 406-541-3276

Mobile 406-546-1706

 

[Wsdlpull-discussion] Broken on Debian unstable: missing includes and wsdl tool broken

[Tim <tim...@se...>]

I'm not sure how it even builds on Fedora, but under Debian it's
missing includes in several .cpp files.  I've attached a patch against
1.23 which represents what I changed to get it to build.  Of course to
make it compatible on other platforms, you may need to tweak ifdefs
and such.

In addition, I can't seem to get the wsdl tool to work.  Just trying
to list some methods and I get:

> wsdl -l https://example.org/Service?wsdl
Error processing https://example.org/Service?wsdl
WsdlParser Exception : Error parsing the schema for the namespace http://schemas.xmlsoap.org/wsdl/soap/
Unable to locate the file /usr/local/share/wsdlpull/soap.xsd
 at 1,273


Unfortunately I can't share the real URL to the wsdl.  It seems like
there's a problem with the soap.xsd, but this file is definitely
installed in the path it indicates.

thoughts?

tim

PS- please be sure to CC me as I'm not on the list.

[Wsdlpull-discussion] fault names

[Irina L. <il...@od...>]

Hello, wsdlpull-discussion.

1. I have fixed a little bug in
bool
WsdlParser::getOperations(const Qname & portType,
                          Operation::cOpIterator _&_begin,
                          Operation::cOpIterator _&_end);
  Iterators are passed to function by value instead of by reference.
  
2. WSDL has fault name in wsdl:operation, but wsdlpull
haven't support it. Are you going to implement this features. If it
possible, I can send you realization as I see it.

3. As I understand, Schema::Element doesn't contain it's namespace,
May be it is better to replace 'std::string elemName' with 'Qname elemName'.

All the best,Irina.

[Wsdlpull-discussion] atomic types

[Irina L. <il...@od...>]

Hello,wsdlpull-discussion.

 There is Schema::XSDType::getBaseTypeId() function in wsdlpull. It
 returns basic schema type id for existent types. But we can't get
 XSDType for the atomic types, so we can't define basic type for
 atomic one. (For example, the xsd:short is the basic type of xsd:byte).

I see an answer in this idea: contain XSDTypes for atomic types in
Schema::TypesTable. What do you think.

All the best, Irina.

[Wsdlpull-discussion] first letter

[Irina L. <il...@od...>]

Irina