You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Pavel Drasil (JIRA)" <ji...@apache.org> on 2008/11/03 13:31:05 UTC
[jira] Created: (SM-1674) Retain NormalizedMessage's
SecuritySubject in Camel message
Retain NormalizedMessage's SecuritySubject in Camel message
-----------------------------------------------------------
Key: SM-1674
URL: https://issues.apache.org/activemq/browse/SM-1674
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-camel
Affects Versions: servicemix-camel-2008.01
Reporter: Pavel Drasil
As far as I can see the SecuritySubject of the NormalizedMessage is lost during its conversion to Camel message. It would be useful to retain the SecuritySubject for further processing in (or even behind) Camel. Possibly in some specific camel-message header.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMXCOMP-17) Retain NormalizedMessage's
SecuritySubject in Camel message
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SMXCOMP-17.
------------------------------------
Resolution: Fixed
Fix Version/s: servicemix-camel-2009.02
3.2.4
Assignee: Gert Vanthienen
The issue has been resolved as a part of the fix for SMXCOMP-629. The unit test in the patch has been added to the test suite.
Thanks to Hans for providing the patch!
> Retain NormalizedMessage's SecuritySubject in Camel message
> -----------------------------------------------------------
>
> Key: SMXCOMP-17
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-17
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2008.01
> Reporter: Pavel Drasil
> Assignee: Gert Vanthienen
> Fix For: 3.2.4, servicemix-camel-2009.02
>
> Attachments: SMXCOMP-17.diff
>
>
> As far as I can see the SecuritySubject of the NormalizedMessage is lost during its conversion to Camel message. It would be useful to retain the SecuritySubject for further processing in (or even behind) Camel. Possibly in some specific camel-message header.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMXCOMP-17) Retain NormalizedMessage's
SecuritySubject in Camel message
Posted by "Hans Couder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Couder updated SMXCOMP-17:
-------------------------------
Attachment: SMXCOMP-17.diff
This patch fixes the problem retaining the SecuritySubject on my machine.
> Retain NormalizedMessage's SecuritySubject in Camel message
> -----------------------------------------------------------
>
> Key: SMXCOMP-17
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-17
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2008.01
> Reporter: Pavel Drasil
> Attachments: SMXCOMP-17.diff
>
>
> As far as I can see the SecuritySubject of the NormalizedMessage is lost during its conversion to Camel message. It would be useful to retain the SecuritySubject for further processing in (or even behind) Camel. Possibly in some specific camel-message header.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.