[jira] [Commented] (QPID-4659) [Java Broker] Refactor broker to separate protocol independent from protocol specific classes
[
https://issues.apache.org/jira/browse/QPID-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709634#comment-13709634
]
ASF subversion and git services commented on QPID-4659:
---
Commit 1503625 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1503625 ]
QPID-4659 : [Java Broker] reduce unnecessary usage of 0-8 classes in tests
[Java Broker] Refactor broker to separate protocol independent from protocol
specific classes
-
Key: QPID-4659
URL: https://issues.apache.org/jira/browse/QPID-4659
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Rob Godfrey
Assignee: Rob Godfrey
The Java Broker currently supports all versions of the AMQP protocol from 0-8
to 1.0, however the current structure of the code within the broker makes it
hard to distinguish between code which is specific to a version of the
protocol and code which is common across all protocols.
By refactoring we can separate the protocol dependent and independent parts
and allow for the possibility of separating out the different protocol
implementations into independently loadable libraries.
Fundamentally the refactoring takes the form of moving protocol specific
classes into org.apache.qpid.server.protocol.v{0-8,0-10,1-0} and sub-packages
and using the QpidClassLoader to load the protocol implementations (there are
three separate implementations to load - the protocol delegate creators that
interface to the IO code; the MessageMetaDataTypes used to (de)serialize the
message data to stores; and MessageConverters used to convert between message
formats and allow 0-8 messages to be received by 1-0 consumers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4659) [Java Broker] Refactor broker to separate protocol independent from protocol specific classes
[
https://issues.apache.org/jira/browse/QPID-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709665#comment-13709665
]
ASF subversion and git services commented on QPID-4659:
---
Commit 1503651 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1503651 ]
QPID-4659 : [Java Broker] move amqp 0-8 implementation into a plugin
[Java Broker] Refactor broker to separate protocol independent from protocol
specific classes
-
Key: QPID-4659
URL: https://issues.apache.org/jira/browse/QPID-4659
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Rob Godfrey
Assignee: Rob Godfrey
The Java Broker currently supports all versions of the AMQP protocol from 0-8
to 1.0, however the current structure of the code within the broker makes it
hard to distinguish between code which is specific to a version of the
protocol and code which is common across all protocols.
By refactoring we can separate the protocol dependent and independent parts
and allow for the possibility of separating out the different protocol
implementations into independently loadable libraries.
Fundamentally the refactoring takes the form of moving protocol specific
classes into org.apache.qpid.server.protocol.v{0-8,0-10,1-0} and sub-packages
and using the QpidClassLoader to load the protocol implementations (there are
three separate implementations to load - the protocol delegate creators that
interface to the IO code; the MessageMetaDataTypes used to (de)serialize the
message data to stores; and MessageConverters used to convert between message
formats and allow 0-8 messages to be received by 1-0 consumers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4988) add some tests for swigged python client
[ https://issues.apache.org/jira/browse/QPID-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709666#comment-13709666 ] ASF subversion and git services commented on QPID-4988: --- Commit 1503652 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1503652 ] QPID-4988: Add test runs using swigged python client add some tests for swigged python client Key: QPID-4988 URL: https://issues.apache.org/jira/browse/QPID-4988 Project: Qpid Issue Type: Test Components: C++ Client, Python Test Suite Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim also allows adding some tests in python for AMQP 1.0 behaviour -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4907) qpid-tool displays duplicate entries for objects managed by the broker.
[ https://issues.apache.org/jira/browse/QPID-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709667#comment-13709667 ] ASF subversion and git services commented on QPID-4907: --- Commit 1503653 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1503653 ] QPID-4907: fix unit test qpid-tool displays duplicate entries for objects managed by the broker. --- Key: QPID-4907 URL: https://issues.apache.org/jira/browse/QPID-4907 Project: Qpid Issue Type: Bug Components: C++ Broker, Python Tools, Qpid Managment Framework Affects Versions: 0.23 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Blocker Fix For: Future qpid-tool displays two entries for each object managed by the broker. Example: $ qpid-config add queue KEN-Q $ qpid-tool Management Tool for QPID qpid: list queue Object Summary: ID Created Destroyed Index 141 14:19:42 - 169.KEN-Q SNIP 156 14:19:42 - org.apache.qpid.broker:queue:KEN-Q SNIP qpid: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4659) [Java Broker] Refactor broker to separate protocol independent from protocol specific classes
[
https://issues.apache.org/jira/browse/QPID-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709685#comment-13709685
]
ASF subversion and git services commented on QPID-4659:
---
Commit 1503663 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1503663 ]
QPID-4659 : [Java Broker] fix bdbstore dependencies on pluggable protocols
[Java Broker] Refactor broker to separate protocol independent from protocol
specific classes
-
Key: QPID-4659
URL: https://issues.apache.org/jira/browse/QPID-4659
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Rob Godfrey
Assignee: Rob Godfrey
The Java Broker currently supports all versions of the AMQP protocol from 0-8
to 1.0, however the current structure of the code within the broker makes it
hard to distinguish between code which is specific to a version of the
protocol and code which is common across all protocols.
By refactoring we can separate the protocol dependent and independent parts
and allow for the possibility of separating out the different protocol
implementations into independently loadable libraries.
Fundamentally the refactoring takes the form of moving protocol specific
classes into org.apache.qpid.server.protocol.v{0-8,0-10,1-0} and sub-packages
and using the QpidClassLoader to load the protocol implementations (there are
three separate implementations to load - the protocol delegate creators that
interface to the IO code; the MessageMetaDataTypes used to (de)serialize the
message data to stores; and MessageConverters used to convert between message
formats and allow 0-8 messages to be received by 1-0 consumers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709692#comment-13709692 ] Rob Godfrey commented on QPID-4991: --- For the AMQP 1-0 JMS client there is (in general) no meaning to the topic:// prefix... AMQP 1-0 addresses are just strings. I believe that ActiveMQ has some requirements around prefixing when used with our JMS client, but this is ActiveMQ specific. When using the Qpid/Java broker, for example... one could use Session.createTopic(amq.direct) (or any other exchange name) to use the given exchange as a topic. JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709696#comment-13709696 ] Axel Podehl commented on QPID-4991: --- Well, the problem is that if you have a generic JMS application creating a topic named 'TEST', then it's not working as expected. A message published to an AMQP topic exchange 'TEST' (or Qpid topic://TEST) will not be received by a subscriber using Session.createTopic(TEST) - that's strange I think. JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709698#comment-13709698 ] Rob Godfrey commented on QPID-4991: --- But Session.createTopic(TEST) doesn't actually create a topic on the broker, it is just creating a JMS Object for a destination which has been administratively created for you. The name of the topic is something that the broker owns, and different broker implementations may make different restrictions on the form of that name. In AMQP terms, all Topic T = Session.createTopic(X) just tells the client that any Producers/Consumers created for T should attempt to link to address X. JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: New Defects reported by Coverity Scan for Apache-Qpid
Hi Steve, I'd be happy to help make sense of the Java results. I'll set up a Coverity account now. Thanks Phil On 2 July 2013 15:43, Steve Huston shus...@riverace.com wrote: Yes, I noticed that too - and Coverity was fairly eager to get a scan of the Qpid Java code back when we started, but they weren't ready to scan Java quite yet. If anyone would like to tackle the Java scans, and is not yet signed up at coverity.com, please let me know and I'll help get you going. From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] Sent: Tuesday, July 02, 2013 10:41 AM To: qpid Cc: Steve Huston Subject: Re: New Defects reported by Coverity Scan for Apache-Qpid As an aside, I notice that they seem to have enabled scanning of Java projects as well as C++ now... we should maybe look to see what a coverity scan of the Java code looks like -- Rob snip
[jira] [Commented] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709707#comment-13709707 ] Axel Podehl commented on QPID-4991: --- Hmm, I think I see what you mean, AMQP doesn't really have a notion of Topic/Queue, so maybe that's an Broker/ActiveMQ question then. Currently, an ActiveMQ JMS application will use a topic://TEST from Session.createTopic(TEST) but not the AMQP 1.0 API, which isn't exactly great. JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Axel Podehl updated QPID-4991: -- Priority: Minor (was: Major) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl Priority: Minor I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4991) JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected
[ https://issues.apache.org/jira/browse/QPID-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709711#comment-13709711 ] Axel Podehl commented on QPID-4991: --- also there's no difference between Session.createTopic() and Session.createQueue() then, is there ? JMS AMQP 1.0 API Session.createTopic( TEST ) does not work as expected Key: QPID-4991 URL: https://issues.apache.org/jira/browse/QPID-4991 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl Priority: Minor I've read that AMQP topics should start with topic:// prefix, but that's really not JMS standard (compare TIBCO EMS or IBM MQSeries implementation). If you create a consumer with Session.createTopic( TEST ), this call does return a org.apache.qpid.amqp_1_0.jms.impl.TopicImpl, but when I publish to it with a producer using Session.createTopic( topic://TEST ) the message is not received. I think, the call to Session.createTopic( String dest ) should automatically add the topic:// prefix if it's not there such that createTopic() always creates a working topic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-355) Closing a consumer does not ensure messages delivery will stop for that subscription
[ https://issues.apache.org/jira/browse/QPID-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709738#comment-13709738 ] ASF subversion and git services commented on QPID-355: -- Commit 1503701 from [~mcpierce] in branch 'proton/trunk' [ https://svn.apache.org/r1503701 ] QPID-355: Fixed the broken Rspec tests. Removed a few tracker spec tests since the expectation has changed. Also removed the negative receive limit since that's no longer an exceptional case. Closing a consumer does not ensure messages delivery will stop for that subscription Key: QPID-355 URL: https://issues.apache.org/jira/browse/QPID-355 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Martin Ritchie Assignee: Martin Ritchie -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
RE: New Defects reported by Coverity Scan for Apache-Qpid
This would be great, Phil! We currently are not scanning the Java code, but it would be great if you can set up the Java scan. If you'd like some help from Coverity please let me know - the mgr I worked with to get the C++ scan going was eager to get Java projects in as well - but they couldn't scan Java at that time. -Original Message- From: philharveyonl...@googlemail.com [mailto:philharveyonl...@googlemail.com] On Behalf Of Phil Harvey Sent: Tuesday, July 16, 2013 8:09 AM To: dev@qpid.apache.org Subject: Re: New Defects reported by Coverity Scan for Apache-Qpid Hi Steve, I'd be happy to help make sense of the Java results. I'll set up a Coverity account now. Thanks Phil On 2 July 2013 15:43, Steve Huston shus...@riverace.com wrote: Yes, I noticed that too - and Coverity was fairly eager to get a scan of the Qpid Java code back when we started, but they weren't ready to scan Java quite yet. If anyone would like to tackle the Java scans, and is not yet signed up at coverity.com, please let me know and I'll help get you going. From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] Sent: Tuesday, July 02, 2013 10:41 AM To: qpid Cc: Steve Huston Subject: Re: New Defects reported by Coverity Scan for Apache-Qpid As an aside, I notice that they seem to have enabled scanning of Java projects as well as C++ now... we should maybe look to see what a coverity scan of the Java code looks like -- Rob snip - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4992) preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP-JMS-AMQP works
[ https://issues.apache.org/jira/browse/QPID-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709860#comment-13709860 ] Axel Podehl commented on QPID-4992: --- see discussion on http://qpid.2158936.n2.nabble.com/JMS-API-incomplete-td7595272.html#a7595407 Rob Godfrey said: .. Work on a complete JMS mapping is underway, in conjunction with the OASIS AMQP Bindings and Mappings Technical Committee. There will be a way to access all properties directly or indirectly once this is complete. preserve all AMQP properties in JMS AMQP 1.0 API, so AMQP-JMS-AMQP works -- Key: QPID-4992 URL: https://issues.apache.org/jira/browse/QPID-4992 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.22 Environment: all Reporter: Axel Podehl As I understand from QPID-3380 there is no way to retrieve all AMQP header properties (e.g. contentType) with the Java API. In my case, I have a generic JMS recordreplay program and would want to use it to record an AMQP message and replay it, simply using the QPid API, but unless I do some nasty type-casts, important AMQP properties are lost, for example AMQP content type. Interestingly enough, if I use the ActiveMQ transport transformer and receive AMQP messages through the ActiveMQ JMS API, all properties are copied for me: https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP So receiving an AMQP messages using the ActiveMQ JMS API gives me more information than with the Qpid AMQP JMS API, which is strange. Qpid's JMS API should be the expert on AMQP properties, not ActiveMQ's message transformer. Wouldn't it make sense to deploy the same mapping of AMQP to JMS properties (https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP) in the QPid API itself ? Or at least have an option (e.g. in the ConnectionFactory) to do so ? That way a bridge of AMQP - JMS - AMQP wouldn't loose important information but could still stick with the real JMS API. Please note, it's quite common for JMS providers to extend the list of properties with a set of properties have a 'JMS' (or better a 'JMSX') prefix. For example MQ: http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fuj25450_.htm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4659) [Java Broker] Refactor broker to separate protocol independent from protocol specific classes
[
https://issues.apache.org/jira/browse/QPID-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709930#comment-13709930
]
ASF subversion and git services commented on QPID-4659:
---
Commit 1503798 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1503798 ]
QPID-4659 : [Java Broker] fix pom generation
[Java Broker] Refactor broker to separate protocol independent from protocol
specific classes
-
Key: QPID-4659
URL: https://issues.apache.org/jira/browse/QPID-4659
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Rob Godfrey
Assignee: Rob Godfrey
The Java Broker currently supports all versions of the AMQP protocol from 0-8
to 1.0, however the current structure of the code within the broker makes it
hard to distinguish between code which is specific to a version of the
protocol and code which is common across all protocols.
By refactoring we can separate the protocol dependent and independent parts
and allow for the possibility of separating out the different protocol
implementations into independently loadable libraries.
Fundamentally the refactoring takes the form of moving protocol specific
classes into org.apache.qpid.server.protocol.v{0-8,0-10,1-0} and sub-packages
and using the QpidClassLoader to load the protocol implementations (there are
three separate implementations to load - the protocol delegate creators that
interface to the IO code; the MessageMetaDataTypes used to (de)serialize the
message data to stores; and MessageConverters used to convert between message
formats and allow 0-8 messages to be received by 1-0 consumers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4990) Website improvements for the 0.24 timeframe
[ https://issues.apache.org/jira/browse/QPID-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709955#comment-13709955 ] ASF subversion and git services commented on QPID-4990: --- Commit 1503800 from [~justi9] [ https://svn.apache.org/r1503800 ] QPID-4990: Add list-resource links for notifications Website improvements for the 0.24 timeframe --- Key: QPID-4990 URL: https://issues.apache.org/jira/browse/QPID-4990 Project: Qpid Issue Type: Task Components: Website Affects Versions: 0.22 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.23 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
