bvfalcon opened a new pull request, #8788:
URL: https://github.com/apache/camel/pull/8788

   At the Image 1 is shown work of application with Google Spreadspeets 
component in "real-life"-mode
   ![Image 1 - Real 
work](https://user-images.githubusercontent.com/49613576/204360806-24d5ccfa-499e-4a6c-a407-cf776c3ca44b.png)
   **Image 1 - Real work**
   
   Tests before (link side) and after (right side) this PR are shown at the 
Image 2
   ![Image 2 - Tests 
changes](https://user-images.githubusercontent.com/49613576/204361924-ab972bed-ea30-48d4-a555-2c6c38b586dd.png)
   **Image 2 - Tests changes**
   
   Advantages of new schema:
   1.  Where are no unnecessary dependencies.
   Dependencies Citrus Framework, Spring Security, AssertJ are used by embedded 
server. These dependencies are test-scoped and were used only to mock remote 
Google Services. This is not necessary: Google Api Client itself [supports 
test-mode](https://github.com/googleapis/google-api-java-client/tree/main/google-api-client/src/main/java/com/google/api/client/googleapis/testing).
   2. OAuth2 realization not necessary and removed.
   OAuth2 Mock server is build with Spring Security OAuth library which [is 
deprecated](https://spring.io/projects/spring-security-oauth). Implementing new 
OAuth2 Mock server using [new Spring 
component](https://spring.io/projects/spring-authorization-server) is difficult 
because required profound knowledge of OAuth2 protocol. And this is not 
necessary ;) -- Google Api Client library makes this work for us.
   
   (!) Not solved problem: both schemas - old and new - have no control of 
Sheets API change. If this API changes, component will be work in corrupted 
mode. Make this check is possible with analysis of [Sheets API 
Schema](https://sheets.googleapis.com/$discovery/rest?version=v4), but this 
aspect is out of scoped for this PR and will stay for future.


-- 
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]

Reply via email to