On Sun, Mar 27, 2011 at 3:50 PM, Isuru Suriarachchi <is...@wso2.com> wrote:
> > > On Sun, Mar 27, 2011 at 3:28 PM, Afkham Azeez <az...@wso2.com> wrote: > >> >> >> On Sun, Mar 27, 2011 at 3:04 PM, Isuru Suriarachchi <is...@wso2.com>wrote: >> >>> Hi all, >>> >>> I'm working on $subject. There are some grey areas that we have to >>> discuss and come to a conclusion. >>> >>> 1. DS UI component has the dashboard menu items registered in it's >>> component.xml. But AS doesn't ship the dashboard. So can we remove this from >>> the DS UI component and add it to somewhere like the DS styles bundle such >>> that it'll be registered only in DSS? >>> >>> >> Does DS UI require the dashboard? What happens if a user simply install DS >> on some Carbon server? Does it pull in the dashboard component as well? If >> so, that is something that is not required. A user who wants DS >> functionality may not necessarily require the dashboard. Features should >> include the minimum required set. >> > > +1. According to the current DS component, it adds the menu item through > the DS UI component. But it doesn't pull the dashboard components. So if a > user install DS on AS, menu item will be there and if the user clicks on it, > there'll be a white page. So I think the dashboard should be added into the > styles bundle in DSS. > No ACK from DS team? Shall I move this dashboard registration into DS styles bundle's component.xml? Thanks, ~Isuru > > There's one more thing that I forgot to mention in my initial mail. Should > we add DS features into AS Stratos service as well? May be that's not > necessary as the user gets access to all the services including DS service. > > Thanks, > ~Isuru > > >> >> >>> 2. How are we going to manage documentation? Are we going to add all DS >>> related docs into AS docs pack or can we add a link to the DS documentation? >>> >> >> For a user it is convenient to have everything in a single download. >> >> >>> >>> 3. Are we going to ship all the DS samples in AS as well? Or is it enough >>> to ship one or two most commonly used ones? >>> >>> >> Again, for users it is convenient if all related items are there in the >> same place. I'd prefer to have samples/dataservices/ and have externals to >> all DS samples. >> >> >> >>> Thanks, >>> ~Isuru >>> >>> -- >>> Isuru Suriarachchi >>> Technical Lead & Product Manager, WSO2 Application Server >>> WSO2 Inc. http://wso2.com >>> email : is...@wso2.com >>> blog : http://isurues.wordpress.com/ >>> >>> lean . enterprise . middleware >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> * >> * >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> * >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > > > -- > Isuru Suriarachchi > Technical Lead & Product Manager, WSO2 Application Server > WSO2 Inc. http://wso2.com > email : is...@wso2.com > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
