-
-
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
QueryParameter.FieldName 'System.IndexOutOfRangeException' #496
Comments
Hi @yvdh, Thanks for opening this ticket. The v1 and v2 queries are handled in the exact same way, so if you run this SOAP query you should also get an error:
Did you also receive this exception with other standard parameters and if so do you remember which ones? Thanks! |
Hi, you are right, it also fails with the SOAP query you provided: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:epcisq="urn:epcglobal:epcis-query:xsd:1" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema"> I tried with a 'GE_eventTime' parameter, and that seems to work, both in SOAP and in JSON. Cheers |
Hi, These parameters are now available in the main branch for both 1.x and 2.0 versions. Thanks again for raising this ticket! |
Hello,
Really great work on this EPCIS 1.x - 2.0 project! We are looking into using this project as our EPCIS repository.
So far I have added our own security model (role based) and swagger to your code, and I am hosting on IIS. All quite straightforward.
The SOAP XML 1.2 interfaces seem to work quite well in PostMan (Query, Capture and Subscriptions tested).
However, when performing queries in the REST-JSON interface (EPCIS 2.0) I get 'System.IndexOutOfRangeException' on parameters like GE_errorDeclarationTime. Looking a the code for the FieldName extension of QueryParameter this seems logical:
public static string FieldName(this QueryParameter parameter) => parameter.Name.Split('_')[1].Split('#')[1];
'GE_errorDeclarationTime' contains no '#' so this has to fail ...
This seems to occur for any LT_ or GE_ query parameter.
The same parameters do work in SOAP-XML (which does not use the same methods, right?).
Is this a bug or am I missing something?
Cheers
Yves
The text was updated successfully, but these errors were encountered: