-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Branch for eXist 5.3.0 #31
Conversation
@claudius108 Something doesn't seem quite right with this PR... from which branch are you trying to send the updates? Perhaps I could help? |
I wanted a PR from claudius108:eXist-5.3.0 to eXist-db:eXist-5.3.0, but I did to eXist-db:master. |
@claudius108 I see there are some conflicts. Will you be able to address this, or do you need assistance? |
Hi, There are some changes that I have to include in my branch. I will try to do this. |
These to functions are duplicates in an XQuery context because their types are not taken into account only the number of arguments: arity(
FS_GENERATE_SIGNATURE_PARAM_DATA,
FS_GENERATE_SIGNATURE_PARAM_CANONICALIZATION_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_DIGEST_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_NAMESPACE_PREFIX,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_TYPE,
FS_GENERATE_SIGNATURE_PARAM_XPATH
),
arity(
FS_GENERATE_SIGNATURE_PARAM_DATA,
FS_GENERATE_SIGNATURE_PARAM_CANONICALIZATION_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_DIGEST_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_NAMESPACE_PREFIX,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_TYPE,
FS_GENERATE_SIGNATURE_PARAM_DIGITAL_CERTIFICATE
), |
These are the signatures that the baseX implementation provides: https://docs.basex.org/wiki/Cryptographic_Module crypto:generate-signature(
$input as node(),
$canonicalization as xs:string,
$digest as xs:string,
$signature as xs:string,
$prefix as xs:string,
$type as xs:string
) as node() crypto:generate-signature(
$input as node(),
$canonicalization as xs:string,
$digest as xs:string,
$signature as xs:string,
$prefix as xs:string,
$type as xs:string,
$xpath as xs:string,
$certificate as node()
) as node() crypto:generate-signature(
$input as node(),
$canonicalization as xs:string,
$digest as xs:string,
$signature as xs:string,
$prefix as xs:string,
$type as xs:string,
$ext as item()
) as node() |
this signature of generate-signature should expect 8 parameters instead of 7 arity(
FS_GENERATE_SIGNATURE_PARAM_DATA,
FS_GENERATE_SIGNATURE_PARAM_CANONICALIZATION_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_DIGEST_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_NAMESPACE_PREFIX,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_TYPE,
== Missing XPATH ==,
FS_GENERATE_SIGNATURE_PARAM_DIGITAL_CERTIFICATE
), according to the baseX implementation crypto:generate-signature(
$input as node(),
$canonicalization as xs:string,
$digest as xs:string,
$signature as xs:string,
$prefix as xs:string,
$type as xs:string,
$xpath as xs:string,
$certificate as node()
) as node() should be arity(
FS_GENERATE_SIGNATURE_PARAM_DATA,
FS_GENERATE_SIGNATURE_PARAM_CANONICALIZATION_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_DIGEST_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_ALGORITHM,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_NAMESPACE_PREFIX,
FS_GENERATE_SIGNATURE_PARAM_SIGNATURE_TYPE,
FS_GENERATE_SIGNATURE_PARAM_XPATH,
FS_GENERATE_SIGNATURE_PARAM_DIGITAL_CERTIFICATE
), |
What are all these empty files for? |
Related: expath/expath-cg#132. |
development will be picked up by the existdb community |
No description provided.