Hi all, I'm developing a web application based on Turbine 2.1. So far, everything works beautifully. Now I've come to a point where I'm stuck:
- I need to extend the Turbine User. For this, I followed the extend-turbine-user-howto. Works. - In at least one table I need to use Java objects instead of primitives to distinguish between 0 and null. The documentation on Torque shows that there is a column attribute javaType which should do just that. However, it doesn't do anything in Turbine 2.1. FYI: I do not need this feature for the user. I figured that the documentation actually reflects Turbine 2.2b1. So I switched and tested javaType="object" with the sample application. Works. I switched my application to Turbine 2.2b1 and this is where the trouble starts. The extended user does not compile anymore because the classes generated by Torque already use the decoupled version while the Turbine user and related classes do not. So I went ahead, got the Turbine 2.2 sources and did all the decoupling myself upto a point where I got everything to compile again (including my own project). The only caveat is that is does not work any more. I get an UnknownEntityException when trying to access the application. BaseSecurityService is unable to instatiate my extended user class. When dumping all the packages it knows about to the log (ie. Package.getPackages()) my package is not there so Turbine cannot find my user class. Where do I go from here? Switch to Turbine 3? Is it "stable enough"? Would it mean a major rewrite of my application? Or can I backport the userType="object" attribute to Turbine 2.1? Or did I simply miss something? ;-) Thanks, -Maik -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
