...
After examining the PUT source generated during this error, as revealed by Firebug, I saw that three groups/lists didn't have all their fields included. I examined the code for these. The first, nagpraClaimNoteList, a repeating note field, had code identical to another (working) repeating notes field (comments in collectionobject). The second, sentToOversightCommitteeGroup, had code identical to another (working) group in nagpraclaim. This second group was, however, inadvertently duplicated in the nagpraclaims_anthropology.xsd schema (it should only be in the nagpraclaims_pahma.xsd schema). Removing it did not resolve the error. The third field, recommendationOfOversightCommitteeGroup, also had code identical to another (working) group in nagpraclaim.
Aron pointed me to the collectionspace.log, which contained the following line:
| Code Block |
|---|
2011-10-06 11:42:42,463 DEBUG \[org.collectionspace.services.common.document.DocumentUtils\] Invalid input document. No such property was found nagpraClaimNoteList in schema nagpraclaims_common
|
This indicates to me that I hadn't properly pointed the field to the proper schema in our-tenant-tenant.xml. And indeed, this is what I found in our-tenant-tenant.xml:
| Code Block |
|---|
<repeat id="nagpraClaimNoteList">
<field id="nagpraClaimNote"></field>
</repeat>
|
I changed this to the following and am redeploying and rebuilding to see if this resolves the error:
| Code Block |
|---|
<repeat id="nagpraClaimNoteList" section="anthropology">
<field id="nagpraClaimNote" section="anthropology"></field>
</repeat>
|
The above did not fix the error.
Solution: unknown.
...
Resolved: Variants of "Status:400:Create request failed: javax.ejb.EJBException: java.lang.NullPointerException"
...