[Andromdaplugins-cvs] CVS update: cartridges/andromda-ejb3/src/main/resources/META-INF/andromda profile.xml

[Vance K. <va...@us...>]

  User: vancek  
  Date: 06/05/12 19:57:17

  Modified:    andromda-ejb3/src/main/resources/META-INF/andromda
                        profile.xml
  Log:
  expanded documentation
  
  Revision  Changes    Path
  1.28      +29 -5     cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/profile.xml
  
  Index: profile.xml
  ===================================================================
  RCS file: /cvsroot/andromdaplugins/cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/profile.xml,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -w -r1.27 -r1.28
  --- profile.xml	17 Apr 2006 01:59:13 -0000	1.27
  +++ profile.xml	13 May 2006 02:57:17 -0000	1.28
  @@ -2,9 +2,33 @@
   
   <profile>
   	<documentation>
  -		Entity query operations (i.e. finders) can be denoted by setting
  -		the query flag on the modeled operation to true (they do not
  -		require any stereotypes).
  +        <p>
  +             Dependencies can be used between Services and Entities, they
  +             won't need any stereotype assigned to them. These dependencies
  +             are used to produce entity references (from an entity or service)
  +             within the base classes (i.e. DaoBase and ServiceBase),
  +             or to produce service references (from another service)
  +             within the ServiceBase classes.
  +         </p>
  +         <p>
  +             Entity business operations can be set to <code>classifier</code> scope
  +             instead of the usual <code>instance</code> scope. By doing so they
  +             will be generated into the corresponding DAO for that entity instead
  +             of the entity implementation class.
  +         </p>
  +         <p>
  +             Entity query operations (i.e. finders) can be denoted by setting the
  +             query flag on the modeled operation to true
  +             (they do not require any stereotypes) and setting it's scope to
  +             <code>classifier</code>.
  +         </p>
  +         <p>
  +             Actors represent roles within your model.  To designate that a role
  +             has access to a given service you must draw a dependency from an Actor
  +             to the <a href="Service"><![CDATA[<<Service>>]]></a>.  To designate the
  +             role has access to to a given operation, you must draw a dependency from
  +             an Actor to the operation.
  +         </p>
   	</documentation>
   	<elements>
   		<elementGroup name="Stereotypes">