Re: [Carbon-dev] Proxy Service UI Review Notes

[Samisa Abeysinghe]

Folks, we need to create Jira issues for each suggestion we came up with as
well as define a deadline by which we will fix these and then do a quick
second review to reevaluate.

On Wed, Feb 23, 2011 at 9:09 AM, Srinath Perera  wrote:

> +1 --Srinath
>
> On Tue, Feb 22, 2011 at 8:32 PM, Samisa Abeysinghe 
> wrote:
> >
> >
> > On Tue, Feb 22, 2011 at 8:24 PM, Hiranya Jayathilaka 
> > wrote:
> >>
> >> Hi Jorge,
> >>
> >> On Tue, Feb 22, 2011 at 6:47 PM, Jorge Infante Osorio 
> >> wrote:
> >>>
> >>> Hi Hiranya.
> >>> The community really appreciate this improvements.
> >>>
> >>> In the Wizard/services parameters:
> >>>
> >>> If the developer don´t know what parameters exist it´s very difficult
> to
> >>> use
> >>> this functionality, even imagined the possibilities that we can use in
> >>> different situation.
> >>>
> >>> I used two or three parameters due to it resolved me some errors in my
> >>> proxy
> >>> services but I found it after a search and find in the ESB
> documentation,
> >>> blogs, forum and this list. In this case you cannot use a list for
> >>> selecting
> >>> the parameters?
> >>
> >> Good point. However there are lots of parameters available for services,
> >> some defined in Axis2, some defined in Synapse and some defined
> elsewhere.
> >> Perhaps what we can do is to list down all the commonly used parameters
> in a
> >> drop down list. That should cover most use cases. We will also have the
> >> ability to type in the parameter name to support various other edge
> cases.
> >
> > +1. This is going to be a great usability improvement.
> >
> >>
> >> We were actually thinking about doing a similar thing in the property
> >> mediator UI (an idea originally suggested by Paul). Basically we were
> >> thinking of listing the most commonly used properties in a drop down. I
> >> think it makes a lot of sense to do the same with service parameters.
> Thanks
> >> for bringing this up.
> >> Thanks,
> >> Hiranya
> >>
> >>>
> >>> This is a usability requesting issue.
> >>>
> >>> Jorge.
> >>>
> >>> De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org]
> En
> >>> nombre de Hiranya Jayathilaka
> >>> Enviado el: martes, 22 de febrero de 2011 3:22
> >>> Para: carbon-dev
> >>> Asunto: [Carbon-dev] Proxy Service UI Review Notes
> >>>
> >>> Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and
> >>> Chanaka
> >>>
> >>> Templates:
> >>> • Use radio buttons instead of a drop down for selecting the target
> >>> endpoint
> >>> type (Enter URL/Predefined Endpoint/Pick from Registry)
> >>> • Add the "WSDL endpoint" to the type of endpoints available in the
> >>> target
> >>> endpoint type drop down. This will make the "WSDL based Proxy" template
> >>> unnecessary
> >>> • When a WSDL endpoint is selected, the service and port fields should
> be
> >>> shown with pre-populated drop downs.
> >>> • When a WSDL endpoint is selected the publish WSDL options should
> >>> display
> >>> the "Publish Same Service Contract" option
> >>> • Rename "Publish WSDL Option" to "Service Contract Publication
> Options"
> >>> • Rename "Back" button to "Cancel"
> >>> • Rename "Log and Forward Proxy" to "Logging Proxy"
> >>> • In Log and Forward proxy, rename "Log Level" to "Request Log Level".
> >>> Also
> >>> make it possible to disable request logging if needed
> >>> • In Log and Forward proxy, remove the "Log Responses" check box and
> add
> >>> a
> >>> "None" option to the response log level drop down
> >>> • In transformation proxy rename "XSLT" to "Request XSLT". Also make it
> >>> possible to skip the transformation by providing a checkbox
> >>>
> >>> Wizard:
> >>> • Move the "Service Parameters" out of the "Transport Settings" box
> >>> • Do not show the text boxes for entering parameter name and value
> until
> >>> the
> >>> user hit the "Add Parameter" option
> >>> • Properly label and describe each step and dialog box in the wizard
> >>> • Remove the proxy name input box from 2nd and 3rd steps of the wizard.
> >>> It
> >>> should be a fixed label instead
> >>> • Rename "In Sequence Options" to "Define In Sequence" (Similar changes
> >>> in
> >>> endpoint options and other sequence options)
> >>> • Under sequence options rename "Anonymous" to "Define Inline". Further
> >>> rename the "Add" option of the Anonymous sequence to "Create".
> >>> • Rename "Import" to "Use Existing Sequence"
> >>> • Make the texts of the radio buttons clickable
> >>> • In step 2, make it look obvious that at least one of the in-sequence
> or
> >>> the endpoint is necessary (might need to change the overall layout of
> the
> >>> wizard - eg: breaking individual option group to multiple steps in the
> >>> wizard)
> >>> • Move the service group input box further up (close to the service
> name
> >>> input box)
> >>> • "Load on Startup" should be changed to "Do not load on startup"
> >>>
> >>> General:
> >>> • Disable submit buttons when necessary fields are not filled out
> >>> • Come up with a generic custom JSP tag for input

