Skip to content
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

Default url #11

Merged
merged 4 commits into from
Feb 19, 2019
Merged

Default url #11

merged 4 commits into from
Feb 19, 2019

Conversation

malcomm
Copy link
Contributor

@malcomm malcomm commented Feb 19, 2019

Fix for #8. Fixing server_address and server.base so that the URLs will work out of the box with Jetty.

malcomm and others added 3 commits February 19, 2019 09:11
Fix for hapifhir#8. Default URLs should work now out of the box for jetty.
Fix for hapifhir#8. Default URLs will now work out of the box with Jetty.
@seanmcilvenna
Copy link
Collaborator

Looking at the failed travis CI build, it just dawned on me why we use the default values that we do... The application is intended to be able to be run on its own using Eclipse/IntelliJ as an "Application", with one of ExampleServerDstu3IT, ExampleServerDstu2IT, ExampleServerR4IT as the main class. In order to make this work with the tests, you would need to modify these test classes to run on the 8080 port, and the /hapi-fhir-jpaserver base url.

hapifhir#8. use the original URLs, but add some commented out configs to help with Jetty
@malcomm
Copy link
Contributor Author

malcomm commented Feb 19, 2019

@seanmcilvenna - I just committed a change that keeps the old URLs, but just puts in a commented out hint version for Jetty.

@seanmcilvenna seanmcilvenna merged commit 9beaedb into hapifhir:master Feb 19, 2019
@jamesagnew
Copy link
Contributor

Chiming in a bit late... :)

I wonder if it would make sense for us to modify the tests to also put the app at the same context root that Jetty does? This would mean one less thing to change in the file...

@seanmcilvenna
Copy link
Collaborator

I would agree with that change. Not sure I know enough about how the tests are built to make the change myself, though. Can investigate (at some point - no guarantee when, though).

@jamesagnew
Copy link
Contributor

I'll have a look at some point.. I guess the other issue is that even with that change, we'd still have to account for the port being different.

Something to figure out in the future.. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants