On Wednesday, June 15, 2011 5:40:43 PM David L wrote: > Hi Dan, > > I am using the default constructor of the client. > I guess the default will just take the wsdl location and servic name from > the wsdl file. > > Then I call client.getXYZWsdlABCWSPort() to get the ABCWSPortType object. // > getXYZWsdlABCWSPort() is generated by CXF, and it takes no arg. I am not > using the getPort(QName portName, Class<?> clazz). > > Then I got the exception. > > Does this answer your question?
Unfortunately, yes. :-( I have no idea what would cause this then. Is there any chance of providing a test case that we could debug? Dan > > Everything was working last Thursday, before my colleague update the wsdl. > I test the NEW wsdl with soapUI, everything is fine, but not the CXF > generated stub. > > Best regards, > > David > > > From: [email protected] > > To: [email protected] > > CC: [email protected] > > Subject: Re: javax.xml.ws.WebServiceException: Unable to create > > JAXBContext Date: Tue, 14 Jun 2011 13:35:40 -0400 > > > > On Tuesday, June 14, 2011 5:31:47 PM David L wrote: > > > Hi Dan, > > > > > > I can't even get to the point where I can make a ws call. > > > I generated the stub, create a client, and get the port type object, > > > then I got the exception. Does this answer your question? > > > > Well, not really. How are you creating the client to create the port > > object? There are several ways to do that so I need to know which. I > > full stack trace MAY also be helpful. > > > > Dan > > > > > Best regards > > > > > > David > > > > > > > From: [email protected] > > > > To: [email protected] > > > > CC: [email protected] > > > > Subject: Re: javax.xml.ws.WebServiceException: Unable to create > > > > JAXBContext Date: Mon, 13 Jun 2011 16:54:18 -0400 > > > > > > > > > > > > Do you have an example testcase for this? When using the > > > > JAX-WS > > > > frontend, it definitely should trap these extra methods. If > > > > using > > > > the simple frontend with these methods, I could definitely > > > > understand > > > > this error as it wouldn't know to remove the JAX-WS specific > > > > methods. > > > > > > > > Dan > > > > > > > > On Monday, June 13, 2011 5:35:45 PM David L wrote: > > > > > Hi all, > > > > > > > > > > I got the following errors when I try to get WS port from > > > > > the CXF > > > > > generated stub. > > > > > > > > > > java.security.PrivilegedActionException: > > > > > com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsExcep > > > > > tion: 4 > > > > > counts of IllegalAnnotationExceptions > > > > > javax.xml.ws.AsyncHandler is > > > > > an interface, and JAXB can't handle interfaces. this problem > > > > > is > > > > > related to the following > > > > > > > > > > location: > > > > > at javax.xml.ws.AsyncHandler > > > > > at public javax.xml.ws.AsyncHandler > > > > > > > > > > org.ws.stub.jaxws.SomeWSMethodAsync.asyncHandler > > > > > javax.xml.ws.AsyncHandler does not have a no-arg default > > > > > constructor. this problem is related to the > > > > > > > > > > following location: > > > > > at javax.xml.ws.AsyncHandler > > > > > at public javax.xml.ws.AsyncHandler > > > > > > > > > > org.ws.stub.jaxws.SomeWSMethodAsync.asyncHandler > > > > > java.util.concurrent.Future is an interface, and JAXB can't > > > > > handle > > > > > > > > > > interfaces. this problem is related to the following location: > > > > > at java.util.concurrent.Future > > > > > at public java.util.concurrent.Future > > > > > > > > > > org.ws.stub.jaxws.SomeWSMethodAsyncResponse._return > > > > > java.util.concurrent.Future does not have a no-arg default > > > > > constructor. > > > > > > > > > > this problem is related to the following location: > > > > > at java.util.concurrent.Future > > > > > at public java.util.concurrent.Future > > > > > > > > > > org.ws.stub.jaxws.SomeWSMethodAsyncResponse._return > > > > > > > > > > Any ideas? > > > > > > > > > > Best regards, > > > > > > > > > > David -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
