Skip to content
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

Qute - methods on Object not resolved for types declared using interfaces #7843

Closed
Maldivia opened this issue Mar 13, 2020 · 1 comment · Fixed by #7917
Closed

Qute - methods on Object not resolved for types declared using interfaces #7843

Maldivia opened this issue Mar 13, 2020 · 1 comment · Fixed by #7917
Assignees
Labels
area/qute The template engine kind/bug Something isn't working
Milestone

Comments

@Maldivia
Copy link
Contributor

Describe the bug
Given a template with

{@java.util.List obj}
{obj.toString()}

results in a BuildException with:

[1] Incorrect expression: obj.toString()
	- property/method [toString()] not found on class [java.util.List] nor handled by an extension method
	- found in template [hello.html] on line 2

The above works as expected if it's a concrete type, for instance:

{@java.util.ArrayList obj}
{obj.toString()}

Environment (please complete the following information):
Quarkus 1.3.0.Final
Java 11.0.6

@Maldivia Maldivia added the kind/bug Something isn't working label Mar 13, 2020
@quarkusbot
Copy link

/cc @mkouba

@quarkusbot quarkusbot added the area/qute The template engine label Mar 13, 2020
@mkouba mkouba added this to the 1.4.0 milestone Mar 13, 2020
@mkouba mkouba self-assigned this Mar 13, 2020
mkouba added a commit to mkouba/quarkus that referenced this issue Mar 17, 2020
gsmet pushed a commit to gsmet/quarkus that referenced this issue Mar 21, 2020
viniciusfcf pushed a commit to viniciusfcf/quarkus-fork that referenced this issue Sep 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qute The template engine kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants