cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kunert" <kun...@yobe.de>
Subject Problem with cascading actions and parameters...
Date Fri, 17 Aug 2001 03:29:51 GMT
ok, my matcher looks like this:

<map:match pattern="forms/*">
	<!-- first validate whether user has logged in -->

      <map:act type="session-validator">
      	<map:parameter name="descriptor"
value="context://protected/data/formdefinition/formdefinition.xml"/>
          	<map:parameter name="validate" value="username"/>

            <!-- user has logged in, try to validate some forms -->
          	<map:act type="form-validator">
            	<map:parameter name="descriptor"
value="context://protected/data/formdefinition/formdefinition.xml"/>

            	<!-- this statement seems to work, the value in {1} is
correctly evaluated -->
			<map:parameter name="constraint-set" value="{1}"/>

            	<!-- if validation succeeds we call the same form -->
			<!-- here the value of {1} seems to be lost somewhere ????? -->
            	<map:redirect-to resource="form_page" target="{1}"/>
		</map:act>

		<!-- if validation failed we call the same form again -->
          	<map:redirect-to resource="form_page" target="{1}"/>

	</map:act>

      <!-- something was wrong, redirect to login page -->
      <map:redirect-to uri="login"/>
</map:match>

when our resource gets called from within that action the value of the
parameter 'target' is null, meaning that the {1} doesn't get evaluated...

any clue?


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Mime
View raw message