Thanks for your reply. We foudn that the JAXBContext created by CXF 2.7.5 is
having an issue. It is throwing IllegalAnnotationsException during the run
time. The same set of binding classes when used with an older version of CXF
(2.2.11) works fine. After debugging a bit, i found that new verison of CXF
when constructs JaxWSProxyFactoryBean is taking more number of classes in
JAXBContext. So I created the jaxbcontet manually and that seems to work
fine.
We wanted to eliminate giving wsdl while creating the client. But looks like
we dont have another option than referencing the wsdl. So I guess we will
have to identify why we are getting a sslhandshake exception?
Also, another thing i noticed today. The new version of CXF is not accepting
"|" character anymore. It is throwing java.net.URISyntaxException: Illegal
character in query at index 646 exception.
java.net.URI$Parser.fail(URI.java:2810)
java.net.URI$Parser.checkChars(URI.java:2983)
java.net.URI$Parser.parseHierarchical(URI.java:3073)
java.net.URI$Parser.parse(URI.java:3015)
java.net.URI.<init>(URI.java:577)
java.net.URI.create(URI.java:839)
org.apache.cxf.javascript.JavascriptQueryHandler.isRecognizedQuery(JavascriptQueryHandler.java:86)
org.apache.cxf.javascript.JavascriptQueryHandler.isRecognizedQuery(JavascriptQueryHandler.java:168)
The same URL worked fine with old version of CXF. Any idea if the new
version expects some extra configuration to accept such characters?
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-client-with-JaxWsProxyFactoryBean-without-WSDL-is-throwing-ServiceConstructionException-tp5731490p5731627.html
Sent from the cxf-user mailing list archive at Nabble.com.
