[jira] [Resolved] (PROTON-1144) IPv6 addresses could be truncated by the accept code

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1144.
-
Resolution: Fixed

> IPv6 addresses could be truncated by the accept code
> 
>
> Key: PROTON-1144
> URL: https://issues.apache.org/jira/browse/PROTON-1144
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding, proton-c
>Affects Versions: 0.12.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.13.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (PROTON-1142) Remove proton-dump executable

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-1142.
-
Resolution: Fixed

> Remove proton-dump executable
> -
>
> Key: PROTON-1142
> URL: https://issues.apache.org/jira/browse/PROTON-1142
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.13.0
>
>
> Remove the old and creaky proton-dump executable.
> As discussed in:
> http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1143) Bump Minimum version of CMake to 2.8.7

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158320#comment-15158320
 ] 

ASF subversion and git services commented on PROTON-1143:
-

Commit 36059eba2cfe0135dacd8dbd11371f041239fdc9 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=36059eb ]

PROTON-1143: CMake minimum version now 2.8.7
- Remove some old cruft


> Bump Minimum version of CMake to 2.8.7
> --
>
> Key: PROTON-1143
> URL: https://issues.apache.org/jira/browse/PROTON-1143
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.13.0
>
>
> As discussed in:
> http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1142) Remove proton-dump executable

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158319#comment-15158319
 ] 

ASF subversion and git services commented on PROTON-1142:
-

Commit 1bfc05e4c15ae4c39ebcb807b95a0cd987f90a8f in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1bfc05e ]

PROTON-1142: Remove proton-dump


> Remove proton-dump executable
> -
>
> Key: PROTON-1142
> URL: https://issues.apache.org/jira/browse/PROTON-1142
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.13.0
>
>
> Remove the old and creaky proton-dump executable.
> As discussed in:
> http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1143) Bump Minimum version of CMake to 2.8.7

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158321#comment-15158321
 ] 

ASF subversion and git services commented on PROTON-1143:
-

Commit 26553f0123bed0cd5997eafc516a0116552da9d5 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=26553f0 ]

PROTON-1143: Simplified some of the CMake system with 2.8.7 features


> Bump Minimum version of CMake to 2.8.7
> --
>
> Key: PROTON-1143
> URL: https://issues.apache.org/jira/browse/PROTON-1143
> Project: Qpid Proton
>  Issue Type: Improvement
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.13.0
>
>
> As discussed in:
> http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1144) IPv6 addresses could be truncated by the accept code

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158318#comment-15158318
 ] 

ASF subversion and git services commented on PROTON-1144:
-

Commit a22e6c77d8f7a14abe97f344e25282ebced128cd in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a22e6c7 ]

PROTON-1144: Fixed some socket level issues:
- Fixed very strange unecessary lookup of protocol "tcp"
- Fixed accepting IPv6 addresses (would have been truncated before)


> IPv6 addresses could be truncated by the accept code
> 
>
> Key: PROTON-1144
> URL: https://issues.apache.org/jira/browse/PROTON-1144
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding, proton-c
>Affects Versions: 0.12.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.13.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (PROTON-1142) Remove proton-dump executable

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher reassigned PROTON-1142:
---

Assignee: Andrew Stitcher

> Remove proton-dump executable
> -
>
> Key: PROTON-1142
> URL: https://issues.apache.org/jira/browse/PROTON-1142
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.13.0
>
>
> Remove the old and creaky proton-dump executable.
> As discussed in:
> http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1144) IPv6 addresses could be truncated by the accept code

[Andrew Stitcher (JIRA)]

Andrew Stitcher created PROTON-1144:
---

 Summary: IPv6 addresses could be truncated by the accept code
 Key: PROTON-1144
 URL: https://issues.apache.org/jira/browse/PROTON-1144
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding, proton-c
Affects Versions: 0.12.0
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher
 Fix For: 0.13.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1143) Bump Minimum version of CMake to 2.8.7

[Andrew Stitcher (JIRA)]

Andrew Stitcher created PROTON-1143:
---

 Summary: Bump Minimum version of CMake to 2.8.7
 Key: PROTON-1143
 URL: https://issues.apache.org/jira/browse/PROTON-1143
 Project: Qpid Proton
  Issue Type: Improvement
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher
Priority: Minor
 Fix For: 0.13.0


