fix(db): change argument order in Exists query for JavaDB

[DaspawnW]

Description

Related issues

• Close Failure in exists query for JavaDB #4620

Checklist

• [ x] I've read the guidelines for contributing to this repository.
• [x ] I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[afdesk]

@DaspawnW thanks for your PR!

it looks like a curious mistake.
how did it work before? )

[afdesk]

but I can't find a case where this mistake matters.

[DaspawnW]

Hi @afdesk,

I guess it's more a matter of performance. The Exists query gets called within the aquasecurity/go-dep-parser
https://github.com/aquasecurity/go-dep-parser/blob/main/pkg/java/jar/parse.go#L144 . In this particular case it will always fail and continue then with the SHA1 based query https://github.com/aquasecurity/go-dep-parser/blob/main/pkg/java/jar/parse.go#L151

So it will work but has to perform for each dependency a second query even though it's available.

[afdesk]

it seems i understood what happens:
this block never runs
https://github.com/aquasecurity/go-dep-parser/blob/main/pkg/java/jar/parse.go#L146

[afdesk]

Hi @DaspawnW
thanks! you're right!

[afdesk]

@DaspawnW I've created an issue from your discussion - it's our workflow.
and updated your comment, i hope it's ok.

[afdesk]

thanks for the good catch!