Forgive me. I'm bringing up the subject of modularization in Lift under a new heading, but the last discussion was, sadly, all over the map and only served to emphasize the problem. So let me narrow it down, a bit, here, and ask:
How is it possible to create two different snippet implementations, or two different models, one JPA and one not, or one using the mapper framework and another the record, and replace one with the other without having to recompile the application? We're not talking here about interface design - you still have to deal with boot. And traits, as has been suggested by others...well, you'd better not expose them to the world outside your implementation, as any changes would require recompilation. In other words, you can't really use traits for your interface. To use Lift in the enterprise does require that teams be able to work independently, doesn't it. Glenn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
