web stats
How to load wsdl from a file - Page 2 - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #11  
Old 12-20-2011, 10:05 AM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

When 2.2 is released we will recommend using the file url instead of public_html, since this was improved for 2.2:
http://www.mirthcorp.com/community/i...wse/MIRTH-1967
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #12  
Old 12-20-2011, 01:31 PM
DavidL DavidL is offline
OBX.1 Kenobi
 
Join Date: Sep 2011
Location: Dayton Ohio
Posts: 43
DavidL is on a distinguished road
Default

I was able to load the WSDL from file, generate the SOAP envelope, etc.

So I put back the https: URL and tried processing a message through the channel. I get an error:
ERROR-410: Web Service Connector error
ERROR MESSAGE: Error connecting to web service.
javax.xml.ws.WebServiceException: Failed to access the WSDL at: file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl. It failed with:
Invalid WSDL file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl, expected {http://schemas.xmlsoap.org/wsdl/}definitions found h2 at (lineLine number = 1
Column number = 5
System Id = file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl
Public Id = null
Location Uri= file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl
CharacterOffset = 8
).
...
-- which to me looks like it's still looking for the file: URL.

However, if I leave the file: URL in the WSDL field, I also get an error.
ERROR-410: Web Service Connector error
ERROR MESSAGE: Error connecting to web service.
java.lang.IllegalStateException: unsupported protocol: 'file'
at org.apache.commons.httpclient.protocol.Protocol.la zyRegisterProtocol(Protocol.java:148)

Anybody out there got any words of wisdom?
Reply With Quote
  #13  
Old 12-20-2011, 02:46 PM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

Quote:
Originally Posted by DavidL View Post
I was able to load the WSDL from file, generate the SOAP envelope, etc.

So I put back the https: URL and tried processing a message through the channel. I get an error:
ERROR-410: Web Service Connector error
ERROR MESSAGE: Error connecting to web service.
javax.xml.ws.WebServiceException: Failed to access the WSDL at: file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl. It failed with:
Invalid WSDL file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl, expected {http://schemas.xmlsoap.org/wsdl/}definitions found h2 at (lineLine number = 1
Column number = 5
System Id = file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl
Public Id = null
Location Uri= file:/C:/Program%20Files/Mirth/Connect/temp/WebServiceSender5969903927816314230.wsdl
CharacterOffset = 8
).
...
-- which to me looks like it's still looking for the file: URL.

However, if I leave the file: URL in the WSDL field, I also get an error.
ERROR-410: Web Service Connector error
ERROR MESSAGE: Error connecting to web service.
java.lang.IllegalStateException: unsupported protocol: 'file'
at org.apache.commons.httpclient.protocol.Protocol.la zyRegisterProtocol(Protocol.java:148)

Anybody out there got any words of wisdom?
I don't think pointing to a file directly will work for sending messages prior to 2.2. You could try the RC if you like. So far it seems pretty stable.

I'm not sure what your issue is when you use the URL. A temp file copy of the WSDL is saved and used during sending when there is authentication involved.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #14  
Old 12-21-2011, 06:04 AM
DavidL DavidL is offline
OBX.1 Kenobi
 
Join Date: Sep 2011
Location: Dayton Ohio
Posts: 43
DavidL is on a distinguished road
Default

> A temp file copy of the WSDL is saved and used during sending
> when there is authentication involved.

I'm guessing the cached WSDL is generated when you press "Get Operations". I'm doing that with the file: URL because I can't get the https: URL to work. But even the file: URL doesn't work if authentication is turned on.
So *after* I get the WSDL I have to change the URL *and* put in the authentication information. But that information no longer matches what's in the cache.

Which makes sense ... unfortunately it would seem to indicate I'm at a dead end.
Reply With Quote
  #15  
Old 07-22-2013, 07:03 AM
cmcwhorter cmcwhorter is offline
OBX.2 Kenobi
 
Join Date: Apr 2008
Location: Texas
Posts: 90
cmcwhorter
Default

