The bfg "repoze.bfg.router.make_app", used by most application paster entry point functions, returns a Router object. This is just a fancy WSGI application. Call make_app from within Pylons to get a WSGI app, serve that WSGI app via some Pylons controller.
Other than that, with respect to application model-agnosticism, I don't really understand the pattern, nor what you're trying to achieve. But you can use full paths in configure.zcml (e.g. rather than ".model.foo", use "mypackage.model.foo"). - C On 8/28/09 12:59 PM, Iain Duncan wrote: > ( apologies if this is a duplicate, it doesn't seem to have made it to > me through the list so resending ) > > Hi folks, I have a bfg app that makes a crud controller, where objects > from the model package get attached through configure.zcml. This > achieves my purpose of having the application completely unaware of the > model. I want to use this app as a wsgi callable in another app ( a > pylons project ), but I'm stuck on a few things with my limited wsgi > knowledge: > > - I understand that run:app provides the paster entry point, but how > would I import my whole app into another python app? > - I want my model to be installable as a separate, framework agnostic, > sqlalchemy model, that only needs to import interfaces from the crud > apps interfaces module > - configure.zcml hooks things up right now with calls like: > > <utility > provides=".model.pet.IPet" > component=".model.pet.Pet" > name="pet" > /> > <adapter > factory=".model.pet.PetFields" > for=".model.pet.IPet .interfaces.IActionView > repoze.bfg.interfaces.IRequest" /> > > But I'm at a loss as to how I make this app know to look in a > configure.zcml file in the model package without touching the stuff in > the app itself? > > Thanks! > Iain > > > _______________________________________________ > Repoze-dev mailing list > Repoze-dev@lists.repoze.org > http://lists.repoze.org/listinfo/repoze-dev > _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
