[
https://issues.apache.org/jira/browse/ISIS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336228#comment-16336228
]
ASF subversion and git services commented on ISIS-1846:
-------------------------------------------------------
Commit da7b58731073f96958807c50722cba309623fe72 in isis's branch
refs/heads/ISIS-1846_internal_utils from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=da7b587 ]
ISIS-1846 minor refactoring: introduces _Context (internal API)
IsisContext is no longer a concrete class, but instead an interface,
that has only static methods and can not hold any state itself.
Singletons are now internal API via _Context. _Context also provides the
framework's internal single entry-point for requesting the framework's
default class-loader. (The public entry-point is via IsisContext.)
> API Cleanup: code deduplication
> -------------------------------
>
> Key: ISIS-1846
> URL: https://issues.apache.org/jira/browse/ISIS-1846
> Project: Isis
> Issue Type: Sub-task
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M1
>
>
> isis-core-applib would be the perfect place to consolidate any internal
> utility classes such as
> NullSafe (common null check idioms), StringExtensions, ordering algorithms,
> etc ...
> but we would want to keep these classes contained, meaning they should not be
> available for public use, just for internal use within Isis' code-base.
> Java 9 has the perfect solution for this. But what can we do in the meantime
> (with Java 8)?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
