Bpm4Struts Cartridge

Please add defaultDateTimeFormat

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 3.1M1
  • Fix Version/s: 3.1-RC1
  • Component/s: CRUD
  • Description:
    Hide
    In my model some Entity attributes require a date format others require a date-time format. The Spring cartridge allows only one default format - defaultDateFormat. What I need in addition is a defaultDateTimeFormat. Also since both type of attributes are of type Date we need some way to distinguish beetween Date and DateTime. Now I know there is a DateTime UML type in the AndroMDA profile, but it appears that this type has been mapped to java.sql.Timestamp. If I use this type then I get a compilation error when using managable entities. So the UML to Java mappings do need some more thought.
    Show
    In my model some Entity attributes require a date format others require a date-time format. The Spring cartridge allows only one default format - defaultDateFormat. What I need in addition is a defaultDateTimeFormat. Also since both type of attributes are of type Date we need some way to distinguish beetween Date and DateTime. Now I know there is a DateTime UML type in the AndroMDA profile, but it appears that this type has been mapped to java.sql.Timestamp. If I use this type then I get a compilation error when using managable entities. So the UML to Java mappings do need some more thought.

Activity

Hide
Wouter Zoons added a comment - 13/Aug/05 8:47 PM
use the @andromda.struts.view.field.format tagged value as documented here: http://galaxy.andromda.org/docs/andromda-bpm4struts-cartridge/profile.html#@andromda_struts_view_field_format
Show
Wouter Zoons added a comment - 13/Aug/05 8:47 PM use the @andromda.struts.view.field.format tagged value as documented here: http://galaxy.andromda.org/docs/andromda-bpm4struts-cartridge/profile.html#@andromda_struts_view_field_format

People

Dates

  • Created:
    13/Aug/05 9:45 AM
    Updated:
    13/Aug/05 8:47 PM
    Resolved:
    13/Aug/05 8:47 PM