On Jul 29, 2013, at 1:48 PM, bhaskerhari <[email protected]> wrote:
> 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. When you run the wsdl2java, you may want to try passing the "-fe jaxws21" flags to see if that helps. Maybe some of the classes are getting annotations that aren't compatible with the runtime (assuming you are using Java6 at runtime). If that doesn't help, a test case would be useful. > 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? Can you log a bug for this? The | character isn't allowed in URL's so behavior would be unpredictable. I'd certainly encourage you to change your URL to not include it. That said, the JavascriptQueryHandler.isRecognizedQuery method should be able to just return false for anything it DOESN'T recognize, including invalid URL's. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
