API handlers for the JMS server
OCI NodeJS client for Jms Service
OCI NodeJS client for Jms Java Downloads Service
JavaScript library to parse and build "purl" aka. package URLs. This is a microlibrary implementing the purl spec at https://github.com/package-url
OCI NodeJS client for Jms Utils Service
Utility for Node's java module to load mvn dependencies.
Genesis JMS Integration
The AsyncAPI generator. It can generate documentation, code, anything!
XB Messaging AMQP V100
Java JMS template for AsyncAPI generator
Command line tool for Jaspero products
Utility for Node's java module to load mvn dependencies.
A set of plugins for [JMS](https://github.com/Jaspero/jms).
Use your AsyncAPI definition to generate java (code based on Micronaut framework) to subscribe and publish messages.
just my socks 流量消耗查询推送
this is a node shell
Event externalization for @nestjs-transactional/outbox via @nestjs/microservices ClientProxy — Spring Modulith @Externalized parity
Standard Tooling for js-multi-seed Development
messageChecker verifies SOAP and Java Message Service (JMS) messages and position delimited messages.
A set of plugins for [JMS](https://github.com/Jaspero/jms).
JavaScript library for the development of Lightstreamer JMS Extender clients running on the Node.js runtime
Node.js API (Node-API)
Utility functions for working with TypeScript's API. Successor to the wonderful tsutils. 🛠️️
Public logs API for OpenTelemetry
JRuby-JMS is a Java and Ruby library that exposes the Java JMS API in a ruby friendly way. For JRuby only.
A Ruby gem to connect your application with the usekamba API
More often than not you don't need a full fledged message queue like ActiveMQ or RabbitMQ with a full size message format. For simple asynchronous distribution tasks a very light weight persistent message queue like starling will be fine. Nevertheless you want a more sophisticated interface to interact with than a memcache interface. Simple Publisher tries to achieve exactly this: While using Starling as the queuing system in the background we provide a messaging terminology well know and understood. The terminology is strongly inspired by JMS which is kind a defacto standard for messaging on the API-level.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.