[MIRTH-1825] SOAP Sender: Variables in WSDL Path causes an error Created:
27/Apr/11 Updated: 24/Apr/12 Resolved: 06/May/11
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Mirth Connect
Administrator
2.0.0, 2.0.1, 2.1.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Scott Meyer
Fixed
None
1 week, 4 days
Operating
System:
Database:
Windows 7
2.1.1
Priority:
Assignee:
Votes:
Major
Jacob Brauer
0
Not Specified
1 week, 4 days
Tested using Windows 7 java 32 bit on Mirth 2.1.0 RC1 and Mirth 2.0.1.
Tested to not be an issue in Mirth 1.8.2.4472
MySQL
Description
Used to be able to have variables in the WSDL Path for a SOAP Sender on Mirth 1.8
Example WSDL Path:
http://$
{ip}/Blah.ASMX?wsdl
But it doesn't work in 2.0 or 2.1 RC 1
In the past we've used the ${ip}
in the Service Endpoint URI as well so that we can use the same sender for different endpoints.
Comments
Comment by Scott Meyer [ 27/Apr/11 ]
On a side note, we do the same thing for LLP senders but I didn't think ahead to check if it
works before switching back to 1.8.
Comment by Mike Lehmann [ 02/May/11 ]
Same issue. Setting the variable as a global map in the deploy scripts and attempting in the
WSDL Path to type something like the following: $
{wsdlPath}
. Works if I type the path in directly without the use of variables. Have also tried creating the
variable inside the channel, too, and that did not work.
Running Win XP and Mirth 2.0.1
Comment by Jacob Brauer [ 06/May/11 ]
Added Web Service Sender variable replacement to the wsdl url, username, password, service
name, port name, soap action, and attachment content type. Since the dispatch object is cached
when processing a message, changes to variable values stored in the dispatch object (url,
username, password, service, port) will cause a new dispatch object to be created and cached.
Comment by yang cai [ 10/Jun/11 ]
good!
Comment by Azza Jay [ 24/Apr/12 ]
Hello Folks, I'm having a similar issue with trying to use a WSDL from Mirth 1.8. Basically I'm
getting the below Error:-Select Get Operations I get the following Error:Error caching WSDL. Please check the WSDL URL and authentication settings (OK)
Generated at Tue Feb 09 17:11:42 PST 2016 using JIRA 6.2.7#6265sha1:91604a8de81892a3e362e0afee505432f29579b0.