[ https://issues.jboss.org/browse/TEIIDDES-1358?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1358: ------------------------------------- The same error occurs with: http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl. It is happening when building the schema tree: !ENTRY org.eclipse.ui 4 0 2012-05-10 14:05:12.099 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.StackOverflowError at org.eclipse.emf.edit.provider.resource.ResourceItemProviderAdapterFactory.isFactoryForType(ResourceItemProviderAdapterFactory.java:155) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.getFactoryForTypes(ComposedAdapterFactory.java:225) at com.metamatrix.modeler.internal.core.metamodel.MetamodelAspectManager$MetamodelComposedAdapterFactory.getFactoryForTypes(MetamodelAspectManager.java:301) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.adapt(ComposedAdapterFactory.java:297) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.adapt(ComposedAdapterFactory.java:277) at com.metamatrix.modeler.internal.core.metamodel.MetamodelAspectManager$MetamodelComposedAdapterFactory.adapt(MetamodelAspectManager.java:315) at org.eclipse.emf.edit.provider.ComposedAdapterFactory.adapt(ComposedAdapterFactory.java:264) at org.eclipse.emf.edit.ui.provider.AdapterFactoryContentProvider.getChildren(AdapterFactoryContentProvider.java:173) at org.teiid.designer.modelgenerator.wsdl.ui.wizards.soap.ImportWsdlSchemaHandler.addAttributes(ImportWsdlSchemaHandler.java:541) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1358?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1358. --------------------------------- Resolution: Done Added a counter when recursively building schema tree models to limit the depth to 1000. The stack overflow was due to circular references in the schemas. A warning message will be displayed when a circular reference is suspected and the user will be allowed to continue modeling the procedures with the caveat that the generated transformation may be adversely affected. Further, they are informed that the Default Procedures may be used since all complex types are broken out into individual procedures. Also changed the names of create/extract to request/response for the legacy procedure generation and added some additional clarifying description text to both procedure generation options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira