Thanks for the clarification. If I've understood
correctly, the best way to
go is to subclass PRStructure for my model classes so that the model objects
can be used directly by Pier, otherwise I'd end up having a duplicate Pier
structure mirroring my model objects. The disadvantage of this is that the
framework infects my classes; using Java terminology they are no longer
POJOs [1], or have I missed something?
PRStructure and subclasses is the model for the hierarchical structure
of Pier. If your model is anything beyond the simple hierarchal folder
and file structure of Pier, I wouldn't implement it as a subclass of
PRStructure.
For example, when you have the typical and highly interconnected
University, Student, Professor, Course, Exam kind of model; I would
implement all these classes separately from Pier. And then you have
different structure subclasses that delegate to your complex domain
model. So you'd probably had a
- a university structure that would delegate to one University
- a person structure, that would delegate to one Student or Professor
- a course structure, that would delegate to one Course and the
exams in that course
Does that make sense?
Another alternative is that you do not work with PRStructures at all,
for example if you don't need the URLs. Then you can simply create
your own model and your own plain Seaside app and embed it into Pier
at some place (or use it independently from Pier).
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch