Hello Matthias,

Did you see the email I just sent (probably at the same time as you sent
yours :-) ) ?

It's indeed a bpm4struts issue, you will need the name="form" attribute on
all input fields, we're fixing it today

(the problem is in the JSPs, they are not correctly rendered, all field are
missing that silly little attribute)


> > 2. in the controller implementation class you don't need to cast the
> forms,
> > you can use the interface directly .. if a field would be missing it
> means
> > you forgot to model it as an argument to your controller operation
> >
> If I change the lines:
> ((ArtistManagementSearchArtistsForm)form).setAllArtists(allArtistsDummyLis
> t3);
> and
> ((EditArtistStoreDataForm)form).setAllArtists(allArtistsDummyList2);
> 
> in searchArtists/storeArtist to not using casts, I get following
> compilation errors:
> 
>     [javac] Compiling 26 source files to
> /data/work/artdb/web/target/classes
> /data/work/artdb/web/src/java/com/mksoft/artdb/admin/artistmgmt/ArtistMgmt
> ControllerImpl.java:55: cannot resolve symbol
> symbol  : method setAllArtists (java.util.Collection)
> location: interface com.mksoft.artdb.admin.artistmgmt.SearchArtistsForm
>       form.setAllArtists(allArtistsDummyList3);
>           ^
> /data/work/artdb/web/src/java/com/mksoft/artdb/admin/artistmgmt/ArtistMgmt
> ControllerImpl.java:71: cannot resolve symbol
> symbol  : method setAllArtists (java.util.Collection)
> location: interface com.mksoft.artdb.admin.artistmgmt.StoreArtistForm
>       form.setAllArtists(allArtistsDummyList2);
> 
> 
> ... that means I've got some modelling error ... but which?
>


[WZ> ] the 'searchArtists' controller operation is missing the 'allArtists'
argument, that's it (all arguments will be exposed as accessors through the
form interface - taking into account backing lists etc...)

 
> 
> > 3. from 'retrieve artist data' to 'edit artist' you can omit the
> parameters
> > on the transition, it is better UML that's true, but bpm4struts will
> > generate jsp code that will display these parameter both as page
> variables
> > as well as input form fields
> >
> Oh - I thought I need them to model the incoming (initial) values.
> 
> OK - since I deleted them they are not shown as page variables anymore.
> I'm not shure if this is good or bad, since nothing changed as I
> described in answer 1 above.
> 

[WZ> ] what you did is fine, I also work in the same way

hth
-- Wouter



-------------------------------------------------------
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