Error rendering page view for clinicianfacing/patient: Make sure you have defined your pages in the right directory under omod/webapp/fragments/fields thats openmrs by default ,
.
However am seeing clinicianfacing/patient directory , guess this is where its messing up and hence this error Cannot find controller or view for fragment: miniPatientAppointments., can you provide your json file definitions
The above repo was built locally and then installed on top of the openmrs platform (2.4.0-SNAPSHOT). The project directory does not have a “omod” sub-directory. Below is the image of the project directory tree:
When the Tomcat server is stopped and a new Refapp server is set up and run using the SDK, everything works well and the new patient registration is successful.
@mozzy You are right about this. When I look at the ‘Manage Modules’ page, I can see that the “Appointment Module” has trouble starting (all other modules are running properly):
Please let me know what can be done about this. Thanks.
This is the underlying cause: cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : org.openmrs.User$HibernateProxy$GBfLB5Vx
Deleting from the serialized_object will hide it for the time being but it will come back after a little while. @nischith can you create a ticket for it? Secondly, is there any reason why you are using a snapshot version of the platform which was released?
The Refapp (2.12.0-SNAPSHOT) I had first downloaded had a dependency on the platform version 2.3.2 going by the Refapp’s pom.xml definitions. So, I installed platform (2.3.2) first and tried to install the latest Refapp (2.12.0-SNAPSHOT) on top of it. This installation however did not succeed and I knew there was some compatibility issue between these two.
After a few days later (on 07/12/2020), I found a new commit to the RefApp GitHub repo → “Switching to platform 2.4.0-SNAPSHOT”. When I installed this new code, the installation was successful. So, I continue to use Refapp (2.12.0-SNAPSHOT) of the above commit along with platform 2.4.0-SNAPSHOT.
Please let me know if there is a better approach. Thanks.
My intention is to have an installation which is best suitable for ‘development’ (for further customisation) and bug fixing if necessary. So, I have been more focusing on starting with the source code, building it and then deploying it. Both with the platform and the Refapp the intention is to start with the source code to facilitate this.
I did try this approach yesterday and it worked very well. I could set up a Refapp server in no time and run it. But when I set up a server using the SDK, I am not sure if I get access to the source code. Is it possible to make changes to the platform/ refapp source code (for bug fixing of the platform code/ customisations) when the server has been set up using the SDK?
I am not talking about building newer modules but about having access to the source code of platform and refapp itself. If the server has been set up using the SDK does one get access to the source code of platform/ refapp itself?