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

Latest snapshot of server throws ConfigurationException: Search param telecom is of unexpected datatype #139

Closed
mojitoholic opened this Issue Mar 31, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@mojitoholic
Contributor

mojitoholic commented Mar 31, 2015

ca.uhn.fhir.context.ConfigurationException: Search param telecom is of unexpected datatype: class ca.uhn.fhir.model.dstu2.composite.ContactPointDt
at ca.uhn.fhir.jpa.dao.SearchParamExtractorDstu2.extractSearchParamTokens(SearchParamExtractorDstu2.java:470) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirDao.extractSearchParamTokens(BaseFhirDao.java:265) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirDao.updateEntity(BaseFhirDao.java:1040) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirResourceDao.doCreate(BaseFhirResourceDao.java:751) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirResourceDao.update(BaseFhirResourceDao.java:1748) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirResourceDao.update(BaseFhirResourceDao.java:1715) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]
at ca.uhn.fhir.jpa.dao.BaseFhirResourceDao.update(BaseFhirResourceDao.java:1710) ~[hapi-fhir-jpaserver-base-1.0-SNAPSHOT.jar:na]

@mojitoholic

This comment has been minimized.

Contributor

mojitoholic commented Mar 31, 2015

My workaround to make the server work for now was to add another else-if block near line 470 in SearchParamExtractorDstu2.java to swallow ContactPointDt and avoid throwing the exception.

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Apr 5, 2015

Thanks for reporting! Fix coming up shortly.

@jamesagnew jamesagnew closed this in 1f51c69 Apr 5, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment