On Wed, 2007-11-07 at 08:45 +0100, Thorsten Scherler wrote:
On Tue, 2007-11-06 at 21:08 +0100, Grzegorz Kossakowski wrote:
Thorsten Scherler pisze:
Hi all,
I found BlockPathModule.java and BlockCompletePathModule to return the
servlet path for a block.
However I need an
Working with Cocoon 2.1.8.
I have set a session value for a user, using the session transformer
in the sitemap. I now want to alter that value, based on other
conditions.
My sample testing flowscript code looks like:
//1. get user's current session value
var _authContext =
Working with Cocoon 2.1.8 and Tomcat 5 on
a Linux box. It appears that changes to flowscript
files are not reflected in Cocoon which continues to
work with a previous version. How do I ensure
that the new version/s are used - without restarting
Tomcat?
(I do not see the same effect on my
Hello,
I need access to session attributes in a subclass of AbstractJavaSelectionList.
Can I get the session with Spring or a factory?
Cheers,
Mike
winmail.dat-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Michel Erard pisze:
Hello,
Hello Michel.
I need access to session attributes in a subclass of
AbstractJavaSelectionList. Can I get the session with Spring or a factory?
I assume that you use Cocoon 2.2. Then yes, you can get session from request
object that is served
by
Thorsten Scherler pisze:
which was working fine since I was testing the dispatcher-block, but now
since I am in my webapp now the relative path is resolved to the current
app and not to the dispatcher block any more.
Meaning the resources cannot be found anymore.
That's something weird I
Grzegorz Kossakowski wrote:
Derek Hohls pisze:
Working with Cocoon 2.1.8 and Tomcat 5 on
a Linux box. It appears that changes to flowscript
files are not reflected in Cocoon which continues to
work with a previous version. How do I ensure
that the new version/s are used - without
Derek Hohls pisze:
Working with Cocoon 2.1.8 and Tomcat 5 on
a Linux box. It appears that changes to flowscript
files are not reflected in Cocoon which continues to
work with a previous version. How do I ensure
that the new version/s are used - without restarting
Tomcat?
(I do not see
I have a 2.1 based app and I am considering moving to 2.2 eventually and I am
trying to determine the upgrade issues.
What are the system requirements for 2.2?
What component versions must I be concerned about?
What happens to my actions built for 2.1?
I looked for this info on the site but
