You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Ted Neward <te...@tedneward.com> on 2007/01/01 06:13:26 UTC
RE: Help diagnosing a simple example
> Well its completely optional to specify @Request/@ResponseWrappers.
> Personally I'm not a big fan of it either.(On the other hand, I
> believe there are edge cases that require a solution like this - I
> just don't remember what they are off hand)
>
I added them because java2wsdl complained about them not being present,
which I thought was odd at the time but didn't put a lot more thought than
that into it.
Let me start over: I want to write a JAXWS-First HelloWorld example,
complete with Speak/SpeakResponse message/parameter types as necessary.
What's the code for that look like? I can't find said example anywhere in
the samples directory, and Google has been less than helpful. (Maybe I'm
Googling it wrong, so pointers to resources--beyond the JAXWS Spec
itself--would be helpful.)
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -----Original Message-----
> From: Dan Diephouse [mailto:dan@envoisolutions.com]
> Sent: Saturday, December 30, 2006 6:57 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: Help diagnosing a simple example
>
> Hola,
>
> On 12/29/06, Ted Neward <te...@tedneward.com> wrote:
> > Hmm. That makes sense, but it seems wasteful to have to conjure up a new
> > type for both request and response on every operation. (I know the
> reasoning
> > behind doc/literal and so forth, but just wondering if there's a happy
> > medium here somewhere.)
> >
>
> Well its completely optional to specify @Request/@ResponseWrappers.
> Personally I'm not a big fan of it either.(On the other hand, I
> believe there are edge cases that require a solution like this - I
> just don't remember what they are off hand)
>
> > On another note, is there any way I can write an "open-ended" endpoint
> in
> > JAXWS? What I mean is to write a method that takes the SOAP message
> itself
> > as a parameter, not some strongly-typed Java bean, so I can pick the
> message
> > apart by hand. (In WCF, this is done via declaring a service contract
> with
> > an operation taking a Message parameter; anything equivalent in JAXWS or
> > CXF?)
> >
> What you want are JAX-WS Providers. :-) This document seems to have a
> decent explanation:
>
> http://java.sun.com/mailers/techtips/enterprise/2006/TechTips_July06.html
>
> Regards
> - Dan
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.16.0/610 - Release Date: 12/30/2006
> 2:59 PM
>
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.1/611 - Release Date: 12/31/2006
12:47 PM