Lee Carroll schrieb:
A couple of days ago I mailed about a problem with the schedule in 1.2.3
I was not sure if this is specific to my set up or a bug.
What appears to be happening is that the process which creates the
scheduled job (and persists it in the jobs.xml file
pub/default/config/scheduler/jobs.xml) creates elements prefixed with
task (ie <task:task> or task:parameter). However jobs.xml does not map
the prefix to a namespace and the rest of lenya which I'm guessing reads
jobs.xml, do not understand these prefixed elements. Hence the errors
(example snippet below)
Has anyone come across this problem. Any ideas what is wrong would be
greatly appreciated.
> (...)
> a.. tomcat 5.0.28
> (...)
> org.xml.sax.SAXParseException: The prefix "task" for element "task:task"
Lee,
I had that same problem when I updated our server from Suse Linux 9.0 to
Suse Linux 9.2; which had the effect of updating to Tomcat 5. Since the
exact same Lenya installation worked before (and also works on another
machines with the "old" Suse Linux), I figured it must have to do with
the XML libraries that the server is using. But I never found out what
exactly is going on, and why the packaged Tomcat seemed to use some
other libraries then I wanted it to. The Java and Tomcat packaging under
the new Suse Linux is so obfuscated, I found it impossible to understand
what exactly was going on.
The way I fixed this was to install a downloaded Tomcat instead of using
the Suse packaged one ... Lenya's XML errors disappeared along with that
Tomcat.
Since in addition to that problem the Suse packaged Tomcat was very
unstable (crashed several times per week), I decided to keep the one I
installed by hand.
Hmm, now that I think about it again, I feel like getting rid of Tomcat
altogether and just run Lenya within Jetty.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
