Created: (XERCESJ-972) Problem using Xerces with Xinetd sockets 2004-05-31 - By jira@(protected)
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESJ-972
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESJ-972
Summary: Problem using Xerces with Xinetd sockets
Type: Bug
Status: Unassigned
Priority: Major
Project: Xerces2-J
Versions:
2.6.2
Assignee:
Reporter: Bilari
Created: Sun, 30 May 2004 11:54 PM
Updated: Sun, 30 May 2004 11:54 PM
Environment: Redhat Linux Enterprise Linux Server version 3 on i686.
Description:
I downloaded the source code for Xerces-J. It is strewn with System.out.println
and System.err.println. This is all very nice for debug purposes, but there are
major complications when an application relies on Xinetd to invoke itself.
Xinetd invokes the application and passes the socket input stream and output
stream to System.in and System.out respectively. So when in the Xerces code,
System.out or System.err is executed, in the context of an application invoked
via Xinetd, it actually performs a write on the Socket and hence to the
invoking application. This is a very tricky issue and I have temporarily fixed
it by calling:
DOMParser.setProperty("error-handler",null).
But I dont think this is a very elegant way of doing it. So I request you to
consider the fact that it is a VERY bad idea of having System.outs or System
.errs in the code. Use proper Logging. Log4J is good, but it also has System
.outs and System.errs in its code.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-dev-help@(protected)
|
|
