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 "Frank Cornelis (JIRA)" <ji...@apache.org> on 2006/04/11 13:29:20 UTC

[jira] Created: (AXIS2-561) codegen schema lookup bug

codegen schema lookup bug
-------------------------

         Key: AXIS2-561
         URL: http://issues.apache.org/jira/browse/AXIS2-561
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug

  Components: wsdl  
    Versions: 0.96    
    Reporter: Frank Cornelis


When you import a schema in your WSDL, codegen cannot locate it since it's only looking in the present work directory. codegen should look in the directory where the WSDL is located, since that's where one also puts the schema XSDs. This bug entered somehow in the SVN version of Axis2. Maybe the codegen Ant task should have a basedir attribute to be able to pass on the directory where to look for additional XSDs when importing.

-- 
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


Re: [jira] Created: (AXIS2-561) codegen schema lookup bug

Posted by Michel Drescher <Mi...@uk.fujitsu.com>.
I can confirm that.

At the end of the day, I currently end up copying all the XSDs and  
WSDLs into the bin directory of the Axis2 binary release.

Cheers,
Michel

On 11 Apr 2006, at 12:29, Frank Cornelis (JIRA) wrote:

> codegen schema lookup bug
> -------------------------
>
>          Key: AXIS2-561
>          URL: http://issues.apache.org/jira/browse/AXIS2-561
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>
>   Components: wsdl
>     Versions: 0.96
>     Reporter: Frank Cornelis
>
>
> When you import a schema in your WSDL, codegen cannot locate it  
> since it's only looking in the present work directory. codegen  
> should look in the directory where the WSDL is located, since  
> that's where one also puts the schema XSDs. This bug entered  
> somehow in the SVN version of Axis2. Maybe the codegen Ant task  
> should have a basedir attribute to be able to pass on the directory  
> where to look for additional XSDs when importing.
>
> -- 
> 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: (AXIS2-561) codegen schema lookup bug

Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-561?page=all ]
     
Ajith Harshana Ranabahu resolved AXIS2-561:
-------------------------------------------

    Resolution: Fixed

This issue is solved by taking the base uri of the WSDLDefinition object and treating it as the base uri for the schemas if the references are relative. It works anyway for absolute references.


> codegen schema lookup bug
> -------------------------
>
>          Key: AXIS2-561
>          URL: http://issues.apache.org/jira/browse/AXIS2-561
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: wsdl
>     Versions: 0.96
>     Reporter: Frank Cornelis
>     Assignee: Ajith Harshana Ranabahu

>
> When you import a schema in your WSDL, codegen cannot locate it since it's only looking in the present work directory. codegen should look in the directory where the WSDL is located, since that's where one also puts the schema XSDs. This bug entered somehow in the SVN version of Axis2. Maybe the codegen Ant task should have a basedir attribute to be able to pass on the directory where to look for additional XSDs when importing.

-- 
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] Assigned: (AXIS2-561) codegen schema lookup bug

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-561?page=all ]

Deepal Jayasinghe reassigned AXIS2-561:
---------------------------------------

    Assign To: Ajith Harshana Ranabahu

> codegen schema lookup bug
> -------------------------
>
>          Key: AXIS2-561
>          URL: http://issues.apache.org/jira/browse/AXIS2-561
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: wsdl
>     Versions: 0.96
>     Reporter: Frank Cornelis
>     Assignee: Ajith Harshana Ranabahu

>
> When you import a schema in your WSDL, codegen cannot locate it since it's only looking in the present work directory. codegen should look in the directory where the WSDL is located, since that's where one also puts the schema XSDs. This bug entered somehow in the SVN version of Axis2. Maybe the codegen Ant task should have a basedir attribute to be able to pass on the directory where to look for additional XSDs when importing.

-- 
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: (AXIS2-561) codegen schema lookup bug

Posted by "Frank Cornelis (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-561?page=comments#action_12374601 ] 

Frank Cornelis commented on AXIS2-561:
--------------------------------------

When in run the codegen Ant task from within a Maven2 build.

> codegen schema lookup bug
> -------------------------
>
>          Key: AXIS2-561
>          URL: http://issues.apache.org/jira/browse/AXIS2-561
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: wsdl
>     Versions: 0.96
>     Reporter: Frank Cornelis

>
> When you import a schema in your WSDL, codegen cannot locate it since it's only looking in the present work directory. codegen should look in the directory where the WSDL is located, since that's where one also puts the schema XSDs. This bug entered somehow in the SVN version of Axis2. Maybe the codegen Ant task should have a basedir attribute to be able to pass on the directory where to look for additional XSDs when importing.

-- 
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: (AXIS2-561) codegen schema lookup bug

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-561?page=comments#action_12374018 ] 

Davanum Srinivas commented on AXIS2-561:
----------------------------------------

Frank,

you mean when you click on "?wsdl" or when you are running WSDL2Java?

thanks,
dims

> codegen schema lookup bug
> -------------------------
>
>          Key: AXIS2-561
>          URL: http://issues.apache.org/jira/browse/AXIS2-561
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: wsdl
>     Versions: 0.96
>     Reporter: Frank Cornelis

>
> When you import a schema in your WSDL, codegen cannot locate it since it's only looking in the present work directory. codegen should look in the directory where the WSDL is located, since that's where one also puts the schema XSDs. This bug entered somehow in the SVN version of Axis2. Maybe the codegen Ant task should have a basedir attribute to be able to pass on the directory where to look for additional XSDs when importing.

-- 
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