cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <>
Subject Re: cxf - aegis service customization
Date Mon, 18 May 2009 21:15:57 GMT

Why do you want to specify the component type at all? If you want the
parameter to be Number and the xsd type to be xsd:long, just say so. After
all, one way or the others, the actual Java decl of the parameter type has
to be Number.

I'm going to add a unit test for Number/xsd:long and fix anything that goes


On Mon, May 18, 2009 at 12:06 PM, Attila Balogh <>wrote:

> dear Benson,
> at this URL:
> you wrote that in CXF 2.2 service customization with Aegis is possible
> again, however i've been struggling with it for a half day now, and
> can't get it working.
> i am using CXF 2.2.1, i have a simple interface and an according
> implementing class with a method that is expecting two
> java.lang.Number parameters, which i want to receive as xsd:long
> types, i created a ..Impl.aegis.xml:
> <mappings xmlns:xsd="">
>    <mapping>
>        <method name="findContents">
>            <parameter index="1" componentType="java.lang.Number"
>                typeName="xsd:long" />
>            <parameter index="2" componentType="java.lang.Number"
>                typeName="xsd:long" />
>        </method>
>    </mapping>
> </mappings>
> But unfortunately it doesn't seem to work. (The same thing (with
> type="java.lang.Number") works for a bean that has also a Number
> property, so in the worst case i'll create a parameter bean for all
> service methods, but that wouldn't be the nicest solution)
> Am i doing something completely wrong and this mapping shouldn't be
> there/ should be in some different format?
> If you are not the person to ask this from then please tell me where
> to turn and apologies for disturbing you.
> Thanks a lot in advance,
> Attila Balogh

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message