[wsas-java-dev] [jira] Closed: (WSAS-512) Exception is not handled correctly when invalid xsdconfig file is specified in WSDL2Code

[Charitha Kankanamge (JIRA)]

     [ http://www.wso2.org/jira/browse/WSAS-512?page=all ]

Charitha Kankanamge closed WSAS-512.
------------------------------------


Verified and closed the bug.

> Exception is not handled correctly when invalid xsdconfig file is specified in WSDL2Code
> ----------------------------------------------------------------------------------------
>
>                 Key: WSAS-512
>                 URL: http://www.wso2.org/jira/browse/WSAS-512
>             Project: WSO2 WSAS
>          Issue Type: Bug
>    Affects Versions: 2.1-RC2
>         Environment: winxp, jdk15
>            Reporter: Charitha Kankanamge
>         Assigned To: Saminda Wishwajith Abeyruwan 
>
> User gets 'java.lang.RuntimeException: java.lang.reflect.InvocationTargetException' in the front end UI when invalid xsdconfig file is given in code generation. 
> The following exception (Caused by) was printed in WSAS runtime console.
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.io.FileNotFoundException: C:
> \wsas\wso2wsas-2.1\wso2wsas-2.1-RC2\te (The system cannot find the file specified)
>         at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java
> :319)
>         ... 37 more
> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: C:\wsas\wso2wsas-2.1\wso2wsas-
> 2.1-RC2\te (The system cannot find the file specified)
>         at org.apache.axis2.xmlbeans.XSDConfig.<init>(XSDConfig.java:98)
>         at org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2BindingConfig.<init>(CodeGenerationU
> tility.java:503)
>         at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java
> :183)
>         ... 37 more
> Caused by: java.io.FileNotFoundException: C:\wsas\wso2wsas-2.1\wso2wsas-2.1-RC2\te (The system canno
> t find the file specified)
>         at java.io.FileInputStream.open(Native Method)
>         at java.io.FileInputStream.<init>(FileInputStream.java:106)
>         at java.io.FileInputStream.<init>(FileInputStream.java:66)
>         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
>         at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
>         at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
>         at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
>         at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
>         at org.apache.axis2.xmlbeans.XSDConfig.<init>(XSDConfig.java:71)
> Steps to reproduce:
> ================
> 1. Access WSAS management console
> 2. Click on 'WSDL2Code' in the left navigation
> 3. Enter a vaild wsdl url
> 4. Select XMLBeans as the data binding
> 5. Enter an invalid file name in -xsdconfig 
> 6. Click on 'Generate'
> User gets 'java.lang.RuntimeException: java.lang.reflect.InvocationTargetException' which is wrong.

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