Hi Prabath,

These were originally designed for the older in-memory registry, but still
being used for unit test-cases because the server environment is not
available. We can probably move these to the test packages in the kernel,
but I don't think we can get rid of them.

However, if there aren't any major concerns we should probably wait for
carbon 5.0.0, where there might be major API changes to the kernel. WDYT?

Thanks,
Senaka.


On Sun, Jul 14, 2013 at 8:54 PM, Prabath Siriwardena <[email protected]>wrote:

> And also InMemoryEmbeddedRegistryService...? Can we please remove those if
> we are not using these any more...
>
> Thanks & regards,
> -Prabath
>
>
> On Sun, Jul 14, 2013 at 8:48 PM, Prabath Siriwardena <[email protected]>wrote:
>
>> Found this code inside InMemoryRealmService - and called from the
>> constructor..
>>
>> Are we ever using InMemoryRealmService ?
>>
>>     public void setup() throws RegistryException {
>>
>>         String derbyDBName = "target/databasetest/CARBON_TEST";
>>         String dbDirectory = "target/databasetest";
>>         if ((new File(dbDirectory)).exists()) {
>>             deleteDBDir(new File(dbDirectory));
>>         }
>>         // create an in-memory realm
>>         try {
>>             // check whether the driver is loaded.
>>             Class.forName("org.h2.Driver");
>>         } catch (ClassNotFoundException e) {
>>             String msg = "Derby database embedded driver is not available
>> in the class path. "
>>                     + "Could not create the database for the user
>> manager.";
>>             log.error(msg, e);
>>             throw new RegistryException(msg, e);
>>         }
>>
>>         dataSource = new BasicDataSource();
>>         String connectionUrl = "jdbc:h2:" + derbyDBName;
>>         dataSource.setUrl(connectionUrl);
>>         dataSource.setDriverClassName("org.h2.Driver");
>>
>>         try {
>>             DatabaseCreator creator = new DatabaseCreator(dataSource);
>>             creator.createRegistryDatabase();
>>             RealmConfigXMLProcessor builder = new
>> RealmConfigXMLProcessor();
>>             InputStream inStream = new FileInputStream(
>>
>> "src/test/resources/user-test/user-mgt-registry-test.xml");
>>             try {
>>                 bootstrapRealmConfig =
>> builder.buildRealmConfiguration(inStream);
>>             } finally {
>>                 inStream.close();
>>             }
>>         } catch (Exception e) {
>>             String msg = "Failed to initialize the user manager. " +
>> e.getMessage();
>>             log.error(msg, e);
>>             throw new RegistryException(msg, e);
>>         }
>>         this.tenantManager = new JDBCTenantManager(dataSource, null);
>>     }
>>
>> On Sun, Jul 14, 2013 at 6:58 PM, Prabath Siriwardena <[email protected]>wrote:
>>
>>> $subject
>>>
>>> --
>>> Thanks & Regards,
>>> Prabath
>>>
>>> Mobile : +94 71 809 6732
>>>
>>> http://blog.facilelogin.com
>>> http://RampartFAQ.com
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
*Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to