Re: Returning Generic Lists Properly Typed?

I'm using the 2.0 release and JAXB. I'd try the 2.1 if that fixes it but im not good enough at this stuff to figure out how to do a build from the source yet. When is that expected to be released as a jar? - Original Message From: Daniel Kulp <[EMAIL PROTECTED]> To: cxf-user@incubator.

Re: Returning Generic Lists Properly Typed?

Jeremy, Are you using the latest 2.1-SNAPSHOT or the 2.0 release? Also, JAXB or Aegis? This SHOULD be fixed in the latest 2.1-SNAPSHOT for JAXB: http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-cxf/2.1-incubator-SNAPSHOT/ Dan On Saturday 28 July 2007 19:32, Jeremy

Re: Returning Generic Lists Properly Typed?

Yeah I had already tried something like that, but it doesnt seem to work for me. Did the dev team say if returning generic Lists was supposed to work like it does in xfire? Would it work better as an array or a collection? Maybe you changed something else at the same time that fixed the proble

Re: Returning Generic Lists Properly Typed?

Jeremy, I had the same issue until I annotated my interface methods like this: @WebMethod(operationName = "getAllProducts") @ResponseWrapper(targetNamespace = " http://catalogService.service.gdservices.com", className = "com.gdservice

Returning Generic Lists Properly Typed?

Sorry for all the activity, I'm on deadline and trying to get some stuff running quickly... I'm trying to return a List where report is a javabean with some string properties. I can get the array back from the webservice but they all come back typed as Item instead of Report is there an annota

Re: webservice proxied with trasaction interceptor throwing errors on WSDL generation

Brad, this problem seems to not occur if you instead apply the transactional proxies to middle tier business objects or something not exposed to cxf. I just moved it into my business object layer (actually just created a business object layer) and it works no problem now. Guess there is just so

Re: webservice proxied with trasaction interceptor throwing errors on WSDL generation

This is the exact same error I get when I apply an aop transaction aspect to my service impls. Strangely enough, 80 percent of my services still pass under unit tests when I enable the transx advice but if I try to view the wsdl from a browser or testing tool, I get the same error as below. FWIW,