Hi Miriam,
I'm not familiar with jwma's implementation of image attachement, but
there are recommended practices when dealing with binary content in
portals. Basically :
- you should not use the encodeURL method on any "download" URL, which
includes static images or binary attachements. There should be directly
served by a SERVLET in the same context as the web application.
Depending on how the web application is designed, this might mean that
you have to add logic to determine if an application URL points to a
binary download URL or not.
- you might also run into issues with the session. By linking directly
to the servlet, you will most probably loose the session (unless you are
using a special configuration with Tomcat 5.5). This is due to the fact
that before Tomcat 5.5 sessions are not shared across web application
contexts (Tomcat 5.5 introduces a new configuration option that allows
this, more info here :
http://weblogs.java.net/blog/wholder/archive/2005/02/session_session.html
).
I hope this helps.
Regards,
Serge Huber.
Miriam wrote:
Hi Stephane,
Stéphane Croisier <scroisier <at> jahia.com> writes:
No this should not be the issue as this only
concerns WebDAV file storage (and not any portlet custom storage system).
OK
Have you tried not urlencoding the attachments?
If I don't make urlencoding:
-In the 1st case (when I should see the image embebbed into the mail), it's the
same, the typical red x meaning that image is not avalaible, but here I see the
real size of the image (with urlencoding, a small square always appears).
-In the 2nd case (url), I lose completely the context and I'm redirected to
login and authentificate again.
Which version of JWMA are you using? I noticed
that a new Struts version is currently being
developped (and was recommeded to you in the
SourceForge JWMA discussion forums)...
Stéphane
I'm using version 0.9.8. And yes, I saw Struts version, but I saw it after
changing all the URL for preparing no struts version for Jahia.
I tried to use to see how it worked, but I got an error and I preferred to
continue with the other version because I thought that the images issue was
going to be easier...
I think the problem relies in that the content type is changed to Image/* in
run time, but when you reach the jsp page where is the code for displaying that
image, the header of this jsp page tells that the content-type is html, so
Jahia displays the content of the image as html (for this reason I see strange
characters if I click the URL like in 2nd case). In 1st case, something
similar...
Any sugerence?
Thank you very much
Miriam
At 17:54 28/06/2005, you wrote:
Hello again,
I forgot to say that I'm using jahia 4.1 and according to
http://www.jahia.org/jira/browse/JAHIA-290, maybe this is the problem...
What do you think?
Thanks in advance,
Rgds.
Miriam
