Temp Fix getStatus #185
Merged
Temp Fix getStatus #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Decided to commit all of the changes; most of them are sorting changes, but they will make future updates easier, as I think they more consistently sort the output.
|
Ah, does appear to be a lot of sorting changes. Wonder why the ordering changed..? 🤔 Changes look pretty good to me. I did notice that the WebServiceClient WSDL locations changed from classpath to file resources. Is that intentional? Example of New Value: @WebServiceClient(name = "EfmUserService",
wsdlLocation = "file:illinois-EFMUserServiceSingle.svc.wsdl",
targetNamespace = "urn:tyler:efm:services")Previously: wsdlLocation = "classpath:wsdl/EFMUserServiceSingle.svc.wsdl", |
Add operations guide and reference.
Note that the latest google-java-format is 1.22.0. Left it at 1.16.0 as the update would require minor formatting changes to many existing files, but something to keep in mind.
Rename DISABLE_QUARTZ_SCHEDULE_FOR_CODE_UPDATE to DISABLE_SCHEDULE_FOR_CODE_UPDATE. Treat immediate and daily Tyler EFM code update schedules as non-exclusive.
…fault. Wonder if we should auto re-formatting?
Noted that CourtPolicy cached in memory and would be need to updated if scaling out. Added link to Tyler.
Add section in the docs about the psql settings page in Supabase. This is useful for restoring a Postgres backup from the Docker postgres.
Enabled continuous deployment to efsp-staging from GitHub.
…eployment vs manual builds.
🤷 I think it has something to do with how wsdl2java works, I assume it's using Sets or something unsorted internally during code generation. It'd be so nice if that wasn't an issue, but eh.
That's not! That is another wsdl2java makes for you, and we have to manually revert. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Schema to 2024.3.
Originally, I was trying to fix this error
However, I got stuck trying to figure it out. Then, another Schema related error started happening in production (
unexpected element (uri:"urn:tyler:ecf:extensions:Common", local:"ServiceConsentEmail")), which forced me to make more progress here.Eventually realized that the GetStatus error has to be on Tyler's side; when we call them with the
Statusattribute inUserType, we get an error (even though it's in the Schema they give us), but when we manually remove it from the client-side schema and Java code, theUserTypethey return has aStatusin it, which the client errors on! I've reached out to them for them to fix the issue, but it seems to be a stage only thing. I turned off that check in the integration test, and every thing else works fine.Going to merge this.