[JIRA] (JSPD-1) Build socket server skeleton on top of a Spring ApplicationContext

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JSPD-1 ( https://shibboleth.atlassian.net/browse/JSPD-1?atlOrigin=eyJpIjoiY2U5YzNlNDc5Mjk4NDU0NzhkZDE4YjVkMWNkMjRhZGUiLCJwIjoiaiJ9 )

Re: Build socket server skeleton on top of a Spring ApplicationContext ( https://shibboleth.atlassian.net/browse/JSPD-1?atlOrigin=eyJpIjoiY2U5YzNlNDc5Mjk4NDU0NzhkZDE4YjVkMWNkMjRhZGUiLCJwIjoiaiJ9 )

I checked out the spring-socket-server and did a bit of playing and reading. So far the one thing I couldn’t seem to do was make NIO work, which seems to be the desirable state of affairs I think (the docs suggest that decouples the request threads from the socket handling, which will help avoid some of the problems we have now).

But if I set use_nio=”true” in the three example gateway designs, it breaks the message correlation, and if I try and fix that, it seems to break the automatic type conversion that the explicit output channel definitions are providing.

I guess the goal would be to somehow solve that. It talks about message headers and how to achieve message correlation when there’s a separate output channel, but I can’t see where that all lines up with the way the service activation is generic and unaware of any of the Spring Integration code.

( https://shibboleth.atlassian.net/browse/JSPD-1#add-comment?atlOrigin=eyJpIjoiY2U5YzNlNDc5Mjk4NDU0NzhkZDE4YjVkMWNkMjRhZGUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JSPD-1#add-comment?atlOrigin=eyJpIjoiY2U5YzNlNDc5Mjk4NDU0NzhkZDE4YjVkMWNkMjRhZGUiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- sha1:943baf4 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220412/b9829bdd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-1de6332c-a7b3-4a16-a43c-6ebade31cbf0
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220412/b9829bdd/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-01356a68-2424-42b6-a7c5-5528d58c4c77
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220412/b9829bdd/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-8092f054-7801-4704-908b-fc4d0aeb530f
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220412/b9829bdd/attachment-0005.png>