Re: [Carbon-dev] Proxy Service UI Review Notes

[Srinath Perera]

+1 --Srinath

On Tue, Feb 22, 2011 at 8:32 PM, Samisa Abeysinghe  wrote:
>
>
> On Tue, Feb 22, 2011 at 8:24 PM, Hiranya Jayathilaka 
> wrote:
>>
>> Hi Jorge,
>>
>> On Tue, Feb 22, 2011 at 6:47 PM, Jorge Infante Osorio 
>> wrote:
>>>
>>> Hi Hiranya.
>>> The community really appreciate this improvements.
>>>
>>> In the Wizard/services parameters:
>>>
>>> If the developer don´t know what parameters exist it´s very difficult to
>>> use
>>> this functionality, even imagined the possibilities that we can use in
>>> different situation.
>>>
>>> I used two or three parameters due to it resolved me some errors in my
>>> proxy
>>> services but I found it after a search and find in the ESB documentation,
>>> blogs, forum and this list. In this case you cannot use a list for
>>> selecting
>>> the parameters?
>>
>> Good point. However there are lots of parameters available for services,
>> some defined in Axis2, some defined in Synapse and some defined elsewhere.
>> Perhaps what we can do is to list down all the commonly used parameters in a
>> drop down list. That should cover most use cases. We will also have the
>> ability to type in the parameter name to support various other edge cases.
>
> +1. This is going to be a great usability improvement.
>
>>
>> We were actually thinking about doing a similar thing in the property
>> mediator UI (an idea originally suggested by Paul). Basically we were
>> thinking of listing the most commonly used properties in a drop down. I
>> think it makes a lot of sense to do the same with service parameters. Thanks
>> for bringing this up.
>> Thanks,
>> Hiranya
>>
>>>
>>> This is a usability requesting issue.
>>>
>>> Jorge.
>>>
>>> De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
>>> nombre de Hiranya Jayathilaka
>>> Enviado el: martes, 22 de febrero de 2011 3:22
>>> Para: carbon-dev
>>> Asunto: [Carbon-dev] Proxy Service UI Review Notes
>>>
>>> Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and
>>> Chanaka
>>>
>>> Templates:
>>> • Use radio buttons instead of a drop down for selecting the target
>>> endpoint
>>> type (Enter URL/Predefined Endpoint/Pick from Registry)
>>> • Add the "WSDL endpoint" to the type of endpoints available in the
>>> target
>>> endpoint type drop down. This will make the "WSDL based Proxy" template
>>> unnecessary
>>> • When a WSDL endpoint is selected, the service and port fields should be
>>> shown with pre-populated drop downs.
>>> • When a WSDL endpoint is selected the publish WSDL options should
>>> display
>>> the "Publish Same Service Contract" option
>>> • Rename "Publish WSDL Option" to "Service Contract Publication Options"
>>> • Rename "Back" button to "Cancel"
>>> • Rename "Log and Forward Proxy" to "Logging Proxy"
>>> • In Log and Forward proxy, rename "Log Level" to "Request Log Level".
>>> Also
>>> make it possible to disable request logging if needed
>>> • In Log and Forward proxy, remove the "Log Responses" check box and add
>>> a
>>> "None" option to the response log level drop down
>>> • In transformation proxy rename "XSLT" to "Request XSLT". Also make it
>>> possible to skip the transformation by providing a checkbox
>>>
>>> Wizard:
>>> • Move the "Service Parameters" out of the "Transport Settings" box
>>> • Do not show the text boxes for entering parameter name and value until
>>> the
>>> user hit the "Add Parameter" option
>>> • Properly label and describe each step and dialog box in the wizard
>>> • Remove the proxy name input box from 2nd and 3rd steps of the wizard.
>>> It
>>> should be a fixed label instead
>>> • Rename "In Sequence Options" to "Define In Sequence" (Similar changes
>>> in
>>> endpoint options and other sequence options)
>>> • Under sequence options rename "Anonymous" to "Define Inline". Further
>>> rename the "Add" option of the Anonymous sequence to "Create".
>>> • Rename "Import" to "Use Existing Sequence"
>>> • Make the texts of the radio buttons clickable
>>> • In step 2, make it look obvious that at least one of the in-sequence or
>>> the endpoint is necessary (might need to change the overall layout of the
>>> wizard - eg: breaking individual option group to multiple steps in the
>>> wizard)
>>> • Move the service group input box further up (close to the service name
>>> input box)
>>> • "Load on Startup" should be changed to "Do not load on startup"
>>>
>>> General:
>>> • Disable submit buttons when necessary fields are not filled out
>>> • Come up with a generic custom JSP tag for input boxes that display a
>>> grey'ed out default/sample value
>>> • Display a single rooted registry browser popup
>>> • Change the layout of the input fields where the value is selected from
>>> the
>>> registry (Move the "Configuration Registry", "Governance Registry" links
>>> to
>>> the left and push the readonly text field further down)
>>> • Provide a separate link (and popup) for selecting local entries
>>>
>>> Thanks
>>> --
>>> Hiranya Jayathilaka
>>> Senior Software Engineer;
>>> 

