[
https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi...
]
Alessio Soldano commented on JBIDE-13527:
-----------------------------------------
Hi Brian,
well, IMHO the problem here is how would a user distinguish between a "complex"
wsdl and a "simple" wsdl and hence understand if the failure he's getting is
because he did something wrong in the his impl *or* the tool is simply not able to
properly parse the wsdl. Where do you draw the line between simple and complex wsdl
contracts? I would expect a tool to be able to parse any spec compliant wsdl; then you
might decide to avoid supporting, e.g., ws-policies or any specific wsdl extension, etc.
But the sample here is really a basic wsdl from a spec point of view, it just happens to
use multiple schemas in a way that is difficult for a human being to follow at first sight
(as a consequence of the service being something like a real world scenario service, not a
echo or helloWorld like service). Just my 2cents though.
This said, if you want to evaluate wrapping wise core in the eclipse tooling, I'd be
happy to give any direction and help in trying it.
[tester] freeze parsing wsdl
----------------------------
Key: JBIDE-13527
URL:
https://issues.jboss.org/browse/JBIDE-13527
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.2
Reporter: Alessio Soldano
Assignee: Brian Fitzpatrick
Attachments: jaxws-complex.war, threaddump.txt
JBT freezes when the ws tester is used to consume the wsdl contract for the
jaxws-complex.war test deployment of JBossWS testsuite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira