Re: How to use Email Templates for struts?
You can use velocity (http://jakarta.apache.org/velocity/) for generating your templates. When you're done parsing you feed it to the JavaMail API. Velocity is a very powerful template engine and you can even use is for Struts' Views. good luck, Martijn Martin Gainty wrote: Zsolt- Most of the Mail Templaing engines I have seen cost money But there is a shareware template library available at jsourcery http://jsourcery.com/output/java.net/atleap/0.5-rc1/com/blandware/atleap/model/core/MailTemplate.html HTH, Martin- - Original Message - From: Zsolt [EMAIL PROTECTED] To: Struts Users Mailing List struts-user@jakarta.apache.org Sent: Saturday, October 29, 2005 12:45 PM Subject: How to use Email Templates for struts? Hi, I want to send my struts-1.2.7 application emails using templates. Which template engine should I use? Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 31.69 nHz = once a year - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: debugging tomcat with eclipse
I'm running Tomcat within Eclipse with the Sysdeo plugin since the dawn of time. As long as you handle your own context definitions (keep a close watch on the occasional xml sysdeo generates) and define the source directories within the Sysdeo general option, you can debug and trace your source perfectly per thread and look at your variables. Martijn Jay Sheth wrote: HI, It would be great if you could give some hints on how to debug tomcat with eclipse. I have tried the following: * Running tomcat with option jpda start and then running a remote java application to debug but doesn't work. * Running the tomcat application with start option. When I run the webapp, the break point is caught in the code, however it doesn't let me evaluate expression/ see the details of variable, saying The selected stack frame must be associated with a java project in the workspace to perform an evaluation. The project is already in eclipse. We are copying the jar file to the tomcat lib folder and then running the tomcat app. Any help / pointers would be useful. Thanks, Jay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 31.69 nHz = once a year - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
displaying JSP errors on screen
Hello list, Since I've upgraded struts a while back all my JSP generated errors are only seen at the console. How do tinker my config so that I see een JSP error in my browser once more? I'm sorry to ask this question here, bus since the terms of my question are somewhat 'generic' I'm not finding any answers... Thanks in advance, Martijn -- 31.69 nHz = once a year - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: displaying JSP errors on screen
Hi Frank, Thanks for your time. In fact the 'errors' I expect are mostly bean:write tags where the expected object cannot be found in any of the scopes. I used to get those javax.servlet.jsp.JspException: Cannot find bean xyz in any scope in my browser but since I switched to 1.2.x they are all silent and I only see them in my Eclipse console. Which is quite ok, but this is itching for some time now. Could be I'm barking up the wrong tree here and forgot to define a valve/logger/whatever in my context of overlooked some 'tinkering' at another config file which accidentally slipped in all my new projects... regards, Martijn Frank W. Zammetti wrote: Hi Martijn, Struts doesn't inherently do anything (that I'm aware of at least) to stop JSP errors from being displayed in the browser... in fact it's kind of unlikely it could since it's more or less out of the picture by the time the JSP is executing (taglib code notwithstanding). Has anything else changed that could cause this? Anything having to do with JSP error page or something like that? And, a slightly more pointed question :) ... are you sure the errors you expect to see in the browser are really errors in the JSP? Generally-speaking, runtime JSP errors are rare (they certainly should be), and I'm assuming that's what we're talking about here rather than compile-time errors. -- 31.69 nHz = once a year - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: displaying JSP errors on screen
Hi Ulrich, Indeed i do use tiles. I haven't tried a pure jsp as all my pages always descend from some base.jsp which is defined in my tiles-defs. Hmm, but this is something I can work with. Never thought that it could be the tiles plugin... Perhaps some property I can set in the definition or the JspException is silently catched.. I'll get back to you.. thanks, Martijn Ulrich Elsner wrote: Hi, are you using tiles as well? I experienced the same problem some time ago, but only in tile-based .jsp, not in 'pure' jsp. I could not pinpoint the exact time when this started since I wasn't working on the display part at that time but one of the bigger changes I did shortly before I noticed this was the switch from 1.1 to 1.2.4. After some time I got used to looking in the console for problems so eventually I just stopped looking for the reason. Sorry that I can offer no help, but it might console pun not intended you to know that others have the same problem. Ulrich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 31.69 nHz = once a year - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
