[ http://issues.apache.org/jira/browse/AXIS2-1222?page=comments#action_12437234 ] Ajith Harshana Ranabahu commented on AXIS2-1222: ------------------------------------------------
I have corrected the cyclic import problem for the wsdl imports but WSDL4J seems to be failing in understanding the MEP (style of the interaction). In investigating I noticed that this set of WSDL's have a sort of abnormal relationship base WSDL (http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl) imports WSDL0(http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl=wsdl0). The base WSDL has the messages,porttype, and the service. However WSDL0 has the binding and it imports (recursively) the base WSDL. I'm not sure whether this is legal or atleast recommended. The usual patter I've seen in importing WSDL is to have a WSDL to represent the interface (types/messages/porttype) and a seperate WSDL to represent the binding/service. > WSDL2Java throws a StackOverflowError > ------------------------------------- > > Key: AXIS2-1222 > URL: http://issues.apache.org/jira/browse/AXIS2-1222 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding > Reporter: Ruchith Udayanga Fernando > Priority: Critical > > Running WSDL2Java on the following WSDL causes a java.lang.StackOverflowError: > http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl > ----------------Output-------------------------- > Retrieving document at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl=wsdl0', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl'. > Retrieving schema at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd1', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl'. > Retrieving schema at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd3', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl'. > Retrieving schema at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd2', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl'. > Retrieving schema at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd0', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?wsdl'. > Retrieving schema at > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd1', > relative to > 'http://131.107.72.15/Security_WsSecurity_Service_Indigo/WsSecurity10.svc?xsd=xsd0'. > Exception in thread "main" java.lang.StackOverflowError -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
