[
https://issues.apache.org/jira/browse/STONEHENGE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas A Hauenstein updated STONEHENGE-101:
---------------------------------------------
Attachment: STONEHENGE-101.patch
> SERVICE table in MS SQL database allows nulls for SEC column, but DAL does no
> null reference checks for same
> ------------------------------------------------------------------------------------------------------------
>
> Key: STONEHENGE-101
> URL: https://issues.apache.org/jira/browse/STONEHENGE-101
> Project: Stonehenge
> Issue Type: Bug
> Affects Versions: M2
> Environment: Windows Server 2008
> Reporter: Nicholas A Hauenstein
> Priority: Trivial
> Fix For: M2
>
> Attachments: STONEHENGE-101.patch
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> The SEC column in the SERVICE table in the MS SQL database allows nulls, but
> there are no null reference checks in the code when accessing this column. If
> the value is null, an exception is thrown. Attached is a patch that will
> default to a value of "false" in the case that the column is null.
> This is a trivial issue, and should not be a problem when dealing with
> endpoints using the UI. However, I did hit this issue when I was unaware of
> all of the features available in the configuration UI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
