You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Dave <sn...@gmail.com> on 2007/09/21 05:47:17 UTC
Texen / Velocity inserting 0 (null byte) values
We use Velocity 1.5 to generate the database creation scripts for
Roller. In the latest 4.0 release candidate a PostgreSQL user had
problems because there are some null bytes in the scripts generated by
Velocity / Texen. The null bytes are not in the source templates.
Here's how we run Texen:
<texen
controlTemplate="control.vm"
contextProperties="${sql}/dbscripts.properties"
useClasspath="true"
outputDirectory="${build.dbscripts}"
outputFile="README.txt" />
I tried saving the input templates with UTF-8 encoding, but that didn't help.
I tried adding inputEncoding="UTF-8" outputEncoding="UTF-8" but that
didn't help.
Any ideas what I'm doing wrong?
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org
Re: Texen / Velocity inserting 0 (null byte) values
Posted by Will Glass-Husain <wg...@gmail.com>.
Ah, great - makes more sense. Thanks for the followup.
WILL
On 9/22/07, Dave <sn...@gmail.com> wrote:
>
> On 9/22/07, Will Glass-Husain <wg...@gmail.com> wrote:
> > That's pretty strange. Haven't heard of this before.
>
> > On 9/20/07, Dave <sn...@gmail.com> wrote:
> > > We use Velocity 1.5 to generate the database creation scripts for
> > > Roller. In the latest 4.0 release candidate a PostgreSQL user had
> > > problems because there are some null bytes in the scripts generated by
> > > Velocity / Texen. The null bytes are not in the source templates.
>
> Hi Will,
>
> Sorry... you can disregard my previous email. Turns out, I was wrong
> and there *was* a problem in the input files.
>
> - Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: Texen / Velocity inserting 0 (null byte) values
Posted by Dave <sn...@gmail.com>.
On 9/22/07, Will Glass-Husain <wg...@gmail.com> wrote:
> That's pretty strange. Haven't heard of this before.
> On 9/20/07, Dave <sn...@gmail.com> wrote:
> > We use Velocity 1.5 to generate the database creation scripts for
> > Roller. In the latest 4.0 release candidate a PostgreSQL user had
> > problems because there are some null bytes in the scripts generated by
> > Velocity / Texen. The null bytes are not in the source templates.
Hi Will,
Sorry... you can disregard my previous email. Turns out, I was wrong
and there *was* a problem in the input files.
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org
Re: Texen / Velocity inserting 0 (null byte) values
Posted by Will Glass-Husain <wg...@gmail.com>.
Hi Dave,
That's pretty strange. Haven't heard of this before.
Are you generating from Windows or Linux? What version of the JDK? Just
wondering if that would make a difference. There used to be inconsistent
line endings with Anakia file generation that were different from Windows
and Linux. Probably not, but worth trying.
Can you post a bug on this? I'll try to work through it. If you have any
time to make a small test case that would really speed things up.
WILL
On 9/20/07, Dave <sn...@gmail.com> wrote:
>
> We use Velocity 1.5 to generate the database creation scripts for
> Roller. In the latest 4.0 release candidate a PostgreSQL user had
> problems because there are some null bytes in the scripts generated by
> Velocity / Texen. The null bytes are not in the source templates.
>
> Here's how we run Texen:
>
> <texen
> controlTemplate="control.vm"
> contextProperties="${sql}/dbscripts.properties"
> useClasspath="true"
> outputDirectory="${build.dbscripts}"
> outputFile="README.txt" />
>
> I tried saving the input templates with UTF-8 encoding, but that didn't
> help.
>
> I tried adding inputEncoding="UTF-8" outputEncoding="UTF-8" but that
> didn't help.
>
> Any ideas what I'm doing wrong?
>
> - Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com