Re: [Carbon-dev] Proxy Service UI Review Notes

[Samisa Abeysinghe]

On Tue, Feb 22, 2011 at 10:44 PM, Jorge Infante Osorio wrote:

> +1.
>
> By the way exist a place, blog, wiki, …. where we can find all this
> parameters and properties?
>

http://wso2.org/project/esb/java/3.0.0/docs/properties_guide.html



Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Proxy Service UI Review Notes

[Jorge Infante Osorio]

+1. 

By the way exist a place, blog, wiki, …. where we can find all this
parameters and properties? 

 

Jorge.

 

 

De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Samisa Abeysinghe
Enviado el: martes, 22 de febrero de 2011 10:02
Para: carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] Proxy Service UI Review Notes

 

 

On Tue, Feb 22, 2011 at 8:24 PM, Hiranya Jayathilaka <
<mailto:hira...@wso2.com> hira...@wso2.com> wrote:

Hi Jorge,

On Tue, Feb 22, 2011 at 6:47 PM, Jorge Infante Osorio <
<mailto:jorg...@uci.cu> jorg...@uci.cu> wrote:

Hi Hiranya.
The community really appreciate this improvements.

In the Wizard/services parameters:

If the developer don´t know what parameters exist it´s very difficult to use
this functionality, even imagined the possibilities that we can use in
different situation.

I used two or three parameters due to it resolved me some errors in my proxy
services but I found it after a search and find in the ESB documentation,
blogs, forum and this list. In this case you cannot use a list for selecting
the parameters?

 

Good point. However there are lots of parameters available for services,
some defined in Axis2, some defined in Synapse and some defined elsewhere.
Perhaps what we can do is to list down all the commonly used parameters in a
drop down list. That should cover most use cases. We will also have the
ability to type in the parameter name to support various other edge cases. 

 

+1. This is going to be a great usability improvement.

 

 

We were actually thinking about doing a similar thing in the property
mediator UI (an idea originally suggested by Paul). Basically we were
thinking of listing the most commonly used properties in a drop down. I
think it makes a lot of sense to do the same with service parameters. Thanks
for bringing this up.

 

Thanks,

Hiranya

 

This is a usability requesting issue.

Jorge.

De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Hiranya Jayathilaka
Enviado el: martes, 22 de febrero de 2011 3:22
Para: carbon-dev
Asunto: [Carbon-dev] Proxy Service UI Review Notes


Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and Chanaka

Templates:
• Use radio buttons instead of a drop down for selecting the target endpoint
type (Enter URL/Predefined Endpoint/Pick from Registry)
• Add the "WSDL endpoint" to the type of endpoints available in the target
endpoint type drop down. This will make the "WSDL based Proxy" template
unnecessary
• When a WSDL endpoint is selected, the service and port fields should be
shown with pre-populated drop downs.
• When a WSDL endpoint is selected the publish WSDL options should display
the "Publish Same Service Contract" option
• Rename "Publish WSDL Option" to "Service Contract Publication Options"
• Rename "Back" button to "Cancel"
• Rename "Log and Forward Proxy" to "Logging Proxy"
• In Log and Forward proxy, rename "Log Level" to "Request Log Level". Also
make it possible to disable request logging if needed
• In Log and Forward proxy, remove the "Log Responses" check box and add a
"None" option to the response log level drop down
• In transformation proxy rename "XSLT" to "Request XSLT". Also make it
possible to skip the transformation by providing a checkbox

