Reshat Sabiq argushealth.com> writes:
> Upon further examination, MyWSResponse and MyWSMethodImpl implement Element
and
> its subinterfaces, but IMyRequestWrapper doesn't. Both were generated
using xjc
> directly.
> Examining a JAXB 1 example, i see that only the root element implements
> jav
Reshat Sabiq argushealth.com> writes:
> JAXB Alone does support arrays/lists. There's a book example,
> w/ the following
> generated, and successfully marshalled/unmarshalled:
> java.util.List getBook();
>
> Above, however, this goes from JAXB back to aegis, for some reason.
> Why would
Reshat Sabiq argushealth.com> writes:
> This was because of i wasn't passing in a JAXBContext thru spring.
Now i've done
> that, i got thru instantiation of at least one mapping for a real request
(saw
> Response object mapped while debugging),
but now getting the following:
> [4/9/07 18:20:53:
Reshat Sabiq argushealth.com> writes:
> I tried running w/ externally-generated JAXB 1 classes, but getting an
> exception. If it tells you something, please let me know:
>
> [4/9/07 16:48:22:692 CDT] 0033 XFireServlet E TRAS0014I: The
> following exception was log
Reshat Sabiq argushealth.com> writes:
> Nested exception is java.lang.NullPointerException:
> null org.codehaus.xfire.XFireRuntimeException: error getting
> qname of jaxb type. Nested exception is
> java.lang.NullPointerException: null
> java
Reshat Sabiq argushealth.com> writes:
> Also, JAXB 2's JAXB 1 support is deprecated, and apparently largely
> disabled in 2.1.2. I've seen their docs saying use JAXB 1 directly instead.
>
I tried running w/ externally-generated JAXB 1 classes, but getting an
exception. If it tells you something,
Reshat Sabiq argushealth.com> writes:
> > As i mentioned in a related bug, retro-translated code
still uses classes like
> > and loses all annotations, javax.jws.soap.SOAPBinding.
I don't see that working
> > under 1.4, but i'll look into the flags you refer to.
> Also, JAXB 2's JAXB 1 support
Reshat Sabiq argushealth.com> writes:
> If you are referring to -source and -target in
> https://jaxb.dev.java.net/nonav/2.1.2/docs/xjcTask.html, then that still
> requires changes to org.codehaus.xfire.gen, such as to WsGen, doesn't it?
>
I was hoping that perhaps an earlier release supported JA
Reshat Sabiq argushealth.com> writes:
> Guillaume Nodet gmail.com> writes:
> > If your problem is to use jaxb on JDK 1.4, you shouldtake a look at using
> jaxb2 + retrotranslator.There is some special flags to set when generating
> thejaxb2 pojos so that all the needed informations are kept
> > u
Reshat Sabiq argushealth.com> writes:
> Guillaume Nodet gmail.com> writes:
> > If your problem is to use jaxb on JDK 1.4, you shouldtake a look at using
> jaxb2 + retrotranslator.There is some special flags to set when generating
> thejaxb2 pojos so that all the needed informations are kept
> > u
Guillaume Nodet gmail.com> writes:
>
>
> If your problem is to use jaxb on JDK 1.4, you shouldtake a look at using
jaxb2 + retrotranslator.There is some special flags to set when generating
thejaxb2 pojos so that all the needed informations are kept
> under JDK 1.4, but I should work.
As i men
If your problem is to use jaxb on JDK 1.4, you should
take a look at using jaxb2 + retrotranslator.
There is some special flags to set when generating the
jaxb2 pojos so that all the needed informations are kept
under JDK 1.4, but I should work.
On 4/5/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Reshat Sabiq
> Sent: Wednesday, April 04, 2007 2:26 PM
> To: dev@xfire.codehaus.org
> Subject: [xfire-dev] Adding JAXB 1 support to WsGen
>
> Folks, I think it’s a pity, well actually a disaster, that WsGen
> doesn’t
13 matches
Mail list logo
