Introducing form based UI for ESB Tooling

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Introducing form based UI for ESB Tooling

Buddhima Wijeweera
Hi All,

For ESB 5.x series we have separated esb-tooling and done certain modifications to it’s earlier version (ESB tooling in Dev-Studio). One considerable change is using forms for some ESB artifacts instead of using property window. After discussions, following areas are identified that need to be transformed.
  1. Scheduled Tasks
  2. Message Stores
  3. Message Processors
  4. Endpoints (Address, Default, HTTP, WSDL named endpoints)
  5. Local Entries
Currently the team is working on refactoring above artifacts to give form based editing functionalities and with that we expect to provide more convenient configuration UI for ESB configuration developers.
Following are few screenshots of form UIs

Scheduled Task


Message Store


Message Processor

Address Endpoint



Please note that still this is at working in progress stage and will be out there with upcoming releases.

Also would like to know your opinion on this.

Thank you,

--
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: +94 71 427 9966

_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: Introducing form based UI for ESB Tooling

sohani
Hi All,

Please find the screenshots of Endpoint Form Pages.

1. Address Endpoint Form Page


2. Adding properties for Address Endpoints


3. Default Endpoint Form Page


4. WSDL Endpoint Form Page


5. Template Endpoint Form Page


​6. Adding parameters for Template Endpoints


​7. HTTP Endpoint Form Page





Also, please find the screenshots of adding properties, endpoint keys and sequence keys etc for schedule task, MP etc

1. Adding Task Implementation properties for Schedule Task


2. Adding Endpoint Key in Message Processor


3. Adding Sequence Key in Message Processor


4. Adding custom parameters in Message Processors


Regards,
Sohani



Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774

On Tue, Jul 5, 2016 at 10:07 PM, Buddhima Wijeweera <[hidden email]> wrote:
Hi All,

For ESB 5.x series we have separated esb-tooling and done certain modifications to it’s earlier version (ESB tooling in Dev-Studio). One considerable change is using forms for some ESB artifacts instead of using property window. After discussions, following areas are identified that need to be transformed.
  1. Scheduled Tasks
  2. Message Stores
  3. Message Processors
  4. Endpoints (Address, Default, HTTP, WSDL named endpoints)
  5. Local Entries
Currently the team is working on refactoring above artifacts to give form based editing functionalities and with that we expect to provide more convenient configuration UI for ESB configuration developers.
Following are few screenshots of form UIs

Scheduled Task


Message Store


Message Processor

Address Endpoint



Please note that still this is at working in progress stage and will be out there with upcoming releases.

Also would like to know your opinion on this.

Thank you,

--
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: <a href="tel:%2B94%2071%20427%209966" value="+94714279966" target="_blank">+94 71 427 9966


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: Introducing form based UI for ESB Tooling

Scott Bechtel
I love this idea!

I find the property views hard to read and skip straight to the raw XML. Also it would be great to have the same view when you edit that you had when you first entered the data. But this change seems like a nice compromise if the view can't be the same.


On Thu, Jul 7, 2016 at 2:07 AM, Sohani Weerasinghe <[hidden email]> wrote:
Hi All,

Please find the screenshots of Endpoint Form Pages.

1. Address Endpoint Form Page


2. Adding properties for Address Endpoints


3. Default Endpoint Form Page


4. WSDL Endpoint Form Page


5. Template Endpoint Form Page


​6. Adding parameters for Template Endpoints


​7. HTTP Endpoint Form Page





Also, please find the screenshots of adding properties, endpoint keys and sequence keys etc for schedule task, MP etc

1. Adding Task Implementation properties for Schedule Task


2. Adding Endpoint Key in Message Processor


3. Adding Sequence Key in Message Processor


4. Adding custom parameters in Message Processors


Regards,
Sohani



Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : <a href="tel:%2B94%20716439774" value="+94716439774" target="_blank">+94 716439774

On Tue, Jul 5, 2016 at 10:07 PM, Buddhima Wijeweera <[hidden email]> wrote:
Hi All,

For ESB 5.x series we have separated esb-tooling and done certain modifications to it’s earlier version (ESB tooling in Dev-Studio). One considerable change is using forms for some ESB artifacts instead of using property window. After discussions, following areas are identified that need to be transformed.
  1. Scheduled Tasks
  2. Message Stores
  3. Message Processors
  4. Endpoints (Address, Default, HTTP, WSDL named endpoints)
  5. Local Entries
Currently the team is working on refactoring above artifacts to give form based editing functionalities and with that we expect to provide more convenient configuration UI for ESB configuration developers.
Following are few screenshots of form UIs

Scheduled Task


Message Store


Message Processor

Address Endpoint



Please note that still this is at working in progress stage and will be out there with upcoming releases.

Also would like to know your opinion on this.

Thank you,

--
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: <a href="tel:%2B94%2071%20427%209966" value="+94714279966" target="_blank">+94 71 427 9966


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture



_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture