1
edit
Changes
→Week 8
* Reproduced bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=203257#c0 203257] on Windows Vista Business OS
* Tried to reproduce bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142301#c0 142301] but couldn't do it due to lack of documentation
=== Week 4 ===
* Downloaded and debugged org.eclipse.wst.wsdl.ui package to find problems
* Used Eclipse tutorial (guided by Jordan) to learn about Eclipse debugging techniques
=== Week 5 ===
* Found that the org.eclipse.wst.wsdl.ui package links to source code present in org.elicpse.wst.wsdl package.
* Downloaded org.eclipse.wst.wsdl package to perform debugging and understand flow of logic through different classes
=== Week 6 ===
* Contributed to Anthony's Bit torrent project. Helped him to install Bit torrent tracker for his project (requested by Dave Humphrey)
* Read tutorials about WSDL and DOM to refresh knowledge
=== Week 7 ===
* Contribution - Helped Sid to set up Eclipse WTP and taught basic functionality
* Found the problem in my bug: reconcileReferences(boolean) method, references are lost before the code gets to this method
=== Week 8 ===
* Debugged the whole WSDL file and learned different things including: WSDL is built using DOM, DOM uses recursion to build child nodes, each node is a different Class and uses the following name format <WSDL_ELEMENT_NAME>+<Impl> e.g PortImpl
* Posted questions on news group - [http://www.eclipse.org/newsportal/article.php?id=18373&group=eclipse.webtools available here]
* Posted a new post - [http://jsinghfoss.wordpress.com/2009/03/07/eclipse-wtp-presentation-by-angel-vera/ available here]
* Posted a new post - [http://jsinghfoss.wordpress.com/2009/03/10/eclipse-wsdl-editor-not-available-in-debugger-m4/ available here]
* Posted a new post - [http://jsinghfoss.wordpress.com/2009/03/12/eclipse-debugging-plug-in-was-long/ available here]
=== Week 9 ===
* Found the involvement of org.eclipse.wst.wsdl.ui.internal.adapters.commands package
* Currently working on finding the GAP where references are lost
* Posted questions on news group - [http://dev.eclipse.org/newslists/news.eclipse.webtools/msg18366.html available here]
=== Week 10 ===
* Posted questions on Bugzilla page - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=203257#c6 available here]
== Projects ==
:If there were any references to the prefix in the WSDL, they will not have been changed. In the [https://bugs.eclipse.org/bugs/attachment.cgi?id=78305 '''attached WSDL'''], the prefix was changed from "pos" to "posCHANGED" only in the namespace definitions section.
---- == Labs ==Comment from [mailto:wuamy@ca.ibm.com Amy Wu] ==== : '''The gorey details''': :In W11EditNamespacesCommand#execute, the prefix is updated by removing the old namespace attribute and then adding the new one. :Removing the old attribute will eventually trigger a reconcile on the definition. :For Port, Binding, Message, WSDLElement#reconcileReferences() looks something like this: :''QName messageQName = createQName(definition,element.getAttribute(WSDLConstants.MESSAGE_ATTRIBUTE), element);'':''Message newMessage = messageQName != null ? (Message)definition.getMessage(messageQName) : null;'':''if (newMessage != getEMessage())'':''{'':'' setEMessage(newMessage);'':''}'' :The problem here is that ''messageQName'' will be null. This is because when trying to create the ''QName'' for the current referenced message, it will return null. It is null because the prefix/namespace attribute has already been deleted, so when it tries to create a new ''QName'' by looking up the prefix, it will find that there is none. So ''QName=null'' which means ''newMessage'' is ''null''. Which means ''newMessage != message'' currently referenced. Which means it will delete the message currently referenced. :So that's how the references are lost. :So it looks like a fix needs to be made somewhere around here to not lose the existing references. : Once this is fixed, the next step to update the references is actually not that bad according to what is being done XSD's ''UpdateNamespaceInformationCommand''. What XSD does is it calls ''schema.updateElement()'' and that will update all the references magically. I'm assuming it does some magic with resolving the prefix/namespaces. The same type of call would need to be made in ''W11EditNamespacesCommand'' for the definition object. (See ''UpdateNamespaceInformationCommand#updateElement()'' for more details). == Releases ===== Release 0.1 ===---- : '''Reproduced bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=203257#c0 Bug 203257] on Eclipse WTP (Stable Build - 20081219210304, Milestone 4)''': '''Inserted a [http://jsinghfoss.wordpress.com/2009/01/31/214/ blog post] on my blog'''