-
Notifications
You must be signed in to change notification settings - Fork 16
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
TypedQuery Parameters ending with > are not parsed correctly #294
Milestone
Comments
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 12, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 12, 2024
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 16, 2024
…e method - converts Wrapper classes (e.g. Integer.class) to their corresponding primitive counterparts (e.g. int.class)
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 16, 2024
…elds - remove MetamodelInitializationException thrown in ClassFieldMetamodelProcessor - check if Wrapper type can be converted to primitive type in DataPropertyFieldStrategy
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 16, 2024
…elds - remove MetamodelInitializationException thrown in ClassFieldMetamodelProcessor - check if Wrapper type can be converted to primitive type in DataPropertyFieldStrategy
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
…e method - converts Wrapper classes (e.g. Integer.class) to their corresponding primitive counterparts (e.g. int.class)
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
…elds - remove MetamodelInitializationException thrown in ClassFieldMetamodelProcessor - check if Wrapper type can be converted to primitive type in DataPropertyFieldStrategy
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
luxbe
added a commit
to luxbe/jopa
that referenced
this issue
Dec 17, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
- converts Wrapper classes (e.g. Integer.class) to their corresponding primitive counterparts (e.g. int.class)
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
- remove MetamodelInitializationException thrown in ClassFieldMetamodelProcessor - check if Wrapper type can be converted to primitive type in DataPropertyFieldStrategy
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parameters in the form of
?abc>
are not parsed correctly starting from JOPA v2.2.0.When creating a TypedQuery, parameters are not parsed correctly since the latest JOPA version. In the following SPARQL query:
With v2.1.0, the following parameters where detected:
?s
,?p
,?o
, and?test
.With v2.2.0, the following parameters where detected:
?s
,?p
,?o
, and?test>
, the last parameter unexpectedly includes the>
characterThe text was updated successfully, but these errors were encountered: