Thank you Jackie,

Now these corrections are made and the documentation has been modified as
discussed in versions 4.8.1, 4.8.0 and 4.7.0. I will also verify with Asela
whether he has any further comments regarding the changes made so far.

Best Regards,


On Wed, Mar 12, 2014 at 11:37 PM, Jackie Wheeler <jac...@wso2.com> wrote:

> Hi Rukshani,
>
> A few notes:
>
>    - The screen shot does not display unless you are logged in because it
>    is pointing off to some other space. Please attach it to this page and
>    point to it from there.
>    - When listing the library articles, please list the titles of the
>    articles and make them links. Don't just list the URLs, which are
>    meaningless (the user should not have to click the URL to find out what it
>    contains).
>    - I think the info on bindings is still not very clear. I found this
>    page [1], which provides a clear explanation, so let's just change the
>    first paragraph to "You can apply policies at the following levels in the
>    binding hierarchy" and make "binding" a link to [1].
>
> [1] http://www.w3schools.com/webservices/ws_wsdl_binding.asp
>
> Thanks,
> Jackie
>
>
> On Mon, Mar 10, 2014 at 11:37 PM, Rukshani Weerasinha 
> <ruksh...@wso2.com>wrote:
>
>> Hi,
>>
>> Now I have finished applying the changes mentioned by Jackie. However, I
>> have further questions relating to comments *5 * and *7 *before this
>> documentation can be considered finalised.
>>
>> With regard to comment number *7*, I included the following text under
>> the title *Defining Policies at Binding Level*.
>>
>> "The WSO2 ESB has the ability to apply policies at the binding
>> hierarchy. This hierarchy includes bindings for the WS-Policy for SOAP 1.1
>> and SOAP 1.2 endpoints which are referred to as SOAP bindings. A SOAP
>> binding specifies the style and the SOAP protocol to be used for operations
>> and messages handled by the WS-Policy."
>>
>> Asela, can you please verify whether this text accurately describes the
>> technical concept?
>>
>> Jackie, do you think this explanation is sufficient or do you think that
>> more information should be included?
>>
>> With regard to comment *5*, I referred the following articles:
>>
>>
>>    1. https://wso2.org/library/3786
>>    2. https://wso2.org/library/23
>>    3. https://wso2.org/library/3132
>>    4. http://msdn.microsoft.com/en-us/library/ms996497.aspx
>>
>> 1. has the same information that we agreed to remove from the page
>> itself. Therefore, this link too will be removed.
>>
>> The other articles have information about WS-Policy in general (not about
>> applying security policies for WSO2 ESB). It did not seem correct to
>> incorporate that information in this page. Therefore, I moved those links
>> to the top of the page (to the introductory paragraph which mentions
>> WS-Policy).
>>
>> Jackie and Asela, can you please let me know what you think about this?
>>
>> Best Regards,
>>
>>
>> On Mon, Mar 10, 2014 at 9:22 AM, Jackie Wheeler <jac...@wso2.com> wrote:
>>
>>> Hi Rukshani,
>>>
>>> Here are some comments for you.
>>>
>>> 1. Whereas the title should use title-case capitalization, the headings
>>> should use sentence-case capitalization. So "Binding Level" should be
>>> "Binding level", "Binding Operation Level" should be "Binding operation
>>> level", etc.
>>>
>>> 2. When there are multiple sections on a page, insert a table of
>>> contents at the top of the page and set the max heading level to 3.
>>>
>>> 3. The following text appears twice on the page, once at the beginning
>>> of the section and then again just before the info on services.xml:
>>>
>>> *Defining Policies at Bindings*
>>>
>>> The WSO2 Carbon has the ability to apply policies at the binding
>>> hierarchy. You can apply policies at three different policy subjects in the
>>> binding hierarchy. They are:
>>>
>>>    - *Binding level*
>>>    - *Binding operation level*
>>>    - *Binding message level*
>>>
>>> 4. Isn't the information on services.xml and the policy editor the part
>>> that was supposed to be removed?
>>>
>>> 5. Rather than point people to library articles, please review those
>>> articles and work the appropriate content into the documentation, where we
>>> can maintain it and keep it updated.
>>>
>>> 6. "The WSO2 Carbon" should be "WSO2 ESB".
>>>
>>> 7. We talk about the bindings hierarchy without giving any explanation
>>> as to what bindings are. Since this is a fairly technical concept, we
>>> should give a very brief introduction to it so people have context for the
>>> type of bindings we're talking about here.
>>>
>>> Thanks,
>>> Jackie
>>>
>>>
>>> On Sun, Mar 9, 2014 at 8:10 PM, Rukshani Weerasinha 
>>> <ruksh...@wso2.com>wrote:
>>>
>>>> Hi Asela,
>>>>
>>>> Can you please check the new sections I have added to the following
>>>> page?
>>>>
>>>> https://docs.wso2.org/display/ESB481/Applying+Security+Policies
>>>>
>>>> The subheadings of the new sections added are *Defining Policies at
>>>> Service Level *and *Policy Selection*. In addition, the following text
>>>> within inverted commas was added under *Defining Policies at Bindings.
>>>> *Can you please check these sections and send me your feedback.
>>>>
>>>> "Binding Level
>>>>
>>>> A security policy defined at the binding level is applicable to both in
>>>> and out messages generated by all the operations connected to the selected
>>>> binding.
>>>>  Binding Operation Level
>>>>
>>>> A security policy defined at the binding operation level is applicable
>>>> to both in and out messages generated by a specific operation connected
>>>> to the selected binding.
>>>>  Binding Operation Message Level
>>>>
>>>> A security policy defined at the binding operation message level
>>>> is applicable to either in or out messages generated by a specific
>>>> operation connected to the selected binding.
>>>>
>>>> *In Message* should be selected if you want the security policy to be
>>>> applicable only for the incoming messages of the ESB relating to the
>>>> selected binding.
>>>>
>>>> *Out Message* should be selected if you want the security policy to be
>>>> applicable only for the outgoing messages of the ESB relating to the
>>>> selected binding."
>>>>
>>>> I have also removed the section *WS-Policy Editor. *However, this
>>>> document still does not answer some of the questions asked in the Jira
>>>> task. Can we please discuss?
>>>>
>>>> Best Regards,
>>>>
>>>>
>>>> On Fri, Mar 7, 2014 at 4:23 PM, Asela Pathberiya <as...@wso2.com>wrote:
>>>>
>>>>> On Fri, Mar 7, 2014 at 4:15 PM, Rukshani Weerasinha <ruksh...@wso2.com>
>>>>> wrote:
>>>>> >
>>>>> >
>>>>> > Hi,
>>>>> >
>>>>> > The Jira task https://wso2.org/jira/browse/DOCUMENTATION-613requires the
>>>>> > following page to have more information about how to use the UI for
>>>>> the
>>>>> > Policy Selection UI.
>>>>> >
>>>>> > https://docs.wso2.org/display/ESB481/Applying+Security+Policies
>>>>> >
>>>>> > When I spoke to the Security Team, I was told that this UI is no
>>>>> longer used
>>>>> > and the functionality no longer works as it is supposed to. It was
>>>>> also said
>>>>> > that there is no services.xml file as mentioned in the documentation
>>>>> file.
>>>>> >
>>>>> > Does anyone have any further input on this? If this page refers to
>>>>> obsolete
>>>>> > functionality, shall I remove it?
>>>>>
>>>>>
>>>>> Yes.. what is in the current document, is not correct now, Because we
>>>>> are not exposing the service.xml file to configure policy attachments
>>>>> ...  Therefore,  users can use the "Policy Selection" management
>>>>> console UI to define policies for service, binding and operational,
>>>>> message levels...  But actually, there are some issues with the UI...
>>>>> some functions are not working as they are provided in the UI. I guess
>>>>> there are public jira for them..  But still we can define separate
>>>>> policies for service and binding level..  Therefore we can update the
>>>>> current document with "Policy Selection"  UI by providing
>>>>> configuration details with screen shots.
>>>>>
>>>>> However design view of  "The WS-Policy Editor"  that is no longer used
>>>>> and It is safe to remove it from the document.
>>>>>
>>>>> Thanks,
>>>>> Asela.
>>>>>
>>>>>
>>>>> >
>>>>> > Best Regards,
>>>>> >
>>>>> > --
>>>>> > Rukshani Weerasinha
>>>>> >
>>>>> > WSO2 Inc.
>>>>> > Web:http://wso2.com
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Rukshani Weerasinha
>>>>> >
>>>>> > WSO2 Inc.
>>>>> > Web:http://wso2.com
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks & Regards,
>>>>> Asela
>>>>>
>>>>> ATL
>>>>> Mobile : +94 777 625 933
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rukshani Weerasinha
>>>>
>>>> WSO2 Inc.
>>>> Web:http://wso2.com
>>>>
>>>>
>>>
>>>
>>> --
>>> *Jackie Wheeler*
>>> VP, Technical Content
>>> WSO2, Inc.
>>> Mobile: +1 510 725-2876
>>> http://wso2.com/
>>>
>>
>>
>>
>> --
>> Rukshani Weerasinha
>>
>> WSO2 Inc.
>> Web:http://wso2.com
>>
>>
>
>
> --
> *Jackie Wheeler*
> VP, Technical Content
> WSO2, Inc.
> Mobile: +1 510 725-2876
> http://wso2.com/
>



-- 
Rukshani Weerasinha

WSO2 Inc.
Web:http://wso2.com
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to