You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Marc SCHNEIDER <ma...@gmail.com> on 2012/01/19 11:20:09 UTC
Null parameter when using jax-ws and aegis
Hello,
I'm a newbie to cxf and I try to call a web service method with a
parameter but this one is not taken in account (null is received).
I'm using :
cxf 2.5.1 with jax-ws front end
aegis databinding
spring 3.0.6
Here is my Spring configuration :
http://pastebin.com/zJnAbF4n
Java web service classes :
http://pastebin.com/jcdqiCUT
So when calling the uniqueValues method, the fieldName parameter is
not taken in account.
Any idea?
Thanks in advance,
Marc.
Re: Null parameter when using jax-ws and aegis
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday, January 19, 2012 3:21:24 PM Marc SCHNEIDER wrote:
> Thanks for your answer,
>
> Ok I'd rather use Aegis because it supports maps and collections out
> of the box. So I'll switch to the simple frontend.
The JAXWS frontend should be fine. I don't understand what you mean by "the
fieldName parameter is not taken in account."
We'd likely need to see the generated WSDL as well as the SOAP message that is
being sent to make sure the two of them match. Once common issue between
JAX-WS and Aegis is that Aegis generally prefers qualified schemas whereas
JAX-WS generally produces unqualified. Thus, making sure the soap message
meets the correct requirements can sometimes be challenging.
Dan
>
> Marc.
>
> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
>
> <ha...@gmail.com> wrote:
> > Try using the JAXB databinding.
> >
> > CXF prefers:
> >
> > Simple Frontend -> Aegis databinding
> > JaxWs Frontend -> JAXB databinding
> >
> >
> > On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
> >
> > <ma...@gmail.com> wrote:
> >> Hello,
> >>
> >> I'm a newbie to cxf and I try to call a web service method with a
> >> parameter but this one is not taken in account (null is received).
> >>
> >> I'm using :
> >> cxf 2.5.1 with jax-ws front end
> >> aegis databinding
> >> spring 3.0.6
> >>
> >> Here is my Spring configuration :
> >> http://pastebin.com/zJnAbF4n
> >>
> >> Java web service classes :
> >> http://pastebin.com/jcdqiCUT
> >>
> >> So when calling the uniqueValues method, the fieldName parameter is
> >> not taken in account.
> >>
> >> Any idea?
> >>
> >> Thanks in advance,
> >> Marc.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Null parameter when using jax-ws and aegis
Posted by Marc SCHNEIDER <ma...@gmail.com>.
Hi thanks for your answers,
@Glen
Thanks for the link. I've been googling a lot and found this document
to handle maps (http://blog.bdoughan.com/2010/07/xmladapter-jaxbs-secret-weapon.html).
But frankly speaking this is a pain to have to write all this code to
handle just a map. And as far as I understand you have to repeat this
process for each Map containing different types.
@Benson
I have the problem mentioned below. But I don't think this is a bug
because it's too trivial in my opinion. So I was asking for help in
case I did something wrong in the configuration.
Regards,
Marc.
On Thu, Jan 19, 2012 at 4:39 PM, Benson Margulies <bi...@gmail.com> wrote:
> I'm sorry for the disparity of opinion here, but I have to quibble
> with both of my colleagues. Aegis works fine with JAX-WS. If you've
> got a case in which it fails, please file a JIRA. I can see Glen's
> point that working with standards to start out has advantages, but
> maps in JAX-B are a giant pain. We have no intention of 'deprecating'
> Aegis or removing it. It might be CXF-specific, but it's not legacy. I
> personally don't understand why the people at Snoracle can't be
> bothered to enhance the standards to be less annoying (not to mention
> advancing to XML 1.1).
>
>
>
> On Thu, Jan 19, 2012 at 10:31 AM, Glen Mazza <gm...@talend.com> wrote:
>> Since you're a newbie starting out, I would be inclined to recommend working
>> with standard JAX-WS and JAXB, it's what seemingly 90% use and you shouldn't
>> have much problem implementing your business needs with it (Article #2 here
>> will provide much of the non-JAXB boilerplate for you:
>> http://www.jroller.com/gmazza/entry/blog_article_index, also article #46 for
>> JAXB might help.)
>>
>> With googling the map/collection on JAXB issue can be resolved
>> (http://blog.bdoughan.com/2010/09/jaxb-collection-properties.html, for
>> example, of many such links), and sticking with these two also give you
>> portability to other web service stacks like Metro if desired. And a much
>> greater proportion of user's list readers will be able to answer your
>> questions that way.
>>
>> While they have their supporters, the simple front end and Aegis are legacy
>> CXF-specific architectures. It's possible, but I would say you would have a
>> unusually rare business need if starting off with those two would be
>> suggested.
>>
>> Glen
>>
>>
>> On 01/19/2012 09:21 AM, Marc SCHNEIDER wrote:
>>>
>>> Thanks for your answer,
>>>
>>> Ok I'd rather use Aegis because it supports maps and collections out
>>> of the box. So I'll switch to the simple frontend.
>>>
>>> Marc.
>>>
>>> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
>>> <ha...@gmail.com> wrote:
>>>>
>>>> Try using the JAXB databinding.
>>>>
>>>> CXF prefers:
>>>>
>>>> Simple Frontend -> Aegis databinding
>>>> JaxWs Frontend -> JAXB databinding
>>>>
>>>>
>>>> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
>>>> <ma...@gmail.com> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I'm a newbie to cxf and I try to call a web service method with a
>>>>> parameter but this one is not taken in account (null is received).
>>>>>
>>>>> I'm using :
>>>>> cxf 2.5.1 with jax-ws front end
>>>>> aegis databinding
>>>>> spring 3.0.6
>>>>>
>>>>> Here is my Spring configuration :
>>>>> http://pastebin.com/zJnAbF4n
>>>>>
>>>>> Java web service classes :
>>>>> http://pastebin.com/jcdqiCUT
>>>>>
>>>>> So when calling the uniqueValues method, the fieldName parameter is
>>>>> not taken in account.
>>>>>
>>>>> Any idea?
>>>>>
>>>>> Thanks in advance,
>>>>> Marc.
>>
>>
Re: Null parameter when using jax-ws and aegis
Posted by Marc SCHNEIDER <ma...@gmail.com>.
Hi Benson,
Do you have a complete example of JAX-WS and Aegis configuration with Spring?
The CXF wiki is quite poor at this level.
Thanks,
Marc.
On Thu, Jan 19, 2012 at 5:15 PM, Glen Mazza <gm...@talend.com> wrote:
> Oracle appears to be bankrolling two separate JAXB efforts, Blaise Doughan's
> quite-active Eclipse implementation (http://blog.bdoughan.com/), as well as
> the standard JAXB implementation as part of their purchase of Sun.
>
> Glen
>
>
> On 01/19/2012 10:39 AM, Benson Margulies wrote:
>>
>> I'm sorry for the disparity of opinion here, but I have to quibble
>> with both of my colleagues. Aegis works fine with JAX-WS. If you've
>> got a case in which it fails, please file a JIRA. I can see Glen's
>> point that working with standards to start out has advantages, but
>> maps in JAX-B are a giant pain. We have no intention of 'deprecating'
>> Aegis or removing it. It might be CXF-specific, but it's not legacy. I
>> personally don't understand why the people at Snoracle can't be
>> bothered to enhance the standards to be less annoying (not to mention
>> advancing to XML 1.1).
>>
>>
>>
>> On Thu, Jan 19, 2012 at 10:31 AM, Glen Mazza<gm...@talend.com> wrote:
>>>
>>> Since you're a newbie starting out, I would be inclined to recommend
>>> working
>>> with standard JAX-WS and JAXB, it's what seemingly 90% use and you
>>> shouldn't
>>> have much problem implementing your business needs with it (Article #2
>>> here
>>> will provide much of the non-JAXB boilerplate for you:
>>> http://www.jroller.com/gmazza/entry/blog_article_index, also article #46
>>> for
>>> JAXB might help.)
>>>
>>> With googling the map/collection on JAXB issue can be resolved
>>> (http://blog.bdoughan.com/2010/09/jaxb-collection-properties.html, for
>>> example, of many such links), and sticking with these two also give you
>>> portability to other web service stacks like Metro if desired. And a
>>> much
>>> greater proportion of user's list readers will be able to answer your
>>> questions that way.
>>>
>>> While they have their supporters, the simple front end and Aegis are
>>> legacy
>>> CXF-specific architectures. It's possible, but I would say you would
>>> have a
>>> unusually rare business need if starting off with those two would be
>>> suggested.
>>>
>>> Glen
>>>
>>>
>>> On 01/19/2012 09:21 AM, Marc SCHNEIDER wrote:
>>>>
>>>> Thanks for your answer,
>>>>
>>>> Ok I'd rather use Aegis because it supports maps and collections out
>>>> of the box. So I'll switch to the simple frontend.
>>>>
>>>> Marc.
>>>>
>>>> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
>>>> <ha...@gmail.com> wrote:
>>>>>
>>>>> Try using the JAXB databinding.
>>>>>
>>>>> CXF prefers:
>>>>>
>>>>> Simple Frontend -> Aegis databinding
>>>>> JaxWs Frontend -> JAXB databinding
>>>>>
>>>>>
>>>>> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
>>>>> <ma...@gmail.com> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I'm a newbie to cxf and I try to call a web service method with a
>>>>>> parameter but this one is not taken in account (null is received).
>>>>>>
>>>>>> I'm using :
>>>>>> cxf 2.5.1 with jax-ws front end
>>>>>> aegis databinding
>>>>>> spring 3.0.6
>>>>>>
>>>>>> Here is my Spring configuration :
>>>>>> http://pastebin.com/zJnAbF4n
>>>>>>
>>>>>> Java web service classes :
>>>>>> http://pastebin.com/jcdqiCUT
>>>>>>
>>>>>> So when calling the uniqueValues method, the fieldName parameter is
>>>>>> not taken in account.
>>>>>>
>>>>>> Any idea?
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Marc.
>>>
>>>
>
>
> --
> Glen Mazza
> Talend Community Coders
> website: coders.talend.com
> blog: www.jroller.com/gmazza
>
Re: Null parameter when using jax-ws and aegis
Posted by Glen Mazza <gm...@talend.com>.
Oracle appears to be bankrolling two separate JAXB efforts, Blaise
Doughan's quite-active Eclipse implementation
(http://blog.bdoughan.com/), as well as the standard JAXB implementation
as part of their purchase of Sun.
Glen
On 01/19/2012 10:39 AM, Benson Margulies wrote:
> I'm sorry for the disparity of opinion here, but I have to quibble
> with both of my colleagues. Aegis works fine with JAX-WS. If you've
> got a case in which it fails, please file a JIRA. I can see Glen's
> point that working with standards to start out has advantages, but
> maps in JAX-B are a giant pain. We have no intention of 'deprecating'
> Aegis or removing it. It might be CXF-specific, but it's not legacy. I
> personally don't understand why the people at Snoracle can't be
> bothered to enhance the standards to be less annoying (not to mention
> advancing to XML 1.1).
>
>
>
> On Thu, Jan 19, 2012 at 10:31 AM, Glen Mazza<gm...@talend.com> wrote:
>> Since you're a newbie starting out, I would be inclined to recommend working
>> with standard JAX-WS and JAXB, it's what seemingly 90% use and you shouldn't
>> have much problem implementing your business needs with it (Article #2 here
>> will provide much of the non-JAXB boilerplate for you:
>> http://www.jroller.com/gmazza/entry/blog_article_index, also article #46 for
>> JAXB might help.)
>>
>> With googling the map/collection on JAXB issue can be resolved
>> (http://blog.bdoughan.com/2010/09/jaxb-collection-properties.html, for
>> example, of many such links), and sticking with these two also give you
>> portability to other web service stacks like Metro if desired. And a much
>> greater proportion of user's list readers will be able to answer your
>> questions that way.
>>
>> While they have their supporters, the simple front end and Aegis are legacy
>> CXF-specific architectures. It's possible, but I would say you would have a
>> unusually rare business need if starting off with those two would be
>> suggested.
>>
>> Glen
>>
>>
>> On 01/19/2012 09:21 AM, Marc SCHNEIDER wrote:
>>> Thanks for your answer,
>>>
>>> Ok I'd rather use Aegis because it supports maps and collections out
>>> of the box. So I'll switch to the simple frontend.
>>>
>>> Marc.
>>>
>>> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
>>> <ha...@gmail.com> wrote:
>>>> Try using the JAXB databinding.
>>>>
>>>> CXF prefers:
>>>>
>>>> Simple Frontend -> Aegis databinding
>>>> JaxWs Frontend -> JAXB databinding
>>>>
>>>>
>>>> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
>>>> <ma...@gmail.com> wrote:
>>>>> Hello,
>>>>>
>>>>> I'm a newbie to cxf and I try to call a web service method with a
>>>>> parameter but this one is not taken in account (null is received).
>>>>>
>>>>> I'm using :
>>>>> cxf 2.5.1 with jax-ws front end
>>>>> aegis databinding
>>>>> spring 3.0.6
>>>>>
>>>>> Here is my Spring configuration :
>>>>> http://pastebin.com/zJnAbF4n
>>>>>
>>>>> Java web service classes :
>>>>> http://pastebin.com/jcdqiCUT
>>>>>
>>>>> So when calling the uniqueValues method, the fieldName parameter is
>>>>> not taken in account.
>>>>>
>>>>> Any idea?
>>>>>
>>>>> Thanks in advance,
>>>>> Marc.
>>
--
Glen Mazza
Talend Community Coders
website: coders.talend.com
blog: www.jroller.com/gmazza
Re: Null parameter when using jax-ws and aegis
Posted by Benson Margulies <bi...@gmail.com>.
I'm sorry for the disparity of opinion here, but I have to quibble
with both of my colleagues. Aegis works fine with JAX-WS. If you've
got a case in which it fails, please file a JIRA. I can see Glen's
point that working with standards to start out has advantages, but
maps in JAX-B are a giant pain. We have no intention of 'deprecating'
Aegis or removing it. It might be CXF-specific, but it's not legacy. I
personally don't understand why the people at Snoracle can't be
bothered to enhance the standards to be less annoying (not to mention
advancing to XML 1.1).
On Thu, Jan 19, 2012 at 10:31 AM, Glen Mazza <gm...@talend.com> wrote:
> Since you're a newbie starting out, I would be inclined to recommend working
> with standard JAX-WS and JAXB, it's what seemingly 90% use and you shouldn't
> have much problem implementing your business needs with it (Article #2 here
> will provide much of the non-JAXB boilerplate for you:
> http://www.jroller.com/gmazza/entry/blog_article_index, also article #46 for
> JAXB might help.)
>
> With googling the map/collection on JAXB issue can be resolved
> (http://blog.bdoughan.com/2010/09/jaxb-collection-properties.html, for
> example, of many such links), and sticking with these two also give you
> portability to other web service stacks like Metro if desired. And a much
> greater proportion of user's list readers will be able to answer your
> questions that way.
>
> While they have their supporters, the simple front end and Aegis are legacy
> CXF-specific architectures. It's possible, but I would say you would have a
> unusually rare business need if starting off with those two would be
> suggested.
>
> Glen
>
>
> On 01/19/2012 09:21 AM, Marc SCHNEIDER wrote:
>>
>> Thanks for your answer,
>>
>> Ok I'd rather use Aegis because it supports maps and collections out
>> of the box. So I'll switch to the simple frontend.
>>
>> Marc.
>>
>> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
>> <ha...@gmail.com> wrote:
>>>
>>> Try using the JAXB databinding.
>>>
>>> CXF prefers:
>>>
>>> Simple Frontend -> Aegis databinding
>>> JaxWs Frontend -> JAXB databinding
>>>
>>>
>>> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
>>> <ma...@gmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I'm a newbie to cxf and I try to call a web service method with a
>>>> parameter but this one is not taken in account (null is received).
>>>>
>>>> I'm using :
>>>> cxf 2.5.1 with jax-ws front end
>>>> aegis databinding
>>>> spring 3.0.6
>>>>
>>>> Here is my Spring configuration :
>>>> http://pastebin.com/zJnAbF4n
>>>>
>>>> Java web service classes :
>>>> http://pastebin.com/jcdqiCUT
>>>>
>>>> So when calling the uniqueValues method, the fieldName parameter is
>>>> not taken in account.
>>>>
>>>> Any idea?
>>>>
>>>> Thanks in advance,
>>>> Marc.
>
>
Re: Null parameter when using jax-ws and aegis
Posted by Glen Mazza <gm...@talend.com>.
Since you're a newbie starting out, I would be inclined to recommend
working with standard JAX-WS and JAXB, it's what seemingly 90% use and
you shouldn't have much problem implementing your business needs with it
(Article #2 here will provide much of the non-JAXB boilerplate for you:
http://www.jroller.com/gmazza/entry/blog_article_index, also article #46
for JAXB might help.)
With googling the map/collection on JAXB issue can be resolved
(http://blog.bdoughan.com/2010/09/jaxb-collection-properties.html, for
example, of many such links), and sticking with these two also give you
portability to other web service stacks like Metro if desired. And a
much greater proportion of user's list readers will be able to answer
your questions that way.
While they have their supporters, the simple front end and Aegis are
legacy CXF-specific architectures. It's possible, but I would say you
would have a unusually rare business need if starting off with those two
would be suggested.
Glen
On 01/19/2012 09:21 AM, Marc SCHNEIDER wrote:
> Thanks for your answer,
>
> Ok I'd rather use Aegis because it supports maps and collections out
> of the box. So I'll switch to the simple frontend.
>
> Marc.
>
> On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
> <ha...@gmail.com> wrote:
>> Try using the JAXB databinding.
>>
>> CXF prefers:
>>
>> Simple Frontend -> Aegis databinding
>> JaxWs Frontend -> JAXB databinding
>>
>>
>> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
>> <ma...@gmail.com> wrote:
>>> Hello,
>>>
>>> I'm a newbie to cxf and I try to call a web service method with a
>>> parameter but this one is not taken in account (null is received).
>>>
>>> I'm using :
>>> cxf 2.5.1 with jax-ws front end
>>> aegis databinding
>>> spring 3.0.6
>>>
>>> Here is my Spring configuration :
>>> http://pastebin.com/zJnAbF4n
>>>
>>> Java web service classes :
>>> http://pastebin.com/jcdqiCUT
>>>
>>> So when calling the uniqueValues method, the fieldName parameter is
>>> not taken in account.
>>>
>>> Any idea?
>>>
>>> Thanks in advance,
>>> Marc.
Re: Null parameter when using jax-ws and aegis
Posted by Marc SCHNEIDER <ma...@gmail.com>.
Thanks for your answer,
Ok I'd rather use Aegis because it supports maps and collections out
of the box. So I'll switch to the simple frontend.
Marc.
On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen
<ha...@gmail.com> wrote:
> Try using the JAXB databinding.
>
> CXF prefers:
>
> Simple Frontend -> Aegis databinding
> JaxWs Frontend -> JAXB databinding
>
>
> On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
> <ma...@gmail.com> wrote:
>> Hello,
>>
>> I'm a newbie to cxf and I try to call a web service method with a
>> parameter but this one is not taken in account (null is received).
>>
>> I'm using :
>> cxf 2.5.1 with jax-ws front end
>> aegis databinding
>> spring 3.0.6
>>
>> Here is my Spring configuration :
>> http://pastebin.com/zJnAbF4n
>>
>> Java web service classes :
>> http://pastebin.com/jcdqiCUT
>>
>> So when calling the uniqueValues method, the fieldName parameter is
>> not taken in account.
>>
>> Any idea?
>>
>> Thanks in advance,
>> Marc.
Re: Null parameter when using jax-ws and aegis
Posted by Hannes Holtzhausen <ha...@gmail.com>.
Try using the JAXB databinding.
CXF prefers:
Simple Frontend -> Aegis databinding
JaxWs Frontend -> JAXB databinding
On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER
<ma...@gmail.com> wrote:
> Hello,
>
> I'm a newbie to cxf and I try to call a web service method with a
> parameter but this one is not taken in account (null is received).
>
> I'm using :
> cxf 2.5.1 with jax-ws front end
> aegis databinding
> spring 3.0.6
>
> Here is my Spring configuration :
> http://pastebin.com/zJnAbF4n
>
> Java web service classes :
> http://pastebin.com/jcdqiCUT
>
> So when calling the uniqueValues method, the fieldName parameter is
> not taken in account.
>
> Any idea?
>
> Thanks in advance,
> Marc.