Hi Rasika, The problem this needs to address are, 1. The IS new version connected to old schema on database. The server should/can not start until migration completes. 2. Migration should only happen when the "migration client jar" is present (and the jvm parameter present-in new way) 3. Migration should not be attempted on normal server starts. 4. The pack which has migration client installed is not a normal server 5. Migration client needs most of the other java packages(related to identity server) exposed. Hence OSGI needs to be partially active.
Cheers, Ruwan On Fri, Nov 24, 2017 at 5:24 PM, Rasika Perera <rasi...@wso2.com> wrote: > Hi Dhanushka and All, > > I don't understand the exact context here. Have few questions based on > what you have mentioned. > > Migration client is called from the identity.core bundle at the >> activation level >> > Would that mean identity.core has a dependency to the Migration Client? > > This is done in that manner because we needed that to run before any of >> the identity bundles get activated > > How does the migration client gets activated if it is not an OSGi bundle ? > > In this discussion Ruwan suggested to use a jvm parameter and wait for the >> migration bundle if jvm parameter is present. > > If the migration client is a non OSGi JAR +1 for the approach. Or else > can't we use OSGi declarative services for this relationship? > > Thanks, > Rasika > > > On Fri, Nov 24, 2017 at 12:10 PM, Danushka Fernando <danush...@wso2.com> > wrote: > >> Hi All >> >> Currently the migration client is developed as an dropin to the server >> package. Migration client is called from the identity.core bundle at the >> activation level. This is done in that manner because we needed that to run >> before any of the identity bundles get activated. So here we are loading >> the migration client class with Class.forName(). >> >> Since this is not a good OSGI pattern, we (Myself, Harsha, Ruwan, Sagara) >> had a discussion over this. In this discussion Ruwan suggested to use a jvm >> parameter and wait for the migration bundle if jvm parameter is present. I >> am going to tryout this solution. >> >> Any suggestions would be appreciated. >> >> Thanks & Regards >> Danushka Fernando >> Associate Tech Lead >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 <+94%2071%20633%202729> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > With Regards, > > *Rasika Perera* > Senior Software Engineer > LinkedIn: http://lk.linkedin.com/in/rasika90 > > <http://wso2.com/signature> > > WSO2 Inc. www.wso2.com > lean.enterprise.middleware >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
