Re: Getting Something into the Boot Classpath
Re: Getting Something into the Boot Classpath
- Subject: Re: Getting Something into the Boot Classpath
- From: Andrew Lindesay <email@hidden>
- Date: Tue, 15 Jul 2008 22:40:09 +1200
Hello Quinton
Yes; I'm trying to work-through a manual-logging startup to avoid this
by loading it from an input stream of a properties file, but I'd
rather use the platform boot sequence for the logging if I can -- so
thought I'd ask. It seems to be tricky -- probably for good reason.
cheers.
How exactly do you initialise the logger? You really shouldn't need
this in the bootclasspath.
..
Am using JUL logging and it gets booted before the main() is run.
I have added some extensions to it and they need JDBC drivers
etc...etc... I don't want to put this stuff into "../lib/ext"
because things are liable to conflict between major releases so I'm
trying to figure out if I can make this happen inside the built
WOA. If you're asking me why MySQL... that's another story. ;)
...
I have to ask why you need to do this.
...
I'm trying to get a jar file to be loaded into the boot classpath
as a WOA loads, but I want the jar to be in the build product ––
is that possible? I was thinking something like this would be
what I would want if it were possible to substitute the $
{APPROOT} somehow!
# JVMOptions == -Xbootclasspath/a:APPROOT/Resources/Java/
jdbc-mysql-connector-java-5.0.6-bin.jar
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden