hill-Smith <[EMAIL PROTECTED]>
> > Sent: Tue, 26 Feb 2008 11:25:16 -0700 (MST)
> > Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
> >
> > On Monday 25 February 2008, Phil Weighill-Smith wrote:
> > > Dan,
> > >
> > > The exc
axb;
> >
> > import com.volantis.openapi.mss.usermodule.User;
> >
> > import javax.xml.bind.annotation.adapters.XmlAdapter;
> >
> > /**
> > * Provides the various Java type adapters required to allow the API
> > to be * appropriately bound to JAX-WS
@Override
> public User unmarshal(final UserImpl user) throws Exception {
> return user;
> }
> }
>
> ...
> }
>
>
> Any suggestions as to why the response for the getUser operation is
> like:
>
>
>
>
>
eased).
>
> Dan
>
>
>
> >
> > - Original Message -
> > From: Daniel Kulp <[EMAIL PROTECTED]>
> > To: cxf-user@incubator.apache.org
> > Cc: Phil Weighill-Smith <[EMAIL PROTECTED]>
> > Sent: Tue, 26 Feb 2008 11:25:16 -
ed
toward the 2.0.x toolset (since 2.0.x is released).
Dan
>
> - Original Message -
> From: Daniel Kulp <[EMAIL PROTECTED]>
> To: cxf-user@incubator.apache.org
> Cc: Phil Weighill-Smith <[EMAIL PROTECTED]>
> Sent: Tue, 26 Feb 2008 11:25:16 -0700 (MST)
> Su
ghill-Smith" <[EMAIL PROTECTED]>
> Sent: 25 February 2008 17:08:00 o'clock (GMT) Europe/London
> Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
>
>
> Hmm..
>
> Is this in maven or other build system? It looks like its picking up
> some old ja
av
> >aT oProcessor.java:87)
> >
> > Note that this is both in the IDEA integration with CXF and via the
> > command line. The JDK I'm using is 1.6.0.03.
> >
> > Any suggestions?
> >
> > Phil :n.
> >
> > - Original Message -
.0.03.
>
> Any suggestions?
>
> Phil :n.
>
> - Original Message -
> From: "Daniel Kulp" <[EMAIL PROTECTED]>
> To: cxf-user@incubator.apache.org
> Cc: "Phil Weighill-Smith" <[EMAIL PROTECTED]>
> Sent: 22 February 2008 17:26:
-
> From: "Daniel Kulp" <[EMAIL PROTECTED]>
> To: cxf-user@incubator.apache.org
> Cc: "Phil Weighill-Smith" <[EMAIL PROTECTED]>
> Sent: 22 February 2008 17:26:59 o'clock (GMT) Europe/London
> Subject: Re: Problem generating WSDL from Java AP
OTECTED]>
Sent: 22 February 2008 17:26:59 o'clock (GMT) Europe/London
Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
On Friday 22 February 2008, Phil Weighill-Smith wrote:
> Dan, sorry it's been several weeks since you e-mailed this to me and
> I
9 o'clock (GMT) Europe/London
Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
On Friday 22 February 2008, Phil Weighill-Smith wrote:
> Dan, sorry it's been several weeks since you e-mailed this to me and
> I've not actioned it. Where do I find CXF's offi
On Friday 22 February 2008, Phil Weighill-Smith wrote:
> Dan, sorry it's been several weeks since you e-mailed this to me and
> I've not actioned it. Where do I find CXF's official JIRA app?
https://issues.apache.org/jira/browse/CXF
That said, the namespace issue in the WrapperClassGenerator sho
Dan, sorry it's been several weeks since you e-mailed this to me and
I've not actioned it. Where do I find CXF's official JIRA app?
By the way, I have also hit a problem where the response parts are
generated with incomplete result definitions. For example, if I have a
method in my SEI like:
@We
This is definitely a bug and I see where the improper code is found.
Line 202 of WrapperClassGenerator specifically sets the namespace to ""
for the generated class. This needs to be updated to either not output
it or output the correct namespace. I'll need to experiment a bit to
figure out
Regarding target namespace and the elementFormDefault issues...
Interestingly the package-info.java approach doesn't seem to work.
Whilst this sets the default element form to qualified, each element is
then generated with the form="unqualified" attribute set. D'oh! I guess
I'll have to use the Xm
Dan,
Sorry, I just spotted that there were some other response e-mails on
nabble.com's archive of this mailing list
(http://www.nabble.com/Problem-generating-WSDL-from-Java-API-with-
CXF-2.0.3-td15084730.html lists this thread) which I didn't actually
get. Not sure why. Were you asking for me to p
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 3:47 PM
To: cxf-user@incubator.apache.org
Cc: Cobery, Marc
Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
Any chance you could turn on FINE level logging?At least for the
org.apache.cxf.jaxb.JAXBDataBinding Logger
eption.
> Before this exception, I could not initialize the web service.
>
> Regards,
> Marc
>
>
> -Original Message-
> From: Phil Weighill-Smith [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 28, 2008 12:20 PM
> To: Daniel Kulp
> Cc: cxf-user@incub
t;com.rulestream.services.knowledge.ws.impl.ClassDefService
>Impl">
>
>
>
>
> Thanks for any help.
> Regards,
> Marc
>
> -Original Message-
> From: Cobery, Marc [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 28, 2008 3:45 PM
&g
Phil Weighill-Smith [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 28, 2008 12:20 PM
> To: Daniel Kulp
> Cc: cxf-user@incubator.apache.org
> Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
>
> Dan,
>
> What I've found so far is that I can dec
I could not initialize the web service.
Regards,
Marc
-Original Message-----
From: Phil Weighill-Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 12:20 PM
To: Daniel Kulp
Cc: cxf-user@incubator.apache.org
Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
: cxf-user@incubator.apache.org
Subject: Re: Problem generating WSDL from Java API with CXF 2.0.3
Dan,
What I've found so far is that I can declare myself a new adapter, e.g.:
public final class SimpleThingArrayAdapter extends
XmlAdapter {
@Override
public
Dan,
What I've found so far is that I can declare myself a new adapter, e.g.:
public final class SimpleThingArrayAdapter extends
XmlAdapter {
@Override
public SimpleThingImpl[] marshal(SimpleThing[] simpleThings)
throws Exception {
if (s
On Monday 28 January 2008, Phil Weighill-Smith wrote:
> I'm trying to apply the pattern I described earlier to my real world
> scenario. The problem I haven't figured out a way round is when I have
> parameters and return types based on arrays of the interfaces. I get
> an annotation error with JAX
Dan,
Thanks again for your useful guidance.
I'm trying to apply the pattern I described earlier to my real world
scenario. The problem I haven't figured out a way round is when I have
parameters and return types based on arrays of the interfaces. I get an
annotation error with JAXB complaining it
That's very cool. This is something I'd actually like to see a complete
project/build/example for as a tutorial or something if you can get it
working.
> * whether the various parameters and results can be "null" (i.e.
> I would like to change the minOccurs="0" to minOccurs="1" - the
> def
Dan/anyone else,
I've got further (not sure if it will actually work with JAXB
marshalling and unmarshalling, will find out later today) whilst still
using interfaces as part of my API - the WSDL now looks more-or-less OK.
The extra steps I've taken, as previously partially outlined, are to:
JAXB generally doesn't like interfaces too much. In general, we
definitely suggest using concrete classes.
That said, one major issue is that your interface doesn't have setter
methods on it. There's no way there's any chance of it working without
that. JAXB would only expose propertie
28 matches
Mail list logo
