|
From: Andy D. <an...@ma...> - 2005-03-03 18:54:19
|
=46rom what I can tell, this appears to be related to JavaMail? If so, it = is=20 not what I need. I'm using Spring's Resource interface to access, well,=20 general resources. Some of these resources actually end up residing on a w= eb=20 server, and may even have a .jsp file extension - even though the .jsp page= =20 might end up generating a binary file of some specific mime type, which=20 the .jsp page will manually set on output. In this case I cannot rely on=20 file extension. It would be useful if the Resource interface could expose = to=20 me a simple way to inspect the mime type. If it is a classpath/file/simple= =20 resource, then it could use the activation framework and detect the mime ty= pe=20 by the file extension (hiding all the gory details from me) - if it is a=20 Resource loaded from a web server, then it could return the mime type that= =20 was returned by the web server - and so on. Am I approaching this the wron= g=20 way? - Andy On Thursday 03 March 2005 10:12 am, Matt Sgarlata wrote: > The mime type support in Spring is based on the mime type support in the > Java Activation Framework. There are plans to add additional MIME types > to Spring. See: > > http://opensource.atlassian.com/projects/spring/browse/SPR-637 > > Does this answer your question? > > Matt |