Major release with incompatible changes:
- Fix duplicate schemas when transforming inheritances from i4.0 models
- Update the Service Level Agreement extensions to the latest version
- Latency and Period metrics are supported
- The subscription callback always receives the channel parameters (even if empty)
- The subscription operation returns the actual Consumer function passed as a callback
- Subscriptions now allow multiple calls to register multiple callbacks
- Operations are no longer used as static classes, but as singletons
- Operation must be called from the Channel
- Refactored the methods in IOperations, and IPublishOperation and IsubscribeOperation
- Added generic publish and subscribe methods, so that they can be used in the measurement instruments
- Added period measurement instrument
- Add example project with QoS
- Also update other example projects accordingly
- Fix wizard window size
Major release with small but incompatible changes:
- Update the Service Level Agreement extensions to the latest version.
NOTE: the changes only affect the SLA extensions, so "normative" AsyncAPI projects and definitions should work as before. Nevertheless, since the grammar for SLAs has changed, we mark this version as backwards incompatible.
Major release with small but incompatible changes:
- Change the way payloads and headers are managed in protocols that support it. Now, headers are managed as a separate entity from the payload, and are not embedded as part of the payload if the protocol does not support headers (e.g., MQTT).
- Change the IMessage interface, which now always has getHeaders and getPayload methods, returning an Optional.
Minor release with a few modifications:
- Add support for raw messages (i.e., do not always send messages in a wrapper with "headers" and "payload"
- Fix declaration of properties whose Schemas are declared as Components
- Add a null check when generating imports from headers and payloads
- Minor fixes in the AsyncAPI to JSON transformation (e.g., commas)
- Add support for inheritance in the UML2AsyncAPI transformation
- Fix imports when imported by embedded headers and messages
- Start preparing the templates to support Kafka (but still throwing UnsupportedOperationExceptions)
Minor release with minor fixes:
- Add support for user/password authentication in MQTT servers.
- Improve error notification on M2M transformation.
- Fix wildcard computation expression, allowing parameters to appear at the beginning of a channel name.
- Minor fix in package name calculation (skip empty segments).
- Catch a few NPE when generating AsyncAPI specifications/code of incomplete models.
Major release, with few but breaking changes:
- Change the metaclass the Broker stereotype extends (Class vs Component) (breaking change!).
- Minor fixes in the New Project wizard window.
- Improve documentation for the UML to AsyncAPI feature (i.e., Industry 4.0 support).
Major release with important changes:
- Include support for QoS and SLA (as
x-...extensions) in the Grammar. - Refactor the old single-file template, by multiple modular files.
- Rework the old templates, to allow the generation of Servers, Channels, Operation, Messages, and Payloads (among other things).
- Add support for multiple AsyncAPI Servers, with multiple subscriptions to different topics.
- Update Target platform to latest Eclipse release (2022-03), and update related dependencies (Xtext, EMF, etc.).
- Ensure that all plug-ins are consistent and require Java-11 as the Execution Environment.
- Migrate the build system from Eclipse legacy to maven/Tycho.
- Add setup files for Oomph installations.
- Add setup files to prepare a development environment.
- Refactor the Ecore to AsyncAPI transformation to a dedicated class.
- Rework and reorganize code generators and creation wizards to generate maven-based projects, rather than Eclipse Java projects.
- Get rid of Ivy-related stuff, since it is no longer needed (rely en maven and m2e projects).
- Migrate from old-style Eclipse Update Site to Tycho
category.xml. - Improve Javadoc of generated source code.
- Add UML profile for Industry 4.0 modeling.
- Create extension point to allow contributing 3rd-party/external project templates.
- Ask for the activation of the Java perspective when creating new projects.
- Implement I4.0 UML model to AsyncAPI M2M transformation.
- Add wizard for Example AsyncAPI Project from I4.0 UML model and AsyncAPI Project from I4.0 UML model.
- Add Papyrus as a dependency if the I4.0 plug-ins are installed.
- Implement automatic deployment of generated Update Sites.
- Add product definitions for pre-built AsyncAPI Toolkit distributions.
- Improve and refactor project documentation.
- Many other code clean-ups and fixes.
Minor bugfixes:
- Update code in main method for the streetlights example to comply with the latest generation templates.
- Minor changes in some Eclipse labels (AsyncApi -> AsyncAPI).
Multiple minor changes:
- Fix bug in Example Ecore-based proyect due to NPE.
- Force the Payload builder to be called from the publish class.
- Use operationId in the publish/subscribe classes when available.
- Update Example Ecore-based proyect to support parameters and operation IDs.
- Reorder arguments when receiving a message with parameters.
- Update README to reflect latest changes in the Ecore-based example project.
Bugfixes and improvements:
-
Fix Java code generation when title is used to generate a friendly name
-
Multiple changes in the Ecore2AsyncApi transformation:
- Add annotation and support custom names for Messages and Schemas.
- Add annotation and support for titles in Schemas and properties.
- Add annotation and support for parameters in Channel names.
- Update README.md file to keep it consistent with new annotations.
Minor fixes:
- Fix regex for calculating wildcards for subscribing to topics (incorrect replacement when the parameter was at the end of the topic name without a trailing slash)
Minor modifications:
- Modify the naming conventions: do not append an extra underscore when a Java identifier already starts with _.
Changes:
- Fix bug where enums in the "components" section were not generated. This bug was evident after fixing the duplicate generation of classes fixed in v0.4.0.
Changes:
- Fix bug where classes in the "components" section were generate twice (both in the components package and within the classes using them).
- Add support for enumerations for APIs imported from Ecore models.
- Add a new project type to the AsyncAPI wizard with an example of project imported from an Ecore file.
Changes:
- Add partial support for typed collections (i.e., obey the schema specified in "items" for "arrays"). Only primitive types or schemas defined as "components" are supported.
- Code generation now generates a addTo(...) method for these many-valued properties.
Minor changes:
- Generate servers, channels, and messages sections only if defined
Add support for the generation of AsyncAPI specifications out of Ecore metamodels.
Minor changes:
- Add support in the AsynAPI grammar for minItemsand maxItems in JSON Schema arrays.
Minor fixes:
- Fix to allow parameters to not span over a complete level name.
- Remove ivy generation from template.
- Make some fields optional to limit the number of errors reported.
- Add template for empty projects.
- Add support for the embedded Moquette server.
- Add autocompletion for JSON types.
- Remove support for generic JSON expressions.
Minor fixes:
- Generate separate methods for publishing and subscribing when channels
- have/don't have parameters.
- Fix naming issue in parameters.
- Cleanup unused methods.
- Fix uncatched CloneNotSupportedException in generated code.
- Add custom icons using the AsyncAPI logo.
- Fix typos in README.
Minor fixes:
- Fix spacing issues in generated code.
- Improve generated Javadoc.
First release supporting publishing messages and subscribing to topics.
- Support for AsyncAPI 2.0.0
- Allow publication and subscription.
- Update wizard with a fully working sample code.
Initial release, first minimally functional product:
- Support AsyncAPI 1.2.0
- Generate internal DSL to build payload messages.