Strange behavior with xml-logicsheet vs. cocoon.properties

[Herbert Hotz <he...@symmetrix.ch>]

Hi,

Found a strange behavior and do not know what is correct thing to do.

Situation 1:
------------

In my db_test.xml file I have a line replaced the recommended line

<?xml-logicsheet href="resource://org/apache/cocoon/processor/xsp/library/sql/esql.xsl"?>

with

<?xml-logicsheet href="/sr/esql.xsl"?>

because cocoon 1.8 couldn't compile without errors otherwise.

I copied for that reason /opt/cocoon-1.8/src/org/apache/cocoon/processor/xsp/library/sql/esql.xsl
to DocumentRoot/sr/esql.xsl

and everything worked fine! (esql.xsl v1.25)


Situation 2:
------------

I changed the cocoon.properties file (see the following lines) so that it reflects the proper
resource path for esql.xsl. Than I removed the esql xml-logicsheet line from db_test.xml to
avoid double declarations. Right? And of course I restarted Apache and JServ!

# Set the libraries associated with the given namespace.
# Use the syntax:
#   processor.xsp.logicsheet.<namespace-tag>.<language> = URL to file
# where "URL to file" is usually starting with file:// if you locate
# your custom library in your file system.
processor.xsp.logicsheet.context.java  = resource://org/apache/cocoon/processor/xsp/library/java/context.xsl
processor.xsp.logicsheet.cookie.java   = resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
processor.xsp.logicsheet.global.java   = resource://org/apache/cocoon/processor/xsp/library/java/global.xsl
processor.xsp.logicsheet.request.java  = resource://org/apache/cocoon/processor/xsp/library/java/request.xsl
processor.xsp.logicsheet.response.java = resource://org/apache/cocoon/processor/xsp/library/java/response.xsl
processor.xsp.logicsheet.session.java  = resource://org/apache/cocoon/processor/xsp/library/java/session.xsl
processor.xsp.logicsheet.util.java     = resource://org/apache/cocoon/processor/xsp/library/java/util.xsl
processor.xsp.logicsheet.sql.java      = resource://org/apache/cocoon/processor/xsp/library/sql/sql.xsl
processor.xsp.logicsheet.fp.java       = resource://org/apache/cocoon/processor/xsp/library/fp/fp.xsl
## added for esql.xsl
#processor.xsp.logicsheet.esql.java     = resource://org/apache/cocoon/processor/xsp/library/sql/esql.xsl


The effect is, that compilation of _db_test.java fails. The comiler is complaining, that a
deprecated method DBroker.getInstance() (or the like) is used. (turbine-pool.jar v1.4).

Any ideas?

Thank's in advance
Herbert
--
+----------------------+-------------------------------------------+
| Herbert Hotz         | Voice:   +41 1 381 8880                   |
| Symmetrix AG         | Fax:     +41 1 381 2127                   |
| Muehle Tiefenbrunnen | GSM-SMS: +41 79 402 5704                  |
| Seefeldstrasse 231   | URL:     http://www.symmetrix.ch/         |
| CH-8008 Zurich       | E-Mail:  mailto:herbert.hotz@symmetrix.ch |
+----------------------+-------------------------------------------+

Re: Strange behavior with xml-logicsheet vs. cocoon.properties

[Herbert Hotz <he...@symmetrix.ch>]

Sorry for the typo in my original mail:

The last line form the cocoon.properties should not be commented out!

processor.xsp.logicsheet.esql.java     = resource://org/apache/cocoon/processor/xsp/library/sql/esql.xsl

I commented it out, because it was not working.

Herbert
--
+----------------------+-------------------------------------------+
| Herbert Hotz         | Voice:   +41 1 381 8880                   |
| Symmetrix AG         | Fax:     +41 1 381 2127                   |
| Muehle Tiefenbrunnen | GSM-SMS: +41 79 402 5704                  |
| Seefeldstrasse 231   | URL:     http://www.symmetrix.ch/         |
| CH-8008 Zurich       | E-Mail:  mailto:herbert.hotz@symmetrix.ch |
+----------------------+-------------------------------------------+