search

sdaschner / jaxrs-analyzer

Creates REST documentation for JAX-RS projects
Apache License 2.0
319 stars 101 forks source link

Analyze JAX-RS AsyncResponse, @Asynchronous #6

Open sdaschner opened 9 years ago

sdaschner commented 9 years ago

Therefore the parameter is taken as the reduction backtrack starting point.

andreacomo commented 7 years ago

Any news on supporting AsyncResponse? I could really use it. Btw, great work so far.

sdaschner commented 7 years ago

No news yet unfortunately, pretty busy with other concerns right now... Which is definitely sad for this project.

Do you know folks interested in OSS and willing to hack on this feature? :-)

andreacomo commented 7 years ago

I could give it a shot :) Any suggestion where to start digging the code?

sdaschner commented 7 years ago

Awesome! Sure: The first thing would be the functionality in the analysis.classes package. These collect the (JAX-RS) information into intermediate result objects and would need to take the AsyncResponse into account. AFAIK for now it is mistakenly considered as request body there.

Then the analysis.results package where the initial results are analyzed following JSR 339 logic. I guess we would need to enhance the model classes a bit.

Thanks a lot, don't feel pressured to deliver something, I already appreciate the willingness to contribute :-)

andreacomo commented 7 years ago

Hi! Today I had the chance to work on it. I'm made some changes to take in consideration @Suspended annotation, but I'm stuck where I try to find instruction corresponding to the call to AsyncResponse.resume in order to extract parameter value. I think because it's nested in a lambda... do you think is there any chance to do that? I'm starting having some doubt :)

rmannibucau commented 6 years ago

+1 to handle it, can be ok to extract the type from the javadoc as a fallback if the bytecode visit doesn't give the exact type