On Wednesday, October 29, 2003, at 05:10 PM, Christopher Oliver wrote:
Can you recreate this problem with a simple example you can post to the list?
Sorry, I have no sample yet ... it is difficult to simplify ...
What appears to be happening :
I am using the FlowScript version of authentication-fw, which defaults to using a pipeline to provide authentication xml to the framework.
The job of this pipeline (called by o.a.c.webapps.authentication.components.PipelineAuthenticator) is to look up a user with a username and password, and output xml to signify success or failure.
Our user data is in SQL. I wanted to be able to use Hibernate to lookup and generate the authentication xml. So instead of having a traditional pipeline with something like the SQL Transformer in it, or XSP, I made one using FlowScript and JXTemplate.
The problems only seems to appear when the authentication pipeline is provided by FlowScript.
After the this pipeline has run and control returns to the original login FlowScript, several of the cocoon.* FOM properties have become null.
Thanks
regards Jeremy
Jeremy Quinn wrote:
On Wednesday, October 29, 2003, at 04:28 PM, Ugo Cei wrote:
Jeremy Quinn wrote:
I will login successfully, logout, then login again, the second time around, I get NPEs from cocoon.log.info. NPEs that I did not get the first time around.
I suggest that you add some more null checks in FOM_Cocoon, if you have identified the source lines that dereference nulls in your case. Defensive programming is A Good Thing (TM).
:)
Yeah, but something has broken to cause them ..... I only put them in because I am trying to see why my request params are sometimes (incorrectly) null ..... when Flow calls Flow Pipelines internally, something very strange starts happening ..... you begin to loose bits of the infrastructure after you come out the other side.
nasty business!!
Is anybody else attempting to do development of FlowScripts ATM with the current CVS and finding these problems? (Or is it just us two?).
regards Jeremy
