feat(Rest) : Releases attachment download is failing

[keerthi-bl]

Description

Download attachment is not working with rest end point.

Response structure has changed from "_embedded" : { "sw360:attachments" : [] } to {'_embedded': {'sw360:attachmentDTOes': […

Screenshots

If applicable, add screenshots to help explain your problem.

Versions

• Last commit id on master:
• Operating System (lsb_release -a):

Logs

Any logs (if any) generated in

SW360 logs

Logs generated under /var/log/sw360/sw360.log

Tomcat logs

Logs generated under /var/log/tomcat/error.log

[tuannn2]

Hi @keerthi-bl,
I am using sw360 in branch Main (4666d87).
I'm still using the donwload attachment functionality for projects, components, releases normally.

May I know which Endpoint you are using?

[keerthi-bl]

Hi @tuannn2 ,
Some response structure has been changed with the rest end point while fetching release attachment info.
Previously it was,
"_embedded" : { "sw360:attachments" : [] } like this.
It has been changed to ,
{'_embedded': {'sw360:attachmentDTOes': [… like this.
This may break when we are trying to fetch with attachments key. This issue is to revert to previous version/code.

[tuannn2]

Hi @keerthi-bl,
Can you change title issues? Because features Download attachment is working normally.

• On response structure has been changed to add field response detail for Listing Attachment Information for Release, Component page in sw360-frontend

Is this change necessary?

[ag4ums]

@keerthi-bl, please create PR with the reverted changes

[keerthi-bl]

#2140 is the PR @ag4ums , already merged. Need to close this issue only.

[keerthi-bl]

Hi @tuannn2 :
The end point is not failing actually.

{.** On response structure has been changed to add field response detail for Listing Attachment Information for Release, Component page in sw360-frontend}**

Its failing to the client who are accepting the key as attachments from the end point . So the above changes affect other clients who are using this end point. So its necessary to revert the changes.

Please confirm, can we close this issue.