01 December, 2006

Linux, Reactor Framework and Case Sensitivity

I finally got my linux box up and running with all my server software as it is required. Copied everything from my windows partition to my linux partition and then made an attempt (though futile) to run my development version of our corporate portal. Now comes a major problem that isn't present for Windows, but is present for Linux, case sensitivity.

The reactor framework has saved me bucketloads of time. Most applications these days I use the MG2 framework, and that requires Coldspring and Reactor, both excellent frameworks which save heaps of time in development. However, Reactor on this specific occasion is causing me grief. It generate all the data-dictionary objects correctly so far except for one table I have called Personnel.

I use MSSQL Server 2000 for my databases, and I can connect and query all my tables and views properly. For some reason though, when Reactor generates the data-objects for my Personnel table, it generates them with a lowercase 'p' instead of the required uppercase 'P'. This shouldn't be a problem except when it checks for the existence of the file, it looks for the uppercase version instead of the lowercase version that it created.

I'm now going through the reactor files to try and find the problem spot, this day could get long...

Edit: Found the problem to be with my Reactor.xml configuration file. In windows I could use personnel in my object relation models and windows wouldn't care. But the Reactor.xml config file creates the objects exactly how they are mentioned in this file. So when it went to access the actual file using the table name, it gave a case sensitivity error in Linux. Once I corrected my Reactor.xml file and re-initialized the project, it worked fine.

Lesson learned: don't let a linux newbie near your development environment. ;)

No comments: