Yepp, that's right - unfortunately, the released version has a bug
which I fixed in the current CVS again :(

Carsten 

> -----Original Message-----
> From: Philippe Guillard [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, June 29, 2004 12:18 PM
> To: [EMAIL PROTECTED]
> Subject: RE: portal-html-eventlink transformer and req-params ?
> 
> Thanks a lot Carsten!
> 
> Just one more quick question : It seems to me that 
> portal-html-eventlink transformer doesn't transform html 
> anchors to events&action on 2.1.5release, as it was doing 
> before (2.1.5dev) and after (head cvs). Am i right?
> 
> Regards,
> 
> Phil
> 
> 
> On Mon, 2004-06-28 at 21:33, Carsten Ziegeler wrote:
> > If I understand you correctly, the problem is in the 
> pipeline calling 
> > your coplet pipeline (calling page2?a=1).
> > 
> > The statement is in the sitemap in coplets/html/sitemap.xmap:
> > 
> > <map:generate
> > 
> src="{coplet:temporaryAttributes/application-uri}?copletid={coplet:#}"
> > />
> > 
> > 
> > "{coplet:temporaryAttributes/application-uri}" should be 
> replaced with 
> > the original URI: page2?a=1, so the src for the generator will be
> > 
> > BASEURL/page2?a=1?copletid=something
> > 
> > which is obviously not a valid URL. If you don't need the 
> coplet id in 
> > your pipeline, you could remove the "?copletid={coplet:#}" 
> from the statement.
> > 
> > If this is your problem, we could solve it by either using 
> a different 
> > approach to build the uri or by always including the 
> copletid in the 
> > uri. This could be done by the html-eventlink transformer.
> > 
> > HTH
> > Carsten
> > 
> > > -----Original Message-----
> > > From: Philippe Guillard [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, June 28, 2004 6:42 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: portal-html-eventlink transformer and req-params ?
> > > 
> > > Hi,
> > > 
> > > On last cvs 2.1, with cachingURI coplet adapter and 
> > > portal-html-eventlink transformer, links like <a 
> > > href="page2?a=1">page2</a> are transformed in action=x&event=y
> > > 
> > > I discovered the original request-params like "a" are put 
> before the 
> > > question mark in the query string :
> > > 
> a=1?copletid=app-test-1&cocoon-portal-action=1&cocoon-portal-event=2
> > > 1
> > > 
> > > I get the request param "a" that is before "?" from 
> sitemap or XSP 
> > > Ok, but i don't know which method i should use to get it directly 
> > > from the servlet, i can only get what is behind the "?". Any idea?
> > > 
> > > Regards,
> > > 
> > > Phil
> > > 
> > 
> > 
> 
> 

Reply via email to