We are facing this strage problem in our code that uses standalone velocity
engine. So far it did send the emails correctly from this standalone program
running (this particular code doesn't reside under struts application) on our
server.
This is the part of teh code we use -
String result = null;
Reader r = null;
StringWriter writer = null;
try {
writer = new StringWriter();
r = new BufferedReader(new FileReader(new File(RESOURCE_PATH,
MAIL_TEMPLATE_FILE)));
boolean status = ve.evaluate(context, writer, "someEmail", r);
if (!status) throw new RuntimeException("Error in evaluation: ");
writer.close();
result = writer.toString();
} catch (ResourceNotFoundException e) {
throw new RuntimeException(e);
} catch (ParseErrorException e) {
throw new RuntimeException(e);
} catch (Exception e) {
throw new RuntimeException(e);
} finally {
if (r!= null) try {r.close();} catch (IOException ioe) {};
if (writer != null) try {writer.close();} catch (IOException ioe) {};
}
return result;
Now this resource path is not changed in last 3 yeas and it's working fine and
sending mails proeprly. Now the mail template (say someMail.vm) refers to 2 VTL
files within itself to parse header and footer for this mail (say header.vm and
footer.vm).
So I have these two new lines added to the the VTL template - "someMail.vm" -
#parse("header.vm")
.......
.......
.......
#parse("footer.vm")
bother these header and footer reside in the same directory to which this
"RESOURCE_PATH" points, the engine is able to parse the mail template correctly,
but it is not able to parse gheader and footer and it fails with
"ResourceNotFoundException ". I am wondering why and how can I fix this???? One
obvious way is to add it to the mail template itself but I don't want to do that
because header & footer will be referred by other pages on site as well.
Why this ResourceNotFoundException exception is thrown though both files reside
in the same RESOURCE_PATH directory? How can I fix this?
TIA,
- Manish
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
