Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Mixed encoding styles not supported

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mixed encoding styles not supported

    I am developing a simple client to send a message to a Mirth Soap Listener. I am getting the following exception and I am not sure based on your wsdl what I am doing wrong. I am sure its something obviously stupid, but I figure I would ask . Thanks in advance.

    org.jboss.ws.WSException: Mixed encoding styles not supported
    at org.jboss.ws.metadata.umdm.EndpointMetaData.setEnc odingStyle(EndpointMetaData.java:270)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataB uilder.processSOAPBinding(JAXWSMetaDataBuilder.jav a:143)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMet aDataBuilder.rebuildEndpointMetaData(JAXWSClientMe taDataBuilder.java:288)
    at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.ge tPortInternal(ServiceDelegateImpl.java:267)
    at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.ge tPort(ServiceDelegateImpl.java:238)
    at javax.xml.ws.Service.getPort(Service.java:169)
    at org.gsi.ws.mirth.MirthServiceBase.getPort(MirthSer viceBase.java:32)
    at org.gsi.ws.mirth.MirthServiceBase.mirthServiceTest (MirthServiceBase.java:37)
    at org.gsi.ws.mirth.MirthServiceBase.main(MirthServic eBase.java:53)

  • #2
    Re:Mixed encoding styles not supported

    I resolved this by using a static copy of the wsdl and changing the encoded to literal. Seems in JSR 181, you are no longer allowed to use encoded with RPC.

    Comment

    Working...
    X