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

Gordon Sim updated QPID-5030:
-----------------------------

    Attachment: Translator.java

At the time the current syntax was being discussed, I wrote a simple utility 
for converting between the different names, which I am attaching here in case 
it os of use in this task.

It works by simply checking any unquoted words against those for which a 
replacement is defined (avoiding replacement within string literals). You can 
run the class against std::in and it will output the translated version (useful 
for tests). It takes an optional command line switch, --jms-to-amqp or 
--amqp-to-jms, to determine the 'direction' of translation (the default is from 
JMS names to AMQP names). 

Since there must currently be two paths for 0-10 in the client (one using the 
Java Broker defined subscription argument, one doing the selection on the 
client), the criteria used in choosing between these could be kept and perhaps 
extended to cover sending the 'amqp format' via a different selector argument.
                
> JMS client to use C++ broker selectors
> --------------------------------------
>
>                 Key: QPID-5030
>                 URL: https://issues.apache.org/jira/browse/QPID-5030
>             Project: Qpid
>          Issue Type: Sub-task
>            Reporter: Andrew Stitcher
>         Attachments: Translator.java
>
>
> As the current C++ broker selector work stands it is compliant with the 
> registered amqp 1.0 filter extension, but the JMS client will not use the C++ 
> broker selectors for anything still falling back to the client side selectors.
> We should allow the JMS client to use the c++ broker selectors.
> There are roughly 2 ways to do this and both may be needed:
> For amqp 1.0 we need the client to translate the JMS specified identifiers to 
> the ones specified in the extension and to use a filter - this may never be 
> work sensible to do in the existing client.
> For earlier protocol versions, we probably need to add code to the C++ broker 
> which accepts the extra subscription property that the java client uses for 
> the selector and add some code which recognises the JMS identifiers instead 
> of the amqp extension identifiers.

--
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

Reply via email to