cxf-codegen-plugin 2.1.9 not honoring extraargs in defaultOptions

[Håkan Dahl <ha...@gmail.com>]

I'm trying to map namespace to package with cxf-codegen-plugin 2.1.9 using
defaultOptions:

    <configuration>

<sourceRoot>${project.build.directory}/generated-sources/cxf</sourceRoot>
      <defaultOptions>
        <extraargs>
          <extraarg>-p</extraarg>
          <extraarg>
            urn:my.namespace:v1=my.namespace.v1
          </extraarg>
        </extraargs>
      </defaultOptions>
      <wsdlOptions>
      ...

but it has no effect.

Works in 2.2.6 (but I would like to stay on 2.1.x).

Should I file a JIRA?

Can I move up to 2.2.6 only for code-gen and then use 2.1.x for runtime (I'm
using plain JAX-WS contract-first) ?


/håkan

Re: cxf-codegen-plugin 2.1.9 not honoring extraargs in defaultOptions

[Daniel Kulp <dk...@apache.org>]

On Wed February 17 2010 11:59:04 am Håkan Dahl wrote:
> I'm trying to map namespace to package with cxf-codegen-plugin 2.1.9 using
> defaultOptions:
> 
>     <configuration>
> 
> <sourceRoot>${project.build.directory}/generated-sources/cxf</sourceRoot>
>       <defaultOptions>
>         <extraargs>
>           <extraarg>-p</extraarg>
>           <extraarg>
>             urn:my.namespace:v1=my.namespace.v1
>           </extraarg>
>         </extraargs>
>       </defaultOptions>
>       <wsdlOptions>
>       ...
> 
> but it has no effect.
> 
> Works in 2.2.6 (but I would like to stay on 2.1.x).
> 
> Should I file a JIRA?

You could, but we'd probably just close it marked fixed in 2.2.6.   :-)


> Can I move up to 2.2.6 only for code-gen and then use 2.1.x for runtime
> (I'm using plain JAX-WS contract-first) ?

I think that would work.   Probably yes.   That said, I would strongly 
recommend upgrading to 2.2.6 across the board.  We won't be releasing any more 
fixes for 2.1.x so moving to a supported version would probably be a good 
thing longer term.

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog