For remoting could have a sense to make DTO for the sake of Singe Responsibility Principle.
2008/11/26 James Carman <[EMAIL PROTECTED]>: > Not exactly. It might be okay for web projects like this, but if you need > to do any remoting, this won't work. Our domain entities have to be > serializable. > > On Wed, Nov 26, 2008 at 11:22 AM, Bruno Cesar Borges < > [EMAIL PROTECTED]> wrote: > >> Now that is a really good advice. :-) >> >> -----Mensagem original----- >> De: kan [mailto:[EMAIL PROTECTED] >> Enviada em: quarta-feira, 26 de novembro de 2008 14:19 >> Para: users@wicket.apache.org >> Assunto: Re: Wicket Session grows too big real fast >> >> >> I am not sure if it always applicable, but usually I do not do >> "implements Serializable" for domain objects (it works well with >> Hibernated POJOs). In this case the Wicket cannot serialize a >> component, and if it was a link to any such object - wicket just >> reports about it into log, so you can see right away which component >> has tried to "steal" a reference to an object (like in your situation >> with inner class). >> >> 2008/11/26 jhp <[EMAIL PROTECTED]>: >> > >> > Removing references pointing to previous pages solved a lot, very good >> point. >> > Also making sure that individual domain objects don't get stored to >> session >> > makes a difference. I have still a lot of code to go through to make >> sure >> > that all unnecessary references don't get stored to session, but making a >> > few changes in the most important pages makes already a big difference. >> > >> > I noticed that this is a problem that others have experienced too. I >> guess >> > it is pretty easy unintentionally stuff the session with domain objects >> ,and >> > if using modern day persistence framework, those domain objects can be >> quite >> > large if they have collections etc. >> > >> > I think there is a need for small document outlining the common pitfalls >> and >> > remedies for them. I haven't seen such. Wicket reference of course tells >> > about LoadableDetachableModel, but this thread has info that I haven't >> found >> > anywhere else. I might try compose such a document, if I just have the >> time >> > and energy in the near future. >> > >> > Thanks to Martijn, Johan and John for your responses! >> > >> > BR, >> > Jukka >> > >> > >> > >> > >> > Martijn Dashorst wrote: >> >> >> >> With Wicket 1.3 only one page should be stored in session. You should >> >> check if you don't keep references between pages -> that would result >> >> in 1+N pages (with N being the number of pages you reference in your >> >> page). >> >> >> >> Other than that: using LDM's and DataView/DataProvider instead of >> >> ListView will help considerably. >> >> >> >> Martijn >> >> >> > >> > -- >> > View this message in context: >> http://www.nabble.com/Wicket-Session-grows-too-big-real-fast-tp20697077p20702093.html >> > Sent from the Wicket - User mailing list archive at Nabble.com. >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> >> -- >> WBR, kan. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> *************************************************************************************************** >> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) >> destinatários(s) acima identificado(s), >> podendo conter informações e/ou documentos confidencias/privilegiados e seu >> sigilo é protegido por >> lei. Caso você tenha recebido por engano, por favor, informe o remetente e >> apague-a de seu sistema. >> Notificamos que é proibido por lei a sua retenção, disseminação, >> distribuição, cópia ou uso sem >> expressa autorização do remetente. Opiniões pessoais do remetente não >> refletem, necessariamente, >> o ponto de vista da CETIP, o qual é divulgado somente por pessoas >> autorizadas." >> >> >> "Warning: This message was sent for exclusive use of the addressees above >> identified, possibly >> containing information and or privileged/confidential documents whose >> content is protected by law. >> In case you have mistakenly received it, please notify the sender and >> delete it from your system. >> Be noticed that the law forbids the retention, dissemination, distribution, >> copy or use without >> express authorization from the sender. Personal opinions of the sender do >> not necessarily reflect >> CETIP's point of view, which is only divulged by authorized personnel." >> >> *************************************************************************************************** >> > -- WBR, kan.
