[
https://issues.apache.org/jira/browse/NIFI-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998809#comment-14998809
]
ASF GitHub Bot commented on NIFI-1000:
--------------------------------------
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/118#discussion_r44423561
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -152,7 +152,8 @@ language governing permissions and limitations under
the License. -->
</dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
- <artifactId>activemq-client</artifactId>
+ <artifactId>activemq-all</artifactId>
+ <scope>test</scope>
--- End diff --
No, we only need javax.jms at runtime. If we do need activeMq at runtime we
are in big trouble unless the intention of JmsFactory and all components around
it was to work with ActiveMq only.
> GetJMSQueue adds wrong value for jms.JMSDestination attribute
> -------------------------------------------------------------
>
> Key: NIFI-1000
> URL: https://issues.apache.org/jira/browse/NIFI-1000
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Oleg Zhurakousky
> Labels: newbie
> Fix For: 0.4.0
>
>
> I used LogAttribute to view the output of messages pulled via GetJMSQueue.
> The Destination's name was the wrong value:
> Key: 'jms.JMSDestination'
> Value: 'org.apache.qpid.amqp_1_0.jms.impl.QueueImpl@1a5bf541'
> It appears that the attribute is being set to the toString() of the
> destination, rather than obtaining the actual name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
