Return-Path: 
 <general-return-4482-apmail-xml-general-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-general-archive@xml.apache.org
Received: (qmail 73300 invoked by uid 500); 27 Jun 2001 22:23:52 -0000
Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:general-help@xml.apache.org>
list-unsubscribe: <mailto:general-unsubscribe@xml.apache.org>
list-post: <mailto:general@xml.apache.org>
Reply-To: general@xml.apache.org
Delivered-To: mailing list general@xml.apache.org
Received: (qmail 73241 invoked from network); 27 Jun 2001 22:23:48 -0000
Message-ID: <20010627222352.83758.qmail@web12103.mail.yahoo.com>
Date: Wed, 27 Jun 2001 15:23:52 -0700 (PDT)
From: Shane Curcuru <shane_curcuru@yahoo.com>
Subject: Re: Xalan-J 2 and System properties
To: xalan-dev@xml.apache.org, general@xml.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Actually, you just caught us as we're beginning to
split the Xalan discussion lists!

Today and in the future you should address
development-oriented issues about Xalan to
xalan-dev@xml.apache.org  This is for people actively
developing new code on Xalan-J or Xalan-C.

Starting today, you should address user-level issues
like this one to one of our new user lists:
xalan-j-users or xalan-c-users as appropriate.  We
need to publicise these lists and get more of the
Xalan committers and Really Helpful People to start
subscribing to those lists too.

general@xml.apache.org should always be for
cross-project issues - some technical, but also
organizational issues.

Sorry, I don't have an answer for you yet but I'm
forwarding this onto xalan-dev for the time being.

- Shane

---- you "Nick Ridout" <costempd@us.ibm.com> wrote
----
Hi,

I just joined this list and xerces-j-user list.  I
didn't see a xalan forum
so I hope this is an appropriate place for this
question.

I have imported Xalan-J 2.0.0 into IBM VisualAge for
Java (along with
Xerces-J 1.2.3 and Xalan-J 1 Compatability classes).

I'm getting SAX Exceptions.  While tracing, I see
System properties being
queried that are not set.  I suspect that in the
process of importing the
code into VisualAge I am losing these.  When I run
from a (Win NT) dos box
with sun JDK, I don't get exceptions so I'm guessing
the System properties
are set (how does this work?).   I can explicity set
System properties from
code, but how do I know what needs to be set and what
they should be set
to?  Are they documented anywhere?  Has anyone else
running Visual Age had
this problem?

Thanks.

Nick Ridout



=====
<eof aka="mailto:shane_curcuru@lotus.com"
 humor="'A Midsummer Night's Dream' - pick your quote" />

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org