but this seems not to be the solution i think. while debugging i compared the behaviour of the tdk installed with the provided servlet- container catalina and the one in my server environment where i have to adapt the instalation to. the result is the following: accessing the rundata object from within a jsp-page works well for the original installation, while the other one using the old tomcat does not work. i'm not quit shure if this is a problem of this old tomcat (3.2.4.) or caused by special patches applied to it :(
is there any possibility to check whether the services of turbine are started correctly? i noticed in my local logs the are entries like:
----------------------------- SNIP -------------------------------
[Thu Feb 27 15:28:07 CET 2003] -- INFO -- Start Initializing service (early): RunDataService
[Thu Feb 27 15:28:07 CET 2003] -- INFO -- Finish Initializing service (early): RunDataService
...
Thu Feb 27 15:28:30 CET 2003] -- INFO -- Start Initializing service (late): RunDataService
[Thu Feb 27 15:28:30 CET 2003] -- INFO -- Finish Initializing service (late): RunDataService
[
----------------------------- SNIP -------------------------------
i assume this is the appropriate service, isn't it ? my logs on the server do not contain any entries of that kind, even not for other services.
again the problem:
the rundata object seems to be created everytime i request it using the procedure described below. it also does not contail any information i put into before when i try to access it again after setting the data. one problem seems to be that no cookie is set while accessing login routines from my jsp page.
-- daniel
Kevin Rutherford wrote:
I haven't kept up with newer releases of Turbine, but in the past, the RunData object has been available to JSP pages as a request attribute. It is added to the request by the JspService, with an attribute name of "rundata".
From JspService.java:
/** The key used to store an instance of RunData in the request */ public static final String RUNDATA = "rundata";
From TurbineJspService.java:
/** * Adds some convenience objects to the request. For example an instance * of JspLink which can be used to generate links to other templates. * * @param RunData the turbine rundata object */ public void addDefaultObjects(RunData data) { HttpServletRequest req = data.getRequest(); req.setAttribute(LINK, new JspLink(data)); req.setAttribute(RUNDATA, data); }
So you should be able to get it directly from the request object.
Kevin
-----Original Message----- From: Daniel Pfuhl [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 6:01 AM To: Turbine Users List Subject: Re: RunData and JSP pages
hmm
also if I use
RunData runData = RunDataFactory.getRunData(request, response, config);
it is not working. during the debugging i realized that the cookie for identifying the session is not set correctly. in my server-environment i have to use tomcat 3.2.4 can this be the problem?
would be nice to get some help debugging this!
thanx!
-- daniel
Daniel Pfuhl wrote:
Hi there,
can anyone give me a clue how to use the RunData object within JSP pages?
I only found something like this to implement it:
RunDataService rds = new TurbineRunDataService();
rds.init(); RunData runData = rds.getRunData(request, response, config);
but in this case the rds will be initiated everytime I load the page - so no data can passed around :(
It would be very nice if someone could point me in the right direction for the handling of jsp/xsp pages.
FYI: I don't want to use the velocity - templates because, we have a working environment using jsp/xsp and want to integrate Turbine in this (what is work to do enough ;-)
any suggestion appreciated !!
thnx
-- daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
