You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Fedor Karpelevitch <fe...@home.com> on 2001/04/23 06:16:46 UTC
[JOB]Looking for job.
Hi!
(I remember it was said that this kind of posting is Ok here, so here we go)
I am looking for a SW Engineer position. Working with Turbine and/or Velocity
would be great, but I would say that more generally I am looking for
server-side Java, SQL, XML and so on.
I am looking for something in SF Bay Area, but may consider elsewhere.
I have expirience with various stuff and am generally bright guy ;-)
I do not have any visa-related issues.
My resume is available upon request.
Best regards.
Fedor.
Re: [PATCH]vtl-reference-guide.xml
Posted by Martin Poeschl <mp...@marmot.at>.
I'm not sure, but this way it works for me ;-)
martin
Index: ./xdocs/vtl-reference-guide.xml
===================================================================
RCS file: /home/cvspublic/jakarta-velocity/xdocs/vtl-reference-guide.xml,v
retrieving revision 1.26
diff -u -r1.26 vtl-reference-guide.xml
--- ./xdocs/vtl-reference-guide.xml 2001/03/27 00:39:24 1.26
+++ ./xdocs/vtl-reference-guide.xml 2001/04/23 21:22:59
@@ -225,7 +225,7 @@
<source><![CDATA[
<table>
#foreach( $customer in $customerList )
- <tr><td>$velocityCounter</td><td>$customer.Name</td></tr>
+ <tr><td>$velocityCount</td><td>$customer.Name</td></tr>
#end
</table>
]]></source>
The command completed successfully.
Re: [PATCH] org.apache.velocity.texen.ant.TexenTask (exception handling
and documentation)
Posted by Jason van Zyl <jv...@apache.org>.
Robert Burrell Donkin wrote:
>
> org.apache.velocity.texen.ant.TexenTask.execute() currently deals with
> exceptions thrown during the generation process by printing a standard
> stack trace. IMHO this is not the best way to handle them. exceptions
> should be rethrown as org.apache.tools.ant.BuildException's for the
> following reasons:
>
> 1. ant understands that when a BuildException is thrown, an error has
> prevented the task from completing. processing of the build then stops.
> this is very useful when you have a single ant build file containing
> both code generation tasks and compilation tasks - if a code generation
> task fails, then compilation does not proceed.
> 2. ant BuildExceptions can contain a causal exception. this means that
> more useful messages can be given to the user rather than a simple stack
> trace. ant does quite a good job of formatting BuildExceptions - texen
> should take advantage.
> 3. (as far as i can see) catching and rethrowing seems to be the ant way
> to do these things.
>
> this patch catchs exceptions and rethrows them as BuildExceptions for
> Ant to deal with. known velocity exceptions are caught and rethrown with
> additional messages.
>
> this patch also contains some small improvements to the (javadoc)
> documentation.
Thanks, I will apply this today. Sorry for the delay. Have been sick
the last couple of days. Thanks for the patch :-)
>
> - robert
>
> ------------------------------------------------------------------------
> Name: TexenTask_patch.txt
> TexenTask_patch.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> ------------------------------------------------------------------------
--
jvz.
Jason van Zyl
jvanzyl@apache.org
http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org
Re: [PATCH] org.apache.velocity.texen.ant.TexenTask (exception
handlingand documentation)
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
I think you are right here. I like the patches. I will put in the
javadoc fixes, and if no one squawks, will do the code paches as well a
little later today. I am not a Texen expert so will wait a few hours.
geir
Robert Burrell Donkin wrote:
>
> org.apache.velocity.texen.ant.TexenTask.execute() currently deals with
> exceptions thrown during the generation process by printing a standard
> stack trace. IMHO this is not the best way to handle them. exceptions
> should be rethrown as org.apache.tools.ant.BuildException's for the
> following reasons:
>
> 1. ant understands that when a BuildException is thrown, an error has
> prevented the task from completing. processing of the build then stops.
> this is very useful when you have a single ant build file containing
> both code generation tasks and compilation tasks - if a code generation
> task fails, then compilation does not proceed.
> 2. ant BuildExceptions can contain a causal exception. this means that
> more useful messages can be given to the user rather than a simple stack
> trace. ant does quite a good job of formatting BuildExceptions - texen
> should take advantage.
> 3. (as far as i can see) catching and rethrowing seems to be the ant way
> to do these things.
>
> this patch catchs exceptions and rethrows them as BuildExceptions for
> Ant to deal with. known velocity exceptions are caught and rethrown with
> additional messages.
>
> this patch also contains some small improvements to the (javadoc)
> documentation.
>
> - robert
>
> ------------------------------------------------------------------------
> Name: TexenTask_patch.txt
> TexenTask_patch.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> ------------------------------------------------------------------------
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Re: texen (and ecs2)
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
Robert Burrell Donkin wrote:
>
> (i can't think of a good way to say this, so i'll just dive straight in.
> i'm sure that people'll straighten me out when i go wrong...)
>
> ecs2 is a new version of jakarta-ecs with a new internal structure.
> there's a lot of repetitive leg-work involved in converting code from
> the old structure to the new.
> i've been working on using code generation with texen to (hopefully)
> make this easier and quicker.
> the idea is to generate elements and attributes from DTDs (via
> xml-schema) and velocity templates.
sounds cool
>
> i've been working on this for the last couple of weeks and i feel that
> i've proved the concept and have stuff which'll do pretty much what's
> needed :-)
>
> what i need to do now is to tidy stuff up, document and make it
> available so that other ecs people can take a look and use it. the
> problem is that i have made general changes and enhancements.
>
general changes to texen? Are the appropriate here? you should give us
a look-see if you want....
> i think that the best thing would be for me to take this code and give
> it a home (for the moment) in the ecs project. that way, it can be used
> over there without worrying.
If the code makes changes to the texen core, and it is deemed good and
of general use by the Texenites, then it prollie should be rolled into
velocity.
(Of course, I wonder if we should graduate texen out of the Velocity
core and into a separate space, like in commons, but that's for another
discussion, I suppose...)
> i will post the design ideas in the code (and patches if they're wanted)
> back to this list and take stuff from there. (i also have some nice
> examples such as generating xml object-model parsers from xml-schema.)
post away. that stuff sounds neat.
> (i'm pretty sure that the generation stuff won't make it into the ecs2
> release so we can worry about where code should live to generate ecs
> element models from DTDs later on.)
>
> comments? is this a good plan?
>
> - robert
geir
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
texen (and ecs2)
Posted by Robert Burrell Donkin <ro...@mac.com>.
(i can't think of a good way to say this, so i'll just dive straight in.
i'm sure that people'll straighten me out when i go wrong...)
ecs2 is a new version of jakarta-ecs with a new internal structure.
there's a lot of repetitive leg-work involved in converting code from
the old structure to the new.
i've been working on using code generation with texen to (hopefully)
make this easier and quicker.
the idea is to generate elements and attributes from DTDs (via
xml-schema) and velocity templates.
i've been working on this for the last couple of weeks and i feel that
i've proved the concept and have stuff which'll do pretty much what's
needed :-)
what i need to do now is to tidy stuff up, document and make it
available so that other ecs people can take a look and use it. the
problem is that i have made general changes and enhancements.
i think that the best thing would be for me to take this code and give
it a home (for the moment) in the ecs project. that way, it can be used
over there without worrying.
i will post the design ideas in the code (and patches if they're wanted)
back to this list and take stuff from there. (i also have some nice
examples such as generating xml object-model parsers from xml-schema.)
(i'm pretty sure that the generation stuff won't make it into the ecs2
release so we can worry about where code should live to generate ecs
element models from DTDs later on.)
comments? is this a good plan?
- robert
Re: [PATCH] org.apache.velocity.texen.ant.TexenTask (exception
handlingand documentation)
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
Completely in. Thanks.
geir
Robert Burrell Donkin wrote:
>
> org.apache.velocity.texen.ant.TexenTask.execute() currently deals with
> exceptions thrown during the generation process by printing a standard
> stack trace. IMHO this is not the best way to handle them. exceptions
> should be rethrown as org.apache.tools.ant.BuildException's for the
> following reasons:
>
> 1. ant understands that when a BuildException is thrown, an error has
> prevented the task from completing. processing of the build then stops.
> this is very useful when you have a single ant build file containing
> both code generation tasks and compilation tasks - if a code generation
> task fails, then compilation does not proceed.
> 2. ant BuildExceptions can contain a causal exception. this means that
> more useful messages can be given to the user rather than a simple stack
> trace. ant does quite a good job of formatting BuildExceptions - texen
> should take advantage.
> 3. (as far as i can see) catching and rethrowing seems to be the ant way
> to do these things.
>
> this patch catchs exceptions and rethrows them as BuildExceptions for
> Ant to deal with. known velocity exceptions are caught and rethrown with
> additional messages.
>
> this patch also contains some small improvements to the (javadoc)
> documentation.
>
> - robert
>
> ------------------------------------------------------------------------
> Name: TexenTask_patch.txt
> TexenTask_patch.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> ------------------------------------------------------------------------
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
[PATCH] org.apache.velocity.texen.ant.TexenTask (exception handling and documentation)
Posted by Robert Burrell Donkin <ro...@mac.com>.
org.apache.velocity.texen.ant.TexenTask.execute() currently deals with
exceptions thrown during the generation process by printing a standard
stack trace. IMHO this is not the best way to handle them. exceptions
should be rethrown as org.apache.tools.ant.BuildException's for the
following reasons:
1. ant understands that when a BuildException is thrown, an error has
prevented the task from completing. processing of the build then stops.
this is very useful when you have a single ant build file containing
both code generation tasks and compilation tasks - if a code generation
task fails, then compilation does not proceed.
2. ant BuildExceptions can contain a causal exception. this means that
more useful messages can be given to the user rather than a simple stack
trace. ant does quite a good job of formatting BuildExceptions - texen
should take advantage.
3. (as far as i can see) catching and rethrowing seems to be the ant way
to do these things.
this patch catchs exceptions and rethrows them as BuildExceptions for
Ant to deal with. known velocity exceptions are caught and rethrown with
additional messages.
this patch also contains some small improvements to the (javadoc)
documentation.
- robert
<Attachment missing>
Re: [JOB]Looking for job.
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
Fedor Karpelevitch wrote:
>
> Hi!
>
> (I remember it was said that this kind of posting is Ok here, so here we go)
>
> I am looking for a SW Engineer position. Working with Turbine and/or Velocity
> would be great, but I would say that more generally I am looking for
> server-side Java, SQL, XML and so on.
> I am looking for something in SF Bay Area, but may consider elsewhere.
> I have expirience with various stuff and am generally bright guy ;-)
> I do not have any visa-related issues.
> My resume is available upon request.
He is generally a bright guy, and specifically too!
We should setup a Jakarta job board or something....
--
Geir Magnusson Jr. geirm@optonline.net
Developing for the web? See http://jakarta.apache.org/velocity/