On Fri, Oct 19, 2012 at 11:34 AM, Muhammed Shariq <[email protected]> wrote:
> What is the advantage? I guess, being able to improve >>>>> them independent of having to release the kernel? >>>>> >>>> >>>> Yes... This will help IS to be released in point releases with the same >>>> Carbon kernel.. >>>> >>> >>> Then I guess IS needs to be released before any other product. Or does >>> other other products have only the admin user login? >>> >> >> The model should be; >> >> 1. Release kernel or depend on a released version of the kernel >> 2. Release components - may be a selected subset >> > > In the current component structure isn't it a bit complicated to release a > subset of components. If we want to do this, we should group the > components preferably the products. That way we should be able to release a > set of components and the corresponding product .. WDYT ?! > I'm -1 on doing this. For faster execution (I mean in the engineering sense not runtime) its critical that Carbon kernel be a totally standalone thing. Why does the proposed change challenge that? Can't we have a simple default realm like tomcat-users.xml type thing built into our user-management.xml? Then if you want more than that you need the components that give you various capabilities like LDAP, JDBC etc.. If you want full stuff you get IS. I'm sure I'm missing some crucial info :). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