As discussed in:
http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1142) Remove proton-dump executable

[Andrew Stitcher (JIRA)]

Andrew Stitcher created PROTON-1142:
---

 Summary: Remove proton-dump executable
 Key: PROTON-1142
 URL: https://issues.apache.org/jira/browse/PROTON-1142
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-c
Affects Versions: 0.12.0
Reporter: Andrew Stitcher
Priority: Minor
 Fix For: 0.13.0


Remove the old and creaky proton-dump executable.

As discussed in:
http://qpid.2158936.n2.nabble.com/Dropping-proton-dump-Moving-to-newer-minimum-CMake-version-td7638474.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (PROTON-250) Add -fvisibility option when building shared libraries

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-250.

   Resolution: Fixed
Fix Version/s: 0.13.0

> Add -fvisibility option when building shared libraries 
> ---
>
> Key: PROTON-250
> URL: https://issues.apache.org/jira/browse/PROTON-250
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.3
> Environment: GNU Compiler
>Reporter: Irina Boverman
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.13.0
>
> Attachments: proton.patch
>
>
> Add an option to "hide" symbols in shared libraries except when they are 
> declared public.
> Extends efforts already in place for Windows builds.
> Excludes an effort to determine what symbols should be considered "public" 
> interfaces.
> The gcc 4 -fvisibility option is said to:
> ...very substantially improve linking and load times of shared object 
> libraries, produce more optimized code, provide near-perfect API export and 
> prevent symbol clashes. It is strongly recommended that you use this in any 
> shared objects you distribute.
> See here: http://gcc.gnu.org/wiki/Visibility
> Attached patch (patch.txt) will build libqpid-proton.so shared library using 
> this flag.
> It reduces number of symbols from 700+ to 500+.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (PROTON-405) [proton-c] Windows install fails to find proton-api.jar file

[Andrew Stitcher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved PROTON-405.

   Resolution: Fixed
Fix Version/s: 0.13.0

> [proton-c] Windows install fails to find proton-api.jar file
> 
>
> Key: PROTON-405
> URL: https://issues.apache.org/jira/browse/PROTON-405
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.4
> Environment: Windows install
>Reporter: Chuck Rolke
>  Labels: windows
> Fix For: 0.13.0
>
>
> The install script is looking for file
> 4>  CMake Error at proton-j/proton-api/cmake_install.cmake:31 (FILE):
> 4>file INSTALL cannot find
> 4>"D:/Users/crolke/svn/proton/build/proton-j/proton-api/proton-api.jar".
> but the actual file is versioned
>  Directory of D:\Users\chug\svn\proton\build\proton-j\proton-api
> 08/17/2013  10:04 AM   120,690 proton-api-0.5.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-405) [proton-c] Windows install fails to find proton-api.jar file

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15158298#comment-15158298
 ] 

ASF subversion and git services commented on PROTON-405:


Commit 1640d20d9b03e97ff2b23aba00773f5d873f873a in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1640d20 ]

PROTON-405: Allow Java install not to fail if symlink file is missing
- This allows the Windows Java Install to succeed
- This is a bit nasty as it just hacks our copy of UseJava.cmake


> [proton-c] Windows install fails to find proton-api.jar file
> 
>
> Key: PROTON-405
> URL: https://issues.apache.org/jira/browse/PROTON-405
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.4
> Environment: Windows install
>Reporter: Chuck Rolke
>  Labels: windows
>
> The install script is looking for file
> 4>  CMake Error at proton-j/proton-api/cmake_install.cmake:31 (FILE):
> 4>file INSTALL cannot find
> 4>"D:/Users/crolke/svn/proton/build/proton-j/proton-api/proton-api.jar".
> but the actual file is versioned
>  Directory of D:\Users\chug\svn\proton\build\proton-j\proton-api
> 08/17/2013  10:04 AM   120,690 proton-api-0.5.jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (PROTON-1141) Update JUnit Dependency and fix some warnings in the tests.

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved PROTON-1141.
--
Resolution: Fixed

> Update JUnit Dependency and fix some warnings in the tests.
> ---
>
> Key: PROTON-1141
> URL: https://issues.apache.org/jira/browse/PROTON-1141
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: 0.12.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.13.0
>
>
> Update to the latest JUnit dependency and fix some use of deprecated JUnit 
> assertions in the tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (PROTON-1141) Update JUnit Dependency and fix some warnings in the tests.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157844#comment-15157844
 ] 

