AsperforMias opened a new pull request, #3348:
URL: https://github.com/apache/dubbo-go/pull/3348

   ### Description
   Fixes #2582  (issue)
   
   ## Background
   
   After `GenericService2` was removed in v3, generic invoke no longer had a 
stable way to access response attachments.
   This affects migration scenarios from older versions: the generic call 
itself still works, but callers can no longer read provider-side response 
attachments as before.
   
   ## Solution
   
   This change uses a compatibility-focused approach and does not modify the 
existing generic filter, protocol invokers, or the core invocation chain.
   
   Specifically, it:
   
   1. restores a `GenericService2` compatibility entry
   2. adds response attachment storage/access support to `GenericService` and 
`GenericService2`
   3. stores result attachments back into the generic service instance after 
proxy invocation returns
   4. allows callers to read response attachments via 
`GetResponseAttachments(ctx)`
   
   ## Changes
   
   - add compatible `GenericService2` type and constructor
   - add `Client.NewGenericService2(...)`
   - add response attachment save/read capability for generic services
   - persist response attachments after generic proxy invocation returns
   - add focused unit tests
   
   ## Compatibility
   
   This is a backward-compatible enhancement:
   
   - it does not change the current `GenericService` invocation style
   - it does not modify existing protocol handling logic
   - it only restores response attachment access for generic invoke
   
   ## Tests
   
   Verified with targeted tests:
   
   - `go test ./filter/generic ./proxy ./config/generic ./client`
   
   ### Checklist
   - [x] I confirm the target branch is `develop`
   - [x] Code has passed local testing
   - [x] I have added tests that prove my fix is effective or that my feature 
works
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to