Comments (5)
Ever figure this out? I am having the same issue. Full stack trace:
2015-07-14 13:18:02,502 ERROR com.aquent.osgi.AquentActivator - Exception testing web service client
java.lang.IllegalArgumentException: Port is invalid
at org.apache.http.util.Args.check(Args.java:36)
at org.apache.http.conn.scheme.Scheme.<init>(Scheme.java:91)
at org.reficio.ws.client.core.SoapClient.registerTlsScheme(SoapClient.java:249)
at org.reficio.ws.client.core.SoapClient.configureTls(SoapClient.java:237)
at org.reficio.ws.client.core.SoapClient.initialize(SoapClient.java:192)
at org.reficio.ws.client.core.SoapClient.access$900(SoapClient.java:72)
at org.reficio.ws.client.core.SoapClient$Builder.initializeClient(SoapClient.java:407)
at org.reficio.ws.client.core.SoapClient$Builder.build(SoapClient.java:385)
at com.aquent.osgi.AquentActivator.start(AquentActivator.java:75)
at com.dotcms.repackage.org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at com.dotcms.repackage.org.apache.felix.framework.Felix.activateBundle(Felix.java:2146)
at com.dotcms.repackage.org.apache.felix.framework.Felix.startBundle(Felix.java:2064)
at com.dotcms.repackage.org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
at com.dotcms.repackage.org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1175)
at com.dotcms.repackage.org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1153)
at com.dotcms.repackage.org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:458)
at com.dotcms.repackage.org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:263)
from soap-ws.
Same issue here! Would be great if somebody could post a workaround or fix...
from soap-ws.
UPDATE: When I add a port to the URI passed in the builder, I get the following exception:
Uncaught exception from servlet
org.reficio.ws.client.TransmissionException: HTTP response=[Internal Server Error] code=[500]
at org.reficio.ws.client.core.SoapClient.executePost(SoapClient.java:171)
at org.reficio.ws.client.core.SoapClient.transmit(SoapClient.java:161)
at org.reficio.ws.client.core.SoapClient.post(SoapClient.java:116)
at org.kiba.api.cif.GetBarcode.performGet(GetBarcode.java:87)
at org.kiba.api.support.APIPage.doGet(APIPage.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125)
Can you check if this is also the case in your situation? Then I can determine if it is the server's fault.
from soap-ws.
Well, for me, the fix was just to add port 443 to the url, though I know in some, or maybe most, cases that won't work as in the OP's and your cases. I think a workaround, if you wanted to internalize the code until a fix is made is to hardcode the port here:
and/or here
What happens is the port ends up being null in those cases.
Or perhaps a check here if port is null than set port to 443 or something?
from soap-ws.
I just set the URI port like it is done here: http://stackoverflow.com/questions/6490014/modifying-the-port-of-a-uri . So it should find 443 and I think it does. So hardcoding is not the solution here. Could it be that the SOAP Server doesn't allow connections on this port (which would be very weird)?
from soap-ws.
Related Issues (20)
- org.reficio.ws.legacy.WsdlUtils.findBindingForOperation(WsdlUtils.java:90)
- bind ip address to soap connection HOT 1
- Request xml Tags are getting generated in language other than english
- validateInputMessage does not appear to validate minOccurs
- Getting invalid sample request XML from http://www.w3schools.com/xml/tempconvert.asmx?wsdl WSDL. HOT 2
- Migration to SLF4J
- WSDL And Auth HOT 1
- post get stucked
- Stack overflow when getting bindings
- Additional dependencies needed
- Add request / response model introspection
- SOAP binding not recognized? HOT 4
- buildOutputMessage is big different with SoapUI HOT 1
- It seems that soap-builder is not thread-safe
- How to change the language on the creation of requests from the operations in the WSDL?
- SOAP UI moved its repo from eviware HOT 3
- reficio.org is down HOT 4
- Your project reficio soap-ws is using buggy third-party libraries [WARNING]
- Is this project still active?
- Reficio.org repository is not active HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from soap-ws.