(No subject)
(No subject)
- Subject: (No subject)
- From: email@hidden
- Date: Mon, 13 Oct 2003 11:57:57 CDT
- Priority: 3 (Normal)
[demime could not interpret encoding binary - treating as plain text]
The problem is that it's not just the method name that's deprecated, it's
actually the BEHAVIOR you are trying to accomplish. Needing to know the
actual path of the resource, that's deprecated. This is presumably
because WO is trying to move to storing resources in a .jar file (perhaps
for J2EE deployment it already does not, not sure), in which case there
isn't really a file path to the resource. The resource is inside a jar file.
By deprecating that method, they're trying to get you to avoid designs
where you need to know a file path to a resource, because this may not
always be possible, in every deployment configuration.
I'm curious why you do need to know the file path, I've never needed this
before myself. But I'm sure there are reasons. You could either try to
redesign your code to not need this, or you could just keep using it, and
deal with it, if it ever becomes impossible because of your deployment
configuration or future changes to WO.
"Robert A. Decker" <email@hidden> writes:
Is there a method around that gives the same results without a deprecated
warning method? Nothing is apparent in WOResourceManager.
There are times where I really do want a path, and not an InputStream or
byte array.
thanks,
Robert A. Decker
http://www.robdecker.com/
_______________________________________________
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.