Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Bugzilla 165556"

Line 88: Line 88:
 
<br>
 
<br>
  
To remove a content rule , press Remove Button.Even the text file will be modified accordingly.
+
To remove a content rule , press Remove Button.Even the membershipcontentrule tag in the  text file will be removed from the text file.
 
               [[Image:AfterRemove.jpg]]
 
               [[Image:AfterRemove.jpg]]
  

Revision as of 08:58, 8 February 2007

Discuss this feature

TPTP feature: 165556

Author: Krishna C Shastry
email: krshastr@in.ibm.com
Committer email: bsubram@us.ibm.com(Balan Subramanian)
Last updated:


Rough workload estimate for design/code/test in person weeks:

ProcessSizing
Design1
Code3
Test1
Documentation0.5
Total 5.5

Rough workload estimate for build and infrastructure in person days: 0.0


Requirement summary

A Service Group is a collection of WS-Resources, each represented as a WS-ServiceGroupEntry, which follow some constraints (possibly none) defined by the Service Group. As part of the definition of a SG, the user must be able to define the membership constraint rules using the service group editor.

User interactions

User interface

Click on New>>Other>>Tooling For Webservice Distributed Management>>New WSDM Manageability Endpoint Type, the following editor will appear.

        File:MRTEditor.jpg


Click on Service Group Check Box, another page is added to the current editor and corresponding capabilities will be added.

        File:MRTEditorAfterCheck.jpg


Click on SGDefinition form.This contains a table where user can add ,edit and delete a membership content rule.

        File:SGEditor.jpg 


Click on Add button , a dialog will come up as shown

         File:AfterClickOnAdd.jpg


Click on AddQNames button, another Dialog will come as shown and user can select the required QNames.

          File:QNamesOKButton.jpg


Select the required QNames and Press OK

        File:AfterClickOnAddQNamesSelected.jpg


Here user can delete teh previously selected QNames. Press OK.

         File:OKPressInMDialog.jpg


Table looks like this.Now save the file.The text file will contain an entry where memebership content rules are mentioned.

         File:AfterAdd.jpg


         File:AfterSave.jpg


To change the contents of the rule, click on Edit button.A dialog comes up where user can change the rule name and modify the QNames(Add extra QNames or Delete the existing QNames) and press OK.

        File:ClickOnEdit.jpg


          File:AfterEdit.jpg


Right Click on mrt file and click OpenWith>>Text Editor.You can see the edited text file as compared to the previous text file.

          File:TextFileAfterEdit.jpg


To remove a content rule , press Remove Button.Even the membershipcontentrule tag in the text file will be removed from the text file.

              File:AfterRemove.jpg
              File:TextFileAfterRemove.jpg 

Extension points

Code interfaces

Design summary

Service Group editor is added as another page to the existing MRT editor.So while creating the MRT file,wizard page will contain two check boxes namely i) Service Group ii) Mata Data Exchange Whenever user selects the service group check box corresponding capabilities will be added to the mrt model and a page will be added to the mrt Editor.In this page user can add,edit and delete the rule.

  • 1. Service group is a resource type. A pre defined WSDL file for this resource type, capabilities like WS-resource Property,WS-resource lifetime,WS-Notification Producer and WS-MetadataExchange are supplied to the API designed by Andrew, which will produce the merged WSDL, which will be checked in.
  • 2. Membership content rule class in the service group ecore model is added to the mrt ecore model. It has content element (Q-names).
  • 3. MRT wizard page will contain two check boxes to select Service Group or MetaData exchange.For Service Group WS-resource Property,WS-resource lifetime,WS-Notification Producer,WS-resource properties ,Service group registration capabilities and WS-MetadataExchange capabilities will be added.For MetaData Exchange WS-MetadataExchangcapability will added.
  • 4. After user clicks on "New WSDM Manageable Endpoint Type" under "Tooling for Web Service Distributed Management" in new >>other, a wizard page will come up, where user can select either service group or meta data exchange.On clicking finish all the corresponding capabilities added to the model and as told earlier a page will be added to the existing mrt editor, where user can add,edit and delete the membership rule.
  • 5. When the user right clicks on the mrt file and clicks on “generate java code” SG.dd file will be created which will have the SG.mrt file in the resource type tab and the corresponding capabilities listed, which are not editable.So DD editor must be changed to incorporate service group definition.
  • 6. Just before the code generation, membership content rule must be persisted in the WSDL of the previously generated resource type (SG.mrt ) by creating a replica of it in-memory.
  • Service group editor is going to take care only the membership content rule.

Membership rules editor:
The MRT editor will also have two check box namely 1) Service Group 2) MEX. Whenever user checks service group check box, corresponding capabilities will be added to tree viewer and a page added to the editor.This will contain table tree viewer to accommodate membership rules.The membership rules are resource property values. So the resource properties document for the service group resource contains not only these property definitions but their values as well. This will be persisted as initialization parameters for the service group or using the persistence mechanism. Membership rules is a set of rules that follow the schema specified in the WS-ServiceGroups specification. User can specify any number of membership rules for a resource. User also has the option not to provide any rules. A membership rule can be specified in terms of the content of the resource properties exposed by the resource. A rule consist of content specification. Each row represents a rule and the first column will be used to specify the rule name, the second for the content Qnames .i.e. Qnames of the child elements that must be present in the resource properties document of the member resource. This column can contain multiple qnames listed for each rule. Editor will contain three buttons.

  • New Rule: New Rule will bring up a dialog that contains an option to select the content Qnames.
  • For Content QNames, - A browse option is provided, that can be used by the user to look at defined capabilities in the workspace an pick the defined type names in XSDs of the those capabilities. - As a stretch goal, allow user to specify an EPR and connect to the resource at the EPR, show the resource properties document (by doing a generic QueryResourceProperty operation), and show the elements in that document for the user to pick up


  • Edit Rule: Edit rule uses the same dialog as New Rule uses, but will also populate the existing content of the selected rule in the dialog.
  • Delete rule: The Delete rule will delete the selected rule from the list.

Back to the top