Re: [Andromda-user] Flexibility of bpm2struts

[Andrzej Dmoch]

Hi,   I thought it does it magically :( (no in fact I didn't think so :)).   Thanks for the hints. But does it mean, I have to know the number of items in the collection in advance if I want to have radiobuttons? I mean in the line: @andromda.struts.view.field.type=radio X  X is a fixed number. If it is true I don't like this solution. I would like to have as many radiobuttons as elements in the collection and to have the names of the radios equal to .toString() method of the elements. Then I think, I should modify the general template for rendering the collections(?).   The number field in the form is just a number of items of the chosen product to add to the basket (so don't bother, that's in the standard).   But generally, it looks like a good subject for the change request. I mean, I would like to pass a set of objects (values) to the page and then render them as I would like. Maybe using XSLT Xtags? (threating the input as XML Beans). I think that would add a lot to bmp4struts. And modifying the cartrigde should not be needed to achieve this goal (just some links to external XSLT or Velocity stylesheets).   But it's just the small flexibility hole in a very, very promising piece of software. I especially like the internal part of the bmp4struts. Could you give me some links to theoretical papers providing the backgroud for this solution? (if there are any). I'm generally really impressed by AndroMDA team's work.   Regards,   Andrzej ----- Original Message ----- From: Wouter Zoons To: 'Andrzej Dmoch' ; [EMAIL PROTECTED] Sent: Tuesday, August 24, 2004 5:00 PM Subject: RE: [Andromda-user] Flexibility of bpm2struts Hi,   First of all, just for the record, AndroMDA does not magically generate applications. For customizations you�ll sometimes need to go into the templates, or the generated code.   Secondly, I am assuming you mean bpm4struts, not bpm2struts J   (1) You can remove the line of code in the generated JSP that prints the �badly formatted text� .. alternatively you can mark the collection to be displayed in a table (that way you�ll get something like this: http://team.andromda.org:8080/OnlineStore/PurchaseItems/EnterNameAndPasswordProceed.do (table at the bottom of the page)   But if you want a configurable view you need to update the JSP or the templates     (2) if you want radiobuttons you need to do this   keep the incoming collection, but remove the line that prints it on the page model the parameter that will send the selected option, for example, have an action �myAction� with the �myParameter� parameter (this action comes out of the page in which you want to display the options) so now you have modeled you want to send a parameter to the server (nothing special) add a tagged value to this parameter to indicate it is selected from a set of options, you can do this like this @andromda.struts.view.field.type=radio X replace X with the number of options to choose from: �radio 5� would render 5 options with default names alternatively you can do this: @andromda.struts.view.field.type=radio firstOption,secondOption,thirdOption this will render te names you specify now you have modeled the parameter is to be selected from a set of options and only one can be selected at a time     what is a number field in the form ?   hth   -- Wouter