wsp | HTTP tunnel over Websocket | Proxy library

Your initial XPath is fine; it is your testing XPath that is faulty.

Your testing XPath,

If the text is stored in a data frame variable, to obtain word frequency and remove Spanish stopwords, you just need the third sequence of your first block of code.

Had to add a specific port QName

Your PRINT token can only be matched by the blk_expr rule through this path:

There is no path for retblock_expr to recognize anything that begins with the PRINT token.

As a result, it will not matter which order you have elk_expr or retblock_expr.

There is no parser rule in your grammar that will match a PRINT token followed by a LPR token. a block_expr is matched by the program rule, and it only matches (ignoring wsp) block_expr or retblock_expr. Neither of these have alternatives that begin with an LPR token, so ANTLR can't match that token.

print(...) would normally be matched as a function call expression that accepts 0 or more comma-separated parameters. You have no sure rule/alternative defined. (I'd guess that it should be an alternative on either retblock_expr or block_expr

That's the immediate cause of this error. ANTLR really does not have any rule/alternative that can accept a LPR token in this position.

Both global and a are listed in your grammer under kwr rule.

kwr is mentioned in the inl rule which isn't used anywhere. So your parser don't know how to deal with inl and don't know what to do with two inl chained together (global a)

I think you're setting yourself up for potential errors by taking this approach - i.e. if you don't type the exact text of the column headings / number of headings within your code etc. Also, using ActiveSheet can be fraught with danger. Having said that, the code below should give you what you want - just change the names to the actual headers, as well as the target file. Let me know how you go.

EDIT

Code edited following clarification from OP.

It‘s a SOAP version mismatch, server expects version 1.2 but client is sending 1.1 (I am confused about SOAP namespaces). You need to implement (here: construct request based on) wsdl from server and make sure to use version 1.2

There are two WSDL versions: 1.1 and 2.0. A history of how these versions got to be can be found on the Wikipedia page for WSDL.

Also on that page it's a useful image of the differences between them and how to recognize the version you are dealing with:

The easiest way is to look at the root element in the XML:

• if it's called then it's a WSDL 1.1;
• if it's called then it's a WSDL 2.0;

Most of the WSDLs you will find out there will be version 1.1, but if the technology is newer, it might also be possible to retrieve a WSDL 2.0. See for example the answer on this post for more details about some conventions of retrieving a SOAP web service's WSDL if it provides one.

For the first question, you need to look inside the WSDL file and see where the soap12 namespace prefix is used. You should find something like , , , etc.

Having a SOAP 1.2 namespace declared in the WSDL isn't enough, you need to have XML elements declared in that namespace for it to be useful at something. If you don't have a binding and an address for the soap12 namespace prefix, then your service probably doesn't support it.

For your second question, the WSDL version does not match the SOAP protocol version. You can have WSDL 1.1 with SOAP 1.1 and a binding extension for SOAP 1.2, and you can have WSDL 2.0 with SOAP 1.1 and SOAP 1.2.

You should feed your WSDL to SoapUI and see in how many ways it allows you to call the service (on SOAP 1.1 or on both SOAP 1.1 and SOAP 1.2).