Containerish class

[observer]

Hi,
Is there a way to model containerish clasess with argouml for use with archgenxml?

Thanks in advance

[Jens W. klein-2]

Am Mon, 13 Apr 2009 07:53:11 -0700 schrieb observer:

> Hi,
> Is there a way to model containerish clasess with argouml for use with
> archgenxml?

a) give the class the stereotype <<folder>>
or
b) let the class contain aggregates or composites using the line with the
romb (empty or filled).

hth
--
Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Archetypes-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/archetypes-users

[observer]

Hi.
Thanks for the answer
I'm not sure if i was clear, following this steps I got a folderish class, but I wan't a containerish class as in the richdocument tutorial, a class that contains other classes but looks like a document not like a folder.
Can I do this in argo or should I do it by hand.

Jens W. klein-2 wrote:

Am Mon, 13 Apr 2009 07:53:11 -0700 schrieb observer:

> Hi,
> Is there a way to model containerish clasess with argouml for use with
> archgenxml?

a) give the class the stereotype <<folder>>
or
b) let the class contain aggregates or composites using the line with the
romb (empty or filled).

hth
--
Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Archetypes-users mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/archetypes-users

[Derek Broughton-3]

observer wrote:

> I'm not sure if i was clear, following this steps I got a folderish class,
> but I wan't a containerish class as in the richdocument tutorial, a class
> that contains other classes but looks like a document not like a folder.
> Can I do this in argo or should I do it by hand.

Yes you can - but I found it awkward.  I'd be happy if Jens has a better
answer.  I have a class that may contain any other classes, but I want
Document-like behaviour.

So it has stereotypes <<atfolder>> and <atdocument>>, and I set the tagged
values "base_class = ATDocument" and "base_schema = ATDocumentSchema".  If
you don't explicitly need all the ATDocument fields, you might not
need "base_schema"
--
derek


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Archetypes-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/archetypes-users

[observer]

I followed your instructions and I've got a document page with a folder icon.
What I want to do is get a document to which I can add more pages and show them inside the containerish document as if they where one but each one with its own publishing workflow.
Is it possible?

[observer]

I want to do another question due to the lack of responses.
What can I do with containerish classes?
I read about it in the richdocument tutorial and I had some ideas related to what I'm doing with AT but I'm not really sure because I couldn't install richdocument as it needs a quick installer for which I haven't even found mention in the tutorials
Thanks

observer wrote:

I followed your instructions and I've got a document page with a folder icon.
What I want to do is get a document to which I can add more pages and show them inside the containerish document as if they where one but each one with its own publishing workflow.
Is it possible?