--- Wouter Zoons <[EMAIL PROTECTED]> wrote:

> Hello Fred, Matthias and Chad,
> 
>  
> 
> Fred: I thoroughly analyzed your model and
> everything seems to be in perfect
> order . I deployed & ran the application and
> everything was working as
> expected, except for the issue you are talking about
> 
>  
> 
> It's a bpm4struts issue .. I will have to talk this
> one over with Chad
> because it's a change we have both been working on,
> in fact what needs to
> happen is that all the input fields in the JSPs need
> to have a name="form"
> attribute
> 
>  
> 
> For example NOT:
> 
>  
> 
>                            <html:text
> property="nomPrenom"
> onmouseover="hints.show('nomPrenom')"
> onmouseout="hints.hide()"
> readonly="readonly"/>
> 
>  
> 
> BUT:
> 
>  
> 
>                            <html:text name="form"
> property="nomPrenom"
> onmouseover="hints.show('nomPrenom')"
> onmouseout="hints.hide()"
> readonly="readonly"/>
> 
>  
> 
>  
> 
> The 'form' object is put in request scope and holds
> the most recent form
> used
> 
>  
> 
> I'm very sorry for the inconvenience, I was under
> the impression this was
> working fine,.. we are going to fix this ASAP!!
> 
>  
> 
> Matthias: this is the same problem you are
> experiencing, but I was not able
> to deploy and run your app so I could not see the
> problem was in the JSPs
> 
>  
> 
> Chad: I am about to adding all these name="form"
> attributes back, I keep
> forgetting why you deleted them in the first place,
> was it because of
> exception handling or something ? Can you please let
> me know asap so I can
> fix this .. I will be back online in 3-4 hours after
> I finished my bike-trip

Sorry, I haven't been following this thread too
closely, what is the issue with the attribute
name="form" missing?  Its been working fine for me. 
The reason I originally removed them is because the
"form" bean was lost from the request scope when an
exception or validation error occured and therefore we
got the "no bean named "form" in any scope error"
(this was before we made the use case action the input
for the struts-config.xml.  So anyway if you add them
back I think it should be ok now.  

> 
> 
>  
> 
>  
> 
> To be conintued, we're on it :-)
> 
>  
> 
> -- Wouter
> 
>  
> 
>  
> 
>   _____  
> 
> From: Frederic Chapuis
> [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, October 31, 2004 11:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Andromda-user] Validation Error: One
> Use-Case per package...
> 
>  
> 
> Sure, here it is.
> 
> I archived the whole project structure so you do not
> have to re write
> implementation files.
> 
> Like this it builds and deployes fine on JBoss
> 3.2.5.
> 
> The model is a MagicDraw 8 version.
> 
>  
> 
> Many thanks
> 
> Fred
> 
> ----- Original Message ----- 
> 
> From: Wouter <mailto:[EMAIL PROTECTED]> 
> Zoons 
> 
> To: 'Frederic <mailto:[EMAIL PROTECTED]> 
> Chapuis' 
> 
> Cc: [EMAIL PROTECTED] 
> 
> Sent: Saturday, October 30, 2004 11:16 PM
> 
> Subject: RE: [Andromda-user] Validation Error: One
> Use-Case per package...
> 
>  
> 
>  
> 
> Can you send me you your model ?
> 
>  
> 
> 
>   _____  
> 
> 
> From: Frederic Chapuis
> [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, October 30, 2004 9:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Andromda-user] Validation Error: One
> Use-Case per package...
> 
>  
> 
> Yes that's what I did (according to posts on the
> list) with some other data
> types (Boolean, Integer, Date...for testing).
> 
> But fields remain empty.
> 
>  
> 
> 



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to