I have to connect to a third-party database which has column names containing spaces.  
Even when I use the javaName attribute in the schema file to specify a sensible name 
for the field, the transformation is only performed on the getter and setter methods, 
not the underlying member variables, so torque generates class files with variable 
names that contain spaces.

Is there any workaround to this?  I would have thought that the 
defaultJavaNamingMethod="javaname" setting should get rid of spaces automatically, but 
the fact that setting javaname explicitly doesn't work is definitely a bug.

Any ideas on how to get around it until it's fixed?

Reply via email to