Hi Valentin, At first, thank you for your help. I have added the filter for wsdl definition. It is perfect! I tried to move the discussion to wtp forum, but I can't log today. The system say: Unable to connect to the database server at this time If you think it is better that moving the discussiont to wtp forum, I will do it when I can login.
BTW, for the validator, I have created one that use wsdl11validator, but can not be called. Is it caused by the issue that you said? I add the partnerlinktype under the wsdl definitions element. Grid 2009/11/18 Valentin Baciu <vba...@ca.ibm.com> > Grid, > > Given that your questions are not really about developing WTP itself, I > propose we move the discussion on the WTP forum (newsgroup) > http://www.eclipse.org/forums/index.php?t=thread&frm_id=88 which we are > monitoring too. This way, other folks that don't subscribe to this mailing > can benefit from this information. > > > To register an extension validator with the WSDL validator use the > wsdl11validator extension point. However, there seems to be a bug in the > WSDL validator: the top level (definition level) extensibility elements are > not passed along to the registered extensions validators. I have opened this > bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=295348 to fix this. > > Regarding the extra definitions element in the context menu, if you look at > the plink schema, you'll notice that all plink elements are specified in > such a way as to allow extensibility elements from namespaces other than the > plink namespace (##other). The WTP XML framework rightfully considers the > WSDL namespace to be one of these other namespaces. > > The model query extensions (WSDLModelQueryExtensions) and the extensibility > elements filtering mechanism filter out most extensibility elements declared > by other namespaces (SOAP, HTTP, MIME, XSD) based on the context, but > there's no filter registered to filter out the WSDL namespace itself. The > WSDL schema declares only one global element declaration: the definitions > element and that's what shows up in the list. > > If you really want to filter out the definitions element look at the > org.eclipse.wst.xml.core.modelQueryExtensions extension point. The WSDL > editor registers such an extension - the > org.eclipse.wst.wsdl.ui.internal.text.WSDLModelQueryExtension class. You > should be able to register one that filters out the definitions element when > the parent is a partner link element. > > > Regards, > Valentin Baciu > Rational XML Web Services Tools > > [image: Inactive hide details for grid qian ---11/17/2009 05:29:12 > AM---Thank you very much! Valentin! I have finished the xml catalog]grid > qian ---11/17/2009 05:29:12 AM---Thank you very much! Valentin! I have > finished the xml catalog and am working on the rename refactor > > > From: grid qian <grid.q...@gmail.com> > To: "General discussion of project-wide or architectural issues." < > wtp-dev@eclipse.org> > Date: 11/17/2009 05:29 AM > Subject: Re: [wtp-dev] how to display a element from other spe in the wsdl > editor > > Sent by: wtp-dev-boun...@eclipse.org > ------------------------------ > > > > Thank you very much! Valentin! > I have finished the xml catalog and am working on the rename refactoring > issue. > > For now, there are some other questions: > > > 1. partnerlinktype validator > After I added a partnerlinktype into a wsdl file, I want to do > validation. I find there are two > extend point: one is extvalidator, the other is wsdl11validator. Which > should I extend? > 2. I extend the org.eclipse.wst.xml.core. > catalogContributions to support add a partnerlinktype in > the xml catalog. But after this, when I right-click a partnerlinktype > in the extensions tab of the > properties view, there is 'New' item in the popup menu. Click the 'New' > itme, there is always > 'definitions' item. If you click it, you will create a wsdl definitions > under the partnerlinktype. This > is not what I want. I have added a filter for this to just let ‘role' > and 'document' to display on the > 'New' popup menu. But the 'definitions' itm always is there. I can not > filter it. Do you know the > reason? > > > 2009/11/17 Valentin Baciu <*vba...@ca.ibm.com* <vba...@ca.ibm.com>> > > Grid, > > As you have noticed, by design, the WSDL editor will only display > components from the WSDL namespace in the design tab and outline view. The > editor is trying to focus the user on the main editing activities: adding, > modifying and removing WSDL services, port types, operations, parameters > and > bindings. Other components, like WSDL messages and bindings extensibility > elements are considered secondary and most times are created automatically > as side effects or explicitly (for example through the Generate binding > content action). Advanced users who want to edit extensibility elements can > do so in the properties view extensions tab or in source mode. The > extensions tab and source mode are dynamic: they are guided by the XML > schemas that describe various extensibility element namespaces. To get the > most out of this, be sure to register the partner link schema with the XML > catalog using this extension point > org.eclipse.wst.xml.core.catalogContributions. > > <extension point="org.eclipse.wst.xml.core.catalogContributions"> > <catalogContribution id="default"> > <uri > name="<schema target namespace>" > uri="<schema location>" /> > <catalogContribution > <extension > > I believe I have answered the port type to partner link port type > rename refactoring question in this bug * > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=202929#c6.*<https://bugs.eclipse.org/bugs/show_bug.cgi?id=202929#c6.>. > > > > Regards, > Valentin Baciu > Rational XML Web Services Tools > > [image: Inactive hide details for grid qian ---11/13/2009 03:20:53 > AM---Hi all, For now, I am working on extending the wsdl editor to s]grid > qian ---11/13/2009 03:20:53 AM---Hi all, For now, I am working on extending > the wsdl editor to support ws-bpel > > > From: grid qian <*grid.q...@gmail.com* <grid.q...@gmail.com>> > To: *wtp-...@eclipse.org* <wtp-dev@eclipse.org> > Date: 11/13/2009 03:20 AM > Subject: [wtp-dev] how to display a element from other spe in the wsdl > editor > > Sent by: *wtp-dev-boun...@eclipse.org* <wtp-dev-boun...@eclipse.org> > ------------------------------ > > > > Hi all, > > For now, I am working on extending the wsdl editor to support ws-bpel > partnerlinktype. > I add a action on a porttype to generate bpel partnerlinktype and give > a label provider > for the bpel partnerlinktype. > But I only can get the generated partnerlinktype in the extensions tab > of the property view. > How can I get the bpel partnerlinktype display in the wsdl editor? > > If I want to display the partnerlinktype in the outline view, I need to > extend the wsdl modle? > How to do this? > > For now, I can use a wsdl element, for example a porttype, in eclipse > bpel editor, if I change > the porttype operation in the wsdl editor, in the bpel file ,will > change it automatically. > But if I change the reference porttype name of a partnerlinktype, the > porttype in the bpel file > will not change automatically. > I want to know, how can I make the change will be done automatically? > > Thanks a lot!! > > Grid_______________________________________________ > > wtp-dev mailing list* > **wtp-...@eclipse.org* <wtp-dev@eclipse.org> > > *https://dev.eclipse.org/mailman/listinfo/wtp-dev*<https://dev.eclipse.org/mailman/listinfo/wtp-dev> > > > _______________________________________________ > wtp-dev mailing list* > **wtp-...@eclipse.org* <wtp-dev@eclipse.org>* > > **https://dev.eclipse.org/mailman/listinfo/wtp-dev*<https://dev.eclipse.org/mailman/listinfo/wtp-dev> > > _______________________________________________ > wtp-dev mailing list > wtp-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/wtp-dev > > > _______________________________________________ > wtp-dev mailing list > wtp-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/wtp-dev > >
<<graycol.gif>>
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
