Hi all, There's been discussion on this list about what should be done to gain wider userbase and more buzz to Tapestry community.
One thing would be somekind of desing guide or best practices. This might be on the way with newcoming documentation, but here's few things I was thinking when I was (I still am) learning Tapestry: - How to integrate with EJB's. Is it ok to have components talking to middleware or should I have more only few 'middleware-aware' Tapestry components. - How to take care of workflow. What should listener do and what it shouldn't do. - What are typically Engines reponsibilites? - Persistent page properties or Visit? - How does Tapestry match up with Security. JAAS? JBossSX? Another issue. I was thinking today that with OGNL Tapestry is going to be very slick with proper objectmodel. This brings us to O/R. This is slight offtopic, but since I know people reading this list has good taste in software, I'd like to hear people's experiences about different solutions to O/R-mapping or middleware in general and possibly how they fit with Tapestry. I'm personally pretty much done with Entity Beans. Hibernate? Object bridge? And so forth. I'm aware that Howard has Sabertooth, but I got the expression that it's more or less on the hold at the moment. This stuff could go to design guide also.. I'm willing to contribute in the limits of my skills and available resources (time). Thanks for you time, -- /ekimmo ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
