----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
>>>>> "j" == jon * <* <[EMAIL PROTECTED]>> writes:
j> I have a document in the docs/ directory that explains all the
j> major differences.
Yes, I know, I have one too, but none of the differences listed have
anything to do with ApJServAction --- it is mostly curious that
referencing all of my applications directly using the /servlet/gsp or
/servlet/jsp shows these servlets are active and can be run, but
/Cocoon.xml produces a page-not-found, and _all_ of the ApJServAction
directive files are simply returned as plain text.
I also notice that your Working Dogs "working configuration" in the
FOM does not use _any_ ApJServAction settings, not even the SSI, which
is why I was curious if something in the final JServ 1.1 had broken
this feature without it being noted anywhere. The _only_ change in my
system is the move from 1.1b2 to the final 1.1 --- and it worked
perfectly well before the upgrade.
There is one other symptom: No matter how I set allow/deny values,
/jserv/ returns a 403 response. This is probably an essential clue.
Just for fun, I also tried to explicitly add the normal Apache
"Action" tag to map .gsp to /servlet/gsp, but, not surprisingly, that
didn't work. I also know it is reading my jserv.conf file because
inserting a syntax error into the file causes the load to fail. The
symptom, however, seems to suggest the ApJServAction directives are
recognized as special files.
Part of my problem is that I have been playing with WorkingDogs
software for too long: I have all of the servlet apps installed on this
server, and before I can really say what has gone wrong, I will have to
rip them all out and reconfigure from scratch. There was nothing in
the upgrade page which suggested there might be any conflict, and nothing in the
INSTALL doc which hinted that JServ 1.1 should be incompatible with any applications
that functioned under 1.1b2.
It is still very curious that ApJServAction and the /jserv/ status
page are the _only_ features which do not work, and there is no
evidence in any of the three logs as to why this might be the case
(yes, full debug is turned on in both jserv.conf and jserv.properties)
The server simply sees any page defined in an ApJServAction line and
serves the page directly as text/plain without any processing.
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Telecom Services : Internet Consulting : http://www.teledyn.com
Linux/GNU Education Group: http://www.egroups.com/group/linux-education/
"Computers are useless. They can only give you answers."(Pablo Picasso)
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
