[
https://issues.apache.org/jira/browse/SLING-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418936#comment-17418936
]
Carsten Ziegeler commented on SLING-8777:
-----------------------------------------
[~sagarmiglani] Thanks for the PR, I'm not familiar enough with the
functionality to decide on the changes. I'm wondering if all the
synchronization needs to change and why the Caller needs to be a member field?
Apart from that, [~olli] has a valid point that there are other activation
bundles out there. If they solve the problem, we could retire Slings
implementation.
> Sling activation bundle overrides default CommandMap with wrong type
> --------------------------------------------------------------------
>
> Key: SLING-8777
> URL: https://issues.apache.org/jira/browse/SLING-8777
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: javax.activation 0.1.0
> Reporter: Ashok Kumar
> Priority: Major
> Fix For: javax.activation 0.2.2
>
> Attachments: SLING-8777.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The root cause of the issue is that the bundle
> org.apache.sling.javax.activation 0.1.0 overrides the Default
> javax.activation.CommandMap extending directly from CommandMap instead of
> MailcapCommandMap:
>
> [https://github.com/apache/sling-org-apache-sling-javax-activation/blob/master/src/main/java/org/apache/sling/javax/activation/internal/OsgiMailcapCommandMap.java#L50]
> The call fails due to this, here:
>
> [https://github.com/samskivert/ikvm-openjdk/blob/master/build/linux-amd64/impsrc/com/sun/xml/internal/messaging/saaj/soap/AttachmentPartImpl.java#L112]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
