By the way, why orm classes need to be aware of the companion object? Could this dependency be eliminated somehow?
- Vesa On 2 marras, 22:02, Vesa <brut...@gmail.com> wrote: > I doubt I can find one, but it still feels awkward having to type the > name of the class so many times. Another option could be to use some > shared object to do this stuff, but I guess it wouldn't be as neat to > use it then. > > - Vesa > > On 2 marras, 18:33, David Pollak <feeder.of.the.be...@gmail.com> > wrote: > > > > > On Mon, Nov 2, 2009 at 8:14 AM, Vesa <brut...@gmail.com> wrote: > > > > It seems like boilerplate that every mapped class needs to define a > > > getSingleton method returning companion object. Can't there be any > > > default with this and is there any way to get rid of the manually > > > defined companion object if user isn't going to define any new methods > > > on it, while still having the default meta functionality? > > > I know of no mechanism in Scala to discover companion objects. If you find > > one (that's not simply Java Reflection), please let me know. > > > > - Vesa > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Surf the harmonics --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