ASF subversion and git services commented on PROTON-1141:
-

Commit 6c09f1c9fbf1603fe729e53874a6825e3290fcaf in qpid-proton's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6c09f1c ]

PROTON-1141 Update to JUnit 4.12 and fix some tests that use deprecated
assertions.

> Update JUnit Dependency and fix some warnings in the tests.
> ---
>
> Key: PROTON-1141
> URL: https://issues.apache.org/jira/browse/PROTON-1141
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-j
>Affects Versions: 0.12.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.13.0
>
>
> Update to the latest JUnit dependency and fix some use of deprecated JUnit 
> assertions in the tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1141) Update JUnit Dependency and fix some warnings in the tests.

[Timothy Bish (JIRA)]

Timothy Bish created PROTON-1141:


 Summary: Update JUnit Dependency and fix some warnings in the 
tests.
 Key: PROTON-1141
 URL: https://issues.apache.org/jira/browse/PROTON-1141
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-j
Affects Versions: 0.12.0
Reporter: Timothy Bish
Assignee: Timothy Bish
 Fix For: 0.13.0


Update to the latest JUnit dependency and fix some use of deprecated JUnit 
assertions in the tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (PROTON-1140) [proton-c] Always set process name and process id as message properties

[Ganesh Murthy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy updated PROTON-1140:
--
Description: The connection initiating peer must set message properties of 
process name and process id. The receiving peer will be able to access these 
properties using pn_connection_remote_properties(connection)  (was: The 
connection initiating peer must set message properties of process name and 
process id. The receiving peer will be able to access there properties using 
pn_connection_remote_properties(connection))

> [proton-c] Always set process name and process id as message properties 
> 
>
> Key: PROTON-1140
> URL: https://issues.apache.org/jira/browse/PROTON-1140
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
>
> The connection initiating peer must set message properties of process name 
> and process id. The receiving peer will be able to access these properties 
> using pn_connection_remote_properties(connection)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (PROTON-1140) [proton-c] Always set process name and process id as message properties

[Ganesh Murthy (JIRA)]

Ganesh Murthy created PROTON-1140:
-

 Summary: [proton-c] Always set process name and process id as 
message properties 
 Key: PROTON-1140
 URL: https://issues.apache.org/jira/browse/PROTON-1140
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-c
Affects Versions: 0.12.0
Reporter: Ganesh Murthy
Priority: Minor


The connection initiating peer must set message properties of process name and 
process id. The receiving peer will be able to access there properties using 
pn_connection_remote_properties(connection)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: How does one setup a topic using qpid-config tyo satisfy QPID JMS requirements?

[Flores, Paul A.]

Thanks for the insight/clarification!


From: Robbie Gemmell [robbie.gemm...@gmail.com]
Sent: Monday, February 22, 2016 11:55 AM
To: proton@qpid.apache.org
Subject: Re: How does one setup a topic using qpid-config tyo satisfy QPID JMS 
requirements?

The topic config in the jndi.properties file is just an example, only
the queue is used by the code for the examples.

But to answer the question, one model of a topic in qpidd would be to
create an exchange of that name, of either topic or fanout type.

Robbie

On 22 February 2016 at 17:47, Flores, Paul A.  wrote:
> Using qpid-config to set up a queue prior to trying the helloworld example 
> from QPID JMS.
>
>
>
> But the jndi properties expects a topic along with a queue.
>
>
>
> How do I set up a topic using qpid-config?
>
>
>
> Thanks for your help!
>
>
>
> Paul

Re: How does one setup a topic using qpid-config tyo satisfy QPID JMS requirements?

[Gordon Sim]

On 22/02/16 17:55, Robbie Gemmell wrote:

The topic config in the jndi.properties file is just an example, only
the queue is used by the code for the examples.

But to answer the question, one model of a topic in qpidd would be to
create an exchange of that name, of either topic or fanout type.


i.e. qpid-config add exchange fanout my-jms-topic

Re: How does one setup a topic using qpid-config tyo satisfy QPID JMS requirements?

[Robbie Gemmell]

The topic config in the jndi.properties file is just an example, only
the queue is used by the code for the examples.

But to answer the question, one model of a topic in qpidd would be to
create an exchange of that name, of either topic or fanout type.

Robbie

On 22 February 2016 at 17:47, Flores, Paul A.  wrote:
> Using qpid-config to set up a queue prior to trying the helloworld example 
> from QPID JMS.
>
>
>
> But the jndi properties expects a topic along with a queue.
>
>
>
> How do I set up a topic using qpid-config?
>
>
>
> Thanks for your help!
>
>
>
> Paul

How does one setup a topic using qpid-config tyo satisfy QPID JMS requirements?

[Flores, Paul A.]

Using qpid-config to set up a queue prior to trying the helloworld example from 
QPID JMS.



But the jndi properties expects a topic along with a queue.



How do I set up a topic using qpid-config?



Thanks for your help!



Paul

RE: Need Help! qpid-cofig: No module named qpid.messaging! Working!

[Flores, Paul A.]

Setting PYTHONPATH prior to install really does help!

Thanks for your help. 

Paul


From: Justin Ross [justin.r...@gmail.com]
Sent: Monday, February 22, 2016 11:05 AM
To: proton@qpid.apache.org
Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging

This is controlled via the standard python search paths.  IOW, set
PYTHONPATH to the location of the libraries you want to see used.

On Mon, Feb 22, 2016 at 8:39 AM, Flores, Paul A. 
wrote:

> I have found one culprit that is contributing to this issue.
>
> My development environment is a VirtualBox Centos 5.11 environment
> (clients choice) that has Python2.4 installed as the primary Python version
> . I am using an alternative install of Python 2.6.8.
>
> The install of the Python has seemed to place critical elements into
> Python 2.4 related folders not in my PATH.
>
> Is it possible to setup the QPID Python version so that it points at an
> alternative Python install?
>
> 
> From: Jakub Scholz [ja...@scholz.cz]
> Sent: Monday, February 22, 2016 10:22 AM
> To: proton@qpid.apache.org
> Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging
>
> I think you need to download and install the Python version of the Qpid
> Messaging API. You can download it for example here
> http://qpid.apache.org/components/messaging-api/index.html or on
> http://qpid.apache.org/download.html. If you don't want to install it into
> the system directories, it should be enough if you copy the mllib and qpid
> directories next to your qpid-config.
>
> On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. 
> wrote:
>
> > Help!
> >
> >
> >
> > All the I can find when I Google on this messaging I am getting is dated
> > 2010.  It references a QMF extras folder that does not exist.
> >
> >
> >
> > Surely there has to be some updated guidance to this issue?
> >
> >
> >
> > This is "blocking" my current sprint progress!
> >
>

Re: Need Help! qpid-cofig: No module named qpid.messaging

[Justin Ross]

This is controlled via the standard python search paths.  IOW, set
PYTHONPATH to the location of the libraries you want to see used.

On Mon, Feb 22, 2016 at 8:39 AM, Flores, Paul A. 
wrote:

> I have found one culprit that is contributing to this issue.
>
> My development environment is a VirtualBox Centos 5.11 environment
> (clients choice) that has Python2.4 installed as the primary Python version
> . I am using an alternative install of Python 2.6.8.
>
> The install of the Python has seemed to place critical elements into
> Python 2.4 related folders not in my PATH.
>
> Is it possible to setup the QPID Python version so that it points at an
> alternative Python install?
>
> 
> From: Jakub Scholz [ja...@scholz.cz]
> Sent: Monday, February 22, 2016 10:22 AM
> To: proton@qpid.apache.org
> Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging
>
> I think you need to download and install the Python version of the Qpid
> Messaging API. You can download it for example here
> http://qpid.apache.org/components/messaging-api/index.html or on
> http://qpid.apache.org/download.html. If you don't want to install it into
> the system directories, it should be enough if you copy the mllib and qpid
> directories next to your qpid-config.
>
> On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. 
> wrote:
>
> > Help!
> >
> >
> >
> > All the I can find when I Google on this messaging I am getting is dated
> > 2010.  It references a QMF extras folder that does not exist.
> >
> >
> >
> > Surely there has to be some updated guidance to this issue?
> >
> >
> >
> > This is "blocking" my current sprint progress!
> >
>

RE: Need Help! qpid-cofig: No module named qpid.messaging

[Flores, Paul A.]

I have found one culprit that is contributing to this issue.

My development environment is a VirtualBox Centos 5.11 environment (clients 
choice) that has Python2.4 installed as the primary Python version . I am using 
an alternative install of Python 2.6.8.  

The install of the Python has seemed to place critical elements into Python 2.4 
related folders not in my PATH.

Is it possible to setup the QPID Python version so that it points at an 
alternative Python install?


From: Jakub Scholz [ja...@scholz.cz]
Sent: Monday, February 22, 2016 10:22 AM
To: proton@qpid.apache.org
Subject: Re: Need Help! qpid-cofig: No module named qpid.messaging

I think you need to download and install the Python version of the Qpid
Messaging API. You can download it for example here
http://qpid.apache.org/components/messaging-api/index.html or on
http://qpid.apache.org/download.html. If you don't want to install it into
the system directories, it should be enough if you copy the mllib and qpid
directories next to your qpid-config.

On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. 
wrote:

> Help!
>
>
>
> All the I can find when I Google on this messaging I am getting is dated
> 2010.  It references a QMF extras folder that does not exist.
>
>
>
> Surely there has to be some updated guidance to this issue?
>
>
>
> This is "blocking" my current sprint progress!
>

Re: Need Help! qpid-cofig: No module named qpid.messaging

[Justin Ross]

Adding to what Jakub said, from the source distribution, you can use
"./setup.py install --user" and set your paths to use standard user-local
python locations.  OS packages are easier if the versions work for you.


On Mon, Feb 22, 2016 at 8:22 AM, Jakub Scholz  wrote:

> I think you need to download and install the Python version of the Qpid
> Messaging API. You can download it for example here
> http://qpid.apache.org/components/messaging-api/index.html or on
> http://qpid.apache.org/download.html. If you don't want to install it into
> the system directories, it should be enough if you copy the mllib and qpid
> directories next to your qpid-config.
>
> On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. 
> wrote:
>
> > Help!
> >
> >
> >
> > All the I can find when I Google on this messaging I am getting is dated
> > 2010.  It references a QMF extras folder that does not exist.
> >
> >
> >
> > Surely there has to be some updated guidance to this issue?
> >
> >
> >
> > This is "blocking" my current sprint progress!
> >
>

Re: Need Help! qpid-cofig: No module named qpid.messaging

[Gordon Sim]

On 22/02/16 15:40, Flores, Paul A. wrote:

Help!



All the I can find when I Google on this messaging I am getting is dated 2010.  
It references a QMF extras folder that does not exist.



Surely there has to be some updated guidance to this issue?



This is "blocking" my current sprint progress!



How did you install qpid-config, from packages (e.g. rpms) or from 
source? Or are you running from a build directory?


You need the python client installed, I.e. qpid-python from:
http://www.apache.org/dyn/closer.lua/qpid/0.32 (qpid-route also requires 
qpid-qmf I believe, but not the other tools).

