The constant is in a Java class in a JAR file. Deleting all _xsp.java and
_xsp.class files will work, although I was hoping for a more elegant
solution. That way many XSPs which don't use the constant at all will also
have to be regenerated.
In my case I happened to know which XSP was using
Update: I was mistake before when I said that if the login suceeds, the
correct html file is shown. It's not. Rather, in both cases I'm redirected
to the pipeline defined in the authentication handler.
To reiterate, this confuses me because I thought no such redirect should
ever occur with
Cocoon wrote:
If I then use the -classpath:
javac -classpath
.;C:\jakarta-tomcat-4.1.24\webapps\cocoon\WEB-INF\lib\cocoon-xmlform-block.jar
HowtoWizardAction.java
I get several messages sarting with:
cannot access org.apache.avalon.excalibur.pool.Poolable
file
Try to put anywhere into your XSPs:
xsp:dependency/absolute/path/to/touchfile/xsp:dependency
Then you only need to touch that single file to force recompiling
all XSPs containing this dependency.
HTH, Alfred.
-Original Message-
From: Sonny Sukumar [mailto:[EMAIL PROTECTED]
Sent:
Sonny
I've had a look and I'm not sure why this is happenning.
There are bits of the sitemap missing which are still part of the auth
process such as your login page itself. Maybe the problem lies there
somewhere???
Sorry I can't help further.
Andrew
Sonny Sukumar wrote:
Update: I was
Thanks Steve but as I'm not familiar with Ant and I don't understand the
connection between compiling my code and that link I'm still stuck.
I've had a stab at the ant method with a modified version of the file you
gave me:
project name=HowTo default=compile
property name=src.java value=. /
