[
https://issues.apache.org/jira/browse/STONEHENGE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792532#action_12792532
]
Nicholas A Hauenstein commented on STONEHENGE-110:
--------------------------------------------------
I would want to test this fix by using a MySQL database with the MSSQL database
detached and unavailable, just to verify that there are absolutely 0 places
where there is a hard dependency on MSSQL. That being said, I don't currently
have a setup where I can test this scenario. Maybe someone else out there can
test and resolve?
> DAL assembly name is hardcoded throughout .NET Business Service implementation
> ------------------------------------------------------------------------------
>
> Key: STONEHENGE-110
> URL: https://issues.apache.org/jira/browse/STONEHENGE-110
> Project: Stonehenge
> Issue Type: Bug
> Components: DOTNET_BS
> Affects Versions: M2
> Reporter: Nicholas A Hauenstein
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I was looking through the .NET implementation of the business service (in
> TradeService.cs), and found a few instances of code like the following:
> dalCustomer = Trade.DALFactory.Customer.Create("Trade.DALSQLServer");
> Instead of something like the following:
> dalCustomer =
> Trade.DALFactory.Customer.Create(SQLHelper.GetAssemblyNameFromDBName(bsConfig.DBName));
> It appears that we are hardcoding the usage of the SQL Server DAL in a few
> places within the service implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
