Alex Little

Went to the final Unfold meeting in Berlin earlier this week, the most useful day for me was the Tuesday when we were discussing the original LD architecture diagram that had been developed at the Valkenburg meeting a couple of years ago, and we were reviewing to see how relevant it still was (if at all). We did come up with a new architecture, which is pretty much based on the adapter model we have used for the CCSI in the recent toolkit project. So that’s pretty good from my point of view – as it’s the architecure I had started to build for Sled and the external services.

Unfortunately spent the last couple of days tearing my hear out over this web services stuff still, and keep going round in circles. At the end of last week I had decided not to continue trying to get Sled connecting to CCSI using web services when they are on the same machine. Instead if they are on the same machine, the java API shoul dbe used, and web services used when they are on remote machines. I guess this is the way you would usually have it set up, but it would have been nice if I could get it working.

I’ve now managed to get another problem occuring though when compiling the CCSI module, when I move the ccsi.war file over to the server and try calling it from a little test java app on my desktop machine, I get the error that there is no class definition for the class: org.coppercore.ccsi.DispatcherSoapBindingImpl. This is a bit odd because it was previously workig and I’ve not changed anything in the build.xml that should affect this. In the online forums etc it just says to ensure the classes are on the classpath – but I need to work out why this has just started to happen. The build file is creating the .java files for the classes, but they are not being compiled and copied into the final ccsi.war.

Will plug on with this – but it’s really starting to do my head in – just as I think I’m getting close to finishing off, something else comes up that seems to take a few days to resolve