-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Jason Malcolm" <[EMAIL PROTECTED]> writes:
> Anyone know the timeframe for being able to use TrAX/JAXP API to create
> translets that accept something besides 'StreamSource' (As documented in
> the 'Translets and TrAX' section of
> http://xml.apache
Anyone know the timeframe for being able to use TrAX/JAXP API to create
translets that accept something besides 'StreamSource' (As documented in
the 'Translets and TrAX' section of
http://xml.apache.org/xalan-j/readme.html). More specifically, it would
be helpful if DOMSource or SAXSource were im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey.
I am working on a project which uses a LOT of Xalan extensions within a number
of stylesheets. There are about 15 extensions and maybe 50 or 60 stylesheets.
The problem is that everytime I want to use an extenion I have to add the
following c
Your input DOM is fine. The problem is with the output. DOM only
allows one Element below the Document Node. This is called the Document
Element. It looks like you're trying to ask Xalan to create a DOM with
more than one Document Element (or possibly a text Node) below the
Document.
If you'r
David --
The results that you're getting just don't seem consistent with that I'm
seeing. I repeat that the most likely cause of this is that your
stylesheet is creating multiple top-level Nodes which is not allowed in
the DOM model. You can have a maximum of one Element, a maximum of one
Docum
morten 01/08/03 07:18:21
Modified:java/src/org/apache/xalan/xsltc/dom DOMImpl.java
java/src/org/apache/xalan/xsltc/trax SAX2DOM.java
Log:
Fix to get around problem with Crimson. Crimson does not like attribute-
nodes to be created with 'null' or "" namespace URI. A
pauldick01/08/02 12:42:10
xml-xalan/test/tests/capi-gold/extensions - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pauldick01/08/02 12:42:03
xml-xalan/test/tests/capi-gold/domcomtests - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pauldick01/08/02 12:41:49
xml-xalan/test/tests/capi-gold - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2979
morten 01/08/03 08:23:21
Modified:java/src/org/apache/xalan/xsltc/compiler CopyOf.java
Step.java
java/src/org/apache/xalan/xsltc/dom DOMImpl.java
UnionIterator.java
Log:
Fix for union-iterators wrapping one or more attr
"Jason Malcolm" <[EMAIL PROTECTED]> writes:
> > Anyone know the timeframe for being able to use TrAX/JAXP API to create
> > translets that accept something besides 'StreamSource' (As documented in
> > the 'Translets and TrAX' section of
> > http://xml.apache.org/xalan-j/readme.html). More specifi
dmarston01/08/03 08:04:14
Modified:test/tests/conf-gold/copy copy03.out copy01.out
Added: test/tests/conf-gold/copy copy24.out copy25.out copy26.out
copy27.out copy28.out copy29.out copy30.out
copy31.out copy32.out copy33.out copy3
Dave --
Thanks. You have tried to place thirty four elements as the top element
of a DOM document. This is what is causing the error. Only one element
is allowed as the top element of a DOM document.
You have: , , and then 32 elements.
An XSL-FO document has to start with , I believe. It
Thank Gary, it did the trick.
-Original Message-
From: Gary L Peskin [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 03, 2001 17:42
To: [EMAIL PROTECTED]
Subject: Re: BUG? SAXParser/XMLReader and TransformerHandler
Dimitry --
By default, SAX parsers created from a SAXParserFactory are
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=919
Hi
Bryan,
Do you
build tree for input document or stylesheet? In both cases stylesheet text
would be helpful to find the problem. Can you send it or part of
it?
Thanks,
Dmitry
-Original Message-From: Bryan Mulvihill
[mailto:[EMAIL PROTECTED]]Sent: Friday, August 03, 2001
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2984
Hi
Bryan,
I've
checked that example. It works and you shouldn't have any problems if you use
DOM 2 Level methods building the DOM: createElementNS, setAttributeNS, etc.
You must specify correct namespace-uri, in the case of XSLT it's "http://www.w3.org/1999/XSL/Transform".
But I
belive us
curcuru 01/08/03 12:08:49
Added: test/java/src/org/apache/qetest/xsl BugzillaFileRules.java
BugzillaTestletDriver.java
Log:
New TestletDriver for Bugzilla tests and associated FilenameFilter
Revision ChangesPath
1.1
xml-xalan/t
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2727
Hi,
I realize that this is most probably Xerces problem. But it affects Xalan
work in my case and there's still chance Xalan doesn't work correctly not
Xerces. So I'm sending this message to this mail-list. Sorry for
inconvenience.
I tried to use SAXParser/XMLReader with
javax.xml.transform.sax.
Thanks, Dave.
Using an old shared library did not seem to work.
I ended up downloading and building the Xerces source, created a new
Xerces library, and now everything seems to be working.
Thanks for your patience in dealing with a newbie. If you would like
me to assemble all the steps you just
I use it for both (although I'm thinking I
shouldn't). I am using the DOM2DOM sample as a test base. I'll
attach it in case you are missing it.
Bryan MulvihillSoftware DeveloperAMCon
Research Inc., Ottawa, Ontario, Canadahttp://www.amconresearch.com
- Original Message -
From
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2969
curcuru 01/08/03 12:07:17
Modified:test/java/src/org/apache/qetest/xsl XHTFileCheckService.java
Log:
Automatically logs message with basic information on non-Passes
about why it failed or was ambiguous; either at WARNINGMSG or ERRORMSG
Revision ChangesPath
1.6 +2
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 03, 2001 3:45 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Bug 1426] - Namespace URIs beginning with a #-sign will
> cause errors
>
>
>
> >Quoting from the NS recommendation:
>
> ... is somewhat dangerous. There was a _MASSI
Morten Jorgensen <[EMAIL PROTECTED]> wrote:
> Yes, it is a bit of a mess. I was trying to say that it would not
> make sense to call transform() on the Transformer (ie. passing it
> a Source object) when the source document is passed to the
> TransformerHandler using SAX events.
Thinking about i
Hi:
When using Xalan transformer, or Serializer for writing DOM to a file, how
to keep the node?
It works fine from command line (java org.apache.xalan.xslt.Process ...),
but not in java code. I tried sample code in xalan.DOM2DOM (Serializer) and
sun's xml tutorial write out a DOM
http://java.
I've implemented a new BugzillaTestletDriver that automates running any
Bugzilla*.java Testlet class or any Bugzilla*.xsl stylesheet that's checked
into tests/bugzilla. I hope (with some documentation) to get to the point
where most Bugzilla bugs will also have a simple 'regression' test that
get
dmarston01/08/03 12:34:41
Added: test/tests/conf/select/err selecterr19.xsl selecterr17.xsl
selecterr18.xml selecterr18.xsl selecterr19.xml
selecterr17.xml
Log:
New error cases for bad // formulations
Revision ChangesPath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> If you can't tell, I am somewhat experimentally trying to improve our
> release process. I'm not sure that the release processes that work for
> traditional software development in companies work in open source. In
> fa
[EMAIL PROTECTED] wrote:
> I have a Java extension element that pipes a number of documents through a
> series of transformations. All is working fine as long as I don't create a
> constructor for this Java class. I wanted a constructor so I could
> instantiate an object from main() and use this f
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2983
Your sample result.xml file does not have a single root element; the
is not actually inside the , and there are other
top-level elements following it. This is _not_ a well-formed XML (or HTML)
document, and may not be represented in the DOM. If you want to output to a
DOM, you must fix your styl
[EMAIL PROTECTED] wrote:
="xalan://org.openprivacy.reptile.extensions.LogExtension"
exclude-result-prefixes=""version="1.0">
Don't you need to define extension-element-prefixes="log" as an attributeon xsl:stylesheet?
Ug... Good point. I gu
jkesselm01/08/03 10:30:04
Modified:java/src/org/apache/xml/utils NamespaceSupport2.java
Log:
Continuing code review.
Revision ChangesPath
1.2 +48 -43xml-xalan/java/src/org/apache/xml/utils/NamespaceSupport2.java
Index: NamespaceSupport2.java
dmarston01/08/03 07:57:23
Added: test/tests/conf/attribset/err attribseterr08.xsl
attribseterr08.xml
Log:
New error cases: premature attribute
Revision ChangesPath
1.1 xml-xalan/test/tests/conf/attribset/err/attribseterr08.xsl
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1269
pauldick01/08/02 12:39:59
xml-xalan/test/tests/capi/domcomtests - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jkesselm01/08/03 10:06:05
Modified:java/src/org/apache/xalan/processor StylesheetHandler.java
java/src/org/apache/xalan/templates ElemTemplateElement.java
java/src/org/apache/xalan/transformer ResultTreeHandler.java
TransformSnapshot
dmarston01/08/03 07:58:11
Added: test/tests/conf/copy/err copyerr05.xsl copyerr04.xsl
copyerr05.xml copyerr04.xml
Log:
New error cases: premature attribute
Revision ChangesPath
1.1 xml-xalan/test/tests/conf/copy/err/copyerr05.xs
"Kevin A. Burton" <[EMAIL PROTECTED]> wrote:
> Realisitically xalan could reduce code complexity by automatically
detecting namepaces which start with xalan:// and make them extensions.
It's a requirement in the XSLT recommendation that
extension-element-prefixes be used, so I don't think it mak
>However, they are still legal, and happen to be used in existing
applications.
>I don't think it's DOM's or XSLT's job to keep people from using them and
I
>can't see any official word from the W3C that would defend that.
This really was discussed. Declining to support them _was_ agreed to be a
>Quoting from the NS recommendation:
... is somewhat dangerous. There was a _MASSIVE_ W3C debate last summer
about what the intent of the Namespaces spec was, versus what some people
thought it ought to be.
There was no consensus on whether a namespace expressed as a relative URI
should be comp
In that case, I'll need to see your java code where you set up the
DOMResult and invoke the transform. Are you using a Node in your
DOMResult constructor? If so, is it a Document Node? If so, does it
already have a child Element? If so, that is your problem because your
DOM structure already h
dmarston01/08/03 07:55:17
Added: test/tests/conf-fail copy29.xml copy29.xsl
Log:
Put these where they can be seen by all participants.
Revision ChangesPath
1.1 xml-xalan/test/tests/conf-fail/copy29.xml
Index: copy29.xml
=
Kevin --
Did this fix your problem?
Gary
"Kevin A. Burton" wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > ="xalan://org.openprivacy.reptile.extensions.LogExtension"
> >
> >> exclude-result-prefixes=""
> >> version="1.0">
> >>
> > Don't you need to define extension-e
>Basically we need to write our own, more effecient, NamespaceSupport
class.
>Joe was going to work on this, but I'm not sure he's found the time.
I haven't really gotten started on it; I desperately had to spend some time
catching up on the DOM... My initial thought was to do our own
lighter-we
tmiller 01/08/03 06:18:15
Modified:java/src/org/apache/xalan/xsltc/trax DOM2SAX.java
Log:
new recursive parse(InputSource) implemented
Revision ChangesPath
1.4 +88 -94xml-xalan/java/src/org/apache/xalan/xsltc/trax/DOM2SAX.java
Index: DOM2SAX.java
===
morten 01/08/03 04:55:26
Modified:java/src/org/apache/xalan/xsltc/compiler Constants.java
DocumentCall.java
java/src/org/apache/xalan/xsltc/dom LoadDocument.java
Log:
Fix for the document() function. The code compiled by DocumentCall now
pas
pauldick01/08/02 12:40:14
xml-xalan/test/tests/capi/smoke - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pauldick01/08/02 12:40:07
xml-xalan/test/tests/capi/extensions - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pauldick01/08/02 12:45:55
Added: test/tests/capi-gold/extensions cextension02.out
cextension01.out
Log:
extension gold files
Revision ChangesPath
1.1 xml-xalan/test/tests/capi-gold/extensions/cextension02.out
Index: cextens
morten 01/08/02 06:25:11
Modified:java/src/org/apache/xalan/xsltc/trax SAX2DOM.java
TransformerFactoryImpl.java TransformerImpl.java
Added: java/src/org/apache/xalan/xsltc/trax
TransformerHandlerImpl.java
Log:
Added an impleme
>This is _not_ a well-formed XML (or HTML)
>document, and may not be represented in the DOM.
Actually, I've overstated that just slightly. If you _had_ to represent
this sort of "xml fragment" in the DOM, you'd do so by either making it
content of a dummy element or of a DocumentFragment (which
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2925
I submitted a bug that occurs when I am testing variables
inside an xsl:choose statement, I think the problem may be
related to variable scope. Now this code may be pushing
the limits on using variables inside XSL, if someone could
take a look at the XSL file and say yes or no on the usage,
that
I'm having problems getting an xml Document as
the result of a transformation. I get a sax exception - Can't have more
than one root on a DOM!
If I use any other result type, Xalan works
fine and I get the output I expect. I double-checked both input files and
the output, and everything
Scott's allowed to go on vacation...
+1
> Given the above, and a weeks vacation that I plan to take this month, I
> [Jason Malcolm]
> Anyone know the timeframe for being able to use TrAX/JAXP API to
> create translets that accept something besides 'StreamSource' (As
> documented in the 'Translets and TrAX' section of
> http://xml.apache.org/xalan-j/readme.html). More specifically, it
> would be helpful if DO
pauldick01/08/02 12:40:22
xml-xalan/test/tests/capi/smoke/smokesubdir - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
pauldick01/08/02 12:51:49
Modified:test/tests/capi/smoke capi01.xsl
Log:
Needed to update relative path name
Revision ChangesPath
1.2 +2 -2 xml-xalan/test/tests/capi/smoke/capi01.xsl
Index: capi01.xsl
Scott & Gulli,
Scott wrote:
> > This does not
> > make sense as the input to the transformation is passed to
> > the TransformHandler as SAX events and not as a Source obj.
>
> I don't understand this statement.
Yes, it is a bit of a mess. I was trying to say that it would not
make sense to cal
>However, the caller is currently free to pass in a
>DocumentFragment or some Element into the DOMResult constructor and
>we'll append to that.
I'd forgotten that option; thanks for the reminder.
I think that's a better answer than trying to do it automagically.
65 matches
Mail list logo
