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.IllegalAnnotationsException: 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
