[ 
http://jira.codehaus.org/browse/MOJO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100010
 ] 

Andrius Šabanas edited comment on MOJO-781 at 6/19/07 8:10 AM:
---------------------------------------------------------------

The support for the class loader trick was removed from WsdlGenTask (method 
setOverridingContextClassLoader). I think this hack was a workaround for 
http://jira.codehaus.org/browse/XFIRE-245.


 was:
The support for the class loader trick was removed from WsdlgenMojo (method 
setOverridingContextClassLoader). I think this hack was a workaround for 
http://jira.codehaus.org/browse/XFIRE-245.

> xfire-maven-plugin needs updated to latest xfire-generator
> ----------------------------------------------------------
>
>                 Key: MOJO-781
>                 URL: http://jira.codehaus.org/browse/MOJO-781
>             Project: Mojo
>          Issue Type: Bug
>         Environment: xfire-maven-plugin 1.0-SNAPSHOT
>            Reporter: Tim Morrow
>            Assignee: Jerome Lacoste
>         Attachments: xfire-maven-plugin-patch.txt, 
> xfire-maven-plugin_rev4444.patch
>
>
> Background on specific problem:
> I recently upgraded by server to use XFire 1.2.6.  I'm using JAX-WS and JAXB 
> 2.0 annotations to generate the web service.  As of XFire 1.2.6, the WSDL 
> changed format slightly.  When I regenerate my client using the 
> xfire-maven-plugin 1.0-SNAPSHOT (specifically 
> xfire-maven-plugin-1.0-20061017.160413-3.pom) it fails to read the WSDL with 
> an XmlSchema error:
>     Embedded error: org.apache.ws.commons.schema.XmlSchemaException: Couldn't 
> map prefix 'xs' to a namespace
> Anyway, I noticed the plugin depends on XFire 1.2.1 which is pretty old now.
> Upgrading to XFire 1.2.6 (and Maven project/plugin 2.0.4) seems to take care 
> of the problem.  Probably due to a later XmlSchema dependency.
> Attached a patch with the changes.  The only caveat being that the method 
> WsdlGenTask.setOverridingContextClassLoader() disappeared.  Commenting out 
> the line that invokes it didn't appear to have any noticeable effect.  
> Obviously it would be useful to understand the ramifications of that change.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to