1. Connection: A Connection object is used to establish a connection to the STOMP broker. It typically contains information such as the broker's address, port, and authentication credentials.
2. Session: A Session object represents a logical session within the connection. It allows you to create, send, and receive messages.
3. Transaction: A Transaction object is used to group multiple messages into a single unit of work. Transactions can be committed or aborted for reliable messaging.
4. Message: A Message object represents a single message that is sent or received. It contains the message body, content-type, headers, and other metadata.
5. Destination: A Destination object represents a named endpoint where messages are sent or consumed. In STOMP, destinations are typically queues or topics.
6. Frame: A Frame is the basic unit of communication between the client and the broker. It contains a command, which specifies the action to be performed, and optional headers and body data.
7. SockJS: STOMP also supports the use of SockJS, which provides an abstraction layer for WebSocket connections. SockJS enables STOMP to work over various transport protocols, such as WebSocket, HTTP, or AJAX long-polling.