Hi Niclas,
I guess that the print message should end up in the catalina.out
Kind regards,
Jeroen Reijn
ZongoZongo wrote:
Juchuu. I found the error. All my fault, like most times. Was really a
problem with the factory. Too complicated to explain in detail ;-)
Anyway, please explain, where I can find the output auf the print method
insinde the flowscript.
Thanx a lot for helping. Most helpful people in this forum.
Niclas
ZongoZongo wrote:
The method writeFormFiles writes the formmodel, the formtemplate and the
formbinding to the filesystem (I need to do it this way, because the
structure of the form is generated dynamically and can be very different
from time to time). Writing back to db always works. After submitting the
form a page is displayed, that shows the data of the DB.
The factory.getFormObject cant be the reason neither. In fact the obj has
to be the identical object, because I want to see the modified data of
that object. The data that is loaded into the form is got from the
function getXMLData that loads the data directly from the db.
Pressing shif-f5 in the browser doesnt work too.
The strange thing is, that everything works fine, when I restart tomcat
after modifying the data. Then the correct data is loaded into the form.
One question. To where does the output of print() go? I have no console
like in java.
kind regards,
Niclas
Ard Schrijvers wrote:
Mark Lundquist-2 wrote:
OK. But I don't think it's the value of a flowscript
variable that's
getting "cached".
It doesn't work that way. But clearly
something is
getting cached!
As Mark already pointed out, cocoon is really caching nothing in what you
are showing. The problem is in your flowscript. What I do not understand
for example, is the obj.writeFormFiles(). What are you writing? Then, you
say to save data back to DB. Perhaps something goes wrong there. Or when
you reload again, perhaps var obj = factory.getFormObject(objectType, id,
0); does not result in something new. OR, try at least to use ctrl-f5 in
your browser, when you have the old form, perhaps it is your browser
cache. In that case you might want to add headers with cache pragmas. Put
as Mark aleady said a print(doc) in your flowscript. At least you should
then see if the flowscript is run again, and what is in the doc var
Ard
From your sitemap, what do the pipelines look like that
are involved in
servicing the client request (i.e., calling the flowscript
function and
serving up the final HTML response)?
Also, if you add type="noncaching" to your <map:pipeline>, does the
behavior change at all?
—ml—
Setting type="noncaching" doesnt help.
Here are some sitemap extractions:
<map:match pattern="**">
<map:call resource="page.html">
<map:parameter name="page" value="{0}"/>
</map:call>
</map:match>
<map:resources>
<map:resource name="page.html">
<map:aggregate element="site">
<map:part element="navigation"
src="cocoon:/navigation"
strip-root="true"/>
<map:part
src="cocoon:/{page}.source" element="main"/>
<map:part element="header"
src="header.xml" strip-root="true"/>
</map:aggregate>
<map:transform type="xslt"
src="stylesheets/finalize.xsl"/>
<map:serialize type="html"/>
</map:resource>
</map:resources>
calls flowscript. Attributes are just for testing
<map:match pattern="showObject.source">
<map:call function="showObject">
<map:attribute name="objectType" value="author"/>
<map:attribute name="id" value="15"/>
</map:call>
</map:match>
is called from the flowscript
<map:match pattern="form/template/*.source">
<map:generate type="jx" src="forms/{1}-template.xml"/>
<map:transform type="browser-update"/>
<map:transform type="i18n">
<map:parameter name="locale" value="en-US"/>
</map:transform>
<map:transform src="forms-samples-styling.xsl"/>
<map:select type="ajax-request">
<map:when test="true">
<map:serialize type="xml"/>
</map:when>
<map:otherwise>
<map:serialize type="xhtml"/>
</map:otherwise>
</map:select>
</map:match>
Maybe you hava an idea ;-)
kind regards,
Niclas
--
View this message in context:
http://www.nabble.com/Caching-Problem-tf2909200.html#a8132146
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
