dobrynya/reajames

Issues

• Fix tests to be successful on travis

  #41 opened 6 years ago
  0

• Make it possible to choose AcknowledgeMode, when creating a JmsReceiver

  #39 opened 7 years ago
  0

• Cross-compile and release for Scala 2.11.x

  #38 opened 7 years ago
  7

• Fix Travis build

  #37 opened 7 years ago
  0

• JmsSender should implement Processor instead of Subscriber

  #36 opened 8 years ago
  0

• Wrap in Try applying message factory when sending messages

  #35 opened 8 years ago
  0

• Make Rejames API to be interoperable with Java clients

  #34 opened 8 years ago
  0

• Do not start receiving while onSubscribe is in progress

  #33 opened 8 years ago
  0

• Fix code quality issues

  #31 opened 8 years ago
  2

• Review documentation

  #29 opened 7 years ago
  2

• Fix JMS session leak

  #27 opened 8 years ago
  2

• Improve test coverage

  #26 opened 7 years ago
  1

• JmsSender stops sending messages sometimes

  #25 opened 8 years ago
  1

• Improve log messages

  #24 opened 7 years ago
  0

• Integrate coverageall.io to analize testing code coverage

  #22 opened 8 years ago
  1

• Client should be able to subscribe a temp destination and enrich messages with JMSReplyTo referring that destination

  #21 opened 8 years ago
  0

• Integrate Swave as another reactive streams implementation

  #20 opened 8 years ago
  0

• TemporaryQueue/Topic should cache a newly created destination to be able to pass this value to another component

  #19 opened 8 years ago
  1

• Implement DestinationFactory for javax.jms.Destination

  #18 opened 8 years ago
  0

• Create integration pattern shortcuts

  #17 opened 7 years ago
  1

• Prepare to publish artifacts to Bintray

  #16 opened 8 years ago
  0

• All integration tests should be run against both brokers

  #15 opened 8 years ago
  1

• Improve JmsSender to reuse already started sending task

  #14 opened 8 years ago
  1

• Make JmsReceiver able to initialize itself asynchronously

  #13 opened 8 years ago
  0

• Implement a component managing JMS related infrastructure

  #12 opened 8 years ago
  0

• Make use travis ci and code coverage tool to sanitize code

  #11 opened 8 years ago
  1

• Change compile dependency on logback to slf4j

  #10 opened 8 years ago
  0

• Write microbenchmark tests on typical use cases implemented using the library and only JMS code

  #9 opened 8 years ago
  3

• Write documentation on the library

  #8 opened 8 years ago
  0

• All subscribers with the same connection factory should be optimized to use common connection and producer

  #7 opened 8 years ago
  1

• Integrate an additional in-memory JMS broker to check with another middleware

  #6 opened 8 years ago
  1

• Integrate reactive-streams-tck into the account

  #5 opened 8 years ago
  0

• Publisher and Subscriber should allow to configure reconnection if case of temporary failures

  #4 opened 8 years ago
  3

• Publisher should reuse already established connection instead of spawning a new one

  #3 opened 8 years ago
  0

• JmsSubscriber should allow to configure all aspects during sending messages

  #2 opened 8 years ago
  0

• JmsSubscriber should not block due to sending messages

  #1 opened 8 years ago
  1