Page History

...

• Project folder structure
• Build tool configuration
• CI server job
• Automated HTML documentation generation.

Phase 1

• Synchronous, Auto-Ack style 'simple client'
• Main operations on JMS Connections, Sessions, Consumers, Producers, Queues, Message (Text?).
  • Include closing/stopping/deleting where applicable.
• Configuration
  • Ability to configure settings such as pre-fetch etc
    • TODO per connection or per consumer or both? If the latter then not sure how to pass this setting in (address options?), given that JMS API doesn't offer an obvious way to do it.
  • TODO define how JNDI configuration will work
• SASL
• Correct handling of non-happy path scenarios, namely:
  • Unexpected errors
  • Failures that are nevertheless AMQP-compliant, e.g. the Broker spontaneously sends a Close or End frame.
  • Timeouts due to connectivity failure etc. Necessary because of the asynchronous nature of AMQP.
  • Interruption of application-owned threads.

...