node.js - Nodejs: npm SOAP: unexpected tag in body, args -


"solved": bug in github package

i used read-me of node-soap git have unexpected problem: see 'requestcontext'-tag bellow.

var args = {readenterprisebyphoneme: {"phoneme":"a", "typeofenterprise": "epp", "activefilter":"true"}}; var url = 'http://kbopub-acc.economie.fgov.be/kbopubws030000/services/wskbopub?wsdl'; soap.createclient(url,function(err, client){   client.setsecurity(new soap.wssecurity('username', 'password', 'passworddigest'));   client.addsoapheader({'id': 'c1576d0a-e762-40fe-abf9-ec3f2102650b', 'language': 'nl'});   console.log('log:');   console.log(client.describe().wskbopubservice.wskbopub.readenterprisebyphoneme);   client.wskbopubservice.wskbopub.readenterprisebyphoneme(args, function(err, response){     if(err){         console.log('soap error!');         //console.log(err);     }else{         console.log('soap success!');         console.log(response);     }   }); });

with console response (unexpected tags manually flagged):

<soap:envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"  xmlns:tns="http://economie.fgov.be/kbopub/webservices/v1" xmlns:messages="http://economie.fgov.be/kbopub/webservices/v1/messages">   <soap:header>     <id>c1576d0a-e762-40fe-abf9-ec3f2102650b</id>     <language>nl</language>     <wsse:security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">       <wsu:timestamp wsu:id="timestamp-2015-08-24t22:45:18z">         <wsu:created>2015-08-24t22:45:18z</wsu:created>         <wsu:expires>2015-08-24t22:55:18z</wsu:expires>       </wsu:timestamp>       <wsse:usernametoken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:id="securitytoken-2015-08-24t22:45:18z">         <wsse:username>username</wsse:username>         <wsse:password type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#passworddigest">passwopapassword</wsse:password>         <wsse:nonce encodingtype="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#base64binary">y5ap7wca16hcluv0n2weepumaqw=</wsse:nonce>         <wsu:created>2015-08-24t22:45:18z</wsu:created>       </wsse:usernametoken>     </wsse:security>   </soap:header>   <soap:body>     **<messages:requestcontext xmlns:messages="http://economie.fgov.be/kbopub/webservices/v1/messages" xmlns="http://economie.fgov.be/kbopub/webservices/v1/messages">**       <messages:readenterprisebyphoneme>         <messages:phoneme>a</messages:phoneme>         <messages:typeofenterprise>epp</messages:typeofenterprise>         <messages:activefilter>true</messages:activefilter>       </messages:readenterprisebyphoneme>     **</messages:requestcontext>**   </soap:body> </soap:envelope>

does has idea on why these appear , how avoid these?

are sure problem? maybe node generated in accordance wsdl? can't sure, wsdl address gave not working.


-

Comments

Post a Comment

Popular posts from this blog

java - UnknownEntityTypeException: Unable to locate persister (Hibernate 5.0) -

Image
in code below when try execute main.java getting exception: exception in thread "main" org.hibernate.unknownentitytypeexception: unable locate persister: com.np.vta.test.pojo.users @ org.hibernate.internal.sessionfactoryimpl.locateentitypersister(sessionfactoryimpl.java:792) @ org.hibernate.internal.sessionimpl.locateentitypersister(sessionimpl.java:2637) @ org.hibernate.internal.sessionimpl.access$2500(sessionimpl.java:164) @ org.hibernate.internal.sessionimpl$identifierloadaccessimpl.<init>(sessionimpl.java:2575) @ org.hibernate.internal.sessionimpl$identifierloadaccessimpl.<init>(sessionimpl.java:2562) @ org.hibernate.internal.sessionimpl.byid(sessionimpl.java:1044) @ org.hibernate.internal.sessionimpl.get(sessionimpl.java:955) @ com.app.test.main.main(main.java:20) but if uncomment cfg.addclass( users.class ).addresource( "com/np/vta/test/pojo/users.hbm.xml" ); code works fine. why not reading <mapping...
Read more

python - ValueError: empty vocabulary; perhaps the documents only contain stop words -

i'm using (for first time) scikit library , got error: valueerror: empty vocabulary; perhaps documents contain stop words file "c:\users\a605563\desktop\velibprojetpreso\traitementtwitterdico.py", line 33, in <module> x_train_counts = count_vect.fit_transform(filetweets) file "c:\python27\lib\site-packages\sklearn\feature_extraction\text.py", line 804, in fit_transform self.fixed_vocabulary_) file "c:\python27\lib\site-packages\sklearn\feature_extraction\text.py", line 751, in _count_vocab raise valueerror("empty vocabulary; perhaps documents contain stop words but don't understand why that's happening. import sklearn sklearn.feature_extraction.text import countvectorizer import pandas pd import numpy import unicodedata import nltk tweetsfile = open('tweets2015-08-13.csv', 'r+') f2 = open('analyzer.txt', 'a') print tweetsfile.readline() count_vect = countvectorizer(strip_accents='ascii...
Read more

ubuntu - collect2: fatal error: ld terminated with signal 9 [Killed] -

Image
i'm trying build precimonious on ubuntu 16.04.3 x64. allocated 1gb memory it. file structure looks like ~ |--- llvm/ |--- precimonious/ where llvm on version 3.0 mentioned @ https://github.com/corvette-berkeley/precimonious#requirement . followed steps on readme command make ended with ... llvm[1]: linking debug shared library libllvm-3.0.so collect2: fatal error: ld terminated signal 9 [killed] compilation terminated. ... i went through answers online , might because there's not enough memory perform link. memory usage the gcc version on machine gcc version 5.4.0 20160609 (ubuntu 5.4.0-6ubuntu1~16.04.4) , installed via apt-get install build-essential . fresh droplet created on digitalocean btw. appreciated. it memory exhaustion. sampling interval memory measurement not small enough covers exact point oom killer kicks in. depending on container/vm technology, may able set vm.overcommit_memory=2 before build, process not killed (but doing requires m...
Read more