Re: Need Help! qpid-cofig: No module named qpid.messaging

[Jakub Scholz]

I think you need to download and install the Python version of the Qpid
Messaging API. You can download it for example here
http://qpid.apache.org/components/messaging-api/index.html or on
http://qpid.apache.org/download.html. If you don't want to install it into
the system directories, it should be enough if you copy the mllib and qpid
directories next to your qpid-config.

On Mon, Feb 22, 2016 at 4:40 PM, Flores, Paul A. 
wrote:

> Help!
>
>
>
> All the I can find when I Google on this messaging I am getting is dated
> 2010.  It references a QMF extras folder that does not exist.
>
>
>
> Surely there has to be some updated guidance to this issue?
>
>
>
> This is "blocking" my current sprint progress!
>

Need Help! qpid-cofig: No module named qpid.messaging

[Flores, Paul A.]

Help!



All the I can find when I Google on this messaging I am getting is dated 2010.  
It references a QMF extras folder that does not exist.



Surely there has to be some updated guidance to this issue?



This is "blocking" my current sprint progress!

Re: Error compiling proton C++ binding 0.12 with GCC 3.4

[TRUFANOW Alexandre]

Hi, 

I must have been doing something wrong, I checked again and specifying
the namespace explicitly works!

I also got errors in ssl.hpp related to accessing ssl_domain::pn_domain
from connection_options::impl 

qpid-proton/proton-c/bindings/cpp/src/connection_options.cpp: In member 
function `void proton::connection_options::impl::apply(proton::connection&)':
qpid-proton/proton-c/bindings/cpp/include/proton/ssl.hpp:125: error: 
`pn_ssl_domain_t* proton::internal::ssl_domain::pn_domain()' is protected
qpid-proton/proton-c/bindings/cpp/src/connection_options.cpp:83: error: within 
this context
qpid-proton/proton-c/bindings/cpp/include/proton/ssl.hpp:125: error: 
`pn_ssl_domain_t* proton::internal::ssl_domain::pn_domain()' is protected
qpid-proton/proton-c/bindings/cpp/src/connection_options.cpp:94: error: within 
this context

I think this is due to 'friend class connection_options' not allowing
the inner private connection_options::impl class to access its private
methods. For my purposes making pn_domain() public was sufficient.

Thanks again for your help!

Alexandre

On ven., 2016-02-19 at 12:28 -0500, Alan Conway wrote:
> On Thu, 2016-02-18 at 13:27 -0500, Andrew Stitcher wrote:
> > On Wed, 2016-02-17 at 10:51 +, TRUFANOW Alexandre wrote:
> > > Hi,
> > > 
> > > I am attempting to compile proton and the C++ binding using GCC
> > > 3.4 
> > 
> > This is a very old compiler (from no later than 2006), and we don't
> > test on it (although we are striving currently to support C++03).
> > 
> > Going forward it is not too unlikely that we will move to using C++11
> > features for our implementation. So if you can use a more recent
> > version of gcc (or clang) then you will be better off.
> > 
> > 
> > > and
> > > get the following error when compiling the C++ bindings. (compiler
> > > flags
> > > have been removed in proton-c/CMakeLists.txt: -pedantic-errors
> > > -Wno-variadic-macros)
> > > 
> > > > [ 33%] Building CXX object proton-c/bindings/cpp/CMakeFiles/qpid-
> > > > proton-cpp.dir/src/acceptor.cpp.o
> > > > In file included from /tmp/qpid-proton-0.12.0/proton-
> > > > c/bindings/cpp/src/contexts.hpp:28,
> > > >  from /tmp/qpid-proton-0.12.0/proton-
> > > > c/bindings/cpp/src/acceptor.cpp:26:
> > > > /tmp/qpid-proton-0.12.0/proton-
> > > > c/bindings/cpp/include/proton/container.hpp:129: error:
> > > > declaration
> > > > of `void proton::container::link_options(const
> > > > proton::link_options&)'
> > > > /tmp/qpid-proton-0.12.0/proton-
> > > > c/bindings/cpp/include/proton/link_options.hpp:60: error: changes
> > > > meaning of `link_options' from `class proton::link_options'
> > > > make[2]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton-
> > > > cpp.dir/src/acceptor.cpp.o] Error 1
> > > > make[1]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton-
> > > > cpp.dir/all] Error 2
> > > 
> > > From what I understand, this is due to a clash between the class
> > > proton::link_options and the method proton::container::link_options
> > > which cannot have the same name. 
> > 
> > As far as I can tell (and the compilers we test on seem to agree)
> > there
> > is no name clash here (it is probably a name lookup bug in the
> > compiler)!
> > 
> 
> We came across this error (changes meaning) a lot when we were re-
> naming things and it is probably not referring to the different
> namespaces but to the fact that the unqualified name "link_options" is
> being used to refer to two different things in the same context: a
> member function and a class.
> 
> > You could try explicitly making the declaration:
> > 
> > void link_options(const proton::link_options&);
> 
> I would have expected that to work since it makes the second use
> qualified. You could try adding a "class" qualifier to tell the
> compiler that you are *intentionally* referring to two different
> things, that is what we usually do when there is a member function that
> is also a class name:
> 
> PN_CPP_EXTERN void link_options(const class link_options &);
> 
> or maybe even
> 
> PN_CPP_EXTERN void link_options(const class proton::link_options &);
> 
> It might not work either but it just might sidestep the name resolution
> quirks in the older compiler. If it does let us know and we'll include
> the fix in next release.
> 

***

This e-mail contains information for the intended recipient only. It may 
contain proprietary material or confidential information. If you are not the 
intended recipient you are not authorised to distribute, copy or use this 
e-mail or any attachment to it. Murex cannot guarantee that it is virus free 
and accepts no responsibility for any loss or damage arising from its use. If 
you have received this e-mail in error please notify immediately the sender and 
delete the original email received, any attachments and all copies from your 
system.