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

Resource Chain not working as documented #286

Closed
lcamilo15 opened this Issue Jan 19, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@lcamilo15

lcamilo15 commented Jan 19, 2016

I'm trying to follow your Dynamic Chains example and I'm noticing it is not updating the Overlay/GUI documentation as it does for Encounter->Patient chain. Can you please point me in the right direction so that I can implement this right or help you fixing the issue inside of the project?

This is what we are trying to accomplish
Production encounter chain

This is how it is being rendered on our local environment
Localhost encounter chain

@Search()
    public List<Encounter> findEncounter(
        @RequiredParam(name = Encounter.SP_PATIENT,
            chainWhitelist = {Patient.SP_FAMILY, Patient.SP_GENDER})
        ReferenceParam theSubject)
{
...
 }

Additional Notes : We are using version 1.3

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Jan 21, 2016

Hi @lcamilo15 - The issue here is definitely that the chains are not being added to the automatically generated conformance statement for your server. I'd say this is an issue with HAPI and not an issue with your code.

The JPA server does add these chains, which is why this works the way you're expecting on our public server. You can see this by looking at the conformance statement for our public server. (search for "chain")

The conformance statement is generated by ServerConformanceProvider.

The JPA module extends that class and adds a few things. One of those things is that chains.

I thing these should be added by ServerConformanceProvider.

Are you interested in taking a crack at this bug? If so, awesome! If not, I'll have a look soon.

jamesagnew added a commit that referenced this issue Jan 21, 2016

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Jan 28, 2016

Ok, I actually found some time to work on this and I'm committing a fix now.

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