NT to Solaris Porting Problems

Creation Date: June 22, 1998
Keywords: Solaris, NT, WebObjects, OPENSTEP

Q: I have an application that compiles and runs correctly on Windows NT.  I've ported it to Solaris and it compiles correctly, but when I run it I get the error message:

Cannot find class or component named <MyCustomScriptedComponent> in runtime or in a loadable bundle.

Why does this error occur on one platform but not the other?

A: Carefully check the capitalization of your component when it is defined and called.  This problem can occur when porting a WebObjects or OPENSTEP application from Solaris to Windows NT as a side effect of the fact that Solaris is case sensitive, while Windows NT is not.  Thus, if a component called "MySuperGreatObject" is called in your application as "MySupergreatObject", it will compile and run correctly on Windows NT.  On Solaris, however, you will get a run-time error.  Since Mach and HP-UX are also case-sensitive, improper capitalization may cause run-time or link-time errors on those platforms as well.