Case of class names
Had an unusal problem this afternoon with J2EE Ref Impl 1.2.1. Some students in class did not use the standard for names. They created a remote interface with the following name "bankteller", the home was "banktellerHome", and the bean was "banktellerBean".
When we tried to deploy we kept getting compilation errors at deploy time. The verifier did not return any errors.
We went and changed names to "BankTeller","BankTellerHome", and "BankTellerBean".
Then when we recreated the applications and redeployed it worked fine. Why does the case of the class names matter? This is the first time I have ever seen this.
Just some thoughts would be appreciated.
Thanks
PossumKing
It is not required that class names are in MixedCase LikeThis. However, the file name of the source file must exactly match the class name. So if you call your class bankteller, it must be in a file called bankteller.java and not BankTeller.java or Bankteller.java.
This is even true for operating systems that have case-insensitive filenames like Windows.
Jesper
The file names and class names did match when we had them in lowercase. We were able to compile the java source without any problems. We modified the class names and file names to follow the standard of distinguishing words with uppercase and then it worked. With the names in lowercase it kept giving us a compilation error in the deployment tool.
I wonder if internally the deployment tool is building the stubs with upper case regardless of the case of the remote, home, and bean objects?
