Community
Participate
Working Groups
Build: WTP 1.5.1 0803 The WS-I validator will run into a infinite loop at BP2202 when trying to validate WSDLs with cross imports. I'll attach sample WSDLs.
Created attachment 47343 [details] Sample WSDLs Unzip these WSDLs/XSDs into a simple project and run validation on the project. The WS-I validator will run forever.
This is a very bad problem, we should fix it in 1.5.1. Changing priority to P2.
Jeff, I fixed a similar (or the same) problem with the WSDL validator. I believe the WS-I validator copied much of the WSDL validator's reader. I think a better approach here is to expose the WSDL model created by the WSDL validator to the WS-I test tools. This should solve this problem and improve the WS-I test tools performance by removing the requirement to parse the documents again.
Not a mainstream scenario, and was a problem since 1.0. Nobody found it until now. We will defer this to 2.0.
While a very bad problem, since Keith says "not main stream" and wants to defer it to 2.0, I assume "major" better captures the severity. (we should fix critical's in maintenance, if we can do so safely). Please correct if I have misunderstood.
Looks like this can be deferred to maintenance stream.
Maintaince came and went, any possibility of getting this addressed. These situations are more main stream than people realize.
Dave, this bug is marked as helpwanted: please feel free to contribute a patch. Once planning for the next major release starts you can propose re-vamping the WS-I validation tools as a plan item (as you mentioned on your blog and evident by looking at my bugzilla inbox :-)). At this time time though I cannot make any committments because there are many other things needing attention and time and resources are scarce.
(In reply to comment #8) > Dave, this bug is marked as helpwanted: please feel free to contribute a patch. > > Once planning for the next major release starts you can propose re-vamping the > WS-I validation tools as a plan item (as you mentioned on your blog and evident > by looking at my bugzilla inbox :-)). At this time time though I cannot make > any committments because there are many other things needing attention and time > and resources are scarce. > Yeah, understandable, which is why I'm willing to help clear out some of the 241 bugs that are sitting there waiting to be triaged. I've verified some already, still have a lot to go through though. but I hope that we can at least address the ones that already have patches in 3.1, it'll help all adopters make sure we have compliant tooling to build off of.
