I'd create a Maven project with the models in it. You can use the resulting JAR file with other projects.
On Tue, Jun 2, 2009 at 9:44 AM, Joe Wass <j...@folktunefinder.com> wrote: > > Hi everyone, > I have three sites that hang off a single database: One central site > to edit information and two browse-only sites which aggregate the > information. Previously I have been doing this by exposing a simple > web service on the central site and having the other two sites consume > and transform that without knowing about the database. The site isn't > massively complex. I'm turning this into Lift (from PHP). > > They are giving different views of different subsets of the data and > shoudl be completely separate. The reason for the separation is ... > marketing. > > So I was thinking of the two view-only sites being complete lift sites > that talk to the database. The only thing in common would be the > models. > > Should I > 1 - copy and paste model source code so they compile into different > places? > 2 - symlink the model source directories so they compile as #1 > 3 - somehow add references to the central compiled model objects (add > a classpath?) > 4 - something else? > > Apologies, I've spent too much time in .NET land and I've forgotten > some Java vocab... > > Joe > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---