You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Shawn Hu (JIRA)" <ax...@ws.apache.org> on 2005/06/01 22:10:52 UTC

[jira] Created: (AXIS-2031) wsdl2java failed with an imported XSD with BOM character in front

wsdl2java failed with an imported XSD with BOM character in front
-----------------------------------------------------------------

         Key: AXIS-2031
         URL: http://issues.apache.org/jira/browse/AXIS-2031
     Project: Axis
        Type: Bug
  Components: WSDL processing  
    Versions: 1.2RC3    
 Environment: Windows XP, run wsdl2java at command line
    Reporter: Shawn Hu


The wsdl2java cannot take a WSDL with an imported XSD with BOM characters in front. The BOM is Byte Order Mark, which is usually added automatically by a tool such as a .NET application.

The error message is ".. missing root element .." once the wsdl2java is running with such wsdl file.

Once the BOM characters are stripped from the XSD, the wsdl2java will be working just fine.



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


[jira] Commented: (AXIS-2031) wsdl2java failed with an imported XSD with BOM character in front

Posted by "Shawn Hu (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS-2031?page=comments#action_66862 ]
     
Shawn Hu commented on AXIS-2031:
--------------------------------

This issue can be closed. The cause of the problem is the Java runtime environment. The wsdl2java is running nicely with the JRE1.5.0, but do have issues with 1.4.2_06

Thanks.
Shawn

> wsdl2java failed with an imported XSD with BOM character in front
> -----------------------------------------------------------------
>
>          Key: AXIS-2031
>          URL: http://issues.apache.org/jira/browse/AXIS-2031
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.2RC3
>  Environment: Windows XP, run wsdl2java at command line
>     Reporter: Shawn Hu

>
> The wsdl2java cannot take a WSDL with an imported XSD with BOM characters in front. The BOM is Byte Order Mark, which is usually added automatically by a tool such as a .NET application.
> The error message is ".. missing root element .." once the wsdl2java is running with such wsdl file.
> Once the BOM characters are stripped from the XSD, the wsdl2java will be working just fine.

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


[jira] Resolved: (AXIS-2031) wsdl2java failed with an imported XSD with BOM character in front

Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS-2031?page=all ]
     
Davanum Srinivas resolved AXIS-2031:
------------------------------------

    Resolution: Invalid

closing as per reporter

> wsdl2java failed with an imported XSD with BOM character in front
> -----------------------------------------------------------------
>
>          Key: AXIS-2031
>          URL: http://issues.apache.org/jira/browse/AXIS-2031
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.2RC3
>  Environment: Windows XP, run wsdl2java at command line
>     Reporter: Shawn Hu

>
> The wsdl2java cannot take a WSDL with an imported XSD with BOM characters in front. The BOM is Byte Order Mark, which is usually added automatically by a tool such as a .NET application.
> The error message is ".. missing root element .." once the wsdl2java is running with such wsdl file.
> Once the BOM characters are stripped from the XSD, the wsdl2java will be working just fine.

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