On Thursday 10 February 2005 17:50, Nathan Bubna wrote:
i only rarely put things directly into the
request myself. i mostly use tools to access my request scoped data.
those are easy enough to keep track of in my toolbox.xml file.
So how do u go on about data that you want to make available
On Friday 11 February 2005 07:21, Shinobu Kawai wrote:
resource files and charset might be your problem. Do you mean
your resource files have non-ascii characters in it? If so, that's
your problem. They must be escaped java-wise like \u1234.
cf.
Just to point out that the data stored in the DB is using cp-1253 :/
So far I didnt have to deal with ResourceBundles so all text was inside the
HTML templates.
I cant seem to understand why setting the output encoding in
velocity.properties to ISO-8859-7 would cause the data coming from the
On Friday 11 February 2005 07:21, Shinobu Kawai wrote:
They must be escaped java-wise like \u1234.
Shinobu I did that and it worked. Thanks.
Although I find it a bit hard to accept that any resource bundle must be in
that format. That makes life a bit harder :/
Still I cannot understand why
I was wondering if there is a convenient way to restrict method calls on
objects I put into VelocityContext. I use Velocity templates to do
dynamic renders high-traffic websites, and I instantiate VelocityEngine
objects along with various POJOs that Spring assembles. These POJOs are
sort of
Hi Markos,
They must be escaped java-wise like \u1234.
Shinobu I did that and it worked. Thanks.
Welcome. :)
Although I find it a bit hard to accept that any resource bundle must be in
that format. That makes life a bit harder :/
It's all Java stuff. Java stores data in memory as
Steve O'Hara [EMAIL PROTECTED] wrote:
I was invalidating the session when the user sends a logout request. It's
a
bit belt and braces but it insures that the session is destroyed and gets
the user back to known state i.e. as though they were first visiting the
site.
I've been doing the same
Serge Knystautas [EMAIL PROTECTED] wrote:
I was wondering if there is a convenient way to restrict method calls on
objects I put into VelocityContext. I use Velocity templates to do
dynamic renders high-traffic websites, and I instantiate VelocityEngine
objects along with various POJOs
Mike Kienenberger wrote:
Well, the easy answer to this part of the question is to implement a custom
Uberspect.
http://jakarta.apache.org/velocity/api/org/apache/velocity/util/introspection/Uberspect.html
There's examples of this on the wiki:
Serge Knystautas [EMAIL PROTECTED] wrote:
Mike Kienenberger wrote:
Well, the easy answer to this part of the question is to implement a
custom
Uberspect.
http://jakarta.apache.org/velocity/api/org/apache/velocity/util/introspection/Uberspect.html
There's examples of this on the
On Friday 11 February 2005 17:45, Shinobu Kawai wrote:
It's all Java stuff. Java stores data in memory as Unicode, so
everything going into Java must be converted into Unicode. Currently,
there is no way Java can tell whether a file is ascii or Greek or
Japanese or whatever. So, you have to
Velocity itself has a rule to accept all public methods. It is up to
the programmer to decide which methods to make available to Velocity
by making the methods public. Velocity, even JAVA, has no way of
knowing if a method will change the underlying class. Making a class
immutable is up to the
On Friday 11 February 2005 17:45, Shinobu Kawai
wrote:
It's all Java stuff. Java stores data in memory
as Unicode, so
everything going into Java must be converted into
Unicode. Currently,
there is no way Java can tell whether a file is
ascii or Greek or
Japanese or whatever. So,
Thanks, Mike. It does look like that's the only decent option. I'll
commit the change to the svn head.
On Fri, 11 Feb 2005 10:50:06 -0500, Mike Kienenberger
[EMAIL PROTECTED] wrote:
Steve O'Hara [EMAIL PROTECTED] wrote:
I was invalidating the session when the user sends a logout request.
On Fri, 11 Feb 2005 07:45:19 -0800, Shinobu Kawai
[EMAIL PROTECTED] wrote:
...
Still I cannot understand why setting the output.encoding to ISO-8859-7 in
velocity.properties has that effect I mentioned earlier.
Even more since you pointed out that the output.encoding doesn't matter
On Fri, 11 Feb 2005 10:15:20 +0200, Markos Charatzas [EMAIL PROTECTED] wrote:
On Thursday 10 February 2005 17:50, Nathan Bubna wrote:
i only rarely put things directly into the
request myself. i mostly use tools to access my request scoped data.
those are easy enough to keep track of in my
Hi Nathan,
Still I cannot understand why setting the output.encoding to ISO-8859-7 in
velocity.properties has that effect I mentioned earlier.
Even more since you pointed out that the output.encoding doesn't matter
unless
you're using VelocityServlet or Anakia and Im using
On Fri, 11 Feb 2005 13:59:38 -0800, Shinobu Kawai
[EMAIL PROTECTED] wrote:
Hi Nathan,
Still I cannot understand why setting the output.encoding to ISO-8859-7
in
velocity.properties has that effect I mentioned earlier.
Even more since you pointed out that the output.encoding
18 matches
Mail list logo
