|
| 1 | +// Jest Snapshot v1, https://goo.gl/fbAQLP |
| 2 | + |
| 3 | +exports[`OnTextMessageHandler component (integration with AsyncAPI document) renders default handler when sendOperations is empty array 1`] = ` |
| 4 | +"@OnTextMessage |
| 5 | + public void processTextMessage(String message, WebSocketClientConnection connection) { |
| 6 | + LOG.info(\\"Received text message: \\" + message); |
| 7 | + }" |
| 8 | +`; |
| 9 | + |
| 10 | +exports[`OnTextMessageHandler component (integration with AsyncAPI document) renders default handler when sendOperations is null 1`] = ` |
| 11 | +"@OnTextMessage |
| 12 | + public void processTextMessage(String message, WebSocketClientConnection connection) { |
| 13 | + LOG.info(\\"Received text message: \\" + message); |
| 14 | + }" |
| 15 | +`; |
| 16 | + |
| 17 | +exports[`OnTextMessageHandler component (integration with AsyncAPI document) renders default handler without sendOperations 1`] = ` |
| 18 | +"@OnTextMessage |
| 19 | + public void processTextMessage(String message, WebSocketClientConnection connection) { |
| 20 | + LOG.info(\\"Received text message: \\" + message); |
| 21 | + }" |
| 22 | +`; |
| 23 | + |
| 24 | +exports[`OnTextMessageHandler component (integration with AsyncAPI document) renders handler with if statement for single send operation 1`] = ` |
| 25 | +"@OnTextMessage |
| 26 | + public void handleTextMessage(String message, WebSocketClientConnection connection) { |
| 27 | + LOG.info(\\"Handler received text message: \\" + message); |
| 28 | + if (message != null && message.contains(\\"sendMessage\\")) { |
| 29 | + sendMessage(message, connection); |
| 30 | + } |
| 31 | + else { |
| 32 | + LOG.warn(\\"Handler received unrecognized message type. Falling back to default handler.\\"); |
| 33 | + // Note: By default, we route unrecognized messages to the first operation handler. |
| 34 | + // Depending on your business logic, you may want to change this behavior. |
| 35 | + sendMessage(message, connection); |
| 36 | + } |
| 37 | + } |
| 38 | +
|
| 39 | + public void sendMessage(String message, WebSocketClientConnection connection) { |
| 40 | + LOG.info(\\"Processing sendMessage type message: \\" + message); |
| 41 | + // TODO: implement processing logic for sendMessage |
| 42 | + }" |
| 43 | +`; |
| 44 | + |
| 45 | +exports[`OnTextMessageHandler component (integration with AsyncAPI document) renders handler with if-else-if chain for multiple send operations 1`] = ` |
| 46 | +"@OnTextMessage |
| 47 | + public void handleTextMessage(String message, WebSocketClientConnection connection) { |
| 48 | + LOG.info(\\"Handler received text message: \\" + message); |
| 49 | + if (message != null && message.contains(\\"sendMessage\\")) { |
| 50 | + sendMessage(message, connection); |
| 51 | + } |
| 52 | + else if (message != null && message.contains(\\"sendNotification\\")) { |
| 53 | + sendNotification(message, connection); |
| 54 | + } |
| 55 | + else { |
| 56 | + LOG.warn(\\"Handler received unrecognized message type. Falling back to default handler.\\"); |
| 57 | + // Note: By default, we route unrecognized messages to the first operation handler. |
| 58 | + // Depending on your business logic, you may want to change this behavior. |
| 59 | + sendMessage(message, connection); |
| 60 | + } |
| 61 | + } |
| 62 | +
|
| 63 | + public void sendMessage(String message, WebSocketClientConnection connection) { |
| 64 | + LOG.info(\\"Processing sendMessage type message: \\" + message); |
| 65 | + // TODO: implement processing logic for sendMessage |
| 66 | + } |
| 67 | +
|
| 68 | + public void sendNotification(String message, WebSocketClientConnection connection) { |
| 69 | + LOG.info(\\"Processing sendNotification type message: \\" + message); |
| 70 | + // TODO: implement processing logic for sendNotification |
| 71 | + }" |
| 72 | +`; |
0 commit comments