Description of problem: At the moment MPR contains C++ Messaging Exceptions Class Hierarchy but not the other languages. There are two possible ways: * remove c++ wording and c++ namespace decorators and make 10.1. Handling Exceptions language independent or * change C++ Messaging Exceptions Class Hierarchy to C++ and dependent Messaging Exceptions Class Hierarchy and add Separate python Messaging Exceptions Class Hierarchy The goal of this defect is to unify Exception reference to support more than languages than just c++ (c# and python). Version-Release number of selected component (if applicable): Vienna MPR How reproducible: 100% Steps to Reproduce: 1. Search for python Exception reference none Actual results: Exception reference specific to C++, missing c#, python ones Expected results: Unified Exception reference covering at least c++, c# and python Additional info:
(In reply to Frantisek Reznicek from comment #0) > Description of problem: > > At the moment MPR contains C++ Messaging Exceptions Class Hierarchy but not > the other languages. > > There are two possible ways: > * remove c++ wording and c++ namespace decorators and make 10.1. Handling > Exceptions language independent > or > * change C++ Messaging Exceptions Class Hierarchy to > C++ and dependent Messaging Exceptions Class Hierarchy and add Separate > python Messaging Exceptions Class Hierarchy > > The goal of this defect is to unify Exception reference to support more than > languages than just c++ (c# and python). > > > Version-Release number of selected component (if applicable): > Vienna MPR > > How reproducible: > 100% > > Steps to Reproduce: > 1. Search for python Exception reference > none > > Actual results: > Exception reference specific to C++, missing c#, python ones > > Expected results: > Unified Exception reference covering at least c++, c# and python Hi Frantisek What would you prefer happen for this issue? That the Exception reference for C++, c# and python be documented in full? If yes, how would I go about resolving this issue satisfactorally. Is there good info existing for c# and python examples for the Exception reference? I noted that there is a SVN repo mentioned in http://docbuilder.usersys.redhat.com/19948/#C_Messaging_Exceptions_Reference. Would that be a place that I could get the c# and python exception references. If so, what pattern in this file should I be looking out for? If we made http://docbuilder.usersys.redhat.com/19948/#sect-Handling_Exceptions language independent as suggested in one of the options, would that prevent customers becoming confused?
> What would you prefer happen for this issue? That the Exception reference > for C++, c# and python be documented in full? If yes, how would I go about > resolving this issue satisfactorally. I'd prefer to have common chapter with all exceptions for all languages which allows to see equivalent exceptions in different languages. This is of course much harder than having separate sections for individual languages. In theory the section talks about the same library qpid messaging so there should be approx. same exceptions in all languages also .NET managed c# library is made on top of unmanaged c++ one. With python it is different, that's why there will be exceptions. This defect tracks that c# and python exceptions are not mentioned by documentation, i.e. if all c++, c# and python exceptions are mentioned then issue is solved. > > Is there good info existing for c# and python examples for the Exception > reference? I noted that there is a SVN repo mentioned in > http://docbuilder.usersys.redhat.com/19948/#C_Messaging_Exceptions_Reference. > Would that be a place that I could get the c# and python exception > references. If so, what pattern in this file should I be looking out for? > > If we made > http://docbuilder.usersys.redhat.com/19948/#sect-Handling_Exceptions > language independent as suggested in one of the options, would that prevent > customers becoming confused? The optimal chapter structure should be very similar to the current one: N. Handling Exceptions N.1 Messaging Exceptions References + add links to c++ c# and python exception references N.2 Connection Exceptions N.3 Session Exceptions N.4 Sender Exceptions N.5 Receiver Exceptions N.6 Other Exceptions I think 'N.6 Other Exceptions' might be the one where we can see the smallest overlap among languages so there might be separate sub-chapters for individual languages (if needed). Python and c# references are probably best to get from sources: * C# exceptions there are unfortunately not in single file https://qpid.apache.org/releases/qpid-0.30/messaging-api/dotnet/api/index.html Majority of exceptions are passed to c++ layer List of exceptions can be obtained (grep 'Exception' */*.cs | grep public) * Python exceptions can be obtained from https://qpid.apache.org/releases/qpid-0.30/messaging-api/python/api/index.html or eventually by typing 'pydoc qpid.messaging.exceptions' when python-qpid is installed
Taking ownership of MRG-M bugs