--- Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > Alex Romayev wrote: > > > > --- 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: > > > > <SNIP/> > > Looks good to me. Hmm. > > Ok, the only hint I can give you at the moment is to > try > to debug the coplet adapter and see if it really > invokes > the coplet with the correct parameters or not.
For a quick look at the code it seems that the parameters (I assume request parameters) are only added if cocoon:raw protocol is used. I thought it was the other way around, raw meant no request parameters? I haven't tried testing with raw -- would have to do it tomorrow and let you know if it works. -Alex > > Carsten > > > > -Alex > > > > > > > > Carsten > > > > > >
