Bugzilla – Full Text Bug Listing
| Summary: | [WSDL4J] org.wsdl4j uses obsolete wsdl schema | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Hristo Sabev <hristo.sabev> | ||||
| Component: | wst.wsdl | Assignee: | Valentin Baciu <valentinbaciu> | ||||
| Status: | CLOSED FIXED | QA Contact: | Craig Salter <csalter> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | Alexander.Veit, david_williams | ||||
| Version: | 1.5.3 | ||||||
| Target Milestone: | 2.0 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Hristo Sabev
Hi, This is similiar to issue 161410. However it's not the same. Issue 161410 treats only the attachemtns, while this one is for the base WSDL schema. Regards, Hristo Hristo, can you please elaborate on why do you believe this should be a major bug? Hi Valentin, I beleave it's a major problem for every enterprise company. In our case SAP claims compatability with the latest WS-I interoperatbility spec i.e basic profile 1.1 2nd edition. As our own product incorporates WTP, now we are in the situation that our product doesn't reflect the current state of basic profile 1.1. This has major usability issues as, one is not able to use the WTP WSDL editor to create/edit WSDLs used in enterprise scnearios, which need security, reliable messaging and so on. Basically the reason for this is that the older schema doesn't allow for certain additional properties to be added. As you can see there's near 1-year difference between the two schemas and more than 2 years since the later one has been in use. Thus a lot of the business-to-business applications already use these extensions facilities. Regards, Hristo Thank you for the detailed justification Hristo. I will investigate this once 1.5.3 is complete. As you hinted in your note, this may not be as simple as correcting the schema. There may be implication in the level of support for this type of extensions in the version of JWSDL/WSDL4J used by WTP as well as in the WSDL EMF model and the graphical WSDL editor. The WSDL schema is mainly used by the WSDL validator which is doing a validating SAX parsing before attempting semantic validation, as well as in the source WSDL editor for content assist. Agreed, we should look into this problem in the WTP 2.0 time frame. Hristo, if you can attach some WSDL test cases that would be very useful. Craig, given that it may take some time, should I preemptively start the IP process to get this schema approved by legal? David, from what I know, in the 2.0 timeframe we will move to use third party jars from Orbit. Is there anything I should be aware of? Do we / I have the same rights to commit code there? Is the process of committing code there similar to WTP? (In reply to comment #6) > ... > > David, from what I know, in the 2.0 timeframe we will move to use third party > jars from Orbit. Is there anything I should be aware of? Do we / I have the > same rights to commit code there? Is the process of committing code there > similar to WTP? > Yes, basically same rights and process. (Well, so far, I'm the only WTP committer, so you'd just tell me what you'd like to have done). The "right" sort of transfers because any one contributing code there must _firt_ have the right to do so in their own project. So ... we'd still do CQ the same as we always have. I filled the CQ and opened https://dev.eclipse.org/ipzilla/show_bug.cgi?id=1349. Created attachment 59546 [details]
example wsdl using custom extensions
Hi, In the attached example xml look at line 429. The problematic tag is <sap:useFeature feature="tns:design_0"/> Regards, Hristo The IPZilla CQ was approved. We'll try to release the fix for this week's I-build. Fix committed and released for I-builds > 200703191335. Verified with I200705030805. Hristo, please confirm and mark as verified if all is OK. Closing. *** Bug 194186 has been marked as a duplicate of this bug. *** |