On Wed, Apr 3, 2013 at 1:22 PM, Nuwan Dias <[email protected]> wrote: > On Wed, Apr 3, 2013 at 12:50 PM, Kishanthan Thangarajah < > [email protected]> wrote: > >> Hi Nuwan, >> >> >> On Tue, Apr 2, 2013 at 9:10 PM, Nuwan Dias <[email protected]> wrote: >> >>> Hi, >>> >>> In any multi-tenanted carbon server, the tenant specific deployment >>> directory structure (Ex: repository/tenants/1/axis2services) is always >>> created when the tenant tries to deploy an artifact for the first time. >>> >> >> They get created on first access to the tenant (mgt-console login, >> request to some artifact, etc). This is where the axisConfiguration for >> that tenant gets created and during that time only, those >> dir-structure gets created. >> >> >>> Is there any possibility of having an extension hook for the deployment >>> directory structure creation so that it could be used to deploy custom >>> artifacts under a chosen directory structure? >>> >>> My use case is that I need to deploy a custom set of sequences under >>> each tenant's synapse-configs/default/sequences directory. >>> >> >> Is the requirement is to deploy those sequences into relevant tenants >> repo, when the tenant being loaded for the first time? >> > Yes. > > >> What I mean is, before any request is received by the tenant, you want >> to have those artifacts deployed there? >> > No, it is sufficient to have these artifacts created when the tenant > receives its first request. What I am looking for is a method to deploy a > set of custom sequences per-tenant. If you look at the > synapse-configs/default/sequences directory of the tenant, you will see > that a fault.xml and main.xml files are created. I want to add a few more > sequences and override the default fault.xml >
OK. This should be possible but we have to give a try first. TenantServiceBusInitializer is the class responsible for initializing the synapse configuration for respective tenants. And it is the one which initializes and adds both main and fault default sequences (check line 396). So if we can add the relevant extension point there, this should work. >> Thanks, >> Kishanthan >> >>> >>> Thanks, >>> NuwanD. >>> >>> -- >>> Nuwan Dias >>> >>> Software Engineer - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Kishanthan Thangarajah* >> Software Engineer, >> Development Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com* >> Twitter - *http://twitter.com/kishanthan* >> > > > > -- > Nuwan Dias > > Software Engineer - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