Maybe this is a dumb question, but Do you have to be running a webserver in order to use the Mirth web services listener?
I've setup a web services listener, when I put the url in a web browser, i get:
"Web Services"
"No JAX-WS context information available"
__________________
cmc
Reply With Quote
  #16  
Old 07-22-2013, 07:05 AM
narupley's Avatar
narupley narupley is online now
Mirth Employee
 
Join Date: Oct 2010
Posts: 7,123
narupley is on a distinguished road
Default

Quote:
Originally Posted by cmcwhorter View Post
Maybe this is a dumb question, but Do you have to be running a webserver in order to use the Mirth web services listener?
I've setup a web services listener, when I put the url in a web browser, i get:
"Web Services"
"No JAX-WS context information available"
Nope, the channel will be acting as the server. Did you deploy your channel? Are you running the browser on the same machine as the Mirth Connect server? What URL did you use?
__________________
Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

Nicholas Rupley
Work: 949-237-6069
Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


- How do I foo?
- You just bar.
Reply With Quote
  #17  
Old 07-22-2013, 07:32 AM
cmcwhorter cmcwhorter is offline
OBX.2 Kenobi
 
Join Date: Apr 2008
Location: Texas
Posts: 90
cmcwhorter
Default

I ran the browser on the Mirth server and got the same messages. The channel is deployed. This is the URL I am using http://svrie04.gvh.local:6211/services/Mirth.
Is the correct URL to use: "http://svrie04.gvh.local:6211/services/Mirth?wsdl"?
__________________
cmc
Reply With Quote
  #18  
Old 07-22-2013, 07:43 AM
cmcwhorter cmcwhorter is offline
OBX.2 Kenobi
 
Join Date: Apr 2008
Location: Texas
Posts: 90
cmcwhorter
Default

Here are the results using this url "http://svrie04.gvh.local:6211/services/Mirth?wsdl"

<?xml version="1.0" encoding="UTF-8" ?>
- <!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6.
-->
- <!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6.
-->
- <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws.connectors.connect.mirth.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://ws.connectors.connect.mirth.com/" name="DefaultAcceptMessageService">
- <types>
- <xsd:schema>
<xsd:import namespace="http://ws.connectors.connect.mirth.com/" schemaLocation="http://svrie04.gvh.local:6211/services/Mirth?xsd=1" />
</xsd:schema>
</types>
- <message name="acceptMessage">
<part name="parameters" element="tns:acceptMessage" />
</message>
- <message name="acceptMessageResponse">
<part name="parameters" element="tns:acceptMessageResponse" />
</message>
- <portType name="DefaultAcceptMessage">
- <operation name="acceptMessage">
<input message="tns:acceptMessage" />
<output message="tns:acceptMessageResponse" />
</operation>
</portType>
- <binding name="DefaultAcceptMessagePortBinding" type="tnsefaultAcceptMessage">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <operation name="acceptMessage">
<soapperation soapAction="" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="DefaultAcceptMessageService">
- <port name="DefaultAcceptMessagePort" binding="tnsefaultAcceptMessagePortBinding">
<soap:address location="http://svrie04.gvh.local:6211/services/Mirth" />
</port>
</service>
</definitions>
__________________
cmc
Reply With Quote
  #19  
Old 07-22-2013, 07:49 AM
narupley's Avatar
narupley narupley is online now
Mirth Employee
 
Join Date: Oct 2010
Posts: 7,123
narupley is on a distinguished road
Default

Looks correct to me at first glance. What's the problem?
__________________
Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

Nicholas Rupley
Work: 949-237-6069
Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


- How do I foo?
- You just bar.
Reply With Quote
  #20  
Old 07-22-2013, 08:06 AM
cmcwhorter cmcwhorter is offline
OBX.2 Kenobi
 
Join Date: Apr 2008
Location: Texas
Posts: 90
cmcwhorter
Default

I am hoping to use this to receive from an ITI-41 vendor interface, however the vendor is indicating it is not configured to receive any type of message they would send.
Would the vendor send to this address?
"http://svrie04.gvh.local:6211/services/Mirth?wsdl"
__________________
cmc
Reply With Quote
Reply

Tags
webservice, wsdl

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 08:32 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation