I’ve sorted the problem I had with specifying truststores in Axis2. I don’t have to use the crude method of specifying the location and password in System properties. Instead, I’ve combined the Guanxi SSL Layer probing functionality with a custom ProtocolSocketFactory that makes use of the truststore that the Guanxi SSL probing populates. (more…)
I have a problem. You can mount various Fedora repositories in the Sakai resource tool but to upload resources you need to use the API-M endpoint, which is normally protected via SSL. That means the client code on the Sakai side needs to verify incoming Fedora server certificates. (more…)
Having sorted out web service client implementations for Fedora, I’ve been abstracting it all out into a set of interfaces and implementations which I’ve termed the Web Services Abstraction Layer (WSAL). This lets me keep the interface between Sakai and Fedora fairly high level, working with metadata and object Objects rather than raw XML. It’s also a possible larger framework for integrating content repositories into Sakai. When I’ve got it all tested and working I’ll commit to our svn and let folk know how to use it.
I’ve now got an Ingest unit test working for the Fedora API-M web services. It was all going swimmingly until I started using a rather large PDF file to ingest, which caused the error:
java.lang.OutOfMemoryError: Java heap space (more…)
I’ve spent the day faffing around with the Fedora API-M web service interface and have managed to ingest a dummy object. The next step is to sort the namespace for the DC metadata as it barfs when I include this. A step in the right direction though.