(Migrated) URL in Plain HTTP outgoing connection

(This message has been automatically imported from the retired mailing list)

Hello.

I am having an issue with using this URL in a Plain HTTP outgoing
connection:

http://server.local/BusinessInteractionWS?wsdl

Message:

Could not perform the update, e:[Traceback (most recent call last):
File
"/opt/zato/2.0.3/zato-web-admin/src/zato/admin/web/views/http_soap.py",
line 203, in edit
response = req.zato.client.invoke(‘zato.http-soap.edit’,
_get_edit_create_message(req.POST, ‘edit-’))
File “/opt/zato/2.0.3/zato-web-admin/src/zato/admin/middleware.py”,
line 70, in invoke
raise Exception(response.inner.text)
Exception: {“zato_env”: {“details”: “Traceback (most recent call
last):\n File
”/opt/zato/2.0.3/zato-server/src/zato/server/connection/http_soap/channel.py",
line 198, in dispatch\n payload, worker_store, self.simple_io_config,
post_data)\n File
"/opt/zato/2.0.3/zato-server/src/zato/server/connection/http_soap/channel.py",
line 351, in handle\n params_priority=channel_item.params_pri)\n
File
"/opt/zato/2.0.3/zato-server/src/zato/server/service/init.py",
line 423, in update_handle\n raise e\nZatoException: Expected
elem:[id] not found in item:[{u’id’: u’’, u’name’: u’’}]\n", “result”:
“ZATO_ERROR”, “cid”: “K04CSYS6GTRP9RM7MFSV60TPZP38”}}
]

But when I remove the “?wsdl” it’s all OK.

The same URL works in a SOAP outgoing connection

Any reason for this behaviour?

regards
Thomas.

On 11/06/2015 08:36, Thomas Lundquist wrote:

raise e\nZatoException: Expected elem:[id] not found in item:[{u’id’:
u’’, u’name’: u’’}]\n"
This is Zato’s generic “something went wrong” exception, which isn’t
very helpful. However if you look in the server log, you may find the
real exception, followed by this exception.

The query part of the URL (after the question mark) is normally
structured as key=val&key=val&… but according to RFC 2396, “?wsdl” by
itself should be valid.