Description of problem:

# java -cp ${CLSSPATH} org.apache.qpid.example.Spout "amq.direct;{create: always,node:{x-bindings: [{ exchange: 'amq.direct', queue: 'q'}]}}"
<snip/>
ExecutionException(errorCode=NOT_ALLOWED, commandId=1, classCode=7, commandCode=1, fieldIndex=0, description=not-allowed: Exchange declared to be of type direct, requested topic
<snip/>

Until qpid-java-*-0.18-5 it was not possible to create node bindings for topic node (Bug 860011). This issue was fixed in qpid-java-*-0.18-5 and the binding was successfully created with the above command.

Starting from qpid-java-*-0.18-6 it is still possible to create bindings for topic node, BUT now the topic type must be specified if the topic type is different from default (type: topic). This applies for both node and link bindings.

So the following command can be used to solve this issue:
# java -cp ${CLSSPATH} org.apache.qpid.example.Spout "amq.direct;{create: always,node:{x-declare:{type:direct},x-bindings: [{ exchange: 'amq.direct', queue: 'q'}]}}"

This issue was also present on previous versions, BUT only if assert was used in the address string, please see Bug 870030.

From my point of view, this is a minor issue as workaround exists, feel free to fix in next version.

Version-Release number of selected component (if applicable):
qpid-java-*-0.18-6

How reproducible:
100%

Steps to Reproduce:
1. qpid-config add queue q
2. java -cp ${CLSSPATH} org.apache.qpid.example.Spout "amq.direct;{create: always,node:{x-bindings: [{ exchange: 'amq.direct', queue: 'q'}]}}"
3. not-allowed exception 
  
Actual results:
The topic type must be specified on creating binding on topic node

Expected results:
It is not necessary to specify the topic type creating binding