RE: [Andromda-user] bpm4struts: form bean not instantiated?

[Wouter Zoons]

Title: Nachricht

I recommend never to model variables using capitalized names, stick to the Java convention when using bpm4struts .. the reason is that most templating engines such as Velocity use introspection and determine property values based on specific characteristics of your (form) beans.   When you deviate from the conventions you’re on your own .. you’ll experience weird effects when variables aren’t resolved as you would expect   I guess it could be made to work by auto-converting all names into the proper format but then the user might start wondering where his variables are, since he modeled them differently, It’s a trade-off I guess   Anyway, stick to the Java naming convention and you’ll be fine   -- Wouter   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr. Stefan Reisner Sent: Tuesday, March 08, 2005 9:59 PM To: [EMAIL PROTECTED]; andromda-user@lists.sourceforge.net Subject: AW: [Andromda-user] bpm4struts: form bean not instantiated?   Hi Wouter,   I am using 3.0M3. By the way, I tried 3.0-RC1 a few days ago. However, I couldn't find some of the bpm4struts stereotypes in the andromda profile, so I went back to 3.0M3. I would like to explore the areas of bpm4struts, hibernate and web services. What version do you recommend?   But meanwhile I found the cause of my problem: apparently the villain was the capital letter in my signal parameter name "Input1". I feel that this is a bug, but it is easy to work around it, since bpm4struts creates nice upper case form labels even if the parameter names are lower case.   And I cannot explain why it *looked* to me like the form reference was null. At least currently it is not null (and I hope it never was, because that would mean that struts was broken).   Best regards, Stefan -----Urspr�ngliche Nachricht----- Von: Wouter Zoons [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 7. M�rz 2005 21:50 An: 'Dr. Stefan Reisner'; andromda-user@lists.sourceforge.net Betreff: RE: [Andromda-user] bpm4struts: form bean not instantiated? Hi Stefan,   Which AndroMDA version are you using ? Did you switch off model validation ? AndroMDA typically stops and complains after code generation instead of generating a faulty application … Did you manually edit the jsp page ?   I would expect the form *never* to be null   -- Wouter