I found a response in the international Stackoverflow that you have to write down your class as follows: @XmlRootElement @GET @Produces("application/json") @XmlRootElement public class MyJaxbBean { public String name; public int age; public MyJaxbBean() {} // JAXB needs this public MyJaxbBean(String name, int age) { this.name = name; this.age = age; } } and then your method would look like this: @GET @Produces("application/json") public MyJaxbBean getMyBean() { return new MyJaxbBean("Agamemnon", 32); } There is a chapter in the latest documentation that deals with this: https://jersey.java.net/documentation/latest/user-guide.html#json Follow link: https://stackoverflow.com/questions/13594945/how-correctly-produce-json-by-restful-web-service

Problem solved! The problem occurred because apparently by default, in Json's options have a precaution to avoid referral looping.What I did then was ignore that, as follows:At the Startup of my project, in ConfigureServices inseri:services.AddMvc().AddJsonOptions(options => { options.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore; }); Get the solution https://stackoverflow.com/questions/42577248/web-api-returns-only-one-child-object-from-one-to-many-relationship-using-entity But now I have another question: Is it wrong to do that? Since I am globally disabling a "precaution"!

The solution to this question was as follows: I had to make the correction of the parameter being sent by the following ajax call:function EnviaCliente() { var json1 = JSON.stringify(Cliente); alert(json1); $.ajax({ type: "POST", url: UrlPadrao, data: json1, contentType: 'application/json; charset=utf-8', datatype: "json", success: function(data) { PopulaCodigoCliente(data) }, error: function(data) { erroJson(data) } });for this model that respects the name of the parameter of the WS and the type of data that should be passed by the parameter in the call Ajax:function EnviaCliente() { var json1 = JSON.stringify(Cliente); alert(json1); $.ajax({ type: "POST", url: UrlPadrao, data: '{Cliente:"Teste de envio"}',//aqui a correcao contentType: 'application/json; charset=utf-8', datatype: "json", async: true, success: function (data) { PopulaCodigoCliente(data) }, error: function (data) { erroJson(data) } });</code></pre></div></div></p><p>I will now quantify the parameters of the Json1 object and describe them in ws so that you can finally use this object. Thank you for your help

An API (Application Programming Interface) is the means by which third parties can write interfaces to communicate with another code. A WebService is an API type, which almost always operates over HTTP (although some, such as SOAP, use alternative protocols such as SMTP). The official definition of W3C mentions that Web Services do not necessarily use HTTP, but this is not common. APIs in general can use any media you want. REST is a style of software architecture, which basically explores the technology and protocols existing on the Web. And RESTful is usually used to refer to web services that implement this architecture.

Notice that in the error is telling you where the problem is, an object is expected, but is receiving an array in json.Do as follows: Gson mGson = new Gson(); mDocumento = Arrays.asList(mGson.fromJson(response.body().getAsJsonArray(), Documento[].class));

I don't know exactly what the cause of the error was, but I can see some problems that may or may not be the cause of error, I'll list them.1. Element Namespace eSocial in XMLThe root element eSocial must contain the eSocial specific namespace for that event, but should not contain the attributes xmlns:xsi and xmlns:xsd, which are usually inserted automatically by the serializer. See item 3 this answer: https://pt.stackoverflow.com/a/348662/86952 , which has a code example to serialize XML without these attributes.2. SOAP elements in XMLIn your XML example there are SOAP elements, such as <s:Envelope> and <s:Body>, that should not be there, because .NET will take over your XML and put in a SOAP envelope to send to the service. In addition, XML has the element <ConsultarIdentificadoresEventosEmpregador> before <eSocial>, and he should not be there in XML either. The element <eSocial> must be the root of the document.3. Wrong wayYou are using the wrong method to call the service! From what I understand, you want to consult the event S-1250 (Acquisition of Rural Production), which is part of the Periodic Events, so in this case you should use the method ConsultarIdentificadoresEventosTrabalhador, instead of method ConsultarIdentificadoresEventosEmpregador.See the description of the methods in https://portal.esocial.gov.br/manuais/manualorientacaodesenvolvedoresocialv1-7.pdf , from page 58:5.6.2.1. Method ConsultarIdentificadoresEventosEmpregadorThe method consultarIdentificadoresEventosEmpregador allows consultation identifiers of the employer's events that do not fall within the categories of events of table or periodic and non-periodic events of the worker.5.6.2.2. Method ConsultarIdentificadoresEventosTabelaThe method consultarIdentificadoresEventosTabela allows consultation employer table event identifiers.5.6.2.3. Method ConsultarIdentificadoresEventosTrabalhadorThe method consultarIdentificadoresEventosTrabalhador allows consultation periodic and non-periodic events of the worker linked to the employer.By my understanding, the first method ConsultarIdentificadoresEventosEmpregador, which is what you tried to use, would only be used to retrieve information sent by the S-1000 event, although this information is very confusing looking at the XSD documentation and schemes, since in the examples of the method manual ConsultarIdentificadoresEventosTabela there is an example just consulting the S-1000 event, and in the scheme of the method ConsultarIdentificadoresEventosEmpregador there is the element tpEvt, although he theoretically should only accept the S-1000.4. ESocial BugI confess I haven't tested that consultation yet, but I know she's still very problematic. I participate in the forum on eSocial of the http://fenainfo.org.br/ (via e-mail) and until a short time ago the few people who had tried said that the service only worked in the Restricted Production environment and in the Production environment (official) if I did not mistakenly give exactly this invalid signature error.If that's your case, I advise you to send a message in the area https://portal.esocial.gov.br/servicos/producao-empresas/producao-empresas-1 of the eSocial Production environment, to report the problem.Example of XMLAn example of how your XML would look, before signing:<?xml version="1.0" encoding="utf-8"?> <eSocial xmlns="http://www.esocial.gov.br/schema/consulta/identificadores-eventos/trabalhador/v1_0_0"> <consultaIdentificadoresEvts> <ideEmpregador> <tpInsc>1</tpInsc> <nrInsc>12345678</nrInsc> </ideEmpregador> <consultaEvtsTrabalhador> <cpfTrab>12345678901</cpfTrab> <dtIni>2019-01-01T00:00:00</dtIni> <dtFim>2019-01-31T00:00:00</dtFim> </consultaEvtsTrabalhador> </consultaIdentificadoresEvts> </eSocial> And after signing:<?xml version="1.0" encoding="utf-8"?> <eSocial xmlns="http://www.esocial.gov.br/schema/consulta/identificadores-eventos/trabalhador/v1_0_0"> <consultaIdentificadoresEvts> <ideEmpregador> <tpInsc>1</tpInsc> <nrInsc>12345678</nrInsc> </ideEmpregador> <consultaEvtsTrabalhador> <cpfTrab>12345678901</cpfTrab> <dtIni>2019-01-01T00:00:00</dtIni> <dtFim>2019-01-31T00:00:00</dtFim> </consultaEvtsTrabalhador> </consultaIdentificadoresEvts> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" /> <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" /> <Reference URI=""> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /> <Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" /> <DigestValue>[...]</DigestValue> </Reference> </SignedInfo> <SignatureValue>[...]</SignatureValue> <KeyInfo> <X509Data> <X509Certificate>[...]</X509Certificate> </X509Data> </KeyInfo> </Signature> </eSocial> Yes, the correct method ConsultarIdentificadoresEventosTrabalhador does not have a field to specify the type of event you want to consult, which leads me to believe that you will receive all the events of that CPF, in the specified period, and you will have to identify them with the event ID that is returned.Other considerationsIt is also good to remember the restrictions of the service, which are listed on pages 57 and 58 of the same manual:Consultations may not be held between days 1 to 7 of each month.Each employer may only hold a consultation at a time, i.e. no parallelism will be allowed on this Webservice.Each employer may make a maximum of 10 accesses per day to Webservices described in sections 5.6 - Webservice to Identifiers of Events and 5.7 - Events Download Request Webservice, that is, the sum of Webservice accesses mentioned above should not exceed 10 per day.The query should be held with a deadline of up to one hour unless the current date.The query returns will contain the events received up to an hour unless the current date.Also information I got on the Fenainfo forum is that this eSocialBX which was released (it is the product name that allows the query and download of the events previously sent to eSocial) is a eSocialBX Surgical, which was released emergencyly only for punctual recovery of certain receipts (so it still has so many restrictions).The full service, which seems to be called eSocialBX Data Lake, is still without accurate government release forecast, and for what all indicates will be a service charged.

From what I understand you get one of the two URLs. So why at the point where you get the URL you don't do something like this:Thread thread = new Thread(new Runnable() { @Override public void run() { try { HttpPost post = new HttpPost("sua url"); HttpClient client = new DefaultHttpClient(); HttpResponse response; try { response = client.execute(post); HttpEntity httpEntity = response.getEntity(); EntityUtils.toString(httpEntity); // Vai imprimir a resposta como json. } catch (ClientProtocolException e) { e.printStackTrace(); } catch (IOException e) { e.printStackTrace(); } } catch (Exception e) { e.printStackTrace(); } } }); thread.start(); This way, you will run any past URL. Check only the need to use HttpPost.

@marianac_costa, there in your Return of Web Service, see that your return return return return It is ResultCert then, would not have been able to assign directly to your object a.Certificado, because it is the same as you force your Certificado turn ResultadoCert. To fix this, you should change the Return of your method in Service, or return the ResultCert Really. It would be like this: Returning ResultCertpublic Task<ResultadoCert> Certificado(string serial) { ResultadoCert resultado = new ResultadoCert(); X509Certificate2Collection collection = Certificados.SelecionarCertificado(serial); if (collection.Count == 1) { resultado.Certificado = collection[0]; resultado.Result = true; return resultado; } else { resultado.Result = false; resultado.Certificado = null; return resultado; } } Obs: Note that I added the Task<Objeto>, this would solve the problem of being returning nullwhen the variable is type var(that you had commented).Service Call (Returning ResultCert)ResultadoCert a = new ResultadoCert(); var resultadoCertoRetornado = await client.CertificadoAsync(item.Serial); if (resultadoCertoRetornado.Certificado.Result) { a.Certificado = await resultadoCertoRetornado.Certificado; } Returning Certificatepublic Task<Certificado> Certificado(string serial) { ResultadoCert resultado = new ResultadoCert(); X509Certificate2Collection collection = Certificados.SelecionarCertificado(serial); if (collection.Count == 1) { return collection[0]; } else { return null; } } Service Call (Returning Certificate)ResultadoCert a = new ResultadoCert(); var certificadoRetornadaService = await client.CertificadoAsync(item.Serial); if (certificadoRetornadaService.IsNotNull()) { a.Certificado = await certificadoRetornadaService; }

I kick that the problem should be in the way you are getting the private key of the certificate, to sign the XML. See that you're getting the properties ProviderType and ProviderName of the object RSACryptoServiceProvider newly created, and not from the private certificate key:var privKey = (RSACryptoServiceProvider)cert.PrivateKey; var enhCsp = new RSACryptoServiceProvider().CspKeyContainerInfo; var cspparams = new CspParameters(enhCsp.ProviderType, enhCsp.ProviderName, privKey.CspKeyContainerInfo.KeyContainerName); privKey = new RSACryptoServiceProvider(cspparams); This may not be your current problem, but it may be a problem in the future, because when you install a new object of the class RSACryptoServiceProvider, the default key is used ( https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.rsacryptoserviceprovider.-ctor#System_Security_Cryptography_RSACryptoServiceProvider__ctor ), and the default key may not be the key you want to use for signature.Here’s my other answer in Stack Overflow on the subject: https://pt.stackoverflow.com/a/277470/86952 There is a routine example used to sign XML and also some motif tips that can cause this invalid signature error.See also this other, more recent answer, which is about EFD-Reinf, but it is very similar to eSocial (the difference is that in EFD-Reinf the attribute reference.Uri must have content and in eSocial must be empty): https://pt.stackoverflow.com/a/349264/86952 Another thing, the event S-2221 ("Professional Driver's Toxicological Exam") that you are trying to send in the example, is part of the events of Worker Health and Safety – SST, which will only be sent from July/2019 to Group 1 companies ( http://portal.esocial.gov.br/noticias/publicado-novo-cronograma-do-esocial ), and this event was specifically included in version 2.5 of eSocial's readings, which was implanted yesterday in the Restricted Production Environment, but will only be 21/01/2019 implemented in the Production Environment ( http://portal.esocial.gov.br/noticias/comite-gestor-aprova-a-versao-2-5-do-leiaute-do-esocial ).If you are now starting at eSocial, the best is to always catch the event S-1000 ("Employer/Contribuinte/Public Organ Information") first, which is the beginning of all.

Note: In Android, it is usually more practical to start the analysis of stack trace from the end going to assess the problems until we find the last reference to "Caused By". This last reference usually points to the specific problem we are facing.You don't have all LogCat output, but the cause of your problem seems to be:java.io.InvalidClassException: android.util.Pair; IllegalAccessException In short, you are trying to access a field or method not accessible during serialization or deserialization.Decomposing a little the problem: http://developer.android.com/reference/java/lang/IllegalAccessException.html Thrown when a program attempts to access a field or method which is not accessible from the location where the reference is made.What translated:Launched when a program tries to access a field or method that is not accessible from where the reference is made. http://developer.android.com/reference/android/util/Pair.html Container to ease passing around a tuple of two objects. This object provides a sensible implementation of equals(), returning true if equals() is true on each of the contained objects.What translated:Contentor to facilitate the passage around a tuple of two objects. This object provides a sensible implementation of equals(), returning true if equals() is true in each of the contained objects. http://developer.android.com/reference/java/io/InvalidClassException.html Signals a problem during the serialization or deserialization of an object.What translated:Signals a problem during serialization or deserialization of an object.

Substitute var request = new XMLHttpRequest(); request.open('GET', 'https://ghibliapi.herokuapp.com/films', true); request.onload = function() { By fetch('url da api', { headers:{ //seus headers } }) .then(retorno =>{ //faz sua tratativa do retorno aqui. }) .catch(error => console.log(error)) Where is the log console you can do its function with all the rest.Enjoy and read in fetch documentation https://developer.mozilla.org/pt-BR/docs/Web/API/Fetch_API/Using_Fetch

Hello I ended up solving the problem, simply deleting and adding the service references again.

A probable diagnosis may be the type of encoding.To fix this, inform the file type header, do not leave any character before and after the output, make sure your tag <?php is the first thing of the file and remove the tag ?> from the end of the file, or else add one exit;:header('Content-Type: application/json'); $final_res = json_encode($jsonObj); echo $final_res; exit; Check which one encoding your database, the PHP file that is printing the data and the file that is receiving the data. If possible put everyone in UTF-8 without https://stackoverflow.com/a/2223926/3497987 English.Complement: Note that there are two files with BOM at the beginning.the code for php header:header("Content-Type: application/json; charset=utf-8;");

You will have to use database and also php had a chat project that it did not update the page anymore in case Php and MYSQL will be used

I believe the problem is that you are using the method JAXBContext.newInstance(Class... classesToBeBound)but it is only passing Parlamentares.class as parameter.Pass the other generated classes JAXBContext.newInstance(ListaParlamentarEmExercicio.class, Parlamentares.class, Parlamentar.class, etc), or use the method JAXBContext.newInstance(String contextPath) passing the name of the package of the generated classes JAXBContext.newInstance("jaxb").The call to the method jaxbUn.unmarshal(br) must return the root element of xml, in case ListaParlamentarEmExercicio.

The main code for accessing the EFD-Reinf WebService is this:using System.Net; using System.ServiceModel; using System.Security.Cryptography.X509Certificates; using System.Xml.Linq; public void EnviarLoteReinf() { // Carrega o certificado digital a partir de um arquivo PFX, informando a senha. X509Certificate2 x509Cert = new X509Certificate2(caminhoArquivoPfx, senhaArquivoPfx); // Carrega o XML de lote a partir de um arquivo. // Mas os XMLs dos eventos devem ser assinados digitalmente antes de inseridos no XML de lote. // Para isso é possível usar a função SignXmlDoc() disponível na resposta abaixo: // https://pt.stackoverflow.com/a/277476/ XDocument loteEventosXDoc = XDocument.Load(caminhoArquivoXml); var urlServicoEnvio = @"https://preprodefdreinf.receita.fazenda.gov.br/wsreinf/RecepcaoLoteReinf.svc"; var address = new EndpointAddress(urlServicoEnvio); // BasicHttpsBinding está disponível somente a partir do .NET Framework 4.5. // Se estiver usando uma versão anterior, use a linha comentada abaixo. //var binding = new BasicHttpBinding(BasicHttpsSecurityMode.Transport); var binding = new BasicHttpsBinding(); // Informa que será usado um certificado digital para acessar o serviço. binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate; // Veja essa pergunta para mais detalhes: // https://pt.stackoverflow.com/q/318351/ ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls; // Cria o objeto cliente (do tipo System.ServiceModel.ClientBase) para acesso ao WebService. var wsClient = new ServiceReference2.RecepcaoLoteReinfClient(binding, address); // Passa o certificado digital para o objeto do tipo System.ServiceModel.ClientBase. wsClient.ClientCredentials.ClientCertificate.Certificate = x509Cert; // Veja: https://stackoverflow.com/a/49303859/ wsClient.Open(); // Chama o WebService de fato, passando o XML do lote. // O método espera um objeto do tipo XElement, e retorna outro objeto XElement. var retornoEnvioXElement = wsClient.ReceberLoteEventos(loteEventosXDoc.Root); wsClient.Close(); } Some important points (and not so much) that are partially commented on the code, or are related:The XML that will be sent to the service is a batch file that will contain one or more EFD-Reinf events. These event XMLs must be signed https://pt.stackoverflow.com/a/283284/86952 before they are inserted into the lot. That https://pt.stackoverflow.com/a/277476/ there is an example of function to sign XML using the digital certificate;The class System.ServiceModel.BasicHttpsBinding is available only from .NET Framework 4.5, if using a previous version, use the class BasicHttpBinding;For more details about the line ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls, see https://pt.stackoverflow.com/q/318351/ ;For interesting information on System.ServiceModel.ClientBase.Open() See https://stackoverflow.com/a/49303859/ ;If you want to see an example of treating exceptions returned by a WCF WebService, see https://stackoverflow.com/a/49271080/ .Here are some useful links to work with EFD-Reinf: http://sped.rfb.gov.br/pasta/show/2133 ; http://sped.rfb.gov.br/pasta/show/2141 ; http://sped.rfb.gov.br/pasta/show/2225 .

Evaluating what is described via WSDL and interpreted via SoapUI, the code below meets the need:<?php $soapServer = 'https://servicoshm.saude.gov.br/cmd/ContatoAssistencialService/v1r0?wsdl'; $arrContextOptions = array("ssl" => array("verify_peer" => false , "verify_peer_name" => false , 'crypto_method' => STREAM_CRYPTO_METHOD_TLS_CLIENT)); $options = array( 'soap_version'=>SOAP_1_2, 'exceptions'=>true, 'trace'=>1, 'cache_wsdl' => WSDL_CACHE_NONE, 'stream_context' => stream_context_create($arrContextOptions) ); try { $soapClient = new SoapClient($soapServer , $options); $ns = 'http://servicos.saude.gov.br/wsdl/cmd/mensageria/v1r0/autenticacaocmd'; $auth = new stdClass(); $auth-&gt;cpf = new SoapVar('111.111.111-11', XSD_STRING, null, null, 'cpf', $ns); $auth-&gt;senha = new SoapVar('pass', XSD_STRING, null, null, 'senha', $ns); $autenticacaoCMD = new SoapVar($auth, SOAP_ENC_OBJECT, null, null, 'AutenticacaoCMD', $ns); $header = new SoapHeader($ns , 'AutenticacaoCMD' , $autenticacaoCMD , false); $soapClient-&gt;__setSoapHeaders($header); $arguments = new stdClass(); $arguments-&gt;codigoContatoAssistencial = 'código'; $retorno = $soapClient-&gt;cancelarContatoAssistencial($arguments); } catch ( SoapFault $fault ) { echo '&lt;pre&gt;' ; var_dump($fault); echo '&lt;/pre&gt;' ; } The XML generated for WS consumption is as follows:<?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://servicos.saude.gov.br/cmd/v1/contatoassistencialservice" xmlns:ns2="http://servicos.saude.gov.br/wsdl/cmd/mensageria/v1r0/autenticacaocmd"> <SOAP-ENV:Header> <ns2:AutenticacaoCMD> <ns2:cpf>111.111.111-11</ns2:cpf> <ns2:senha>pass</ns2:senha> </ns2:AutenticacaoCMD> </SOAP-ENV:Header> &lt;SOAP-ENV:Body&gt; &lt;ns1:RequestCancelarContatoAssistencial&gt; &lt;ns1:codigoContatoAssistencial&gt;código&lt;/ns1:codigoContatoAssistencial&gt; &lt;/ns1:RequestCancelarContatoAssistencial&gt; &lt;/SOAP-ENV:Body&gt; </SOAP-ENV:Envelope> If you really need to add the tag Security, just transform the variable $header in an array (now it will be called $headers) and add how many headers are needed to add a new header:<?php $soapServer = 'https://servicoshm.saude.gov.br/cmd/ContatoAssistencialService/v1r0?wsdl'; $arrContextOptions = array("ssl" => array("verify_peer" => false , "verify_peer_name" => false , 'crypto_method' => STREAM_CRYPTO_METHOD_TLS_CLIENT)); $options = array( 'soap_version'=>SOAP_1_2, 'exceptions'=>true, 'trace'=>1, 'cache_wsdl' => WSDL_CACHE_NONE, 'stream_context' => stream_context_create($arrContextOptions) ); try { $securityNS = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'; $auth = new stdClass(); $auth-&gt;Username = new SoapVar('user', XSD_STRING, null, null, 'Username', $securityNS); $auth-&gt;Password = new SoapVar('pass', XSD_STRING, null, null, 'Password', $securityNS); $usernameToken = new SoapVar($auth, SOAP_ENC_OBJECT, null, null, 'UsernameToken', $securityNS); $security = new SoapVar($usernameToken, SOAP_ENC_OBJECT, null, null, 'Security', $securityNS); $headers[] = new SoapHeader($securityNS , 'Security' , $security , true); $soapClient = new SoapClient($soapServer , $options); $ns = 'http://servicos.saude.gov.br/wsdl/cmd/mensageria/v1r0/autenticacaocmd'; $auth = new stdClass(); $auth-&gt;cpf = new SoapVar('111.111.111-11', XSD_STRING, null, null, 'cpf', $ns); $auth-&gt;senha = new SoapVar('pass', XSD_STRING, null, null, 'senha', $ns); $autenticacaoCMD = new SoapVar($auth, SOAP_ENC_OBJECT, null, null, 'AutenticacaoCMD', $ns); $headers[] = new SoapHeader($ns , 'AutenticacaoCMD' , $autenticacaoCMD , false); $soapClient-&gt;__setSoapHeaders($headers); $arguments = new stdClass(); $arguments-&gt;codigoContatoAssistencial = 'código'; $retorno = $soapClient-&gt;cancelarContatoAssistencial($arguments); } catch ( SoapFault $fault ) { echo '&lt;pre&gt;' ; var_dump($fault); echo '&lt;/pre&gt;' ; } The XML generated for WS consumption is as follows:<?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://servicos.saude.gov.br/cmd/v1/contatoassistencialservice" xmlns:ns2='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' xmlns:ns3="http://servicos.saude.gov.br/wsdl/cmd/mensageria/v1r0/autenticacaocmd"> <SOAP-ENV:Header> <ns2:Security SOAP-ENV:mustUnderstand="1"> <ns2:Username>user</ns2:Username> <ns2:Password>pass</ns2:Password> </ns2:Security> &lt;ns3:AutenticacaoCMD&gt; &lt;ns3:cpf&gt;111.111.111-11&lt;/ns3:cpf&gt; &lt;ns3:senha&gt;pass&lt;/ns3:senha&gt; &lt;/ns3:AutenticacaoCMD&gt; &lt;/SOAP-ENV:Header&gt; &lt;SOAP-ENV:Body&gt; &lt;ns1:RequestCancelarContatoAssistencial&gt; &lt;ns1:codigoContatoAssistencial&gt;código&lt;/ns1:codigoContatoAssistencial&gt; &lt;/ns1:RequestCancelarContatoAssistencial&gt; &lt;/SOAP-ENV:Body&gt; </SOAP-ENV:Envelope>

The designation for the expression given as an example is https://developer.mozilla.org/pt-BR/docs/Web/JavaScript/Reference/Operators/Atribuicao_via_desestruturacao . https://developer.mozilla.org/pt-BR/docs/Web/JavaScript/Reference/Operators/Atribuicao_via_desestruturacao .The syntax assignment via destructuring assignment is a JavaScript expression that allows you to extract data from arrays or objects into distinct variables.var a, b, rest; [a, b] = [1, 2]; console.log(a); // 1 console.log(b); // 2 [a, b, ...rest] = [1, 2, 3, 4, 5]; console.log(a); // 1 console.log(b); // 2 console.log(rest); // [3, 4, 5] ({a, b} = {a:1, b:2}); console.log(a); // 1 console.log(b); // 2 In your example you are assigning the property home of the variable app.controllers directly to a constant of the same name. Other ways of performing the same assignment would be:const home = app.controllers.home; // Ou const { controller: { home } } = app;

Good afternoon!Use https://ionicframework.com/ , https://phonegap.com/ or https://www.nativescript.org/ to make your application hybrid. I would recommend using a WebView ( https://developer.apple.com/documentation/uikit/uiwebview or https://developer.android.com/reference/android/webkit/WebView ) you already have a Web application, but if you want to save the data if the user is offline, Webview does not have this feature. With the aforementioned hybrid platforms you can save this information until the device accesses the internet again. At Ionic I was able to find a quick and easy solution to use the call feature https://ionicframework.com/docs/storage/ . "Ionic Storage is a simple way to store data in the key/value format either in a PWA (Progressive Web App) or in a native app. " Source: http://www.fabricadecodigo.com/como-armazenar-dados-offline-com-ionic-storage/ I hope I helped. A hug!

If you use the data= to send your parameters, along with a string, in the case, the coded JSON, the content is sent "brut" in the body of the HTTP request. If the server is not expecting a JSON response, which can come, in this case, with incorrect headers, will not work even.If the server accepts JSON, instead of calling a json.dumps with your data, pass them directly to the parameter json= in the call of the post medium. This will not only encode the data, but will put the correct headers:... params = {'field': 'id', 'value': '31198'} s = requests.session() s.verify=False response = s.post(serverUrlDisc, json=params) ... Now, if the application on the server is not expecting JSON, and yes, the data encoded as form-encoded, in this case you pass the data in the form of direct dictionary in the parameter data=, without serializing JSON before:... params = {'field': 'id', 'value': '31198'} s = requests.session() s.verify=False response = s.post(serverUrlDisc, data=params) ...