Alex Little

Progress on the LAMS tool is still being a bit grindingly slow but the reason for this is that the laptop I’m trying to run LAMS on isn’t really quite up to the job – it’s been taking about 6-8 mins to start up JBoss, and almost every change I make to the code requires a complete restart. Unfortunately I can’t just restart the tool context, because the LAMS core may have made references to the objects in my tool, so redeploying the tool corrupts all the references

At least I am beginning to understand more of how it all works though – so that’s a good start!!

Spent a little time yesterday looking at the Enterprise SDK and seeing how to get that working. My first step was to try running the very simple example (at http://www.cetis.ac.uk/content2/20040624131946) and I did get this running ok with JRun, I didn’t get it working with JBoss. Altough I had it running on JRun, in that I got the message on screen that there was an axis service available, when I actually tried to view the wsdl (as I’m still unclear as to exactly what the input parameters and outputs are for the service methods), I get an error.

With JBoss, I didn’t actually get an error (or in the logs), but just a blank page in the browser – so it was as if the the page/service was found, but no content generated. I’m not sure if this is to do with the version of Axis that I have running on my JBoss, or something like that?

I also thought I’d have a go at downloading and compiling the demo application on the cetis-es sourceforge site, but I didn’t get that finished, so I’ll give that another go today and I’ve been looking at the BEWT site, as they appear to have it all working.

 I got a new desktop PC a week or so ago and so have been busy getting that set up. On my previous machine I was getting a port conflict whenever I tried to run Jboss (on port 1098) – at the time this didn’t matter too much as I was doing the development work on the desktop, then just using an old laptop as the development Jboss server. I’ve now got rid of the old laptop so I really need to get the problem fixed. After a couple of searches on the internet, found out that the problem was a port conflict between Jboss and Microsoft Active Sync Connection (which runs as the program wcescomm.exe) – so what I need to do now, whenever I wasn’t to be able to run Jboss is to turn off the active sync, which is a bit of a pain !