--- Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Alex Romayev wrote:
>
> >
> > 2. Actions: Implement login coplet as a URICoplet
> and use
> > actions instead of flow.
> >
> > I've tried this as well, however CForms populate
> form
> > attributes from request, which is not available
> for
> > URICoplets. I tried adding:
> >
> > <attribute>
> > <name>handleParameters</name>
> > <value xsi:type="java:java.lang.Boolean"
> >
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>true</value>
> > </attribute>
> >
> > but it didn't seem to have any effect, the request
> was still blank.
> >
> > Is there a way of making request parameters
> available to CForms?
> >
> Adding the above configuration should actually do
> the trick. Hmm.
> Just to make sure: Does Cocoon receive the form
> values at all (which
> means is the form running standalone)?
The the form outside of portal works fine.
Where did you
> add the above
> configuration to?
I've added the configuration to copletdata xml:
<coplet-data id="login-cforms" name="standard">
<title>Login CForms</title>
<coplet-base-data>URICoplet</coplet-base-data>
<attribute>
<name>uri</name>
<value
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="java:java.lang.String">cocoon:raw:/coplets/registration/login-cforms</value>
</attribute>
<attribute>
<name>handleParameters</name>
<value xsi:type="java:java.lang.Boolean"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>true</value>
</attribute>
<aspect>
<name>mandatory</name>
<value
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="java:java.lang.Boolean">true</value>
</aspect>
<aspect>
<name>sizable</name>
<value
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="java:java.lang.Boolean">false</value>
</aspect>
<aspect>
<name>fullScreen</name>
<value
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:type="java:java.lang.Boolean">false</value>
</aspect>
</coplet-data>
-Alex
>
> Carsten
>
