Community
Participate
Working Groups
NewWSDLWizard creates invalid WSDL when definition.updateElement() is not called before the Binding is created. Kihup, you mentioned the fix is in RAD.
Keith, As discussed. I am re-assigning this defect to you. Thanks.
This doesn't sound urgent... but it'd be nice to know why updateElement() needs to be called since as a rule one shouln't need to call that method. Valentin please investigate when time permits.
I commented out the call to updateElement in NewWSDLWizard then stepped through the code. I noticed a NPE in ComponentReferenceUtil#setComponentReference(Part part, boolean isType, String componentName). I'm attaching a stack trace with the exact location. This method tries to manipulate a Part's underlying element and of course it NPEs because the model does not have a backing DOM yet. That's why calling updateElement solves the issue - it creates the DOM up-front instead of waiting until the resource is serialized. I believe I pointed this class to Rich a little while back as one of the cases where we're still manipulating the DOM directly instead of going through the model. If I remember correctly the assessment was that the risk of changing it was too big for 1.5.1. Rich, please correct me if I'm wrong. Based on the above, I think this is not a model bug after all - or at least not yet :-). If there are still problems after correcting the editor we'll take it from there.
Created attachment 48333 [details] Stack trace with the location where the NPE happens Here's the stack trace I mentioned. Let's get past this and we'll take it from there.
Rich, reassigning to you. As per my comment, I belive some things need to be corrected in the editor. If you encounter further model issues after fixing the editor please re-assign to me.
ping.
This doesn't seem to be causing any grief. I would be good to refactor the code but this can wait.
