Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
DTOInForm
StrutsResumeSupport




JSPWiki v2.2.33

[RSS]


Hide Menu

POJOsToForms


Difference between version 23 and version 12:

At line 3 changed 1 line.
__Send your POJOs to the UI rather than converting them to ActionForms first.__
__Send your [POJO]s to the UI rather than converting them to ActionForms first.__
At line 15 added 6 lines.
''Are you saying that you would populate the form manually in the view?'' ~ [mojavelinux]
I suggest looking at Struts' __Nested__ taglib. It does set properties if complex DTO objects
and does not require (semi)manual conversion between strings and actual data types.
With little wrapper to BeanUtilities, which registers a Date handler with desired formatting pattern, it allows correct handling of dates.
At line 16 changed 1 line.
* [ValueObjectInForm]
* [DTOInForm]
* [Nested Extension|http://keyboardmonkey.com/next/index.jsp]
At line 23 changed 8 lines.
For example a form field called "pet/name" will call getPet() - your existing model POJO - and then setName() on it. Your action then just needs to store the updated POJO. Very neat.
~ mike cannon-brookes
----
Matt, I have been actually meaning to ask you about this. I am trying to get a handle on how you are handling information passed down to the view. At this point in the game I am just passing my value object (are these supposed to be called DTOs now?) into my view. However, this brings me back to my first question to you. Consider the case where I want to display full name for a user. I would create a method getFullName() which would do a few tests to determine if the user has a first/middle/last name and then concat them together and split them out. I think, following your model, you would recommend putting this method in the UserForm object, but that would mean that I would have to transfer data from my user object into my UserForm object for use in the view. But then, would I still be able to get to the CompanyForm from the UserForm by using getCompany() in the UserForm? (nested forms). I am just trying to develop a standard here that I can use and I am floating around a bit.
~ [mojavelinux]
For example a form field called

Back to POJOsToForms, or to the Page History.