Hi All, Please see my comments inline.
On Thu, Nov 14, 2013 at 11:43 AM, Sriskandarajah Suhothayan <[email protected]>wrote: > > Hi all, > > As we are planing to go for the CEP 3.0.0 plugin, I think we have to focus > more on the its GUI and the usability aspects of it. > > CEP has two main concepts > 1. Streams > 2. Execution Plan. > > Execution Plan creation can look like the CEP 3.0.0 UI. > > But for Streams I think we have to do some Improvements. I'm not expecting > all this to be done for the next release, but this kind of a long term > vision, we have to find what should be and can be done now and execute > them. Please give your comments and improvements. > > *1*.We need to have some sort of virtual Stream Store in DevS itself, > this will allow us to select streams from drop down at the Execution Plan > creation GUI. > > 1.1 This Stream Store will be populated by connecting DevS with CEP and/or > by exporting Streams from CEP and importing to DevS and/or through > configs. > > (for now we'll go with configs) > > I believe these Streams are stored in the registry. In that we can provide users following options to select a stream as in ESB Editor. 1. From Workspace - Locate and list the stream definitions in the Eclipse Workspace 2. From Registry - Allow user to browse registry of the CEP and select from it. This approach is consistent across our other tools and users will feel comfortable around this since it is the general practice in in DevS. > > *2*. We can have a similar UI of CEP for Stream creation > +1 > > *3*. Event Builder and Formatters will be associated to the Streams. > > 3.1 Stream listing UI will list its associated Builders and Formatters > under it. Event Builder and Formatters won't have a separate listing > page/GUI. Therefore Builder and Formatter can be only created after > creating the Stream. > > > 3.2 Need to figure out a proper way to export new/modified streams and > apply that to CEP. > > Correct. Previously we used to have just one file. Now that we have multiple files, we may have to introduce a packaging mechanism for them with a new deployer. Need to discuss this further whether we can reuse the existing Registry Resource artifacts, etc for this and avoid introduction of new packaging mechanism. > > 3.3 Event Formatter creation GUI can look like the current CEP 3.0.0 UI. > > > 3.4 Event Builder GUI need to be fixed, the Event Builder GUI also need to > use drop down to select the Stream. The mapping form need to be auto > created based on the selected stream whereby only allowing the user to fill > the incoming message related info. > > Aslong as Stream has the necessary information to do this, we can do it. > > *4*. Input and Output Adapter types and their Message configurations > fields for the Event Builder and Formatter need to be imported to the DevS. > > 4.1 The available Adapter types and their Message configurations fields > will be imported by connecting DevS with CEP and/or by exporting from CEP > and importing to DevS and/or through configs. > > (for now we'll go with configs) > > This is again have to consider how they are persisted in the CEP side at the moment and decide how we should do it. Shall we have a brief design discussion next week over this to finalize these gray areas? Thanks and Regards, Harshana > > Any suggestions appreciated! > > Regards > Suho > > -- > > *S. Suhothayan * > Associate Technical Lead, > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/> twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > > -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
