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

Keith Wall updated QPID-7622:
-----------------------------
    Description: 
As discussed here:

http://qpid.2158936.n2.nabble.com/DISCUSS-Drop-the-AMQP-0-x-client-from-the-Qpid-for-Java-7-0-release-td7657770.html

The proposal is to move the code and documentation that comprises the 0-x 
client to its own SVN root:

https://svn.apache.org/repos/asf/qpid/qpid-jms-amqp-0-x

The Java Broker and integration tests suites will remain at: 
https://svn.apache.org/repos/asf/qpid/qpid-java

Maven dependencies will be used to pull in the appropriate 0-x client for 
integration testing purposes (as we already do with the Qpid JMS Client).

The {{qpid-common}} module (and maven release artefact) will be eliminated.

* Classes that the Broker requires will be moved into the class hierarchy of 
the existing plugin modules {{amqp-0-10-protocol}} and {{amqp-0-8-protocol}} 
e.g. {{org/apache/qpid/server/protocol/vx_y}}.*
* Code that the 0-x client requires will be moved into the class hierarchy of 
the client {{org/apache/qpid/client}}.

This will allow the Broker and 0-x Client to co-exist in the same JVM with 
class loading collision.



  was:
As discussed here:

http://qpid.2158936.n2.nabble.com/DISCUSS-Drop-the-AMQP-0-x-client-from-the-Qpid-for-Java-7-0-release-td7657770.html

The proposal is to move the code and documentation that comprises the 0-x 
client to its own SVN root:

https://svn.apache.org/repos/asf/qpid/qpid-jms-amqp-0-x

The Java Broker and integration tests suites will remain at: 
https://svn.apache.org/repos/asf/qpid/qpid-java

Maven dependencies will be used to pull in the appropriate 0-x client for 
integration testing purposes (as we already do with the Qpid JMS Client).

The {{qpid-common}} module will be eliminated.

* Classes that the Broker requires will be moved into the class hierarchy of 
the existing plugin modules {{amqp-0-10-protocol}} and {{amqp-0-8-protocol}} 
e.g. {{org/apache/qpid/server/protocol/vx_y}}.*
* Code that the 0-x client requires will be moved into the class hierarchy of 
the client {{org/apache/qpid/client}}.

This will allow the Broker and 0-x Client to co-exist in the same JVM with 
class loading collision.




> Separate Qpid Broker for Java and 0-x JMS Client in source tree
> ---------------------------------------------------------------
>
>                 Key: QPID-7622
>                 URL: https://issues.apache.org/jira/browse/QPID-7622
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client
>            Reporter: Keith Wall
>             Fix For: qpid-java-7.0
>
>
> As discussed here:
> http://qpid.2158936.n2.nabble.com/DISCUSS-Drop-the-AMQP-0-x-client-from-the-Qpid-for-Java-7-0-release-td7657770.html
> The proposal is to move the code and documentation that comprises the 0-x 
> client to its own SVN root:
> https://svn.apache.org/repos/asf/qpid/qpid-jms-amqp-0-x
> The Java Broker and integration tests suites will remain at: 
> https://svn.apache.org/repos/asf/qpid/qpid-java
> Maven dependencies will be used to pull in the appropriate 0-x client for 
> integration testing purposes (as we already do with the Qpid JMS Client).
> The {{qpid-common}} module (and maven release artefact) will be eliminated.
> * Classes that the Broker requires will be moved into the class hierarchy of 
> the existing plugin modules {{amqp-0-10-protocol}} and {{amqp-0-8-protocol}} 
> e.g. {{org/apache/qpid/server/protocol/vx_y}}.*
> * Code that the 0-x client requires will be moved into the class hierarchy of 
> the client {{org/apache/qpid/client}}.
> This will allow the Broker and 0-x Client to co-exist in the same JVM with 
> class loading collision.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to