I reported this bug and posted a fix many months ago, but nothing has
been done with it. It seems to only affect certain databases. I'd be
glad to forward you the code.
Brian
On Wednesday, May 28, 2003, at 09:36 AM, Carmona Perez, David wrote:
Dear Cocooners,
I've think I found a bug in the
connection
causing
NullPointerException when accessing ResultSet
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12173
Andreas
- Original Message -
From: Brian Johnson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 29, 2003 10:30 PM
Subject: Re: SQLTransformer bug
I reported
In my case, I would rather have it use the case returned by the query.
Maybe calling toLowerCase() should be an option?
Brian
On Thursday, March 13, 2003, at 09:53 AM, Luca Morandini wrote:
-Original Message-
From: Brian Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003
, March 13, 2003, at 10:28 AM, Luca Morandini wrote:
-Original Message-
From: Brian Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 4:14 PM
To: [EMAIL PROTECTED]
Subject: Re: sql result tags = column names minus case / any way to
get
case sensitive tags?
In my case, I
I have also started to look into this, but have not come up with
anything yet. I'd be very interested in anything you come up with, and
will certainly pass along any ideas I have.
Brian
On Wednesday, March 5, 2003, at 12:15 PM, Irv Salisbury III wrote:
We'd like to use paging in our
What do you want to do with this parameter? The FileGenerator doesn't
use any parameters. The TraxTransformer allows you to pass parameters
to the stylesheet that can be accessed with xsl:param, but there is no
similar function for a generic xml document. The FileGenerator simply
loads the xml
are looking for.
Brian
On Sunday, March 2, 2003, at 07:29 AM, Brian Johnson wrote:
What do you want to do with this parameter? The FileGenerator doesn't
use any parameters. The TraxTransformer allows you to pass parameters
to the stylesheet that can be accessed with xsl:param, but there is no
similar
information to a sitemap source that I can see...
Brian
On Sunday, March 2, 2003, at 07:46 AM, Brian Johnson wrote:
Ok, I see what you are trying to do... Again though, the FileGenerator
doesn't use any parameters that are passed to it. It is possible to
extend FileGenerator and override
Unfortunately, as long as you are using the cocoon:// protocol, you are
going to run into the same problem with passing parameters to the
pipeline. Both generators use the resolver to retrieve a SitemapSource,
which will place any parameters you pass to it into the objectModel. I
think Marco's
It may be a problem with your connection string. This is working for me:
jdbc:firebirdsql:localhost/3050:/home/firebird/mydatabase.gdb
Can you connect with the driver using JDBC outside of Cocoon?
Brian
On Tuesday, February 18, 2003, at 07:36 PM, Upayavira wrote:
Dear All,
Has anyone out
Everything looks ok in your config files. It's strange that you had to
restart the server... what version of Firebird are you using? Maybe
it's a problem with the server?? Also, there is a bug in the
SQLTransformer that affects Firebird. The connection gets closed before
the data is retrieved,
1.3). Suddenly
everything was fine...
Bye, Nils
-Ursprungliche Nachricht-
Von: Upayavira [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 19. Februar 2003 15:06
An: Brian Johnson; [EMAIL PROTECTED]
Betreff: Re: Firebird with Cocoon
Dear Brian,
It may be a problem with your connection
If you want to change it for both, just remove conn.close() and conn =
null in the finally block of the Query.exceute() method in the
SQLTransformer. conn.close() is called in Query.close() and should not
be called in execute().
On Wednesday, February 19, 2003, at 02:43 PM, Upayavira wrote:
/1999/XSL/Transform;
!-- je nach Hierarchietiefe relative Pfade anpassen --
xsl:variable name=basepath
xsl:text/development//xsl:text
/xsl:variable
/xsl:stylesheet
- Original Message -
From: Brian Johnson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February
You have an error in your stylesheet. The name template does not end
with a name tag. Also, I believe you need the identity template at the
top, so it has the lowest priority.
Brian
On Friday, February 7, 2003, at 11:14 AM, Lionel Crine wrote:
I made a query in my XMLDB :
In the sitemap :
Is there any way to access a running Environment from within a
Transformer in Cocoon 2.1? It appears to be accessible in the
ObjectModel through the CocoonComponentManager, but after looking over
the CocoonComponentManager code, I think it's probably not a good idea
to rely on accessing it
well.
Brian
On Thursday, February 6, 2003, at 11:28 AM, David Trammell wrote:
We are using version 2.0.4.
Brian Johnson wrote:
Almost forgot, are you using 2.0.x or 2.1? There are some small
differences in the way the processor is called. I'm pretty sure all
the
Environment classes
well.
Brian
On Thursday, February 6, 2003, at 11:28 AM, David Trammell wrote:
We are using version 2.0.4.
Brian Johnson wrote:
Almost forgot, are you using 2.0.x or 2.1? There are some small
differences in the way the processor is called. I'm pretty sure all
the
Environment classes
I tried to switch to xsltc with Cocoon 2.1. After a few days of trying
to modify my stylesheets to make it happy, I finally gave up.
Transformations that worked fine under standard Xalan and Saxon would
not work under xsltc. Are you having problems configuring Cocoon to use
xsltc, or are you
I'm using the latest stable version of Saxon with no problems at all.
I've used it under both 2.0.x and 2.1. Are you using one of the
experimental releases?
On Wednesday, February 5, 2003, at 07:14 AM, Beat De Martin wrote:
I'm using Saxon as well, it seems faster than Xalan. And with Xalan I
for your help.
Rob
- Original Message -
From: Brian Johnson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 1:24 PM
Subject: Re: status quo: cocoon with xsltc
I'm using the latest stable version of Saxon with no problems at all.
I've used it under both 2.0.x and 2.1
--
xsl:template match=ABSTRACT[@DIREKTANZEIGE = '1']
DIV class=abstract_ueberschrift_direktxsl:value-of
select=UEBERSCHRIFT//DIV
DIV class=abstract_direktanzeigexsl:apply-templates
select=TEXT//DIV
/xsl:template
...
- Original Message -
From: Brian Johnson [EMAIL PROTECTED
I am working on a transformer that allows you to take XML fragments
from a pipeline and run them through other pipelines. The transformer
itself is very specific to my application, but if you're interested,
you might be able to adapt parts of it to whatever you're doing. It
creates a new
xsl:text/development//xsl:text
/xsl:variable
/xsl:stylesheet
- Original Message -
From: Brian Johnson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 4:41 PM
Subject: Re: status quo: cocoon with xsltc
Can you also post the include-basepath.xsl? Are there any
, David Trammell wrote:
Brian,
Thank you for your response! I would be interested in looking at what
you
have.
David
Brian Johnson wrote:
I am working on a transformer that allows you to take XML fragments
from a pipeline and run them through other pipelines. The transformer
itself is very specific
You need to call endSerializedXMLRecording in your endElement method.
The AbstractSAXTransformer is setup to pick out elements based on a
namespace uri. You can look at the code for startElement and endElement
to see how to pick the xml fragment you want based on a qname.
Brian
On Tuesday,
Have you looked at Captor http://outerthought.net/captor.html? It works
on 2.0.x, and can easily be modified to work on 2.1.
On Monday, January 27, 2003, at 05:41 PM, Mark H wrote:
Hi Luca,
I don't use XSLT debuggers, I've just configured logkit to put all
messages
produced by Xalan into a
I would like to log the cocoon sitemap to Log4J so that I can view it
chainsaw on a remote host. It appears that the LogKit SocketAppender is
not compatible with Chainsaw. I set enableLogging on cocoon with a
Log4JLogger, but it only logs a few random core messages to Log4J. Does
anybody know
. I'm not sure if this will
work with Cocoon 2.0.x. Thanks.
Brian
On Wednesday, January 15, 2003, at 09:41 AM, Brian Johnson wrote:
I would like to log the cocoon sitemap to Log4J so that I can view it
chainsaw on a remote host. It appears that the LogKit SocketAppender
is not compatible
Sorry, missed one step. I created a new public Logger2LogKitManager
class in my own project with identical code so I could use it directly.
Brian
On Wednesday, January 15, 2003, at 03:47 PM, Brian Johnson wrote:
For anybody else that's interested, The latest CVS of Excalibur and
Avalon
Do you have the Cocoon webapp mounted under /cocoon instead of /? All
of the sitemaps assume that cocoon is not part of the path of the
request.
On Monday, January 13, 2003, at 01:19 PM, e nio wrote:
Well, I didn't get much additional info since last I posted. I
tried to back down to
I have a transformer that sends portions of an xml document through
another sitemap pipeline and inserts the results in the current
pipeline. Under Cocoon 2.0.4, I used the ComponentManager to lookup a
Processor and process a new environment with the xml fragment, but
under Cocoon 2.1 it seems
I have a transformer that sends portions of an xml document through
another sitemap pipeline and inserts the results in the current
pipeline. Under Cocoon 2.0.4, I used the ComponentManager to lookup a
Processor and process a new environment with the xml fragment, but
under Cocoon 2.1 it seems
With a well-designed set of transformation, you won't have to update
every one of your stylesheets for a single attribute change. For
instance, I use the xsl:copy tag to simply copy as-is any element that
I'm not interested in doing something with in a particular stylesheet.
On Thursday,
34 matches
Mail list logo
