[
https://issues.apache.org/jira/browse/XALANJ-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972885#action_12972885
]
Dave Brosius commented on XALANJ-2169:
--
>>> This bug is still present
[
https://issues.apache.org/jira/browse/XALANJ-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966236#action_12966236
]
Dave Brosius commented on XALANJ-2526:
--
While the memory consumption is concer
[
https://issues.apache.org/jira/browse/XALANJ-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965986#action_12965986
]
Dave Brosius commented on XALANJ-2526:
--
does defining
ANT_OPTS=-Xss=1m
(Ordinary problems in
Xalan projects. Anybody can view the issue.)
Components: XPath
Affects Versions: 2.7.1
Reporter: Dave Brosius
Fix For: The Latest Development Code
Attachments: uselesscode.diff
(Minor) Code has guard code that will never fire
[
https://issues.apache.org/jira/browse/XALANJ-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788816#action_12788816
]
Dave Brosius commented on XALANJ-2510:
--
I'm an observer and lover of xalan
[
https://issues.apache.org/jira/browse/XALANJ-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676091#action_12676091
]
Dave Brosius commented on XALANJ-2487:
--
interestingly,
name(//proces
security risk; visible to anyone (Ordinary problems in
Xalan projects. Anybody can view the issue.)
Components: XSLTC
Affects Versions: The Latest Development Code
Reporter: Dave Brosius
Priority: Trivial
Fix For: The Latest Development Code
(Ordinary problems in
Xalan projects. Anybody can view the issue.)
Components: Xalan-extensions
Affects Versions: The Latest Development Code
Reporter: Dave Brosius
Priority: Trivial
Fix For: The Latest Development Code
Attachments
: No security risk; visible to anyone (Ordinary problems in
Xalan projects. Anybody can view the issue.)
Components: XSLTC
Affects Versions: The Latest Development Code
Reporter: Dave Brosius
Priority: Trivial
Fix For: The Latest Development Code
Xalan-extensions
Affects Versions: The Latest Development Code
Reporter: Dave Brosius
If you use XPathFactory to create a new XPath inside an extension function,
the xpath evaluation fails
because the context node is a DTMNodeProxy, and the wrong XPathContext is
referred to,
rowse/XALANJ-2421
Project: XalanJ2
Issue Type: Bug
Components: Serialization
Affects Versions: 2.7.1
Reporter: Dave Brosius
Priority: Minor
Fix For: 2.7.1
Attachments: MutableAttrListImplTest.java
MutableAttrListIm
[
https://issues.apache.org/jira/browse/XALANJ-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2114.
Fix applied correctly
> odd non-shortcircuited boolean lo
[
https://issues.apache.org/jira/browse/XALANJ-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2061.
Patch applied correctly (with noted differences)
> [Patch] Cleanup some dead c
[
https://issues.apache.org/jira/browse/XALANJ-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2208.
Patch applied correctly
> [PATCH] removal of some cruft that does noth
[
https://issues.apache.org/jira/browse/XALANJ-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2217.
Patch applied correctly (with noted missing String.valueOf(ch) change)
> [PATCH] cleaup some Str
[
https://issues.apache.org/jira/browse/XALANJ-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2224.
Patch applied correctly
> [PATCH] Switch to use 'new' co
[
https://issues.apache.org/jira/browse/XALANJ-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2268.
Patch applied correctly
> [PATCH] Simplify some dubious URI c
[
https://issues.apache.org/jira/browse/XALANJ-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2284.
Patch applied correctly
> [PATCH] remove needless synchronizat
[
https://issues.apache.org/jira/browse/XALANJ-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2283.
> [PATCH] remove needless synchronizat
[
https://issues.apache.org/jira/browse/XALANJ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2307.
> [PATCH] remove some unused code
> ---
>
>
[
https://issues.apache.org/jira/browse/XALANJ-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2236.
Patch applied correctly
> [PATCH] clean up static calls thru instance referen
[
https://issues.apache.org/jira/browse/XALANJ-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius closed XALANJ-2221.
Patch applied correctly
> [PATCH] System.arraycopy is more efficient, so use
[
https://issues.apache.org/jira/browse/XALANJ-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557115#action_12557115
]
Dave Brosius commented on XALANJ-2221:
--
Fixed
> [PATCH] System.arraycopy
[
http://issues.apache.org/jira/browse/XALANJ-2346?page=comments#action_12452555
]
Dave Brosius commented on XALANJ-2346:
--
Oops, forgot to set the Priority, sorry
> [PATCH] fixes for faulty NaN handl
Development Code
Reporter: Dave Brosius
By definition, NaN is not equal to itself, therefore
if (d == Double.NaN)
will always be false. Changed such instances to
if (Double.isNaN(d))
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact
[
http://issues.apache.org/jira/browse/XALANJ-2242?page=comments#action_12448373
]
Dave Brosius commented on XALANJ-2242:
--
Sun's implemenation of java.lang.Thread calls wait and notify on 'this' for
it's own purposes.
Reporter: Dave Brosius
Priority: Trivial
Attachments: remove_unusd.diff
remove some code that isn't used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/s
[PATCH] remove needless synchronization
---
Key: XALANJ-2284
URL: http://issues.apache.org/jira/browse/XALANJ-2284
Project: XalanJ2
Type: Improvement
Versions: Latest Development Code
Reporter: Dave Brosius
several
[PATCH] remove needless synchronization
---
Key: XALANJ-2283
URL: http://issues.apache.org/jira/browse/XALANJ-2283
Project: XalanJ2
Type: Improvement
Versions: Latest Development Code
Reporter: Dave Brosius
Reporter: Dave Brosius
Priority: Trivial
Some URI code does unnecessary histrionics which just makes the code
confusing.. Patch just simplifies things..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
: Other
Versions: Latest Development Code
Reporter: Dave Brosius
Priority: Minor
Calling wait or notify/notifyAll on the thread object itself, interferes with
the basic Thread management built into the jvm, causing spurious thread states,
including threads waking up when not expected
Reporter: Dave Brosius
Priority: Trivial
for code documentation purposes, it is better to call static methods thru the
class rather than an instance of the class, especially in the
myThread.yield() call, when in fact, you are calling it on the current thread,
not necessarily myThread.
patch
[PATCH] Switch to use 'new' collection apis
---
Key: XALANJ-2224
URL: http://issues.apache.org/jira/browse/XALANJ-2224
Project: XalanJ2
Type: Improvement
Versions: Latest Development Code
Reporter: Da
Reporter: Dave Brosius
Priority: Trivial
System.arraycopy is better performing that simple manual array copying in a loop
1) It's native
2) it avoids all the array range check, except one up front.
This patch changes this.
--
This message is automatically generated by JIRA.
-
If you think i
: Dave Brosius
Priority: Trivial
This patch cleans up some String class sillyness like creating an object just
to convert to string, or calling toString on a String, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
Type: Bug
Components: XPath-function
Versions: Latest Development Code
Reporter: Dave Brosius
The resolveFunction does not handle the className variable correctly resulting
in possible NPEs
For instance className is unitialized in the else, but used none the less
Development Code
Reporter: Dave Brosius
Priority: Minor
Attachments: fix_equals.diff
A QName is attempted to be .equals with a string. This will always be false.
compare the stringrep instead
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly
Reporter: Dave Brosius
Priority: Trivial
Attachments: remove_cruft.diff
Found some arbitrary code that has no value, removed it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira
This question probably has been asked many times
before, and i realize it's beyond xalan's devs to be the authority on everything
sax, but indulge me if you wouldn't mind.
Was there any consideration to have the
startElement signature return a boolean which informed the parser as to wheth
odd non-shortcircuited boolean logic
Key: XALANJ-2114
URL: http://issues.apache.org/jira/browse/XALANJ-2114
Project: XalanJ2
Type: Bug
Versions: CurrentCVS
Environment: win32 xp
Reporter: Dave Brosius
Priority
: Dave Brosius
Priority: Minor
Three instances of TranformFactoryImpl's implement the method newXMLFilter.
In each case these methods create an Exception but do not throw it. It would
seem that that was the intent of creating the exception.
--
This message is automatically generated by
: Dave Brosius
In class: org.apache.xalan.xsltc.dom.NodeSortRecord
In method: public final void initialize(int node, int last, DOM dom,
SortSettings settings)
The following lines will cause a ClassCastException as a cast from
Class to CollatorFactory is attempted.
Object candObj
The newXMLFilter code in the the
TransformerFactoryImpls create exceptions but don't throw them.. seems
odd.
--dave
TypeDescendantIterator actually
needed?
thanks, dave
i confused?
--dave
Hmm, i suppose i could derive from SAXSource, or
DOMSource which would probably be ok. But am I correct that Source, itself, is
closed to extension?
- Original Message -
From:
Dave Brosius
To: xalan-dev@xml.apache.org
Sent: Saturday, March 12, 2005 12:59
AM
If I wanted to create my own implementation of
Source, i don't see how the transformer uses it, as the methods available are
just the cryptic
java.lang.String
getSystemId()
Get the
system identifier that was set with setSystemId.
void
set
org.apache.xalan.serialize.SerializerUtils
public static boolean isDefinedNSDecl(
SerializationHandler serializer,
int attr,
DTM dtm)
does this:
if ((null != uri) && uri.equals(dtm.getStringValue(attr)))
return true;
this part:
uri.equals(dtm.getStr
org.apache.xalan.xsltc.compilerAttributeSet
parseContents does this:
if ((_name == null) || (_name.equals(EMPTYSTRING))) {
as _name is a QName, and QName equals uses ==
this if statement is the same as
if (_name == null)
which is probably not what is wanted.
Probably want
if ((_name == null) ||
[Patch] Cleanup some dead code
--
Key: XALANJ-2061
URL: http://issues.apache.org/jira/browse/XALANJ-2061
Project: XalanJ2
Type: Improvement
Versions: CurrentCVS
Reporter: Dave Brosius
Priority: Trivial
This patch cleans
[ http://issues.apache.org/jira/browse/XALANJ-2061?page=history ]
Dave Brosius updated XALANJ-2061:
-
Attachment: simple_dls.patch
> [Patch] Cleanup some dead code
> --
>
> Key: XALANJ-2061
>
In org/apache/xalan/xsltc/dom/DocumentCache is this method
private synchronized void replaceDocument(String uri, CachedDocument doc) {
CachedDocument old = (CachedDocument)_references.get(uri);
if (doc == null)
insertDocument(uri, doc);
else
_references.put(uri, doc);
}
This looks suspect t
Hi folks,
Not to be stupid what are these?
soft-virii?
- Original Message -
From:
Donald
To: Xalan-dev
Sent: Tuesday, August 10, 2004 1:51
PM
Subject: Re:
>fotoinfo:)
-To
unsubscr
Sorry to pester, but does anyone have an idea on this?
Dave
Dave Oxley wrote:
Sorry if this message has already come through to this list. I
couldn't see it, so I'm now subscribed and resending!
Using Xalan 2.5.2 I get the following exception when trying to
transform a DOM with a
something I've done?
Cheers.
Dave.
16 Feb 2004 16:52:35,500 FATALCriticalException -
javax.xml.transform.TransformerException: org.xml.sax.SAXException:
Attempt to output character of integral value 233 that is not
represented in specified output encoding of .
javax.xml.trans
Just downloaded the latest xalan 2.5.2. The xalan.jar includes some
org.apache.bcel classes, but seemingly not the complete, latest
version
of BCEL (5.1). Specifically, the following things are missing:
class: org.apache.bcel.util.Repository (although
org.apache.bcel.Repository is there)
c
: Re: Problems using an istream in XSLTInputSource
>
>
> Hey Dave,
>
> I think it may be this rather horrible bug:
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13190
>
> try this diff and see if it fixes the problem:
>
>cvs -z9 diff Std
erely,
Dave Jarvis
--
$ set | grep CROOT
XALANCROOT=/usr/local/src/xml-xalan
XERCESCROOT=/usr/local/src/xerces-c-src2_0_0
$ pwd
/usr/local/src/xml-xalan/c/src
$ uname -a
Linux xerces 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown
$ ./runConfigure -p linux
Generating makefiles with the foll
Could there be some reason why dld is not looking at SHLIB_PATH?
Thank you very much in advance,
Dave
Thanks Gary,
Sorry to make you look into an already fixed problem. I looked for a bug
report before reporting this but didn't find one. I'll try it out with
2.2.D06.
-Dave
-Original Message-
From: Gary L Peskin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001
nd as Gary verified, strings are always supposed to be
converted to numbers in comparisons, and if both entities in a comparison
are nodes, then apparently the proper behavior is to attempt to convert the
text of both to numbers and then compare.
-Dave
-Original Message-
From: everett stauff
than .
Dave
-Original Message-
From: Dave [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 7:01 PM
To: [EMAIL PROTECTED]
Subject: RE: RelationalExpr doing alpha comparisons?
Gary,
Thanks for your response. I'm using Xalan 2.1.0. I'm invoking xalan
through the JAXP
you would like a prime power factorization for:
Again, the element that shows this issue is:
,
whereas
produces the correct result.
The same result can be produced when specifying a number as a string as in:
Please let me know what you figure out.
Dave
-Original Message-
From:
r at all this. Is this a problem with Xalan,
Michael Kay, or me?
Thanks,
Dave Kaplan
Any chance of http://xml.apache.org/mail.html being updated? (That would
help with the publicity!)
Dave Connet
> -Original Message-
> From: Shane Curcuru [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 27, 2001 5:24 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Split
That is what I have been using, they send you a message that after you click
and send mail to the unsubscribe.I even turned HTML off and just use plain
text in my empty reply.
Still get the stuff.
Pool
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent:
SP5 works fine. We're using it.
Just remember to re-apply the Dinkumware patches _after_ installing the SP.
Dave Connet
> -Original Message-
> From: Mike Garcia [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 1:38 PM
> To: [EMAIL PROTECTED]
> Subject: Re: P
67 matches
Mail list logo
