You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Philip Schlesinger (JIRA)" <qp...@incubator.apache.org> on 2010/08/24 20:19:15 UTC
[jira] Updated: (QPID-2823) HermesJMS QPID integration document
refers to jar files no longer used in QPID 0.6
[ https://issues.apache.org/jira/browse/QPID-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Schlesinger updated QPID-2823:
-------------------------------------
Description:
This web page: https://cwiki.apache.org/qpid/hermesjms.html
refers to configuring HermesJMS to add to its classpath several jars, many of which no longer exist in the 0.6 distribution. I cannot find in the 0.6 distribution:
* client-launch.jar
* slf4j-simple.jar (is this slf4j-api-1.4.0.jar?)
* client.jar (is this qpid-client-0.6.jar?)
* common.jar (is this qpid-common-0.6.jar?)
I'm assuming the two mina jars can be just replaced with their newer versions.
Please update the diagram to show the new filenames to use and where they're located relative to the directory tree.
was:
This web page: https://cwiki.apache.org/qpid/hermesjms.html
refers to configuring HermesJMS to add to its classpath several jars, many of which no longer exist in the 0.6 distribution. I cannot find in the 0.6 distribution:
* client-launch.jar
* slf4j-simple.jar (is this slf4j-api-1.4.0.jar?)
* client.jar (is this qpid-client-0.6.jar?)
* common.jar (is this qpid-common-0.6.jar?)
I'm assuming the two mina jars can be just replaced with their newer versions.
Please update the diagram to show the new filenames to use and where they're located relative to the directory tree.
I tried building qpid\java\client\ with ant calling every one of the targets in the build.xml, then importing all of the jars in qpid\java\client\release\qpid-client-0.6\lib\ -- this is the exception I received when I clicked Discover on the HermesJMS session icon that I created:
{quote}
hermes.HermesException: The default provider extension cannot discover queues or topics on org.apache.qpid.client.AMQConnectionFactory
at hermes.ext.HermesAdminSupport.discoverDestinationConfigs(HermesAdminSupport.java:449)
at hermes.impl.HermesAdminAdapter.discoverDestinationConfigs(HermesAdminAdapter.java:84)
at hermes.impl.DefaultHermesImpl.discoverDestinationConfigs(DefaultHermesImpl.java:1357)
at hermes.browser.tasks.DiscoverDestinationsTask.invoke(DiscoverDestinationsTask.java:76)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:175)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:170)
at java.lang.Thread.run(Thread.java:619)
{quote}
> HermesJMS QPID integration document refers to jar files no longer used in QPID 0.6
> ----------------------------------------------------------------------------------
>
> Key: QPID-2823
> URL: https://issues.apache.org/jira/browse/QPID-2823
> Project: Qpid
> Issue Type: Improvement
> Components: website
> Affects Versions: 0.6
> Environment: Website, HermesJMS 1.13
> Reporter: Philip Schlesinger
>
> This web page: https://cwiki.apache.org/qpid/hermesjms.html
> refers to configuring HermesJMS to add to its classpath several jars, many of which no longer exist in the 0.6 distribution. I cannot find in the 0.6 distribution:
> * client-launch.jar
> * slf4j-simple.jar (is this slf4j-api-1.4.0.jar?)
> * client.jar (is this qpid-client-0.6.jar?)
> * common.jar (is this qpid-common-0.6.jar?)
> I'm assuming the two mina jars can be just replaced with their newer versions.
> Please update the diagram to show the new filenames to use and where they're located relative to the directory tree.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org