Is the configuration flow of DS as same as what is available in WSAS admin console ?.
Thank you Saminda > We should have data services IDE as a separate plugin independent from > WSAS IDE so that anybody can independently download only the Data > Services IDE to do DS development. > > Azeez > > Lahiru Sandakith wrote: >> The refactoring should be not that hard, because it was in order of the >> plugin architecture of eclipse. Currently we have 8 set of plugins for >> WSAS IDE and in that UI and core parts are also in different plugins. So >> the unified products can use them or bit alter it and use them. >> >> So what about the DATA Services IDE idea, I guess the work I started on >> having a wizard for data services dbs file creation would be anyway a >> necessary thing in the product line as I see and it can build >> independently as pluggable. I think this is the idea for any other >> plugins that we will have for other product that will come in unified >> set. >> >> Thanks >> Lahiru Sandakith >> >> Sanjiva Weerawarana wrote: >>> Sandakith, can you start figuring out to refactor the WSAS IDE in the >>> context of our product unification plans? We need an IDE for all the >>> products. >>> >>> Sanjiva. >>> >>> Lahiru Sandakith wrote: >>>> Hi Azeez, >>>> >>>> Afkham Azeez wrote: >>>>> Hi Folks, >>>>> It will be great if we could have some tooling support in Eclipse >>>>> for Data Services. >>>> +1, lets do it as a part of the WSAS IDE , but being able to self >>>> distribute also. >>>> >>>>> Here are some of the high level requirements I came up with. (in >>>>> order of priority) >>>>> >>>>> 1. The user will be able to connect to a database, and visually >>>>> define a data service. >>>> Will look at the WTP Datatools plugins so that we can get reuse the >>>> database stuff. >>>>> 2. The data services file (.dbs) will be validated >>>>> 3. When a .dbs file is loaded, the IDE will try to automatically >>>>> connect to the relevant data sources. An error message will be >>>>> displayed if connection cannot be established. There will be a retry >>>>> connection option for trying to connect to the data source at a >>>>> later time. >>>>> 4. Ability to debug the data service. This will enable users to find >>>>> errors in the .dbs file >>>>> 5. IntelliSense will be built into this. As a first step, we can >>>>> have auto completion of database table names, column names, queryIDs >>>>> and so forth >>>>> 6. Ability to upload a data service to a remote WSAS instance >>>>> >>>>> I have created a JIRA issue to track the progress of >>>>> this.(https://wso2.org/jira/browse/WSAS-715) >>>> Thanks >>>> Lahiru Sandakith >>>>> >>>>> Please contribute your valuable ideas & suggestions. >>>>> >>>>> Thanks >>>>> Azeez >>>>> >>>>> _______________________________________________ >>>>> Wsas-java-dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev >>>>> >>>> >>> >> > > > _______________________________________________ > Wsas-java-user mailing list > [EMAIL PROTECTED] > http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-user > _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
