It's not horrible for me, but there are two issues: 1) I miss out on the autobuilding that Tapestry can do, and have to pass around parameters to initialize my User object whenever I need to create one (such as services, etc.).
2) I want to avoid using new for my own classes to avoid classloader issues inside Tapestry. Cheers, Levi Sergey Didenko wrote: > > Is it so bad to create new session user using explicit "new"? > > Regards, Sergey. > > -- View this message in context: http://n2.nabble.com/-T5.1--Avoiding-%22new%22-tp3346190p3350456.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
