cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johannes Textor <>
Subject Re: Cocoon portal and META Tag
Date Mon, 22 Nov 2004 23:21:43 GMT
Hi Anna,

I'm having a hard time figuring out what your problem
might be ... it would be useful if you could include source
codes for your xsp and provide more information about how
you actually pass your parameters.

cocoon itself does not differentiate between post and get
request methods neither does it store values of previous
request, so I would guess you're either doing something wrong
when reading out the parameters ore it's a browser cache issue.


Anna Bikkina wrote:

>Can anyone provide input on this problem? I still cannot get the
>post/get methods working as they should.
>On Wed, 2004-11-17 at 16:53, Anna Bikkina wrote:
>>I think cocoon is somewhere internally storing my previous request
>>values because before submit I called a javascript and checked the
>>variables entered in page2 it displays right variables but then it still
>>posts page1 variables and this is happening only when the submit type of
>>form in page2 is post. How can I get rid of this?
>>On Wed, 2004-11-17 at 16:32, Anna Bikkina wrote:
>>>I have a wierd problem using META tab in <HEAD> of my HTML in cocoon
>>>portal. May be this is a html question more than a portal question. Can
>>>someone please help me solve this one.. I have been working on this for
>>>more than a week now.
>>>I have a html form in a cocoon coplet(page1.xsp). When I submit the form
>>>it goes to wait.xsp which just displays a animated gif saying searching
>>>results . Wait.xsp  has 
>>><meta http-equiv="refresh" 
>>>where the url in content  contains all the request parameters that come
>>>to wait.xsp.
>>>Now this one goes to the same sitemap match as page1  and the sitemap
>>>directs it to page2 depending on some conditions page2 displays results
>>>and also has  almost the same html form as in page1. When I submit the
>>>form in page2 it submits details as in page1 when the method type =
>>>"post" when the method type = "get" it works the way it should by
>>>posting parameters in page2 .Not sure what difference it makes when it
>>>is a get/post. Any  help is greatly appreciated.
>>>Here is the sitemap component for the coplet
>>>    <map:match pattern="page1.xsp">
>>>    	<map:select type="request-parameter">
>>>    		<map:parameter name="parameter-name" value="nowait"/>
>>>    		<map:when test="false">
>>>			<map:generate type="serverpages" src="wait.xsp" />
>>>		</map:when>
>>>    		<map:otherwise>
>>>	    		<map:generate type="serverpages" src="page2.xsp"
>>>label="raw"/>					    			  		</map:otherwise>
>>>  			<map:transform
>>>src="con	text://newhistoryserver/styles/searchresult.xsl"/>
>>>			<map:serialize/> 
>>>    	</map:select>
>>>       	<map:generate src="page2.xsp" type="serverpages"/>	      
>>>	<map:transform	src="context:/newhistoryserver/styles/search.xsl"/>    
>>>	<map:serialize/>  
>>>   </map:match>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message