[
https://issues.apache.org/jira/browse/CXF-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671581#action_12671581
]
Christian Schneider commented on CXF-2026:
------------------------------------------
I will remove messageIdEnabled and messageTimeStampEnabled.
The pubSubNoLocal and subscriptionDurable will be set on the jmsListener.
Additionally I will remove the useJndi as it is not used anymore. Jndi is now
simply a fallback if no connectionFactory is set.
I am not sure about ServerBehaviorPolicyType.useMessageIDAsCorrelationID.
Should I remove it or simply set it as deprecated and remove in 2.2? In the
deprecated case: How do I do this in xsd?
Christian
> jms transport: Unused jms properties
> ------------------------------------
>
> Key: CXF-2026
> URL: https://issues.apache.org/jira/browse/CXF-2026
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1.4
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Minor
> Fix For: 2.2
>
>
> Dan wrote on the cxf dev list:
> While looking at some things, I've noticed that some of the JMSConfiguration
> properties are never used: (getters never called)
> boolean isPubSubNoLocal()
> boolean isMessageTimestampEnabled()
> boolean isMessageIdEnabled()
> boolean isSubscriptionDurable()
> Also, in the JMSOldConfigHolder, the
> ServerBehaviorPolicyType.useMessageIDAsCorrelationID
> property isn't mapped into anything.
> Can you look into them and see if anything is just an oversight and easily
> correctable? Or remove them or something?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
