Illegal Argument Exception : in getItemType
We had ecore model based Jazz Component which we migrated from RTC 1. to RTC 2.0.0.2. We created the DB (Derby) and ran our application. The application worked fine accessing the DB. After a couple of restart of the server, suddenly, no calls to DB work. We end up getting this kind of error.
java.lang.IllegalArgumentException: The type name Glossary and the namespace URI com.ibm.research do not resolve to an IItemType.
at com.ibm.team.repository.common.internal.querypath.AbstractQueryPathModel$Implementation.getItemType(AbstractQueryPathModel.java:190)
at com.ibm.team.repository.common.query.IQuery$Factory.newInstance(IQuery.java:92)
Where, the "Glossary" is the Eclassifier name and com.ibm.research is the nsURI.
When we tried this in debug mode, The EPackage corresponding to this artifact is coming as null - and hence this issue being reported.
What we are not able to understand is - the DB seems to be working fine - and all of a sudden this error starts coming up.
Once we delete the db and recreate it again, things all work fine for some time -- and after a couple of restart to the server, this issue again comes up.
Can anyone help us here to understand whats happening.
java.lang.IllegalArgumentException: The type name Glossary and the namespace URI com.ibm.research do not resolve to an IItemType.
at com.ibm.team.repository.common.internal.querypath.AbstractQueryPathModel$Implementation.getItemType(AbstractQueryPathModel.java:190)
at com.ibm.team.repository.common.query.IQuery$Factory.newInstance(IQuery.java:92)
Where, the "Glossary" is the Eclassifier name and com.ibm.research is the nsURI.
When we tried this in debug mode, The EPackage corresponding to this artifact is coming as null - and hence this issue being reported.
What we are not able to understand is - the DB seems to be working fine - and all of a sudden this error starts coming up.
Once we delete the db and recreate it again, things all work fine for some time -- and after a couple of restart to the server, this issue again comes up.
Can anyone help us here to understand whats happening.