Portal - Idea between Copletinstance and CopletData

[Frank Taffelt <fr...@interface-business.de>]

Hi,

after playing arround with the new Portal-Framework, there is one thing that
i don't undertstand in the philosophy of the cocoon portal:

in the cocoon portal documentation the following phrase is used:

" ... The set of coplet datas defines the set of available coplets a user
can choose from. If a user chooses to view a coplet, an instance of this
coplet data is created. If, e.g. the user chooses the same coplet twice, two
instances are created. This is useful for configurable coplets where the
user can choose the same coplet with different configurations...."

This implies an analogy to objects/classes and their instances, where
parameters and configurations are passed to Copletinstances (= the same what
an OO constructor does). Ok, this makes copletdata and copletinstances easy
to understand.

But after playing arround i cannot see how i can pass parameters to coplet
instances. The only way to give some parameters is to feed them to the
copletdata (which is the object/class and not the instance), is this the
supposed way of using coplets? Is there a way to configure coplet instances
in the copletinstancedata/portal.xml



+--------------+---------------------------------+---------------------+
| Frank Taffelt| f.taffelt@interface-projects.de |Tel: +49 351 31809 37|
+--------------+---------+-----------------------+---------------------+
| interface:projects gmbh| Tolkewitzer Str. 49, 01277 Dresden, Germany |
+------------------------+---------------------------------------------+


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Portal - Idea between Copletinstance and CopletData

[Ralph Goers <Ra...@dslextreme.com>]

There are a couple of ways to pass parameters to coplets:
1. In the layout.  Parameters are specified as <parameter name="" value=""/>
    a.) Parameters under items are added as attributes to the items
generated in the portal xml.
    b.) Parameters under layouts are passed as parameters to the
stylesheets configured in the appropriate XSLTAspect.
2. In the XSLTAspect configuration (new with 2.1.6).

Note that all these parameters can contain input module references so they
are resolved when at execution time.

Ralph


Frank Taffelt said:
> Hi,
>
> after playing arround with the new Portal-Framework, there is one thing
> that
> i don't undertstand in the philosophy of the cocoon portal:
>
> in the cocoon portal documentation the following phrase is used:
>
> " ... The set of coplet datas defines the set of available coplets a user
> can choose from. If a user chooses to view a coplet, an instance of this
> coplet data is created. If, e.g. the user chooses the same coplet twice,
> two
> instances are created. This is useful for configurable coplets where the
> user can choose the same coplet with different configurations...."
>
> This implies an analogy to objects/classes and their instances, where
> parameters and configurations are passed to Copletinstances (= the same
> what
> an OO constructor does). Ok, this makes copletdata and copletinstances
> easy
> to understand.
>
> But after playing arround i cannot see how i can pass parameters to coplet
> instances. The only way to give some parameters is to feed them to the
> copletdata (which is the object/class and not the instance), is this the
> supposed way of using coplets? Is there a way to configure coplet
> instances
> in the copletinstancedata/portal.xml
>
>
>
> +--------------+---------------------------------+---------------------+
> | Frank Taffelt| f.taffelt@interface-projects.de |Tel: +49 351 31809 37|
> +--------------+---------+-----------------------+---------------------+
> | interface:projects gmbh| Tolkewitzer Str. 49, 01277 Dresden, Germany |
> +------------------------+---------------------------------------------+
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org