Closed rsprinkle closed 5 years ago
Hi,
I couldn't reproduce it. MyBatipse does not check if it is an interface or a concrete class. It seems that your Eclipse could not find these classes in the project's classpath, for some reason. If cleaning the project didn't help, try creating a new workspace, please.
@rsprinkle Could you confirm @harawata 's comment?
I also have this error, it happens on every typeAlias and typeHandler. The classes are definitely found, as the Mybatis functionality works for both. It's just the Mybatis XML validation that seems to not find the class.
In my particular instance, the project is setup like this: MainProject (pom = pom)
The Mybatis configuration is found in Project_common/src/resources while the types specified are found in Project_model. I was planning on looking into this issue myself, if I have time and do it, I will update accordingly.
@kenjdavidson , It's quite possible that the plugin does not support multi-module project. It would be great if you could take a look. Thank you!
I couldn't replicate the original issue either.
With regards to my issue, it looks like the person on my team just had their build path configured incorrectly so the error was actually correct. I should have noticed it the first time I looked by it was Friday.
Can probably close this.
Thanks for the follow-up! It's been a while with no reply from the reporter, so let's close.
The validator give a "Class/TypeAlias 'java.sql.Blob' not found." for the following declaration:
<typeHandler javaType="java.sql.Blob" jdbcType="BLOB" handler="EMBlobHandler" />
The declaration works fine in MyBatis. I believe the problem is that the validator is expecting a concrete class. I get an identical error for "java.sql.Clob".