Re: Endorsed dir in Tomcat

[Dain Sundstrom]

Do people actually want to do that?  Anyway, you can change the parser 
if you want.  The user just needs to pass the -Djava.endorsed.dirs 
command line arg to the server.  My new code simply appends our dir to 
the system property, so users can always put their stuff first.  Of 
course they will have to add their parser to classpath, which is more 
if an issue as our class path comes from the manifest, which can't be 
overridden.  Also, if you change the xml parser, you will no longer be 
running a certified server (once we are certified) as the parser is 
part of the J2EE tested binary.

-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Feb 18, 2005, at 10:10 AM, Alan D. Cabrera wrote:
 Virtually, it's a single endorsed dir anyway, no?� Not sure how the 
mechanics of where the dirs are and how the system property is 
relevant to the issue of parser versions.

 Regards,
 Alan
 anita kulshreshtha wrote:
This should work for now. I am not sure if Tomcat
users will be unhappy if they could not use a parser
different than Geronimo. May be Jeff can comment on
this.
Thanks
Anita
--- Dain Sundstrom <[EMAIL PROTECTED]>  wrote:
Geronimo is required to ship xerces 2, and the only
way to get the JVM
to pick up the parser is to set the endorsed dir
system property and to
adding the xml parser to the manifest class path.
We now set the
system property in our main boot class based on a
manifest entry in the
startup jar.  This allows us to control the setting
of the endorsed
property, without having to resort to a messy shell
script.
Is there something else you want added to the
endorsed directory, or
something we need to do differently to make tomcat
happy?
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Feb 16, 2005, at 7:18 AM, Jeff Genender wrote:
I think there has been some discussion about a
Geronimo-wide endorsed
dir as there actually were some other parts of
Geronimo (or supporting
tools) that also required it.  I think adc and
dain were chatting
about this not too long ago, so hopefully they can
chime in on this.
I definately would like them to comment here
before we get a patch on
this as we may just need to remove the endorsed
setting code in the
TomcatContainer and this may be fixed.
anita kulshreshtha wrote:
Hi all (Jacek, Jeff),
    The latest changes (rev 153934) to include
endorsed dir in lib and starting server.jar with
endorsed dirs option do not work. Currently
Tomcat can
not be started without deleting
lib\endorsed\xercesImpl...jar. Having an
"endorsed"
property is a good idea. But this is a tomcat
feature
and only tomcat should be started with endorsed
dir
option. If you want, I can submit a fix for this.
Regards
Anita
__________________________________ Do you Yahoo!?
Yahoo! Mail -
Easier than ever with enhanced search. Learn
more.
http://info.mail.yahoo.com/mail_250
--
Jeff Genender
 http://geronimo.apache.org


__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
 http://info.mail.yahoo.com/mail_250