Hi Jaime, I think it may be choking on the download function because you are describing an error I have seen. To check, you could try a hyperlink to another "normal" component and see if it gets returned as you expect. If it is the download function that is the culprit, you may want to check the wiki for the "return file to browser" stuff. Off the top of my head I remember something about having to change the headers returned to the browser for IE. This is the code that I am using in my download class in case it helps: public void appendToResponse( WOResponse aResponse, WOContext aContext) { super.appendToResponse(aResponse, aContext); try { // this is to stop the IE problems: aResponse.disableClientCaching(); aResponse.removeHeadersForKey("Cache-Control"); aResponse.removeHeadersForKey("pragma"); aResponse.setContent(artifactToDownload.getFile()); // Set the headers for browser want to save instead of displaying aResponse.setHeader("application/octet-stream", "content-type"); // Give the data a default name to save as String contentDisposition = "attachment;filename=\""+artifactToDownload.filename()+"\""; aResponse.setHeader(contentDisposition, "content-disposition"); } catch(Exception e) { aResponse.setContent("There was a problem downloading the file you specified."); e.printStackTrace(); } } -- It's like driving a car at night. You never see further than your headlights, but you can make the whole trip that way. E. L. Doctorow from Sunbeams: http://www.thesunmagazine.org On 21 Sep 2006, at 4:45 PM, Jaime Magiera wrote:
|
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com