[ 
https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759541#action_12759541
 ] 

Pablo Mariano Cibraro commented on STONEHENGE-73:
-------------------------------------------------

I replaced the existing business_service, common, and trader_client folders 
(that I got from the trunk in svn) with the folders attached in the zip. 
However, I am getting a compilation error, it looks like some methods are 
missing in the SQLHelper class,

Error   2       'Trade.Utility.SQLHelper' does not contain a definition for 
'ExecuteReaderSingleParm'   C:\src\dotnet\common\DALSQLServer\Customer.cs   180 
    47      StockTraderDALSQLServer

Error   3       'Trade.Utility.SQLHelper' does not contain a definition for 
'ExecuteReaderSingleRow'    C:\src\dotnet\common\DALSQLServer\Customer.cs   222 
    47      StockTraderDALSQLServer

Error   7       'Trade.Utility.SQLHelper' does not contain a definition for 
'ExecuteNonQuery'   C:\src\dotnet\common\DALSQLServer\Customer.cs   296     27  
    StockTraderDALSQLServer

Thanks
Pablo.

> Change Stonehenge to use claims based security
> ----------------------------------------------
>
>                 Key: STONEHENGE-73
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-73
>             Project: Stonehenge
>          Issue Type: New Feature
>          Components: Documentation, DOTNET_BS, DOTNET_CLIENT, DOTNET_OPS, 
> PHP_BS, PHP_CLIENT, PHP_OPS, WSAS_BS, WSAS_OPS
>    Affects Versions: M2
>         Environment: All of the Stonehenge stock trader applications
>            Reporter: Scott Golightly
>            Assignee: Scott Golightly
>         Attachments: Changes to Apache Stonehenge to Support Claims Based 
> Security.docx, Changes to Apache Stonehenge to Support Claims Based 
> Security.docx, Changes to Apache Stonehenge to Support Claims Based 
> Security.pdf, Changes to Apache Stonehenge to Support Claims Based 
> Security.pdf, StonehengeIdentity-02-Sep-2009.zip, 
> StonehengeIdentity-08-Aug-2009.zip
>
>
> I am proposing that we change the authentication and authorization mechanism 
> in Stonehenge to use claims based tokens rather than the current user 
> name/password. I am attaching a word document and a .PDF of the document that 
> explains in greater detail the proposal.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to