You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
UX design is needed for JMS (Java Messaging Service) connector and S3 connector
JMS broker between producer and consumer; if we receive from JMS, we’re getting messages from the queue but we don’t know data type, so user must provide data type - via json example, json schema, xml example, xml schema, or other descriptor.
Java objects (twitter); json data (salesforce); xml
Use for JMS to/from another type of connector - will require configuration, upload schema or infer from sample data
UX: when data types don’t match add a notification (“data types are not compatible”) - the corrective is to provide a transformation/mapping
Example: JMS to Twitter (we know twitter expects java object; need step to define JMS data type)
The text was updated successfully, but these errors were encountered:
Notes from meeting with @kcbabo:
The text was updated successfully, but these errors were encountered: