[EMAIL PROTECTED] grava:
>hmm,
>
>I'll have to think about this for a while ... to see exactly what it 
>requires from the cartridge
>could you give a real-life example or something to make sure I fully 
>understand the context in which one would use this ?
>
>from your email I was thinking about an online shop where one purchases 
>items and puts them in a basket, would this be such a case ?

Yes, the "basket ---- items" is a good example.

>if yes, than I have to think about it ... I am not yet convinced it is a 
>good idea to model business logic into the process flow ...
>someone else has an idea perhaps ?

It looks to me like designing the interface back-end, not the business
logic. Anyway I don't think it's very important for now... After the
version 3 we can talk about, again.

By the way, I'm not an UML expert, so I have a lot of doubts about the use
of the diagrams, and I will be very happy if you or somebody suggest
books, tutorials and examples about the use of the state/activity diagrams
(portugese, english or spanish, please).

Thanks,

Walter

>
>thanks for the feedback dude!
>Wouter.
>
>Walter Mour�o wrote:
>
>>Hi Woulter,
>>
>>Sorry, I thought "master detail" was a common expression. I'm talking
>>about situations where we have an object (master) and a grid of other
>>objects  (detail) being edited. Generally they have an aggregation
>linking
>>then. I think a common example is an "order" (master) with its "items"
>>(details) in the same form.
>>
>>Thanks,
>>
>>Walter
>>
>>[EMAIL PROTECTED] grava:
>>  
>>
>>>hello Walter,
>>>
>>>I don't know what you mean with master detail, but you will be able to 
>>>model individual input elements with their validation attributes when 
>>>the cartridge is released, this feature is new and is not supported by 
>>>the (current and never officially released) bpm4struts CVS version
>>>
>>>maybe you can explain in more details what you have in mind ?
>>>
>>>thanks
>>>Wouter.
>>>
>>>Walter Mour�o wrote:
>>>
>>>    
>>>
>>>>Hi folks,
>>>>
>>>>I was thinking about a UML way to represent the 'master detail'
>behavior
>>>>inside a form, and started designing a association between a the form
>>>>class ( <<FrontEndModel>> ) and a class representing the detail item.
>So
>>>>      
>>>>
>>>I
>>>    
>>>
>>>>have:
>>>>
>>>>FormClass --------- Grid -------- ItemClass
>>>>
>>>>where Grid is an one to many association between the FormClass and the
>>>>ItemClass.
>>>>
>>>>It looks good... but the bpm4struts cartridge does not understand that.
>>>>
>>>>First of all: is this a good way to represent the 'master detail'
>>>>      
>>>>
>>>behavior
>>>    
>>>
>>>>? if so my suggestion is the generation of the ItemClass and the grid
>>>>property inside the FormClass. 
>>>>
>>>>
>>>>Regards,
>>>>      
>>>>
>
>




---------------------------------------------------------------------------
Walter Itamar Mour�o - Diretor de Tecnologia e Projetos - Arcadian S/A
www.arcadian.com.br



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to