Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-20 Thread Vadim Gritsenko
Matthew Hailstone wrote: Awesome! I changed the xsp file to declare a namespace of: xmlns:session=http://apache.org/xsp/session/2.0; create-session=true instead of xmlns:xsp-session=http://apache.org/xsp/session/2.0; create-session=true and changed all the tags

RE: Cocoon 2.0.3 under Enhydra 3.1

2002-09-20 Thread Matthew Hailstone
Vadim, How do I _explicitly_ create a session? Isn't the following supposed to do that? xmlns:session=http://apache.org/xsp/session/2.0; create-session=true I looked on the website for the short list of xsp-session tags to use, but couldn't find anything to do this. I also have

Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-20 Thread Vadim Gritsenko
Matthew Hailstone wrote: Vadim, How do I _explicitly_ create a session? Isn't the following supposed to do that? xmlns:session=http://apache.org/xsp/session/2.0; create-session=true Yes, this will create the session. Other ways are get-session-id/, and request.getSession(). PS

RE: Cocoon 2.0.3 under Enhydra 3.1

2002-09-20 Thread Matthew Hailstone
] Subject: Re: Cocoon 2.0.3 under Enhydra 3.1 Matthew Hailstone wrote: Vadim, How do I _explicitly_ create a session? Isn't the following supposed to do that? xmlns:session=http://apache.org/xsp/session/2.0; create-session=true Yes, this will create the session

Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-19 Thread Vadim Gritsenko
Matthew, The code generated with 2.0.1 means that session logicsheet was not applied. Please look at 2.0.1 samples for session logicsheet usage. It might be that with 2.0.1 you have to use session namespace, not xsp-session. This bug was fixed, now (2.0.3) you can use any namespace prefix you

RE: Cocoon 2.0.3 under Enhydra 3.1

2002-09-18 Thread Matthew Hailstone
Vadim, In the second email it was recommended to use Paranoid servlet which makes me to think that enhyndra has broken class loader. Issues with broken class loading can be endless and hard to trace. In your install, however, you are trying to start with regular CocoonServlet (as far

Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-18 Thread Vadim Gritsenko
Matthew Hailstone wrote: Vadim, In the second email it was recommended to use Paranoid servlet which makes me to think that enhyndra has broken class loader. Issues with broken class loading can be endless and hard to trace. In your install, however, you are trying to start with regular

Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-18 Thread Vadim Gritsenko
Matthew Hailstone wrote: Vadim, Here is a portion of my xsp file: if( xsp:contentxsp-session:get-attribute name=test-name-wcart//xsp:content == null || ((String)xsp:contentxsp-session:get-attribute name=test-name-wcart//xsp:content).length() == 0 ){

RE: Cocoon 2.0.3 under Enhydra 3.1

2002-09-18 Thread Matthew Hailstone
oops. Yeah, I put the xsp:content elements in the 'if' condition to see if it would help. But, after comparing the working java file from 2.0.3 with the one created with 2.0.1, I found the following commented below: Matthew Hailstone wrote: Vadim, Here is a portion of my xsp file:

Cocoon 2.0.3 under Enhydra 3.1

2002-09-17 Thread Matthew Hailstone
I am trying to run Cocoon 2.0.3 under Enhydra 3.1. Here is my environment: Win2K jdk1.3.1_03 I get the following in my Enhydra log: 2002.09.17 10:48:02: WebQuery,INFO: DEBUG (2002-09-17) 10:48.02:619 [] (Unknown-URI) Unknown-thread/DefaultLogTargetFactoryManager: added new

Re: Cocoon 2.0.3 under Enhydra 3.1

2002-09-17 Thread Vadim Gritsenko
Matthew Hailstone wrote: I am trying to run Cocoon 2.0.3 under Enhydra 3.1. Here is my environment: Win2K jdk1.3.1_03 I get the following in my Enhydra log: java.lang.NullPointerException at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:999

RE: Cocoon 2.0.3 under Enhydra 3.1

2002-09-17 Thread Matthew Hailstone
Vadim, Thanks for your reply and the reference to the patch. I've been pulling my hair out trying to make Cocoon work under Enhydra3.1. :) I performed a CVS update on a previously checkedout cocoon_2_0_3_branch tag module. It appears to be the 2.0.4-dev version. I verified that the patch that