[JIRA] (JSPS-1) Build socket server skeleton on top of a Spring ApplicationContext
Scott Cantor (Jira)
jira at shibboleth.atlassian.net
Thu May 19 20:10:13 UTC 2022
Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JSPS-1 ( https://shibboleth.atlassian.net/browse/JSPS-1?atlOrigin=eyJpIjoiZTcwNjJmYzFkNDBiNGZjNWIyNTNhNzUwMWI4MDYxMzYiLCJwIjoiaiJ9 )
Re: Build socket server skeleton on top of a Spring ApplicationContext ( https://shibboleth.atlassian.net/browse/JSPS-1?atlOrigin=eyJpIjoiZTcwNjJmYzFkNDBiNGZjNWIyNTNhNzUwMWI4MDYxMzYiLCJwIjoiaiJ9 )
Outstanding issues:
* NIO just doesn’t seem to allow the standard gateway to work, it doesn’t find the connection to use for the response. I tried manually creating the output message with the connection ID header intact and it didn’t help.
* I tried using a channel interceptor to enforce client address rules. That works, but raising an exception there doesn’t make it to the error channel. That isn’t entirely a problem since arguably just dropping the connection might be the right thing to do, but it also precludes access to the client address later for logging. Moving to a Message<DDF> input parameter on the activator method allowed me to move that checking into the activator natively, and that allows the address to be captured for logging later at the cost of making the activator Spring Integration aware.
( https://shibboleth.atlassian.net/browse/JSPS-1#add-comment?atlOrigin=eyJpIjoiZTcwNjJmYzFkNDBiNGZjNWIyNTNhNzUwMWI4MDYxMzYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JSPS-1#add-comment?atlOrigin=eyJpIjoiZTcwNjJmYzFkNDBiNGZjNWIyNTNhNzUwMWI4MDYxMzYiLCJwIjoiaiJ9 )
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:0f60739 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220519/99115867/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-28e8a97d-3b24-4f15-bc32-05f228ca9946
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220519/99115867/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a5149067-a259-41e9-8ec4-ef49580cc94c
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220519/99115867/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-6036a550-f790-4ea4-96bc-71fae9f48a1c
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220519/99115867/attachment-0005.png>
More information about the commits
mailing list