Hi, I'm building a portal project. It provides a login page and some links to some static content.
I'll be reusing quite a bit of the DAO and JPA gubbins from an existing base application, just giving it a different and cut down front end. Is there any way of the portal web app to bind up with the Tapestry services already running in the base application so I can reuse the DAO and other backend goodies that's already registered? A bit like a shared registry? At the moment it looks like I really need to move over to a JEE container just to implement a few shared services. That's quite a big step and I'm averse to JEE and all tat comes with it. Or perhaps the portal should just be a subdirectory in the base application, but then it really needs to appear with its own seperate context path as it's served using a different hostname? regards, John
