Re: (No subject)
Re: (No subject)
- Subject: Re: (No subject)
- From: Hsu <email@hidden>
- Date: Mon, 13 Oct 2003 20:58:24 -0700
Well, for example, if you use lucene and just want to do a quick check
to
see if a document index exists, you can just check for the existence of
the index directory. That's not a great example in my case though
because
I actually keep my lucene index under ~ even though it's on a
per-application basis.
You definitely wouldn't be storing something like that in a .jar.
But you also probably won't be storing something like that in the
application or framework bundle, would you?
That sounds like data, not code or resources.
Another example is a config file that we keep as a Resource in the
application. We sometimes have need to edit the file on the server
while
the application is running, and keeping it in a .jar adds extra work. I
could probably move this to ~ as well, but this one really does make
sense
to keep under the application.
Not a _whole_ lot of extra work, but that's a valid point.
I can also see times where third-party code may only accept a path as
an argument. Again, I don't have a good example - I thought I did with
reportmill, but did find the consructor that takes an InputStream.
This is why the path APIs are only deprecated, not removed :)
Does it really make sense to store application resources in a jar? Is
that
just how it's done in java apps?
Yes. (c.f. WAR format)
Karl
--
The Compleat Demystified Idiots Guide to the Zen of Dummies in a
Nutshell in Seven Days, Unleashed
Homepage:
http://homepage.mac.com/khsu/index.html
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.