We recently ran into some interesting behavior caused by ASM.
We use the @ResponseWrapper in one of our services to change the name of the
Response element returned by our service.
With ASM 3.3 on the classpath (which is transitive dependency on
cxf-rt-frontend-jaxws) calling the following
Me
Yes that seems to have fixed it.
Thank you
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Monday, September 12, 2011 2:34 PM
To: users@cxf.apache.org
Cc: Timothy Paul Hanna
Subject: Re: WSDL caching the host name in cxf 2.4.0
Is this with SOAP 1.2 endpoint
When you navigate to the services page or the WSDL itself from a URL the WSDL
will cache the host name for all of its URLs. If you click on the WSDL from
another host name it will still display the host name from whichever URL first
navigated to the services page or the WSDL. For example, if y
AM
To: users@cxf.apache.org
Subject: Re: Problem with WADL generation and returning a List of objects
Hi
See comments below
On Tue, Aug 23, 2011 at 10:37 PM, Timothy Paul Hanna
wrote:
> Let me try to do a better job explaining.
>
> I have the following example api:
>
> @Elemen
ugust 23, 2011 5:40 AM
To: users@cxf.apache.org
Subject: Re: Problem with WADL generation and returning a List of objects
Hi
On Mon, Aug 22, 2011 at 6:43 PM, Timothy Paul Hanna
wrote:
> It actually isn't hard to fix. I am using the @ElementClass annotation to
> show that the service
ence to the custom schema or even WADL
instance
Cheers, Sergey
On Thu, Aug 18, 2011 at 9:55 PM, Daniel Kulp wrote:
>
> This definitely sounds like a bug. Can you log an issue (and maybe attach a
> patch?)
>
> Thanks!
> Dan
>
>
> On Thursday, August 18, 2011 2:42:42 P
I attempted to replace the WadlGenerator with one of my own by adding it as a
provider to my JAXRS server in spring. The server didn't see the new
WadlGenerator unless it extending the WadlGenerator that comes with CXF.
However extending the WadlGenerator in CXF is difficult because it declar
I have a service that returns a list of objects using application/xml. The
WADL doesn't display these object in the grammar nor connects them to the
operations response.
While debugging in CXF it seems the problem is in
ResourceUtils.getAllRequestResponseTypes The problem is the this method do
