Reason: No property 'key' found on class **** Did you mean: key?

[eatenupme]

ok do @Table("t_name") and @Component conflict?

[schauder]

Sorry, I can't read that language and I doubt anyone else in the team can. Please update the question to English.

[eatenupme]

do @table("t_name") and @component conflict?

[schauder]

I don't think they should, although it is a weird combination.

@Table is for entities, i.e. things you load from a database or create in your application and persist to a database.

@Component is for well beans, i.e. things that (mostly) get created during startup, and stay around in memory until the application ends, or for a well defined scope, like one web request.

I have a hard time imagining why a class would be annotated with both.

Could you explain your use case or provide a reproducer so that we can determine a workaround or the source of the problem?

[eatenupme]

just for study .

I want to know why.