Wizard:
• Move the "Service Parameters" out of the "Transport Settings" box
• Do not show the text boxes for entering parameter name and value until the
user hit the "Add Parameter" option
• Properly label and describe each step and dialog box in the wizard
• Remove the proxy name input box from 2nd and 3rd steps of the wizard. It
should be a fixed label instead
• Rename "In Sequence Options" to "Define In Sequence" (Similar changes in
endpoint options and other sequence options)
• Under sequence options rename "Anonymous" to "Define Inline". Further
rename the "Add" option of the Anonymous sequence to "Create". 
• Rename "Import" to "Use Existing Sequence"
• Make the texts of the radio buttons clickable
• In step 2, make it look obvious that at least one of the in-sequence or
the endpoint is necessary (might need to change the overall layout of the
wizard - eg: breaking individual option group to multiple steps in the
wizard)
• Move the service group input box further up (close to the service name
input box)
• "Load on Startup" should be changed to "Do not load on startup"

General:
• Disable submit buttons when necessary fields are not filled out
• Come up with a generic custom JSP tag for input boxes that display a
grey'ed out default/sample value
• Display a single rooted registry browser popup
• Change the layout of the input fields where the value is selected from

Re: [Carbon-dev] Proxy Service UI Review Notes

[Samisa Abeysinghe]

On Tue, Feb 22, 2011 at 8:24 PM, Hiranya Jayathilaka wrote:

> Hi Jorge,
>
> On Tue, Feb 22, 2011 at 6:47 PM, Jorge Infante Osorio wrote:
>
>> Hi Hiranya.
>> The community really appreciate this improvements.
>>
>> In the Wizard/services parameters:
>>
>> If the developer don´t know what parameters exist it´s very difficult to
>> use
>> this functionality, even imagined the possibilities that we can use in
>> different situation.
>>
>> I used two or three parameters due to it resolved me some errors in my
>> proxy
>> services but I found it after a search and find in the ESB documentation,
>> blogs, forum and this list. In this case you cannot use a list for
>> selecting
>> the parameters?
>
>
> Good point. However there are lots of parameters available for services,
> some defined in Axis2, some defined in Synapse and some defined elsewhere.
> Perhaps what we can do is to list down all the commonly used parameters in a
> drop down list. That should cover most use cases. We will also have the
> ability to type in the parameter name to support various other edge cases.
>

+1. This is going to be a great usability improvement.


>
> We were actually thinking about doing a similar thing in the property
> mediator UI (an idea originally suggested by Paul). Basically we were
> thinking of listing the most commonly used properties in a drop down. I
> think it makes a lot of sense to do the same with service parameters. Thanks
> for bringing this up.
>
> Thanks,
> Hiranya
>
>
>> This is a usability requesting issue.
>>
>> Jorge.
>>
>> De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
>> nombre de Hiranya Jayathilaka
>> Enviado el: martes, 22 de febrero de 2011 3:22
>> Para: carbon-dev
>> Asunto: [Carbon-dev] Proxy Service UI Review Notes
>>
>> Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and
>> Chanaka
>>
>> Templates:
>> • Use radio buttons instead of a drop down for selecting the target
>> endpoint
>> type (Enter URL/Predefined Endpoint/Pick from Registry)
>> • Add the "WSDL endpoint" to the type of endpoints available in the target
>> endpoint type drop down. This will make the "WSDL based Proxy" template
>> unnecessary
>> • When a WSDL endpoint is selected, the service and port fields should be
>> shown with pre-populated drop downs.
>> • When a WSDL endpoint is selected the publish WSDL options should display
>> the "Publish Same Service Contract" option
>> • Rename "Publish WSDL Option" to "Service Contract Publication Options"
>> • Rename "Back" button to "Cancel"
>> • Rename "Log and Forward Proxy" to "Logging Proxy"
>> • In Log and Forward proxy, rename "Log Level" to "Request Log Level".
>> Also
>> make it possible to disable request logging if needed
>> • In Log and Forward proxy, remove the "Log Responses" check box and add a
>> "None" option to the response log level drop down
>> • In transformation proxy rename "XSLT" to "Request XSLT". Also make it
>> possible to skip the transformation by providing a checkbox
>>
>> Wizard:
>> • Move the "Service Parameters" out of the "Transport Settings" box
>> • Do not show the text boxes for entering parameter name and value until
>> the
>> user hit the "Add Parameter" option
>> • Properly label and describe each step and dialog box in the wizard
>> • Remove the proxy name input box from 2nd and 3rd steps of the wizard. It
>> should be a fixed label instead
>> • Rename "In Sequence Options" to "Define In Sequence" (Similar changes in
>> endpoint options and other sequence options)
>> • Under sequence options rename "Anonymous" to "Define Inline". Further
>> rename the "Add" option of the Anonymous sequence to "Create".
>> • Rename "Import" to "Use Existing Sequence"
>> • Make the texts of the radio buttons clickable
>> • In step 2, make it look obvious that at least one of the in-sequence or
>> the endpoint is necessary (might need to change the overall layout of the
>> wizard - eg: breaking individual option group to multiple steps in the
>> wizard)
>> • Move the service group input box further up (close to the service name
>> input box)
>> • "Load on Startup" should be changed to "Do not load on startup"
>>
>> General:
>> • Disable submit buttons when necessary fields are not filled out
>> • Come up with a generic custom JSP tag for input boxes that display a
>> grey'ed out default/sample value
>> • Display a single rooted registry browser popup
>> • Change the layout of the input fields where the value is selected from
>> the
>> registry (Move the "Configuration Registry", "Governance Registry" links
>> to
>> the left and push the readonly text field further down)
>> • Provide a separate link (and popup) for selecting local entries
>>
>> Thanks
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> Carbon-dev mailing list
>> Carb

Re: [Carbon-dev] Proxy Service UI Review Notes

[Hiranya Jayathilaka]

Hi Jorge,

On Tue, Feb 22, 2011 at 6:47 PM, Jorge Infante Osorio wrote:

> Hi Hiranya.
> The community really appreciate this improvements.
>
> In the Wizard/services parameters:
>
> If the developer don´t know what parameters exist it´s very difficult to
> use
> this functionality, even imagined the possibilities that we can use in
> different situation.
>
> I used two or three parameters due to it resolved me some errors in my
> proxy
> services but I found it after a search and find in the ESB documentation,
> blogs, forum and this list. In this case you cannot use a list for
> selecting
> the parameters?


Good point. However there are lots of parameters available for services,
some defined in Axis2, some defined in Synapse and some defined elsewhere.
Perhaps what we can do is to list down all the commonly used parameters in a
drop down list. That should cover most use cases. We will also have the
ability to type in the parameter name to support various other edge cases.

We were actually thinking about doing a similar thing in the property
mediator UI (an idea originally suggested by Paul). Basically we were
thinking of listing the most commonly used properties in a drop down. I
think it makes a lot of sense to do the same with service parameters. Thanks
for bringing this up.

Thanks,
Hiranya


> This is a usability requesting issue.
>
> Jorge.
>
> De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
> nombre de Hiranya Jayathilaka
> Enviado el: martes, 22 de febrero de 2011 3:22
> Para: carbon-dev
> Asunto: [Carbon-dev] Proxy Service UI Review Notes
>
> Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and Chanaka
>
> Templates:
> • Use radio buttons instead of a drop down for selecting the target
> endpoint
> type (Enter URL/Predefined Endpoint/Pick from Registry)
> • Add the "WSDL endpoint" to the type of endpoints available in the target
> endpoint type drop down. This will make the "WSDL based Proxy" template
> unnecessary
> • When a WSDL endpoint is selected, the service and port fields should be
> shown with pre-populated drop downs.
> • When a WSDL endpoint is selected the publish WSDL options should display
> the "Publish Same Service Contract" option
> • Rename "Publish WSDL Option" to "Service Contract Publication Options"
> • Rename "Back" button to "Cancel"
> • Rename "Log and Forward Proxy" to "Logging Proxy"
> • In Log and Forward proxy, rename "Log Level" to "Request Log Level". Also
> make it possible to disable request logging if needed
> • In Log and Forward proxy, remove the "Log Responses" check box and add a
> "None" option to the response log level drop down
> • In transformation proxy rename "XSLT" to "Request XSLT". Also make it
> possible to skip the transformation by providing a checkbox
>
> Wizard:
> • Move the "Service Parameters" out of the "Transport Settings" box
> • Do not show the text boxes for entering parameter name and value until
> the
> user hit the "Add Parameter" option
> • Properly label and describe each step and dialog box in the wizard
> • Remove the proxy name input box from 2nd and 3rd steps of the wizard. It
> should be a fixed label instead
> • Rename "In Sequence Options" to "Define In Sequence" (Similar changes in
> endpoint options and other sequence options)
> • Under sequence options rename "Anonymous" to "Define Inline". Further
> rename the "Add" option of the Anonymous sequence to "Create".
> • Rename "Import" to "Use Existing Sequence"
> • Make the texts of the radio buttons clickable
> • In step 2, make it look obvious that at least one of the in-sequence or
> the endpoint is necessary (might need to change the overall layout of the
> wizard - eg: breaking individual option group to multiple steps in the
> wizard)
> • Move the service group input box further up (close to the service name
> input box)
> • "Load on Startup" should be changed to "Do not load on startup"
>
> General:
> • Disable submit buttons when necessary fields are not filled out
> • Come up with a generic custom JSP tag for input boxes that display a
> grey'ed out default/sample value
> • Display a single rooted registry browser popup
> • Change the layout of the input fields where the value is selected from
> the
> registry (Move the "Configuration Registry", "Governance Registry" links to
> the left and push the readonly text field further down)
> • Provide a separate link (and popup) for selecting local entries
>
> Thanks
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
__

Re: [Carbon-dev] Proxy Service UI Review Notes

[Jorge Infante Osorio]

Hi Hiranya.
The community really appreciate this improvements.

In the Wizard/services parameters: 

If the developer don´t know what parameters exist it´s very difficult to use
this functionality, even imagined the possibilities that we can use in
different situation.  

I used two or three parameters due to it resolved me some errors in my proxy
services but I found it after a search and find in the ESB documentation,
blogs, forum and this list. In this case you cannot use a list for selecting
the parameters? This is a usability requesting issue.

Jorge.

De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Hiranya Jayathilaka
Enviado el: martes, 22 de febrero de 2011 3:22
Para: carbon-dev
Asunto: [Carbon-dev] Proxy Service UI Review Notes

Participants: Sanjiva, Samisa, Shankar, ESB team, QA team, Amal and Chanaka

Templates:
• Use radio buttons instead of a drop down for selecting the target endpoint
type (Enter URL/Predefined Endpoint/Pick from Registry)
• Add the "WSDL endpoint" to the type of endpoints available in the target
endpoint type drop down. This will make the "WSDL based Proxy" template
unnecessary
• When a WSDL endpoint is selected, the service and port fields should be
shown with pre-populated drop downs.
• When a WSDL endpoint is selected the publish WSDL options should display
the "Publish Same Service Contract" option
• Rename "Publish WSDL Option" to "Service Contract Publication Options"
• Rename "Back" button to "Cancel"
• Rename "Log and Forward Proxy" to "Logging Proxy"
• In Log and Forward proxy, rename "Log Level" to "Request Log Level". Also
make it possible to disable request logging if needed
• In Log and Forward proxy, remove the "Log Responses" check box and add a
"None" option to the response log level drop down
• In transformation proxy rename "XSLT" to "Request XSLT". Also make it
possible to skip the transformation by providing a checkbox

Wizard:
• Move the "Service Parameters" out of the "Transport Settings" box
• Do not show the text boxes for entering parameter name and value until the
user hit the "Add Parameter" option
• Properly label and describe each step and dialog box in the wizard
• Remove the proxy name input box from 2nd and 3rd steps of the wizard. It
should be a fixed label instead
• Rename "In Sequence Options" to "Define In Sequence" (Similar changes in
endpoint options and other sequence options)
• Under sequence options rename "Anonymous" to "Define Inline". Further
rename the "Add" option of the Anonymous sequence to "Create". 
• Rename "Import" to "Use Existing Sequence"
• Make the texts of the radio buttons clickable
• In step 2, make it look obvious that at least one of the in-sequence or
the endpoint is necessary (might need to change the overall layout of the
wizard - eg: breaking individual option group to multiple steps in the
wizard)
• Move the service group input box further up (close to the service name
input box)
• "Load on Startup" should be changed to "Do not load on startup"

General:
• Disable submit buttons when necessary fields are not filled out
• Come up with a generic custom JSP tag for input boxes that display a
grey'ed out default/sample value
• Display a single rooted registry browser popup
• Change the layout of the input fields where the value is selected from the
registry (Move the "Configuration Registry", "Governance Registry" links to
the left and push the readonly text field further down)
• Provide a separate link (and popup) for selecting local entries 

Thanks
-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev