You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by kwesterfeld <gi...@git.apache.org> on 2015/12/16 14:24:31 UTC

[GitHub] karaf pull request: [KARAF-4218] Mark Principal classes as Seriali...

GitHub user kwesterfeld opened a pull request:

    https://github.com/apache/karaf/pull/120

    [KARAF-4218] Mark Principal classes as Serializable

    This fixes an issue regarding serializability of sessions when using karaf along with hawtio.  I am sure a number of other applications that would require some sort of clustering involving serialized instances of javax.security.auth.Subject (container of Principal) would benefit as well.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kwesterfeld/karaf master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/karaf/pull/120.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #120
    
----
commit fa5f3a6e5ff2e68574890aa46b46f50d97db524f
Author: Kurt Westerfeld <ku...@yellowbrick.io>
Date:   2015-12-16T13:22:08Z

    [KARAF-4218] Mark Principal classes as Serializable

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request: [KARAF-4218] Mark Principal classes as Seriali...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/karaf/pull/120


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---