[ 
https://issues.apache.org/jira/browse/JENA-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477257#comment-15477257
 ] 

ASF subversion and git services commented on JENA-1231:
-------------------------------------------------------

Commit 1b48d4983b3bec76e2241027f098abebd9b2b49d in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1b48d49 ]

JENA-1231: Merge commit 'refs/pull/168/head' of github.com:apache/jena

This closes #168.


> Update "executeInTransaction" to Java8 style (Model, TransactionHandler).
> -------------------------------------------------------------------------
>
>                 Key: JENA-1231
>                 URL: https://issues.apache.org/jira/browse/JENA-1231
>             Project: Apache Jena
>          Issue Type: Bug
>    Affects Versions: Jena 3.1.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>
> The proposal is to deprecate {{executeInTransaction}}, which returns "Object" 
> and have operations:
> {noformat}
>     <T> T executeRtn( Supplier<T> action ) ;
> {noformat}
> and the non-result version:
> {noformat}
>     void execute( Runnable action );
> {noformat}
> It helps in the IDE to have different names because they both start 
> "{{()\->...}}".  In my experience (Eclipse) completion and error messages are 
> not good when there is the same name and ambiguity over the inferred type. 
> Using the {{()->methodresultsvalue()}} form is ambiguous.
> For model, call them {{executeInTxnRtn}} and {{executeInTxn}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to