Re: Issue with WSDLManagerImpl on 2.2.5 [was: Re: [VOTE] Release CXF 2.2.5]

2009-11-17 Thread Alessio Soldano
I've taken a deeper look at this. Se don't have a custom ResourceResolver installed and that's the point, as Cxf fails in getting a WEB-INF/wsdl/foo.wsdl resource from tue classloader when the classloader jboss provides is the one you get for a war app (a Url classloader pointing to WEB-INF/classe

Re: Issue with WSDLManagerImpl on 2.2.5 [was: Re: [VOTE] Release CXF 2.2.5]

2009-11-16 Thread Alessio Soldano
Hi Dan, I'll do this investigation/debug tomorrow morning (Europe time) and let you know as soon as possible. Thanks Alessio Daniel Kulp wrote: Alessio, This SOUNDS like there a ResourceResolver registered on the Bus's ResourceManager that can resolve a URL, but for some reason is not able t

Re: Issue with WSDLManagerImpl on 2.2.5 [was: Re: [VOTE] Release CXF 2.2.5]

2009-11-16 Thread Daniel Kulp
Alessio, This SOUNDS like there a ResourceResolver registered on the Bus's ResourceManager that can resolve a URL, but for some reason is not able to open a stream for it.Does JBoss integrations stuff register a ResourceResolver?If so, can you do a quick debug with that and check if t

Issue with WSDLManagerImpl on 2.2.5 [was: Re: [VOTE] Release CXF 2.2.5]

2009-11-16 Thread Alessio Soldano
Hi Dan, I've just tried integrating the 2.2.5 in JBossWS-CXF and I see a lot of failures in our testsuite. Basically I'm getting an exception from StaxUtils.createXMLStreamReader(InputSource src) because both byte and character streams are null. That causes the WSDLManagerImpl to fail in getti