On Tue, Nov 12, 2013 at 11:10 AM, Piyum Fernando <[email protected]> wrote: > Hi Ajanthan, > > AS team also had a small internal discussion on implementing this and the > approach is somewhat similar. > And also there will be few changes in our JNDI implementation with C5 effort > so better we make everything clear before start. > > Shall we have a meeting with AS+Carbon and discuss this?. +1 > > Thanks. > > > On Tue, Nov 12, 2013 at 10:52 AM, Ajanthan Balachandran <[email protected]> > wrote: >> >> Hi all, >> Currently in AppFactory all the JNDI resources (Eg: Datasources) are >> visible to all the applications within a tenant.By default in our >> platform each tenant is getting separate subcontext with in >> initialContext. Same way we can provide a subcontext per deployed >> application in the application server. >> In order to achieve it we have to create an application aware >> InitialJNDIContextFactoryBuilder and InitialContextFactory. >> The behavior of the application aware InitialJNDIContextFactoryBuilder >> will be as follows. >> While initializing the JNDI context first it will create a subcontext >> for tenant and if the request is for an application (in such situation >> there will be an application name in Carboncontext) then it will >> create a subcontext for that application and return. >> With this approach the JNDI resources that are created for a >> tenant(Eg: Transaction Manager) will not be available for the >> applications.In this case the JNDI look up of the application >> subcontext will happen as follows. First it will search within >> application subcontext if it not there it will look up within tenant >> subcontext. >> In this way if we want to provide a resource for an application then >> we have to put it into the application subcontext and if the resource >> meant to be shared within a tenant we have to put into tenant >> subcontext. >> >> Implementation >> ------------------- >> Currently in our platform InitialJNDIContextFactoryBuilder is not >> configurable but default InitialContextFactory is configurable.To >> achieve this we have to make InitialJNDIContextFactoryBuilder >> configurable. >> >> Appreciate any feedback on this approach. >> >> -- >> ajanthan >> -- >> Ajanthan Balachandiran >> Senior Software Engineer; >> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >> >> email: [email protected]; cell: +94775581497 >> blog: http://bkayts.blogspot.com/ >> >> Lean . Enterprise . Middleware >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > -- > Piyum Fernando > Software Engineer > WSO2 Inc.; http://wso2.com > > Mobile: +94 77 22 93 880 > Tel: +94 31 22 75 715 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >
-- ajanthan -- Ajanthan Balachandiran Senior Software Engineer; Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware _______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
