Hi Sanjiva, Yeah, sorry, I wasn't actually very clear about what I meant. I was giving the service template idea as an example of what we are planning on the re-usability features of data services. And yeah, as you said, Jorge's requirements can be implemented far more easily. Also yeah, will send a note to architecture@ with the design beforehand.
Cheers, Anjana. On Wed, Mar 23, 2011 at 10:28 AM, Sanjiva Weerawarana <sanj...@wso2.com> wrote: > Anjana please do a design of this and send to architecture@ before > implementing it. > I think what Jorge suggests is simpler than that .. not a full service > template concept but just being able to reuse mapping definitions across > queries within the same service. > > We can do that relatively easily by simply having a naming mechanism and > allowing those to be defined outside of queries (for clarity). > Sanjiva. > On Wed, Mar 23, 2011 at 10:14 AM, Anjana Fernando <anj...@wso2.com> wrote: >> >> Hi Jorge, >> >> Thank you for the suggestions. Yeah we are planning to provide similar >> functionality, for example, we are considering having a feature like a >> data service template, where other data services can derive from it. >> So basically, in the future we are going to consider re-usability >> factors of data services, for example, data sources, queries, and also >> as you said, data types as well. >> >> Cheers, >> Anjana. >> >> On Tue, Mar 22, 2011 at 9:49 PM, Jorge Infante Osorio <jorg...@uci.cu> >> wrote: >> > Hi all. >> > Greats improvement to the DS usability. >> > >> > A question: Do you take into account the reusability of data input >> > mapping >> > and the data output mapping of one query into another queries? >> > >> > In some case I have to copy/paste from the code of one query to another >> > the >> > input or output mapping elements because I don´t have a way to reuse >> > them. >> > >> > Also if I duplicate this mapping elements I need to separate it using >> > namespace to avoid name class collision in the client side during code >> > gen. >> > >> > Thanks, >> > Jorge. >> > >> > De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En >> > nombre de Dinusha Senanayaka >> > Enviado el: martes, 22 de marzo de 2011 11:16 >> > Para: carbon-dev@wso2.org >> > Asunto: [Carbon-dev] Notes From Data Services UI Review - Round 2 >> > >> > Mentioned below are the notes taken during the DS UI wizard usability >> > review >> > round 2. >> > >> > In service details page: >> > Manage Password >> > >> > ---------------------------------------------------------------------------- >> > -- >> > Secure vault should be server specific configuration. >> > User should be able to override password provider class by his own class >> > if >> > needed. >> > >> > Remove the flag enable distributed transactions. >> > >> > >> > In Add New Data Source page: >> > >> > ---------------------------------------------------------------------------- >> > -- >> > Provide check-box instead of drop down box to identify XA-DataSources >> > and >> > non-XA_DataSources. >> > Currently XA specific configurations are defined in separate page. >> > Define XA >> > specific configuration in the same location as we are adding a new data >> > source. >> > >> > Introduce a way to share all data sources across data services. >> > Currently if we create a data source through the DS wizard, it is >> > specific >> > for that service. >> > If we need to share the same data source from collection of services >> > there >> > is no option. >> > >> > >> > In addQuery.jsp: >> > >> > ---------------------------------------------------------------------------- >> > ---- >> > Change IDs as names - Eg: Query Id - Query Name >> > If the same query name is given validate at the given time, not when the >> > next button click. >> > >> > >> > SQL Dialects: >> > >> > ---------------------------------------------------------------------------- >> > ----- >> > Enable user to decide upon the keywords that can be used to identify the >> > database types (currently we are using standard driver >> > prifixes such as mssql, mysql,etc as they appear in the jdbc url), keep >> > a >> > default location to keep the dialect types. >> > >> > >> > Allowed User Roles: >> > >> > ---------------------------------------------------------------------------- >> > ----- >> > This should be an advanced configuration. >> > User roles can be applied only if security is applied. >> > If click on user roles, pop up a message telling service should be >> > secured >> > to apply user roles. >> > Implementation of the everyone role should be reconsidered and handled >> > from >> > IS side. >> > >> > If there is only one data source defined, user should not have to define >> > data source again and again when adding a new query. >> > In this scenario, the corresponding Data source should be considered by >> > default for queries that are defined. >> > >> > >> > General comments: >> > >> > ---------------------------------------------------------------------------- >> > ------ >> > If there are default values associated with fields, they can be shown in >> > input fields before the user enters the desired value and, >> > at that point the default value should be disappeared with the mouse >> > enter >> > event gets triggered. >> > >> > Put the advanced configurations into a seperate section and hide them. >> > >> > Add paginations to add new queries and add new operations >> > >> > >> > Please add any points if i have missed. >> > >> > Regards, >> > Dinusha. >> > >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> >> >> >> -- >> Anjana Fernando >> Software Engineer >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > -- Anjana Fernando Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware _______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
