Re: Extracting tokens
Hi Peter, you seem to be seeking to list the references in your templates... The TemplateTool should help you here: http://svn.apache.org/viewvc/jakarta/velocity/engine/trunk/experimental/templatetool/TemplateTool.java?revision=HEAD Nathan gave pointers how to load a template from a string. Cheers, Christoph [EMAIL PROTECTED] wrote: > Hi, > Let me explain. I refer to "dynamic template" from the velocity > documentation (template = Velocity.getTemplate("mytemplate.vm")) //non > dynamic template; > > > I try to illustrate what I want to do with the following fictional code > snippet: > > String string = "\nHello $apa"; > > attributes[] = Velocity.getTemplateFromStringReader(new > StringReader(string)).extractAllPossibleVariableNamesInTemplate(); > for(int i=0;i System.out.println(attributes[i].getName()); // Would print $apa > or apa > } > > I hope this clarify what I want to do.. I guess I have to go really low > level interacting with the Parser or something similar to accomplish > this? > > Peter > > > -Original Message- > From: Nathan Bubna [mailto:[EMAIL PROTECTED] > Sent: den 28 november 2006 18:28 > To: Velocity Developers List > Subject: Re: Extracting tokens > > what do you mean by "dynamic template"? > > On 11/28/06, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: >> Thanks alot! Is this possible to do with dynamic templates? >> I havent seen a way for getting the Template object from a dynamic >> template. >> >> Peter Larnholt >> >> >> >> -Original Message- >> From: Nathan Bubna [mailto:[EMAIL PROTECTED] >> Sent: den 28 november 2006 17:44 >> To: Velocity Developers List >> Subject: Re: Extracting tokens >> >> http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/experime >> nt >> al/templatetool/ >> >> On 11/28/06, [EMAIL PROTECTED] >> <[EMAIL PROTECTED]> wrote: >>> Hello, >>> >>> I'm a velocity newbie. We have a portal framework with a propretary >> MVC. >>> We are thinking of using velocity for rendering the views. In our >>> publishing tool we need to extract all defined variables from a >>> template. Reading the documentation I cannot find this. A lot of >>> information exists to do the other way around (extract objects into >>> Context variables). >>> >>> Anyone that could give me some pointers. >>> >>> What I'm looking for really is someting like; variables[] = >>> Velocity.getTemplate("mytemplate.vm").extractAllPossibleVariableName >>> sI >>> nT >>> emplate(); >>> >>> Cheers. >>> Peter >>> >>> >>> >>> - 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] >> >> >> - >> 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] > > > - > 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]
Re: [jira] Created: (VELOCITY-509) Add new directive #evaluate
No, the #evaluate directive is to be used as it the following example: #set( $error = $i18n_tool.getMessage("ERROR123") ) #evaluate( $error )## reder by merging with context It something like the #parse directive, but the content comes from a string and not a file. :) Christoph Geir Magnusson Jr. wrote: > Do you mean > > $foo = "#foreach($a in $b) .. #end" > > ? > > If so, why not just do it that way, rather than add a new directive? > > geir > > > On Jan 2, 2007, at 11:47 PM, Will Glass-Husain (JIRA) wrote: > >> Add new directive #evaluate >> --- >> >> Key: VELOCITY-509 >> URL: https://issues.apache.org/jira/browse/VELOCITY-509 >> Project: Velocity >> Issue Type: New Feature >> Components: Engine >> Affects Versions: 1.5 beta2 >> Reporter: Will Glass-Husain >> Priority: Minor >> Fix For: 1.6 >> >> >> On a separate issue (VELOCITY-504) we came up with the idea of a new >> directive, #evaluate. Basically, it would act just like >> Velocity.evaluate(). >> >> Users are always asking for this capability (internal evaluation). >> Usually we tell them to "use a tool". Instead, we should just put in >> a simple directive that would evaluate a VTL string using the current >> context. >> >> Incidentally, this should be the current local context, e.g. if inside >> a macro or a foreach loop (or worse, both) it should use that >> context. See VELOCITY-504 for why this is needed. >> >> --This message is automatically generated by JIRA. >> - >> If you think it was sent incorrectly contact one of the >> administrators: https://issues.apache.org/jira/secure/Administrators.jspa >> - >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >> >> - >> 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )
+1 from me! :) Christoph Henning Schmiedehausen wrote: > Due to a misunderstanding in the vote procedure, we actually have to > repeat the release vote, because we should vote only on really rolled > releases. > > The candidate for the Apache Velocity 1.5 release is available from > http://people.apache.org/dist/velocity/1.5/ > > Shall we release this code base as Apache Velocity 1.5 > > [ ] +1 Yes. > [ ] 0 I still don't care. > [ ] -1 No, because . > > Vote period is > > Monday, Jan 29th 0:00 MET to Wednesday, Jan 31st 0:00 MET > > Best regards > Henning > > > > > - > 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]
Re: new directive - #evaluate
> Be curious if there are any comments. Great! Many users have asked for such a feature, for example when a string comes from a DB or internationalized templates, etc. In the past I solved this using a nicely wrapped tool, which does exactly the same: #macro( evaluate $param )$renderTool.eval($param)#end Does your #evaluate directive implementation do some AST caching of the string for performance improvement? Most languages have such an "eval"-Functionality and therefore there is no reason for Velocity missing it. Maybe Ahmed did not manage to advocate Velocity to some more projects, because the decision makers missed some handy features ;) But I do agree with Ahmed on #5: 5. Better and simpler whitespace control for the output. Cheers, Christoph P.S. It is like my other handy macro: #macro( call $dummy )if($dummy)#end#end - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remove Author tags?
Please stop the noise! >:) Christoph Jonathan Revusky wrote: > Konstantin Priblouda wrote: >> --- Jonathan Revusky <[EMAIL PROTECTED]> wrote: >> >> >>> lead developer, FreeMarker project, >>> http://freemarker.org/ >> >> >> For a lead developer of concurrent project you are >> spending a lot of time on wrong list. Are you trying >> to paralize any discussion here? > > > > No, not really. I think that people here are quite capable of reaching a > state of total paralysis without any help from me... :-) > > I don't really keep an eye on the Velocity lists to know what is going > on here. (Since nothing is ever really going on) The only real value > I get out of following Velocity lists is that, occasionally, somebody > comes up with an idea that really is kind of interesting. Not a Velocity > developer, ever, I mean an end-user may request a feature that obviously > has merit. In many cases, features that were added to FreeMarker > originated in feature requests made on a Velocity list. > > As for comments I make, like on the @author tags, it is hard for me to > refrain from saying certain things when people are making nonsensical > arguments. As for Henning insisting that Ahmed Mohombe send in patches, > I think it was quite appropriate to point out that there is a history > here of ignoring patches for periods of years. > >> I must admit, that you and Dacotha Jack is the cause (for me) to not >> to use freemakrer at all - regardless of its quality. > > Interesting that you admit something like this. To me, quite frankly, > Konstantin, it is tantamount to admitting that one is a complete idiot. > Also, it goes to show how much research goes into your tool selection. > Dakota Jack (whoever he is) is a disgruntled Struts user. He has nothing > to do with FreeMarker. Go look at http://freemarker.org/whoWeAre.html . > > I am just going to ask you the same question I asked Christopher > Schultz. Do you object to anything I am saying on the grounds of it not > being true? Or more specifically, I suggested that the behavior of > somebody like Henning is not really consistent with being interested in > doing any work on Velocity or being interested in the overall space. Do > you actually disagree with that assessment? > > Jonathan Revusky > -- > lead developer, FreeMarker project, http://freemarker.org/ > > >> >> regards, >> >> [ Konstantin Pribluda http://www.pribluda.de ] >> JTec quality components: http://www.pribluda.de/projects/ >> >> __ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam protection around >> http://mail.yahoo.com > > > - > 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]
Re: #set warning if null
Hi Claude, I originally proposed to allow the bang character in the #set( $!bar = $!foo ) directive to: a) avoid logging the null from $!foo (this is current behaviour when rendering foo) b) allowing setting the context to null with then bang in $!bar I sent a patch many years ago (was rejected, event though it is BC). See the threads at: "how to set null value" http://mail-archives.apache.org/mod_mbox/velocity-user/200505.mbox/[EMAIL PROTECTED] "Quiet reference in set" http://mail-archives.apache.org/mod_mbox/velocity-user/200102.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/velocity-user/200103.mbox/[EMAIL PROTECTED] [PATCH] ASTSetDirective to handle a bang http://mail-archives.apache.org/mod_mbox/velocity-dev/200101.mbox/[EMAIL PROTECTED] "wish list" (you participated in this thread!) http://mail-archives.apache.org/mod_mbox/velocity-dev/200310.mbox/[EMAIL PROTECTED] more embedded: Claude Brisson wrote: > Hi dev, > > I'd like to change the behaviour of #set($foo = $evaluates_to_null) > > The current behaviour is to log (debug loglevel) the message "RHS of > #set statement is null...". > > What I'd like to do: > > - set the loglevel of this message to warn +0 > > - don't log anything if the left reference is quiet, as in > #set($!foo = $evaluates_to_null) >(this syntax is already allowed but does nothing special) I proposed here to not log when the bang is on the RHS, conform to the current notation: #set( $foo = $!null ) Using a bang in the LHS, should allow setting the context variable to null: #set( $!foo = $null )## this may or may not put a warning in the log > > This will allow template coders > - to anticipate whether an assignment can be null +1 > - to be warned if another assignment is null for a warn loglevel > > > Any objection? > > > Claude > :) Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Call a velocity macro
Hi Adrian, in a similar scenario I use the #parse directive and placed the code snippets (aka. macros) into a *.vtl file each. Something like: #set( $component = ... ) #set( $type = $component.type ) #parse("renderComponent${type}.vtl" ) This has the advantage, that these rendering Templates parsed once and cached. The downside is that the parameter passing is implicit (here $component is the input parameter for the parsed template) and that these parsed templates must be careful not to overwrite existing variables. For this I used a different namespace (postfixed variables with "_"), but you can also use the new #local directive to avoid conflicts. Cheers, Christoph Adrian Tarau wrote: I've always imagined a macro as a function, but as the name says, the macro body is expanded at parsing time in the current template. This has the advantage to have the template tree in memory and the rendering speed is the fastest possible. What I need is more like calling a template as a function(which behave like a function) in the context of the current execution context(same context, same writer) without too much overhead. I will try to implement something like that and I will publish the result, maybe it will be useful for somebody else. Thanks. Massip, Etienne wrote: A dynamic call of a parameter-given name is a minimal parsing, but still is, preventing any kind of "compile-time linkage" from being done. The "expression" seems to be known only at template-parsing-time, isn't it ? I think #call('render'+$component.type $component) makes very little difference with #evaluate('#render' + $component.type + '($component)') If the evaluate directive really performs poorly, then maybe it should be a good idea to speed it up other than create a new and specialized one ? -Message d'origine- De : Adrian Tarau [mailto:[EMAIL PROTECTED] Envoyé : mardi 19 février 2008 16:14 À : Velocity Developers List Objet : Re: Call a velocity macro Velocity.evaluate or Velocity.invokeVelocimacro(which calls evaluate) doesn't provide support to pass objects as parameters and is not suitable to be called from a template. The new directive #evaluate is actually Velocity.evaluate. It is still an evaluate, which means expression parsing. I would like to avoid that. If you will call "call/invoke" directive too often I think it will perform badly, due the fact that a parsing step is performed. In this case, a call to a velocity macro, we don't need the parsing step. We know the "expression", and what we need is to prepare the node without parsing.I don't know much about the velocity internals, but I presume it should be possible. And I think such a directive should be part of the core, I mean it will be easy to implement a "switch"(is what I need actually) based on some variable. Like in my case : #macro(renderLabel $component) #end #macro(renderTextField $component) #end #macro(renderRadioButton $component) #end . #call('render'+$component.type $component) where 'type' is 'label', 'text-field', 'radio-button'(of course there is a normalization of the type value, first character upper case, '-' makes the next character uppercase, etc). Instead of lots of tests with #if, it will be better(and faster) to have this 'switch'.At least it looks better, the template is cleaner and it is (it will be)also faster. Thanks. /Reader reader = *new* BufferedReader(*new* StringReader(sourceText)); String templateName = context.getCurrentTemplateName(); SimpleNode nodeTree = *null*; *try* { *nodeTree* = rsvc.parse(reader, templateName); } *catch* (ParseException pex) { use the line/column from the template Info info = *new* Info( templateName, node.getLine(), node.getColumn() ); *throw* *new* ParseErrorException( pex.getMessage(), info ); } *catch* (TemplateInitException pex) { Info info = *new* Info( templateName, node.getLine(), node.getColumn() ); *throw* *new* ParseErrorException( pex.getMessage(), info ); }/ Massip, Etienne wrote: Hello Take a look at the actual RenderTool (http://velocity.apache.org/tools/releases/1.4/generic/RenderTool.html). Or at the new evaluate directive, although still in developement (http://velocity.apache.org/engine/devel/vtl-reference-guide.html#aevaluate_-_dynamically_evaluates_a_string_or_reference). Etienne -Message d'origine- De : Adrian Tarau [mailto:[EMAIL PROTECTED] Envoyé : mardi 19 février 2008 07:29 À : dev@velocity.apache.org Objet : Call a velocity macro Hello, I have the following problem : I would like to call a macro but the macro name must be a variable. Ex: instead of #renderLabel($component) to have #call("renderLabel" $component) - of course "renderLabel" can be any (existing) macro name. I started to create a dire
Re: [jira] Commented: (VELOCITY-613) Wrong Velocity 1.5 POM file in Maven repository
Hi Adrian, thanks for assisting Nathan on the maven issues! Some of these things happened March last year in this area by Carlos Sanchez, see the whole thread at: http://www.nabble.com/Re:--repo---www-people.apache.org-repo-m1-ibiblio-rsync-repository--td9481767.html Best regards, Christoph Adrian Tarau (JIRA) wrote: [ https://issues.apache.org/jira/browse/VELOCITY-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634381#action_12634381 ] Adrian Tarau commented on VELOCITY-613: --- Done. You can download the POM from : http://repo.adrian.tarau.org/velocity/velocity/1.5/. Just dump the POM(and checksums) here http://repo1.maven.org/maven2/velocity/velocity/1.5/. You can remove everything that exists now at http://repo1.maven.org/maven2/velocity/velocity/1.5/ ,just a POM with relocation is enough to point to the real POM. I will have a second look tomorrow in all groups and build a relocation POM for them. You can use this dummy project to see how it works first : http://repo.adrian.tarau.org/org/tarau/adrian/dummy/0.1-SNAPSHOT/dummy-0.1-20080925.055220-1.pom. You can change the informational message (Please change Velocity groupId from velocity to org.apache.velocity.) with a different one. I think I know how those POMs got there. I presume many artifacts in Maven 2 repository were just moved to the new repository format using the Maven 1 repository .What I don't understand is why a (valid) Maven 2 POM existed in Velocity Maven 1 repository at the conversion time. If you look at http://repo1.maven.org/maven/velocity/poms/ there is a velocity-1.5.pom.carlos which gives me the idea that somebody played with those files (who's Carlos? :) ). Wrong Velocity 1.5 POM file in Maven repository --- Key: VELOCITY-613 URL: https://issues.apache.org/jira/browse/VELOCITY-613 Project: Velocity Issue Type: Bug Affects Versions: 1.5 Reporter: Zdeněk Zikán Velocity's POM file in Maven repository has incorrect groupId: http://repo1.maven.org/maven2/velocity/velocity/1.5/velocity-1.5.pom It does not match the jar file Currently: org.apache.velocity Should be: velocity - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: GUI Framework on top of Velcoity
Hi, You should also take a look at http://swixml.org (sample code, XML parts) and JellySwing at http://commons.apache.org/jelly/libs/swing/index.html (examples at http://svn.apache.org/viewvc/commons/proper/jelly/trunk/jelly-tags/swing/src/test/org/apache/commons/jelly/swing/) that provide similar capabilites and are extensible. Using Velocity for this is also a possibility, but looking at your example: it seems to me that you did not code using Velocity #directives but used some XSLT to do the magic. My 2c, Christoph Omer Uretzky wrote: > Hi, > > I have developed a framework (in Java) on top of the velocity template engine. > My framework is very simple, it creates input screens for a template (based > on predefined XML) > You can see attached a simple example: > > This example generates a simple letter (letter.txt). My tool reads the XML > (letter.xml) and create the input screen (attached). The user put his inputs > in the input screen and press OK. The tool takes the inputs and using the > Velocity engine combines the inputs with the template to generate the file. > > The tool also implements a storage where many templates and inputs screens > (XML) resides. So when the user activates the tool, he gets a list of > possible templates to generate. After choosing the desired template, the tool > opens the appropriate input screen. > > The attached example is the simplest example I could create for you. > Let me know if you care to hear more. > > Thanks, Omer > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: #set null in 2.0
Hi, > Does anyone out there even remember why it wasn't allowed in the first place? Several Map implementations do not allow null values, so as the original Hashtable context implementation. > Does anyone out there rely on not being able to change variables to null? not me... Greetings, Christoph Nathan Bubna wrote: > In 1.x we have: > > directive.set.null.allowed = false > > I think that we should flip that to true and perhaps even remove the > option in 2.0. > > Does anyone out there rely on not being able to change variables to null? > Does anyone out there even remember why it wasn't allowed in the first place? > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: scripting return values from a called function
Hi, your question is not clear. You seem to be familiar with some other programming or scripting language - please get up-to-date with Java for the application side, also look at the examples in the Velocity developers guide: http://velocity.apache.org/engine/releases/velocity-1.6.2/developer-guide.html and Velocity syntax for the template side; read the Velocity users guide: http://velocity.apache.org/engine/releases/velocity-1.6.2/user-guide.html If your function is part of a Java class, place an instance into the Velocity context either with the ToolboxManager or using Java code in your application before merging: context.put("Functions", new Function()); (more at: http://velocity.apache.org/engine/releases/velocity-1.6.2/developer-guide.html#How_Velocity_Works ) and use it in your template: #set( $retvalue = $Functions.function() ) If you want to define scripted code in your Velocity template (called macros), you can do: #macro( Function ) ...do something wise #end and use it in your template: #set( $retvalue = "#Function()" ) Please note that macros can only return strings! So if you need variant return types, you need a Java class with a corresponding method (in which case a "void" parameter does not make sense - how will it differentiate what to return?). Hope this helped, Christoph bren36 wrote: > Hi > > I have the following scenario > > string retvlaue = Function (void) :I There are no void pass-in parameters in Java. > > How can i script this inside velocity > Original Message > Subject: return value > Date: Thu, 16 Apr 2009 12:14:12 -0700 (PDT) > From: bren36 > Reply-To: Velocity Users List > To: u...@velocity.apache.org > > > Hi , > > Want to achieve the following using vm get a return value from a function > - the return value can be a structure /integer /string type . > > eg . > > temp FUNCTION_call () > > Anyone have any ideas how i can achieve this in.vm ? - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: macro question
Hi, if the macro returns a string, use the string-interpolation capability: #set( $myVar = "#returnField($fieldPath $varName)" ) if the $varname (note the single '$', more on this below) returns an object, I believe you can assign it either to a global variable (depends on the local scope behavior set in the velocity properties - some changes happened here towards release 1.6.2 - needs testing), or to one of the macro parameters (also release 1.6.x/1.7.x changes something here in the pass by reference functionality - needs testing): #macro( call $foo )#if($foo)#**##end#end #macro( returnField $fieldPath $varName ) ... #set( #myGlobal = $varName($fieldPath.field.id) ) #end ... #set( $myGlobal = false ) #call( "#returnField($fieldPath $varName)" ) Your macro updated: $myGlobal or #macro( call $foo )#if($foo)#**##end#end #macro( returnField $fieldPath $varName $returnVal ) ... #set( #returnVal = $varName($fieldPath.field.id) ) #end ... #set( $returnVal = false ) #call( "#returnField( $fieldPath $varName $returnVal )" ) Your macro returned: $returnVal Note 1: the call macro allows calling something but ignores any string output generated within the macro (or a java method call). Note 2: you cannot do indirect variable access (see $$varName in your example). You could use the #evaluate directive or tool for this. Note 3: this looks like too much programming in the template, it might be wise to reconsider the architecture. Consider placing the macro functionality into a java pojo tool and call it via the context - results in much cleaner template code: #set( $returnVal = $myTool.returnField( $fieldPath $varName ) Kind regards, Christoph bren36 wrote: > Hi , > > Is there a way that i can return a value from a velocity macro > > My macro looks something like so > > #macro(returnField $fieldPath $varName) > #if($fieldPath.subfield) > $$varName($fieldPath.field.id) > #returnField ($varName $fieldPath.subfield ) > #end > #end > > Where i need to return $$varName($fieldPath.field.id) > > how can i call the returnField macro and assign it to a variable ?? > > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: macro question
Reconsidering the question, just use the velocity 1.6 #evaluate directive, see: http://velocity.apache.org/engine/releases/velocity-1.6.2/user-guide.html#Evaluate applied to your example (note the single quotes): #evaluate('#set( $returnVal = $varName($fieldPath.field.id)') Returned value: $returnVal Let us know if this worked for you. :) Christoph > bren36 wrote: >> Hi , >> >> Is there a way that i can return a value from a velocity macro >> >> My macro looks something like so >> >> #macro(returnField $fieldPath $varName) >> #if($fieldPath.subfield) >> $$varName($fieldPath.field.id) >> #returnField ($varName $fieldPath.subfield ) >> #end >> #end >> >> Where i need to return $$varName($fieldPath.field.id) >> >> how can i call the returnField macro and assign it to a variable ?? >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Fwd: [VOTE] VelocityTools 2.0 final release
I'm with it! +1 The new tools.xml format in velocity-toos 2.0 is a great simplification. P.S. I am missing some documented way to get the dependency jars (commons-*, struts-*, etc). I guess this is typically resolved through the pom? (a direct maven build out of eclipse failed in the tests) I finally found the libs in http://people.apache.org/~nbubna/velocity/tools/2.0/velocity-tools-2.0.zip :) Christoph Original Message Subject: [VOTE] VelocityTools 2.0 final release Date: Fri, 16 Apr 2010 15:16:01 -0700 From: Nathan Bubna Reply-To: Velocity Developers List To: Velocity Developers List , private Ok, everyone seems happy with the build at this point, so it's time to vote: The build is still available here: http://people.apache.org/~nbubna/velocity/tools/2.0/ Please vote regarding your support for releasing this new test build as VelocityTools 2.0: [ ] +1 Let's do it [ ] +0 Have fun; i don't care. [ ] -0 Not sure about this, but i won't stop you. [ ] -1 No, because __ The voting period is typically 72 hours, putting its close time as roughly 3pm PST on Monday, but given the current snail's pace of responses to the Engine 1.7-beta1 i will keep it going until either 3 PMC +1s, a -1 or 2 weeks happen. If the vote passes, I'll push this to the mirrors, change the web site and get Henning to deploy it. On Tue, Apr 13, 2010 at 9:44 AM, Nathan Bubna wrote: > Ok, i've updated the test build to revision 933536. It is still at: > > http://people.apache.org/~nbubna/velocity/tools/2.0/ > > and i still hope to call for a vote this weekend-ish. :) > > On Tue, Apr 13, 2010 at 9:26 AM, Nathan Bubna wrote: >> i'll do it. that part is quick. >> >> On Tue, Apr 13, 2010 at 8:25 AM, Claude Brisson wrote: >>> Ok, then tell me if you want me to put a new test build online or if >>> you're on the way to do it... >>> >>> Claude >>> >>> On mar., 2010-04-13 at 08:04 -0700, Nathan Bubna wrote: If you want it to be in the release, it must be in the test build, since those are the actual bits we release. But putting up a new test build needn't necessarily delay the vote. On Tue, Apr 13, 2010 at 2:48 AM, Claude Brisson wrote: > There is one little change I'd really like to see in 2.0, sorry for > being late, but since it's triggered by a new config param which doesn't > change anything by default, it shouldn't invalidate this week tests, so > no need to rebuild the test build or delay the vote... I commit it right > away. > > > Claude > > On lun., 2010-04-12 at 11:48 -0700, Nathan Bubna wrote: >> Ok, it's long overdue for us to put out a Tools 2.0 final release. >> Here's the test build. >> Please test it. I'll hopefully call for a vote by the end of the week. >> >> http://people.apache.org/~nbubna/velocity/tools/2.0/ >> >> Here's the list of changes since 2.0-beta4 >> >> - Added beta-quality UiDependencyTool for managing style and script >> dependencies >> - Added alpha-quality MarkupTool for generating xml/html on the fly >> (both new tools are intentionally left out of the default tools.xml >> due to their status) >> - updated various docs (yay!) >> - Added $convert.toIntegers(Object) as a synonym for .toInts() >> - fixed some typos in showcase demo >> - Add $loop.this to workaround VELTOOLS-124 >> - Partially fixed VELTOOLS-124 >> - implemented ViewToolContext.containsKey() >> - made ToolContext.ketSet() rely on getToolboxes() >> - VelocityLayoutServlet checks request attributes for non-default >> layouts >> - fixed VelocityViewTag tld >> - added Accept-Language header handling to BrowserTool >> - Improved exception and http management in VelocityView >> >> (based on revision 91) >> >> - >> To unsubscribe, e-mail: private-unsubscr...@velocity.apache.org >> For additional commands, e-mail: private-h...@velocity.apache.org >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org >>> For additional commands, e-mail: dev-h...@velocity.apache.org >>> >>> >> > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: d
Re: [VOTE] Velocity Engine 1.6.4 final (GA) bugfix release
+0 Nathan, thanks for the lead. :) Christoph - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: [VOTE] VelocityTools 2.0 final release (take 2)
+1, works for me! I will continue to use and test it. Thanks, Christoph On 2010-05-03 18:17, Nathan Bubna wrote: > Ok, there were no complaints about the 2nd test build. Let's try the > vote again... > > The build is still available here: > http://people.apache.org/~nbubna/velocity/tools/2.0/ > > Please vote regarding your support for releasing this new test build as > VelocityTools 2.0: > > [ ] +1 Let's do it > [ ] +0 Have fun; i don't care. > [ ] -0 Not sure about this, but i won't stop you. > [ ] -1 No, because __ > > If we have the necessary votes, i will close the vote Thursday (May > 6), around 9am PST. If not, i'll start nagging, which is oh-so-fun. > If this doesn't pass or get vetoed by two weeks from today, i'll close > the vote anyway. Can't drag this out forever... > > > > On Mon, Apr 26, 2010 at 10:57 AM, Nathan Bubna wrote: >> Ok, i fixed the problem with the missing showcase war. Nothing else >> has changed. I'll call for a new vote in a few days. Please test it >> now, rather than before the vote starts. :) >> >> http://people.apache.org/~nbubna/velocity/tools/2.0/ >> >> (based on revision 938119) >> > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: Potential Regression? Escaped Quotes in String Literals
Hi, even though I would love to have the established character escaping with a backslash used in many programming languages, velocity is not up to it yet (the tendency is not to make it into a programming language). Some time ago it was chosen to allow embedded double-quotes in a string by doubling it up - as done e.g. in CVS exports and some other M$-near string tools. To my knowledge escaping of quotes was never supported by Velocity. Only literals can be escaped - with some curiosities - see the User Manual "Escaping Valid VTL References". So in the doxia case either use a single quote for the XML attributes, or double-up the quotes, or use the poor-mans-escaping (TM): #set( $Q = '"' ) Kind regards, Christoph On 2010-08-02 06:18, Stefan Bodewig wrote: > Hi all, > > there is a build failure showing up in some Gump builds that seems to > indicate a backwards incompatible change inside Velocity - which may or > may not be intentional. > > One example of the failure can be seen in the Cargo build > <http://vmgump.apache.org/gump/public/cargo/cargo/gump_work/build_cargo_cargo.html>. > I'll be happy to explain what Gump does, but the failure itself can be > understood without that background. > > The doxia-site-renderer Maven module contains a Velocity template which > itself contains a line > > #set ( $documentHeader = "" > ) > > probably with the expectaation that \" would escape the quote. This > seems to work with the version referenced by the module: 1.5. > > If you try to parse the same template with the trunk of Velocity engine > you get > > [ERROR] org.apache.velocity.exception.ParseErrorException: Encountered "1.0" > at org/apache/maven/doxia/siterenderer/resources/default-site.vm[line 308, > column 51] > Was expecting one of: > ... > ... > > which looks as if the " before 1.0 was terminating the string literal. > > I can't find any hint in Velocity's documentation that would say you can > escape quotes in string literals, but if it worked in older versions you > are setting some sort of expectation 8-) > > Is this a regression that can/will be fixed or is this something the > downstream users like doxia would need to adapt to? > > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by RobertBrandner
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by RobertBrandner: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity The comment on the change is: added entry for PANDORA framework -- ||[http://myvelcont.sourceforge.net/ MyVelocityController]||MyVelocityController is a simple Servlet controller (under the MVC pattern) which uses Velocity as its unique templating engine. It uses a set of templates to show HTML and another set to access a JDBC database.|| ||[http://www.niggle.org/ Niggle]||Niggle is a Java class library intended for use in development of robust, maintainable web applications. The Niggle framework is designed to alleviate the repetitive, tedious details typical of those kinds of applications|| ||[http://www.openedit.org OpenEdit]|| OpenEdit is a platform used by web design firms for creating and maintaining web sites. It includes content management, eCommerce and blog editing tools and is built from the ground up with Velocity. Uses Spring for Java objects and actions and requires no database. || + ||[http://pandora-frmwrk.sourceforge.net PANDORA]||PANDORA is a lightweight web-application framework with single servlet, multi controller architecture. It supports the ''Pull MVC'' pattern providing models for Forms, Tables, Trees, Lists and the ''Open Session in View'' pattern in combination with pluggable Hibnerate support.|| ||[http://www.restlet.org Restlet]||Restlet is a lightweight REST framework for Java that natively supports Velocity templates as well as FreeMarker templates, JSON, XML and other types of representations.|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityWhitespaceGobbling" by MarcNovakowski
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by MarcNovakowski: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbling -- * Marino Jonsson (marinoj AT centrum DOT is) * Peter Urban (urban AT jaist DOT ac DOT jp) * Claude Brisson (claude AT renegat DOT net) -- bkoz it's almost identical to "Globbing No Whitespace" for people that use few indented directives + * Marc Novakowski (marc AT pandora DOT com) Add any write-in candidates below: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "StreamLayoutServlet" by ClaudeBrisson
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by ClaudeBrisson: http://wiki.apache.org/jakarta-velocity/StreamLayoutServlet -- The following directives are used to control the behaviour of the page: * #layout("layout-template") - The layout of this page. If not specified, the page will use the default layout (see below). - * #head("text") - Put text in the page eader. Cumulative if used several times. + * #head("text") - Put text in the page header. Cumulative if used several times. * #title("title") - the title of the page. * #page-parameter("parameter-name","parameter-value"") - a named parameter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityNews" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/VelocityNews The comment on the change is: "recent" news -- + === Velocity Approved as Top Level Project === + + The Board of the Apache Software Foundation has passed a resolution to upgrade + Jakarta Velocity into an Apache Top Level Project (TLP), to be renamed Apache Velocity. + We are excited of the new prominence of the Velocity project. + + + Please stay tuned for our new website at + http://velocity.apache.org/. In the meantime, + note that our new mailing lists are + user@velocity.apache.org (subscribe at + [EMAIL PROTECTED]) + for general questions, and + dev@velocity.apache.org + (subscribe at + [EMAIL PROTECTED]) for + development-related activity. + + (''2006-10-26'') + + + === Velocity 1.5 Beta 1 Released === + + The Velocity developers are proud to announce the first beta version of + Velocity 1.5. + You may download it from + http://people.apache.org/dist/jakarta/velocity/v1.5beta1/ . + + This is an early release intended as a preview of things to + come. Many bugs have been fixed and new features have been added. A sampling: + + * floating point number arithmetic + * new event handlers for altering #include/#parse behavior + * literal map syntax + + A complete list of changes is available at our + [http://issues.apache.org/jira/browse/VELOCITY?report=com.atlassian.jira.plugin.system.project:roadmap-panel JIRA]. + Please report any additional bugs there, especially those that need to be fixed before our + final release. (use 1.5 beta 1 as the version). + + (''2006-09-13'') + === New Issue Tracker === The Velocity Project has moved from Bugzilla to [http://issues.apache.org/jira/browse/VELOCITY JIRA]. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "LocalSpellingWords" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/LocalSpellingWords -- Gobbling schmoo templating + about above Action add Add Adding adds against aka alaska all All almost Alternatives Among ancient Structured structured these this This those up use was ways we whitespace Whitespace write - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "LocalSpellingWords" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/LocalSpellingWords -- Gobbling schmoo templating about above Action add Add Adding adds against aka alaska all All almost Alternatives Among ancient Structured structured these this This those up use was ways we whitespace Whitespace write + + admiring and Andrew answer answers any apache Apocalypse are argument artificially as As bug buggy Bugzilla bugzilla But but by close code consistency consistent documents fiercely guidelines indented Loy or original other question quite second Secondary sure - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "LocalSpellingWords" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/LocalSpellingWords -- about above Action add Add Adding adds against aka alaska all All almost Alternatives Among ancient Structured structured these this This those up use was ways we whitespace Whitespace write admiring and Andrew answer answers any apache Apocalypse are argument artificially as As bug buggy Bugzilla bugzilla But but by close code consistency consistent documents fiercely guidelines indented Loy or original other question quite second Secondary sure + + at Backwards be chosen concerns Discussion for handle issues make many no No None not Paul paul remove So so urban Urban Will with within workaround - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "LocalSpellingWords" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/LocalSpellingWords -- admiring and Andrew answer answers any apache Apocalypse are argument artificially as As bug buggy Bugzilla bugzilla But but by close code consistency consistent documents fiercely guidelines indented Loy or original other question quite second Secondary sure at Backwards be chosen concerns Discussion for handle issues make many no No None not Paul paul remove So so urban Urban Will with within workaround + + become been before beg civil com Comment current dealt Debate easier eliminated embrace end Enhance gamut Glass go Gobble gobble gobbled identical if ignored in leading Line line long maintaining move name net nothing over page pandora parser particular people Peter points remain remember response result Results roll Some spaces steps such support tabs tactic then things threads Tidy tightly times to To variety velocity vote voted votes want your - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "LocalSpellingWords" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/LocalSpellingWords -- at Backwards be chosen concerns Discussion for handle issues make many no No None not Paul paul remove So so urban Urban Will with within workaround become been before beg civil com Comment current dealt Debate easier eliminated embrace end Enhance gamut Glass go Gobble gobble gobbled identical if ignored in leading Line line long maintaining move name net nothing over page pandora parser particular people Peter points remain remember response result Results roll Some spaces steps such support tabs tactic then things threads Tidy tightly times to To variety velocity vote voted votes want your + + behavior below blissfully can candidates carefully comment compatible compelling competing complex complexity compliant concern configure contested control create debating debugging default Democracy Different different direct directives does dreadful each elements etc even everyone existing few fought gobbling Great grown guilt handling happened has have History hold How - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityWhitespaceGobbling" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbling -- Alternatives and Workarounds * JTidy - * VelocityWhitespaceTruncatedByLineComment (Use a Velocity comment to artificially end a line) + * VelocityWhitespaceTruncatedByLineComment (Use a Velocity comment to artificially end a line, but doesn't remove leading or trailing spaces, tabs, etc.) + + Discussion of JTidy as a Workaround + + I have looked into using JTidy as a workaround and it's quite promising. But we have to remember a few things before we all embrace the JTidyness. + + * JTidy is only for HTML and XHTML (up to XHTML 1.0, not yet XHTML 1.1) so it can't be used for other documents and, in particular, text documents where whitespace does not get gobbled by the parser. + * JTidy is buggy and at times does not create W3C compliant code even if your original code is W3C compliant. + * As JTidy can add, remove or move elements in your HTML you don't have direct control over the end result. So you can't just roll this out to all your HTML output in one go. This is the same argument as the one against whitespace gobbling in Velocity -- you would have to test evey single page (template) to make sure that nothing funny has happened. + * The more steps you have before you output adds more complexity, more maintaining and more debugging. + + All these points are quite compelling reasons not to use JTidy. Democracy in Action (aka Democracy Inaction) @@ -35, +46 @@ * For Gobbling As Usual * everyone who has read this and not voted! (yes, this is a guilt trip) + * Paul Andrew Loy (paul ART keteracel DOT com) -- for consistency with current templates but would want the option for new templates to use gobble all or structured as long as it was consistent * For Gobbling All Whitespace * (no votes yet) * For Gobbling No Whitespace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityWhitespaceGobbling" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbling -- * For Gobbling As Usual * everyone who has read this and not voted! (yes, this is a guilt trip) - * Paul Andrew Loy (paul ART keteracel DOT com) -- for consistency with current templates but would want the option for new templates to use gobble all or structured as long as it was consistent + * [http://www.keteracel.com Paul Andrew Loy] (paul ART keteracel DOT com) -- for consistency with current templates but would want the option for new templates to use gobble all or structured as long as it was consistent * For Gobbling All Whitespace * (no votes yet) * For Gobbling No Whitespace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityWhitespaceGobbling" by MHall119
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by MHall119: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbling -- * Peter Urban (urban AT jaist DOT ac DOT jp) * Claude Brisson (claude AT renegat DOT net) -- bkoz it's almost identical to "Globbing No Whitespace" for people that use few indented directives * Marc Novakowski (marc AT pandora DOT com) + * Michael Hall (mhall AT lakeland DOT net) -- I like the #pragma idea, but would it be possible to apply whitespace rules to a block, rather than the entire template? Add any write-in candidates below: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "StreamLayoutServlet" by ClaudeBrisson
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by ClaudeBrisson: http://wiki.apache.org/jakarta-velocity/StreamLayoutServlet -- * tools.view.servlet.layout.default.template the default layout template. Default is default.vtl. * tools.view.servlet.error.template the error template. Default is error.vtl. - Performance issue: when the resource loader cache is off, the page template is parsed twice per request. Be sure to turn on the cache in a production environment. + When the resource loader cache is off, the page template is parsed twice per request. Apart from a performence issue, there is also a problem + with the #head directive since it works in a cumulative way. Since there is no generic way for the servlet to know whether cache is on or off, + there is currently no simple workaround to this problem, which means that cache MUST be turned on for #head() to work properly. The patch is attached. Please note that the new directives make use of the new velocity-1.5 TemplateInitException, so you will have to compile velocity-tools against velocity-1.5-dev. Otherwise you can easily adapt the sources to have it work with velocity-1.4 by replacing TemplateInitException with a generic Exception. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityWhitespaceGobbling" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbling -- * JTidy * VelocityWhitespaceTruncatedByLineComment (Use a Velocity comment to artificially end a line, but doesn't remove leading or trailing spaces, tabs, etc.) + * Create a lightweight whitespace gobbling filter to pass the velocity output through Discussion of JTidy as a Workaround - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityNews" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/VelocityNews The comment on the change is: change download URL -- The Velocity developers are proud to announce the first beta version of Velocity 1.5. You may download it from - http://people.apache.org/dist/jakarta/velocity/v1.5beta1/ . + http://www.apache.org/dist/jakarta/velocity/beta/velocity-1.5-beta1/ . This is an early release intended as a preview of things to come. Many bugs have been fixed and new features have been added. A sampling: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/ReleaseProcess The comment on the change is: ant package now generates the checksums, so we don't need to list this step -- * check this change in using `svn commit` * build the release packages using `ant package` * enter the `bin` directory - * run the following shell script to build MD5 and SHA1 checksums: - {{{ - #! /bin/bash - for i in *.tar.gz *.zip *jar; do - md5sum < $i | cut -d' ' -f1 > $i.md5 - sha1sum < $i | cut -d' ' -f1 > $i.sha1 - done - }}} - * Generate GPG signatures: {{{ #! /bin/bash - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/ReleaseProcess The comment on the change is: apparently the java distribution directory has moved (readme file at old loc) -- * make sure that your umask is 002! If not, please enter `umask 002` * create the distribution directory: `/www/www.apache.org/dist/jakarta/velocity/velocity-`. Make sure that its permissions are set to 775! * move the .tar.gz and .zip related files from your personal directory to the distribution directory. - * move the .jar related files to /www/www.apache.org/dist/java-repository/velocity/jars + * copy the .jar (and md5 related files) to /www/people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars * go to the distribution directory. * check the MD5 and SHA1 sums by running the md5 and sha1 programs on the .tar.gz and .zip files. The output must be identical to the contents of the .md5 and .sha1 files. '''Please do not skip this step!''' Upload errors happen more frequently that commonly believed and testing the checksums is essential in catching these. * verify the GPG signatures, too using gpg --verify. - * go to the java distribution directory: /www/www.apache.org/dist/java-repository/velocity/jars + * go to the java distribution directory: /www/people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars * please repeat the check and verify as with the distribution files - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "Velocity15ReleaseNotes" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/Velocity15ReleaseNotes -- * Velocity singleton and engine will attempt to auto-init() when reasonable and possible instead of throwing NPEs when used without calling init() first. * Anakia generates consistent line endings on Windows platforms. * Fixed error in which Velocity would complain if the template ended with "##". + * Fixed race condition in template retrieval that caused macros to fail under simultaneous load. + * Methods were not being properly cached due to use of inconsistent keys. === VTL Enhancements === @@ -29, +31 @@ * Line breaks are allowed in directive calls, macro calls, method calls, and string literals. * Macros now accept spaces or commas in separating arguments. * Directives can now be delimited with curly braces, for example #if($condition)something#{else}otherthing#{end}. + === Velocity Enhancements === @@ -47, +50 @@ * You can now deploy the Velocity jar file in the container classpath while keeping your application in a webapp classpath. * !FileResourceLoader now accepts absolute paths (when configured to accept them). * The default resource cache implementation now has an upper bound on cache size. + * New !StringResourceLoader can retrieve templates from repository of in-memory Strings. + * !MethodInvocationException now contains line, column, template name allowing application to produce more useful error messages. + * Change the meaning of localscope for macros to allow access to references from calling context. + * New event handler !InvalidReferenceHandler allows application to catch invalid references. Sample implementation collects them in list and optionally throws exception. + * New, optional !SecureIntrospector prohibits methods that involve manipulation of classes, classloaders or reflection objects. Use this introspector to secure Velocity against a risk of template writers using reflection to perform malicious acts. === Dependency Notes === @@ -60, +68 @@ === Known Issues === - There are a few known bugs and issues to be addressed before a Velocity 1.5 release. See [http://issues.apache.org/jira/browse/VELOCITY JIRA] for details. + There are a few known bugs. See [http://issues.apache.org/jira/browse/VELOCITY JIRA] for details. - * The new Event Handlers needed to be documented. * There remain various subtle escaping bugs - * DVSL is incompatible with Velocity 1.5 * Macros cannot be defined in one file and included with #parse in another. See MacroIssues for more information. === Other Notes === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/ReleaseProcess The comment on the change is: reminder about changes.xml -- === Before you start === + * Make sure the file changes.xml has the most recent updates listed. * Run `svn update` to get the most recent tree for release. * check whether everything has checked in correctly: `svn status` should be empty. * remove the `bin` and `target` directories. @@ -90, +91 @@ === Building the release === * change the version property in `build.properties` to reflect the version to be released. + * edit the file "changes.xml", changing the "version" attribute of the topmost "release" tag to indicate the most version number to be released. * check this change in using `svn commit` * build the release packages using `ant package` * enter the `bin` directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Trivial Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/ReleaseProcess The comment on the change is: fix font -- === Before you start === - * Make sure the file changes.xml has the most recent updates listed. + * Make sure the file `changes.xml` has the most recent updates listed. * Run `svn update` to get the most recent tree for release. * check whether everything has checked in correctly: `svn status` should be empty. * remove the `bin` and `target` directories. @@ -91, +91 @@ === Building the release === * change the version property in `build.properties` to reflect the version to be released. - * edit the file "changes.xml", changing the "version" attribute of the topmost "release" tag to indicate the most version number to be released. + * edit the file `changes.xml`, changing the `version` attribute of the topmost `release` tag to indicate the most version number to be released. * check this change in using `svn commit` * build the release packages using `ant package` * enter the `bin` directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityNews" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/VelocityNews The comment on the change is: news item about beta 2 -- + === Velocity 1.5 Beta 2 Released === + + The Velocity developers are pleased to announce the second beta release of Velocity 1.5. + You may download it http://www.apache.org/dist/jakarta/velocity/beta/velocity-1.5-beta2/";>here. + + This beta version is one of the final steps before the long-awaited version 1.5. Since Beta 1 we have added a new !InvalidReferenceEventHandler (to catch invalid references), the !SecureUberspector (to prevent introspection on "dangerous objects"), and a !StringResourceLoader. We've also fixed some critical bugs, including a subtle synchronization problem causing page generation to fail under heavy loads. + + (''2006-11-24'') + === Velocity Approved as Top Level Project === The Board of the Apache Software Foundation has passed a resolution to upgrade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityNews" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/jakarta-velocity/VelocityNews The comment on the change is: need to remember to use the preview button -- === Velocity 1.5 Beta 2 Released === The Velocity developers are pleased to announce the second beta release of Velocity 1.5. - You may download it http://www.apache.org/dist/jakarta/velocity/beta/velocity-1.5-beta2/";>here. + You may download it at http://www.apache.org/dist/jakarta/velocity/beta/velocity-1.5-beta2/ . This beta version is one of the final steps before the long-awaited version 1.5. Since Beta 1 we have added a new !InvalidReferenceEventHandler (to catch invalid references), the !SecureUberspector (to prevent introspection on "dangerous objects"), and a !StringResourceLoader. We've also fixed some critical bugs, including a subtle synchronization problem causing page generation to fail under heavy loads. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by Jacklondon Chen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Jacklondon Chen: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| ||[http://sourceforge.net/projects/webwork/ WebWork]||WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks. WebWork now supports Velocity with their 1.0 release.|| ||[http://www.ztemplates.org/ ztemplates]|| web framework with java 1.5 - uses object injection, annotations , generics and reflection - support for templating, data binding, form validation (with Ajax/DWR), security, search-engine friendly urls and i18n - gui components like tree and tabbed pane - supports Apache Velocity, JSP and other technologies for rendering webpages.|| + ||[http://velocityweb.sourceforge.net/]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by Jacklondon Chen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Jacklondon Chen: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| ||[http://sourceforge.net/projects/webwork/ WebWork]||WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks. WebWork now supports Velocity with their 1.0 release.|| ||[http://www.ztemplates.org/ ztemplates]|| web framework with java 1.5 - uses object injection, annotations , generics and reflection - support for templating, data binding, form validation (with Ajax/DWR), security, search-engine friendly urls and i18n - gui components like tree and tabbed pane - supports Apache Velocity, JSP and other technologies for rendering webpages.|| - ||[http://velocityweb.sourceforge.net/]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| + ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by Jacklondon Chen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Jacklondon Chen: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.restlet.org Restlet]||Restlet is a lightweight REST framework for Java that natively supports Velocity templates as well as FreeMarker templates, JSON, XML and other types of representations.|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| + ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| ||[http://sourceforge.net/projects/webwork/ WebWork]||WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks. WebWork now supports Velocity with their 1.0 release.|| ||[http://www.ztemplates.org/ ztemplates]|| web framework with java 1.5 - uses object injection, annotations , generics and reflection - support for templating, data binding, form validation (with Ajax/DWR), security, search-engine friendly urls and i18n - gui components like tree and tabbed pane - supports Apache Velocity, JSP and other technologies for rendering webpages.|| - ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by Jacklondon Chen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Jacklondon Chen: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.restlet.org Restlet]||Restlet is a lightweight REST framework for Java that natively supports Velocity templates as well as FreeMarker templates, JSON, XML and other types of representations.|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| - ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provide real unit test for J2EE servlet-dao without server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for TRANSACTION_PER_REQUEST, uniform success/fail page. It aims at faster J2EE web developing.|| + ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provides unit test for whole request process without J2EE server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for design pattern named as TRANSACTION_PER_REQUEST, uniform success/fail page.|| ||[http://sourceforge.net/projects/webwork/ WebWork]||WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks. WebWork now supports Velocity with their 1.0 release.|| ||[http://www.ztemplates.org/ ztemplates]|| web framework with java 1.5 - uses object injection, annotations , generics and reflection - support for templating, data binding, form validation (with Ajax/DWR), security, search-engine friendly urls and i18n - gui components like tree and tabbed pane - supports Apache Velocity, JSP and other technologies for rendering webpages.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by Paul Loy
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by Paul Loy: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.cidental.com/ http://www.cidental.com/]||Careington Dental Discount Plans. Online application based on Struts, Velocity and Castor JDO.||[http://www.cidental.com/ cidental.com]|| ||[http://www.123case.it www.123case.it]||123case.it is an italian real estate portal developed using Velocity template engine.||[http://www.igate.it www.igate.it]|| ||[http://www.3java.net www.3java.net]||A comprehensive directory of Java(tm) open source software, as well as an evaluation system that aids in the selection of open source software. Developed with Struts & Velocity.||[http://www.3java.net www.3java.net]|| + ||[http://www.peoplesarchive.com Peoples Archive]||Video (movie) website whose tagline is 'great people telling their life stories'. Soon to include Donald Knuth for those who are interested! Developed originally (badly) by my predecessor in taglibs, jsp + nasty java, now being converted (by [http://www.keteracel.com/paul me]) into Velocity.||[http://www.keteracel.com]|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by sdumitriu
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by sdumitriu: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.churchandpeople.com/ Church and People]||Church and People is a web site that provides churches with community building and administration tools, such as online event registration, credit card processing, resource management, membership directories, private forums, an event calendar, e-mail tools, and more. Velocity was used during development to generate most of the application, from HTML to configuration XML to business logic classes, based on input from a domain-specific language created with JavaCC.|| ||[http://www.alphaworks.ibm.com/tech/hirixml/ Hierarchical Inherited Rule-Interpreted XML]||A dynamic XML Engine that creates dynamic DOMs built on dynamic rules and expressions in which Velocity may be used as the expression interpreter.|| ||[http://www.mcoletti.net/dev/iskb/velociowlPlugin.html Velociowl, a reporting plugin for Protege]||Allows the production of reports and other output from the powerful OWL knowledgebase editor of Stanford University.|| + ||[http://www.xwiki.org XWiki]||A second generation wiki platform written in Java. It uses Velocity for the interface templates, and as the main in-page programming language.|| == Velocity Powered Websites == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "VelocityEditors" by DennisLundberg
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by DennisLundberg: http://wiki.apache.org/jakarta-velocity/VelocityEditors The comment on the change is: Add section on syntax highlighting for IDEA. -- Rickard Oberg ([EMAIL PROTECTED]) has contributed templates for the [http://www.intellij.com/ IntelliJ IDEA] IDE. View it at ["IntelliJTemplates"]. + Dennis Lundberg has contributed a ["IntelliJSyntaxHighlighting"] file type configuration for IntelliJ IDEA. + It gives you syntax highlighting for .vm files. + === UltraEdit Editor === Herve Guidetti ([EMAIL PROTECTED]) contributed a 'word.txt' addition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "IntelliJSyntaxHighlighting" by DennisLundberg
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by DennisLundberg: http://wiki.apache.org/jakarta-velocity/IntelliJSyntaxHighlighting The comment on the change is: Add VelocityTemplateLanguage.xml file type configuration New page: {{{VelocityTemplateLanguage.xml}}} is a file type configuration for IntelliJ IDEA (http://www.jetbrains.com/idea/). It will give you syntax highlighting in .vm files. Contributed by Dennis Lundberg (dennisl AT apache DOT org). Put the text below in a file called {{{VelocityTemplateLanguage.xml}}} and save that file in IDEA's {{{config/filetypes/}}} directory. '''{{{VelocityTemplateLanguage.xml}}}''' {{{ }}} - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by JohnEichelsdorfer
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by JohnEichelsdorfer: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.123case.it www.123case.it]||123case.it is an italian real estate portal developed using Velocity template engine.||[http://www.igate.it www.igate.it]|| ||[http://www.3java.net www.3java.net]||A comprehensive directory of Java(tm) open source software, as well as an evaluation system that aids in the selection of open source software. Developed with Struts & Velocity.||[http://www.3java.net www.3java.net]|| ||[http://www.peoplesarchive.com Peoples Archive]||Video (movie) website whose tagline is 'great people telling their life stories'. Soon to include Donald Knuth for those who are interested! Developed originally (badly) by my predecessor in taglibs, jsp + nasty java, now being converted (by [http://www.keteracel.com/paul me]) into Velocity.||[http://www.keteracel.com]|| - + ||[http://www.jobbank.com jobbank.com]||Employment site for job searches, posting jobs, posting resumes, and career tools. This MVC site uses Velocity to render its entire view including templated emails.||[http://www.jmjmedia.com JMJ Media]|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||<30%tablewidth="100%">'''Name'''||'''Description'''|| ||[http://jakarta.apache.org/velocity/anakia.html Anakia]||Essentially an XML transformation tool, Anakia uses JDOM and Velocity to transform XML documents into the format of your choice. It provides an alternative to using Ant's
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||<30%tablewidth="100%">'''Name'''||'''Description'''|| ||[http://jakarta.apache.org/velocity/anakia.html Anakia]||Essentially an XML transformation tool, Anakia uses JDOM and Velocity to transform XML documents into the format of your choice. It provides an alternative to using Ant's
[Jakarta-velocity Wiki] Update of "MyEclipse" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/MyEclipse New page: MyEclipse is an innovative approach to offering affordable tools for Java and J2EE developers. Starting at $29.95 annual membership, MyEclipse members have access to the Enterprise Workbench, monthly feature releases, online support and tutorials. Our mission is to deliver business value and to maximize developers' productivity by consistently delivering reliable products and a true end-to-end seamless J2EE development environment. MyEclipse is the eclipse plugin solution for all your UML, AJAX, Web, J2EE, JSP, XML, Struts, JSF, Hibernate and application server integration needs. More information on MyEclipse can be found at: [http://www.myeclipseide.com MyEclipse] [http://www.genuitec.com Genuitec] [http://www.myeclipseide.com Eclipse Plugins] [http://www.jroller.com/page/myeclipseblog MyEclipse Blog] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "MyEclipse" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/MyEclipse -- - MyEclipse is an innovative approach to offering affordable tools for Java and J2EE developers. Starting at $29.95 annual membership, MyEclipse members have access to the Enterprise Workbench, monthly feature releases, online support and tutorials. Our mission is to deliver business value and to maximize developers' productivity by consistently delivering reliable products and a true end-to-end seamless J2EE development environment. MyEclipse is the eclipse plugin solution for all your UML, AJAX, Web, J2EE, JSP, XML, Struts, JSF, Hibernate and application server integration needs. + Genuitec's MyEclipse Enterprise Workbench is a leading J2EE IDE in the Eclipse space. MyEclipse's distribution includes a large number of easy-to-use wizards which abstract the user from complex configuration files and source + code. MyEclipse utlizes Velocity as its template engine and finds Velocity both versatile and powerful enough to transform user input from these wizards into markup or Java code. - More information on MyEclipse can be found at: + Back to [http://wiki.apache.org/jakarta-velocity/PoweredByVelocity Powered by Velocity] - [http://www.myeclipseide.com MyEclipse] - - [http://www.genuitec.com Genuitec] - - [http://www.myeclipseide.com Eclipse Plugins] - - [http://www.jroller.com/page/myeclipseblog MyEclipse Blog] - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "PoweredByVelocity" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/PoweredByVelocity -- ||[http://www.alphaworks.ibm.com/tech/hirixml/ Hierarchical Inherited Rule-Interpreted XML]||A dynamic XML Engine that creates dynamic DOMs built on dynamic rules and expressions in which Velocity may be used as the expression interpreter.|| ||[http://www.mcoletti.net/dev/iskb/velociowlPlugin.html Velociowl, a reporting plugin for Protege]||Allows the production of reports and other output from the powerful OWL knowledgebase editor of Stanford University.|| ||[http://www.xwiki.org XWiki]||A second generation wiki platform written in Java. It uses Velocity for the interface templates, and as the main in-page programming language.|| - ||[http://www.myeclipseide.com MyEclipse]||Genuitec's MyEclipse Enterprise Workbench is the leading J2EE IDE in the Eclipse space. With a full-featured toolkit, MyEclipse utilizes Velocity for many types of code generation throughout the product.|| + ||[http://www.myeclipseide.com MyEclipse]||Genuitec's MyEclipse Enterprise Workbench is a leading J2EE IDE in the Eclipse space. With a full-featured toolkit, MyEclipse utilizes Velocity for many types of code generation throughout the product.|| == Velocity Powered Websites == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta-velocity Wiki] Update of "MyEclipse" by jenseckels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-velocity Wiki" for change notification. The following page has been changed by jenseckels: http://wiki.apache.org/jakarta-velocity/MyEclipse -- Back to [http://wiki.apache.org/jakarta-velocity/PoweredByVelocity Powered by Velocity] + More information can be found at [http://www.myeclipseide.com MyEclipse] + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "FrontPage" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/FrontPage -- * Velocity15ReleaseNotes -- Release Notes compilation for the 1.5 release * HackaThon2006 + === Organizational === + * BoardReports + Special pages * '''WantedPages''' - linked pages that do not exist * '''OrphanedPages''' - pages not linked to from anywhere - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReports" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReports The comment on the change is: home page for drafting board reports New page: As part of the Apache Software Foundation we must report to the board about our activity. These reports are quarterly due and public. As part of our move to become a top-level project (TLP), we have to report monthly for the first three months (November 2006 to January 2007). Reports are then due in mid-February, May, August, and November of each year. Reports are normally written by the PMC Chair, with contributions from the PMC and community. Each quarter we draft the report on the Wiki. When the report is submitted to the board we move it to the [http://velocity.apache.org/board-reports.html Velocity website]. If you have a contribution that is to be considered private, please email it directly to [EMAIL PROTECTED] Read the BoardReportTemplate. == Quarterly Reports == * February2007Report - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReportTemplate" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReportTemplate The comment on the change is: drafted template for Board report New page: == Month Year Board Report == === Status === Chair to summarize Velocity-wide news + the current state of affairs. Can be broken into an extra section (e.g. infrastructure) if something significant occurred. === Community changes === New committers, pmc persons, asf members and departures. === Velocity Engine project === Summary of new code, releases, activity, or list discussion. === Velocity Engine project === Summary of new code, releases, activity, or list discussion. === Velocity DVSL project === Summary of new code, releases, activity, or list discussion. If none, write: There were no changes in the DVSL code base. No DVSL development happened in the last month. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReportTemplate" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReportTemplate -- Summary of new code, releases, activity, or list discussion. - === Velocity Engine project === + === Velocity Tools project === Summary of new code, releases, activity, or list discussion. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReportTemplate" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReportTemplate The comment on the change is: added a little more sample language -- Chair to summarize Velocity-wide news + the current state of affairs. Can be broken into an extra section (e.g. infrastructure) if something significant occurred. + If no Board action is required, say: + + The Velocity project currently has no board-level issues at this time. + === Community changes === - New committers, pmc persons, asf members and departures. + List new committers, pmc persons, asf members and departures. Or say: + + No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. === Velocity Engine project === Summary of new code, releases, activity, or list discussion. + If no releases, say: + + No beta or final releases were made since the last board report. + + === Velocity Tools project === Summary of new code, releases, activity, or list discussion. + + If no releases, say: + + No beta or final releases were made since the last board report. === Velocity DVSL project === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReports" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReports -- == Quarterly Reports == - * February2007Report + * ["BoardReport-February2007"] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReports" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReports -- == Quarterly Reports == * ["BoardReport-February2007"] + * ["BoardReport-January2007"] + * ["BoardReport-December2006"] + * ["BoardReport-November2006"] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-February2007" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-February2007 The comment on the change is: empty board report for Feb 2007 - will fill in later New page: == February 2007 Board Report == === Status === (As our esteemed chair Henning Schmiedehausen is on vacation this month, this quarter's report is being prepared by Will Glass-Husain). === Community changes === No new committers were voted in since the last board report. No new PMC members were voted in since the last board report. === Velocity Engine project === === Velocity Tools project === === Velocity DVSL project === There were no changes in the DVSL code base. No DVSL development happened in the last month. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-January2007" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-January2007 The comment on the change is: placeholder for old board report New page: == January 2007 Board Report == Sent to the board and published at http://velocity.apache.org/reports/report-2007-01.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-December2006" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-December2006 The comment on the change is: placeholder for old board report New page: == December 2006 Board Report == Sent to the board and published at http://velocity.apache.org/reports/report-2006-12.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-November2006" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-November2006 The comment on the change is: placeholder for old board report New page: == November 2006 Board Report == Sent to the board and published at http://velocity.apache.org/reports/report-2006-11.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-February2007" by HenningSchmiedehausen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by HenningSchmiedehausen: http://wiki.apache.org/velocity/BoardReport-February2007 -- == February 2007 Board Report == - === Status === + === General information === (As our esteemed chair Henning Schmiedehausen is on vacation this month, this quarter's report is being prepared by Will Glass-Husain). + + TBD + + The Velocity project has no board-level issues at this time. ''remove or change that line if we do have board-level issues (things that must be discussed by the board)'' + === Community changes === @@ -12, +17 @@ === Velocity Engine project === + TBD === Velocity Tools project === + TBD === Velocity DVSL project === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "FrontPage" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/FrontPage The comment on the change is: fix links -- #pragma section-numbers off = Introduction to Velocity = - [http://jakarta.apache.org/velocity/ Velocity] + [http://velocity.apache.org/ Velocity] is a simple yet powerful Java-based template engine that renders data from plain Java objects to text, xml, email, SQL, Post Script, HTML etc. The template syntax and rendering engine are both easy to understand and @@ -19, +19 @@ the template for more direct access to data. VelocityTools is a sub-project which contains extensions aimed at solving - common web and non-web problems. For example, [http://jakarta.apache.org/velocity/tools/generic/ GenericTools] provide + common web and non-web problems. For example, [http://velocity.apache.org/tools/devel/generic/ GenericTools] provide - Date/Number formatting, Math operations, and more. [http://jakarta.apache.org/velocity/tools/view/ VelocityView] provides a + Date/Number formatting, Math operations, and more. [http://velocity.apache.org/tools/devel/view/ VelocityView] provides a time-tested servlet which can render *.vm files in web applications. - Finally, [http://jakarta.apache.org/velocity/tools/struts/ VelocityStruts] builds upon this foundation to give Struts + Finally, [http://velocity.apache.org/tools/devel/struts/ VelocityStruts] builds upon this foundation to give Struts developers a robust and easy-to-implement alternative to JSP. Additional non-web examples are Anakia and DVSL which use Velocity for "easier than XSLT" transformations of XML. - More details and the official documentation are on the [http://jakarta.apache.org/velocity/ Velocity Home Page]. + More details and the official documentation are on the [http://velocity.apache.org/ Velocity Home Page]. Be sure to read the - [http://jakarta.apache.org/velocity/overview.html Overview], + [http://velocity.apache.org/engine/devel/overview.html Overview], - [http://jakarta.apache.org/velocity/getting-started.html Getting Started], and the + [http://velocity.apache.org/engine/devel/getting-started.html Getting Started], and the - [http://jakarta.apache.org/velocity/webapps.html Web Application Guide]. You'll also want to check out the ["VelocityFAQ"], or post your question to the [http://jakarta.apache.org/site/mail2.html#Velocity Velocity user list]. + [http://velocity.apache.org/engine/devel/webapps.html Web Application Guide]. You'll also want to check out the ["VelocityFAQ"], or post your question to the [http://velocity.apache.org/contact.html Velocity user list]. This Wiki contains community and developer-oriented content. Please feel free to add new articles, FAQ entries, or code examples. If you've created a website or application that uses Velocity, add it to the PoweredByVelocity page! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools The comment on the change is: fix links -- * Velocity-View provides a time-tested servlet and tools for Velocity-based web applications. * Velocity-Struts - a robust and easy-to-implement alternative to JSP for Struts Webapps. - '''Velocity Tools 1.2 is now available!''' + '''Velocity Tools 1.3-rc1 is now available!''' - Both source and binary distributions are [http://jakarta.apache.org/site/downloads/downloads_velocity.cgi available for download] through the the usual Apache mirror sites. Please remember to verify the + Both source and binary distributions are [http://velocity.apache.org/download.cgi available for download] through the the usual Apache mirror sites. Please remember to verify the - signatures of the distribution using the keys found on the main [http://www.apache.org/dist/jakarta/velocity-tools/KEYS Apache website] when downloading + signatures of the distribution using the keys found on the main [http://www.apache.org/dist/velocity/KEYS Apache website] when downloading from a mirror. Useful Links - * [http://jakarta.apache.org/velocity/tools/ Project Website] + * [http://velocity.apache.org/tools/devel/ Project Website] * [http://www.jajakarta.org/velocity/tools/ Project Website in Japanese] - * [http://svn.apache.org/viewcvs.cgi/jakarta/velocity/tools/trunk/ ViewCVS/SVN] + * [http://svn.apache.org/viewcvs.cgi/velocity/tools/trunk/ ViewCVS/SVN] Contributed Code and Examples @@ -45, +45 @@ * EscapeTool -- A generic Tool that works with escaping. Depends on commons-lang 2.0. Velocimacro Library - The mailing list often has questions/suggestions for for common macros. We'd like to gather the good ones [http://wiki.apache.org/jakarta-velocity/VelocimacroLibrary here]. :) And this is a Wiki, so contributions are very welcome! + The mailing list often has questions/suggestions for for common macros. We'd like to gather the good ones in our VelocimacroLibrary. :) And this is a Wiki, so contributions are very welcome! * VelocityGenericMacros -- non-web macros, applicable in '''any''' Velocity setting, these might make use of the Generic Tools. - * VelocityViewMacros -- web-oriented macro and/or make use of Velocity View tools (using the recommended keys!) + * VelocityViewMacros -- web-oriented macro and/or make use of !VelocityView tools (using the recommended keys!) * VelocityStrutsMacros -- applicable for !VelocityStruts applications, and will generally but optionally use the Velocity-Struts tools (using recommended keys!). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "PoweredByVelocity" by HuyTran
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by HuyTran: http://wiki.apache.org/velocity/PoweredByVelocity The comment on the change is: Added ThinkUI SQL Client to list of Velocity-Powered Products and Projects. -- ||[http://www.mcoletti.net/dev/iskb/velociowlPlugin.html Velociowl, a reporting plugin for Protege]||Allows the production of reports and other output from the powerful OWL knowledgebase editor of Stanford University.|| ||[http://www.xwiki.org XWiki]||A second generation wiki platform written in Java. It uses Velocity for the interface templates, and as the main in-page programming language.|| ||[http://www.myeclipseide.com MyEclipse]||Genuitec's MyEclipse Enterprise Workbench is a leading J2EE IDE in the Eclipse space. With a full-featured toolkit, MyEclipse utilizes Velocity for many types of code generation throughout the product.|| + ||[http://www.thinkui.com ThinkUI SQL Client]||ThinkUI SQL Client is a graphical program that allows Java developers to browse a database structure, edit data in the tables, issue SQL queries, and generate code (e.g. Java Bean, DAO, SQL queries, JSP files, etc.) based on customizable Velocity templates. [http://www.thinkui.com/tutorial.html Online Flash Demo] is available.|| == Velocity Powered Websites == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools -- * Velocity-View provides a time-tested servlet and tools for Velocity-based web applications. * Velocity-Struts - a robust and easy-to-implement alternative to JSP for Struts Webapps. - '''Velocity Tools 1.3-rc1 is now available!''' + '''Velocity Tools 1.3 is now available!''' Both source and binary distributions are [http://velocity.apache.org/download.cgi available for download] through the the usual Apache mirror sites. Please remember to verify the signatures of the distribution using the keys found on the main [http://www.apache.org/dist/velocity/KEYS Apache website] when downloading - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "PoweredByVelocity" by FyodorKupolov
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by FyodorKupolov: http://wiki.apache.org/velocity/PoweredByVelocity The comment on the change is: Scriptella ETL open source tool added -- ||[http://www.openedit.org OpenEdit]|| OpenEdit is a platform used by web design firms for creating and maintaining web sites. It includes content management, eCommerce and blog editing tools and is built from the ground up with Velocity. Uses Spring for Java objects and actions and requires no database. || ||[http://pandora-frmwrk.sourceforge.net PANDORA]||PANDORA is a lightweight web-application framework with single servlet, multi controller architecture. It supports the ''Pull MVC'' pattern providing models for Forms, Tables, Trees, Lists and the ''Open Session in View'' pattern in combination with pluggable Hibnerate support.|| ||[http://www.restlet.org Restlet]||Restlet is a lightweight REST framework for Java that natively supports Velocity templates as well as FreeMarker templates, JSON, XML and other types of representations.|| + ||[http://scriptella.javaforge.com Scriptella ETL]||Scriptella is an open source ETL(Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows the use of SQL or another scripting language suitable for the data source to perform required transformations. Scriptella [http://scriptella.javaforge.com/docs/api/scriptella/driver/velocity/package-summary.html supports] Velocity templates in ETL files|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provides unit test for whole request process without J2EE server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for design pattern named as TRANSACTION_PER_REQUEST, uniform success/fail page.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "PoweredByVelocity" by FyodorKupolov
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by FyodorKupolov: http://wiki.apache.org/velocity/PoweredByVelocity The comment on the change is: cosmetic fix -- ||[http://www.openedit.org OpenEdit]|| OpenEdit is a platform used by web design firms for creating and maintaining web sites. It includes content management, eCommerce and blog editing tools and is built from the ground up with Velocity. Uses Spring for Java objects and actions and requires no database. || ||[http://pandora-frmwrk.sourceforge.net PANDORA]||PANDORA is a lightweight web-application framework with single servlet, multi controller architecture. It supports the ''Pull MVC'' pattern providing models for Forms, Tables, Trees, Lists and the ''Open Session in View'' pattern in combination with pluggable Hibnerate support.|| ||[http://www.restlet.org Restlet]||Restlet is a lightweight REST framework for Java that natively supports Velocity templates as well as FreeMarker templates, JSON, XML and other types of representations.|| - ||[http://scriptella.javaforge.com Scriptella ETL]||Scriptella is an open source ETL(Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows the use of SQL or another scripting language suitable for the data source to perform required transformations. Scriptella [http://scriptella.javaforge.com/docs/api/scriptella/driver/velocity/package-summary.html supports] Velocity templates in ETL files|| + ||[http://scriptella.javaforge.com Scriptella ETL]||Scriptella is an open source ETL(Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows the use of SQL or another scripting language suitable for the data source to perform required transformations. Scriptella [http://scriptella.javaforge.com/docs/api/scriptella/driver/velocity/package-summary.html provides built-in support] for Velocity templates in ETL files|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provides unit test for whole request process without J2EE server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for design pattern named as TRANSACTION_PER_REQUEST, uniform success/fail page.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-February2007" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-February2007 The comment on the change is: draft of new report -- (As our esteemed chair Henning Schmiedehausen is on vacation this month, this quarter's report is being prepared by Will Glass-Husain). - TBD + The Velocity project is inches away from the eagerly anticipated release of Velocity 1.5, the first major release of our engine in almost three years. December and January saw a flurry of activity in cleaning up last minute bugs, updating documentation, and preparing the release. - The Velocity project has no board-level issues at this time. ''remove or change that line if we do have board-level issues (things that must be discussed by the board)'' + We have had passionate recent discussion on the dev and private list about release procedure. In part, this is due to the anticipated visibility of the Velocity 1.5 release and in part due to the relatively young nature of the Velocity TLP / PMC as we establish correct release practice. + For recent beta / rc releases we have had a "vote-then-build" process in which a PMC member announces they are ready to release, a vote is held, then the release is shipped. In mid-January such a vote was announced for Velocity 1.5. Midway through the vote one of the PMC members expressed concern that there were no binaries to examine. A consensus opinion urged a switch to a "build-then-vote" procedure and the current vote was tabled. A few days later, a second vote was held to release Velocity 1.5 with +1's from almost all parties except for a last-minute -1 (from a different PMC member). The concerns driving the -1 vote were not serious (minor documentation / site issues), but the -1 voter felt strongly that these issues should be addressed before release. (Being a release vote, the -1 was not binding but our release manager agreed to table the release in light of the concerns). + + A frustrating aspect of this process was that these issues could not be directly fixed, but needed to wait for the vote to conclude, then a rebuild of the distro then a new vote. The departure of our chair (who had been driving the release) on a month-long vacation has temporarily paused this process. Will Glass-Husain has offered to push the release through to conclusion in the meantime but personal committments have led to a several week delay. + + In related news, we have prepared a press release for distribution regarding the Velocity 1.5. Due to the low-key but wide-spread use of this library in the Java community we anticipate getting plenty of attention when the release occurs. The release was shared with the PRC committee list (which was somewhat unresponsive) but suggestions for improvements were received from several members. + + The Velocity project has no board-level issues at this time. === Community changes === @@ -17, +24 @@ === Velocity Engine project === - TBD + As noted above, the entire Velocity community is eagerly awaiting the momentary release of Velocity 1.5. We fully expect this release to conclude as previously predicted during Q1. === Velocity Tools project === - TBD + Velocity Tools 1.3 was released on February 14. + === Velocity DVSL project === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-February2007" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/BoardReport-February2007 -- A frustrating aspect of this process was that these issues could not be directly fixed, but needed to wait for the vote to conclude, then a rebuild of the distro then a new vote. The departure of our chair (who had been driving the release) on a month-long vacation has temporarily paused this process. Will Glass-Husain has offered to push the release through to conclusion in the meantime but personal committments have led to a several week delay. - In related news, we have prepared a press release for distribution regarding the Velocity 1.5. Due to the low-key but wide-spread use of this library in the Java community we anticipate getting plenty of attention when the release occurs. The release was shared with the PRC committee list (which was somewhat unresponsive) but suggestions for improvements were received from several members. + In related news, we have prepared a press release for distribution regarding the Velocity 1.5. Due to the wide-spread use of this library in the Java community we anticipate getting plenty of attention when the release occurs. The release was shared with the PRC committee list (which was somewhat unresponsive) but suggestions for improvements were received from several members. The Velocity project has no board-level issues at this time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "BoardReport-February2007" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/BoardReport-February2007 The comment on the change is: fix release date; add note about 1.4-dev starting -- === Velocity Tools project === - Velocity Tools 1.3 was released on February 14. + Velocity Tools 1.3 was released on February 8. Work on the next 1.x version has already begun. === Velocity DVSL project === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/ReleaseProcess The comment on the change is: note the jdk version -- The information on this page is intended for Velocity committers, not as end-user documentation. + (Note - some of the specific paths in this document are out of date now that Velocity has left Jakarta and gone TLP) == Building and Releasing the Velocity Engine == @@ -90, +91 @@ === Building the release === + * Make sure you are using J2SDK 1.4.2 to build the release. This will allow the jar files to be used with JDK 1.3, 1.4, 1.5, and 1.6. * change the version property in `build.properties` to reflect the version to be released. * edit the file `changes.xml`, changing the `version` attribute of the topmost `release` tag to indicate the most version number to be released. * check this change in using `svn commit` - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Trivial Update of "ReleaseProcess" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/ReleaseProcess The comment on the change is: add new paragraph -- The information on this page is intended for Velocity committers, not as end-user documentation. + (Note - some of the specific paths in this document are out of date now that Velocity has left Jakarta and gone TLP) == Building and Releasing the Velocity Engine == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "RoadMap" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/RoadMap -- Having said all that, we welcome feedback and new ideas! Please send your thoughts to the velocity-dev mailing list or post enhancement requests on [http://issues.apache.org/jira/browse/VELOCITY JIRA] to take part in the discussion. - - - = Release 1.5 = + = Release 1.6 = '''Objective''' - Address well-defined enhancement requests and all outstanding bug reports. This update is intended to be a drop-in replacment for Velocity 1.4 and as such strict backwards compatibility is required. + Address well-defined enhancement requests and all outstanding bug reports. This update is intended to be a drop-in replacment for Velocity 1.5 and as such strict backwards compatibility is required. Issues accompanied by actual code will receive special consideration. - '''Key Enhancements''' + Specific issues are listed in [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310104&fixfor=12310290 JIRA] - A specific list of enhancements and targeted bugs can be found on [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310104&fixfor=12310253 JIRA]. + Issues of particular consideration include - Significant enhancements include: + * Substantial revision to user documentation with new DocBook format [http://issues.apache.org/jira/browse/VELOCITY-463 VELOCITY-463] + * Allow macros to be defined in files loaded with #parse [http://issues.apache.org/jira/browse/VELOCITY-281 VELOCITY-281] (WGH) + * New directive #evaluate [http://issues.apache.org/jira/browse/VELOCITY-509 VELOCITY-509] (WGH) + * Move Texen and Anakia to become separately released subprojects [http://issues.apache.org/jira/browse/VELOCITY-522 VELOCITY-522] (WGH) + (other suggestions for critical issues to include? leave initials if you are enthused enough to drive the issue) - * Ability to use decimal numbers in #set and #if directives - * New map literal syntax - * New event handlers addressing #include and #parse behavior - * Ability for #set and #foreach to manipulate null objects - * Directives may now include whitespace within expression - * Revised Maven build system - In addition a large number of bugs have been resolved. '''Release Plan''' + no specific timetable as of yet - Fall 2006 - - * 1.5 beta - feature freeze (all enhancements implemented or rescheduled) - * 1.5 rc1 - all known bugs fixed - ready for testing by users - * 1.5 - final release about a month after rc1 - - - = Release 1.6 = - (under discussion) - - '''Objective''' - - Include other enhancement requests that are requested by the Velocity community and that provide backwards compatibility. Issues accompanied by actual code will receive special consideration. - - Specific issues are listed in [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310104&fixfor=12310290 JIRA] - - Of special note is a security-enhanced Uberspector that will prevent execution of "dangerous" classes and methods like getClassloader(). See [http://issues.apache.org/jira/browse/VELOCITY-179 JIRA] for more details. Note: these restrictions are configurable and can be turned on/off. It's proposed (by patch author Will GH) that this be a rare break in backwards-compatibility and be on by default for enhanced security. - - '''Release Plan''' - - Spring 2007 = Release 2.0 = @@ -69, +44 @@ * Cleaning up syntax and API inconsistencies * Adding new features and syntax that complement existing ones - + The basic operation and focus will remain the same. This release will not be a complete code rewrite. Instead it continues the incremental improvements but loosens backwards-compatibility requirements. Most old Velocity templates would still work fine with Velocity 2.0 and others will require a small amount of change. '''Possible Enhancements''' + * Make parser pluggable, allowing for variations in technology and syntax * Support for tag library ("VSTL"?) to use in JSP * Improve whitespace processing * Integrate commons-logging - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "ContributedCode" by MichaelGuymon
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGuymon: http://wiki.apache.org/velocity/ContributedCode -- * MultiUberspect -- an Uberspector that can dispatch introspection tasks to custom Uberspectors on a per-class basis * LuceneDocumentUberspect -- An Uberspect for Lucene Documents that works with the above class * JythonUberspect -- An uberspect for handling Jython (Java Python) objects + * JRubyUberspect -- An Uberspect for JRuby [http://sprocket.slackworks.com/wiki/show/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/show/Slackocity project] == Custom Directives == * ["XPath"] -- XPath evaluating directive, by VladimirKirichenko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "ContributedCode" by MichaelGuymon
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGuymon: http://wiki.apache.org/velocity/ContributedCode -- * MultiUberspect -- an Uberspector that can dispatch introspection tasks to custom Uberspectors on a per-class basis * LuceneDocumentUberspect -- An Uberspect for Lucene Documents that works with the above class * JythonUberspect -- An uberspect for handling Jython (Java Python) objects - * JRubyUberspect -- An Uberspect for JRuby [http://sprocket.slackworks.com/wiki/show/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/show/Slackocity project] + * JRubyUberspect -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/show/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/show/Slackocity project] == Custom Directives == * ["XPath"] -- XPath evaluating directive, by VladimirKirichenko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "ContributedCode" by MichaelGuymon
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGuymon: http://wiki.apache.org/velocity/ContributedCode -- * MultiUberspect -- an Uberspector that can dispatch introspection tasks to custom Uberspectors on a per-class basis * LuceneDocumentUberspect -- An Uberspect for Lucene Documents that works with the above class * JythonUberspect -- An uberspect for handling Jython (Java Python) objects - * JRubyUberspect -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/show/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/show/Slackocity project] + * [JRubyUberspect] -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/published/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/published/Slackocity project] == Custom Directives == * ["XPath"] -- XPath evaluating directive, by VladimirKirichenko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "ContributedCode" by MichaelGuymon
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGuymon: http://wiki.apache.org/velocity/ContributedCode -- * MultiUberspect -- an Uberspector that can dispatch introspection tasks to custom Uberspectors on a per-class basis * LuceneDocumentUberspect -- An Uberspect for Lucene Documents that works with the above class * JythonUberspect -- An uberspect for handling Jython (Java Python) objects - * [JRubyUberspect] -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/published/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/published/Slackocity project] + * ["JRubyUberspect"] -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/published/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/published/Slackocity project] == Custom Directives == * ["XPath"] -- XPath evaluating directive, by VladimirKirichenko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Trivial Update of "Velocity15ReleaseNotes" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/Velocity15ReleaseNotes -- === Other Notes === - * The documentation has been significantly improved. Please note that many but not all new beta features are written up. + * The documentation has been significantly improved. Please note that many but not all new features are written up. * !VelocityServlet is now officially deprecated. Please use [http://jakarta.apache.org/velocity/tools/view/ VelocityViewServlet] from the VelocityTools subproject instead. * !VelocityFormatter is also deprecated. Please use the various formatting tools in the VelocityTools subproject. * An optional Maven build is now available. However, ant remains the primary build tool. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools2Planning" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools2Planning The comment on the change is: put example toolbox in code box -- 3. SimplifiedToolboxXML: In line with the ideas above, we could cut out some repetition in toolbox.xml by better organizing it and using XML more appropriately. For instance, the [http://svn.apache.org/viewvc/velocity/tools/trunk/examples/simple/WEB-INF/toolbox.xml?revision=487337&view=markup toolbox.xml for the "simple" example] could be simplified further to something like: - + {{{ - - @@ -28, +26 @@ this is bar. + }}} 4. FactorOutBasicVelocityViewStuff: This would create a better basis for bring the [http://velocity.apache.org/engine/devel/veltag.html Veltag] into the project as a sibling of the VelocityViewServlet. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools2Planning" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools2Planning The comment on the change is: fix sub-items of idea 2 -- == Ideas For VelocityTools 2.x == - 1. TransparentOnDemandToolsLoading: Instead of a standard HashMap, the idea here is to have a Toolbox, perhaps inheriting HashMap, which will instantiate a tool from its tool-info only when the generic getter is called. This should be a quite interesting performance gain in some situations. We maybe need some attribute to have tools instantiated at toolbox initialization ('instantiate-on-load' ?). The Toolboxes may then pool or at least hold on to instantiated tools for subsequent requests from the template or from other parts of the webapp (see idea 2 below). + 1. TransparentOnDemandToolsLoading: Instead of a standard HashMap, the idea here is to have a Toolbox, perhaps inheriting from !HashMap, which will instantiate a tool from its tool-info only when the generic getter is called. This should be a quite interesting performance gain in some situations. We maybe need some attribute to have tools instantiated at toolbox initialization ('instantiate-on-load' ?). The Toolboxes may then pool or at least hold on to instantiated tools for subsequent requests from the template or from other parts of the webapp (see idea 2 below). - 2. EasierToolAccessOutsideTemplates: Other objects in my webapp are often jealous of the VelocityViewServlet. They also would like to use some of the tools. Session scoped tools can be reached via the session, but it's not the case for application or request scoped tools. To achieve this, there would be two things to do: + 2. EasierToolAccessOutsideTemplates: Other objects in my webapp are often jealous of the VelocityViewServlet. They also would like to use some of the tools. Session scoped tools can be reached via the session, but it's not the case for application or request scoped tools. To achieve this, there would be a few things to do: - - create a separate Toolbox for each scope and store it in the attributes of the corresponding servlet API object (request->!ServletRequest, session->!HttpSession, application->!ServletContext). + * create a separate Toolbox for each scope and store it in the attributes of the corresponding servlet API object (request->!ServletRequest, session->!HttpSession, application->!ServletContext). - - the ChainedContext would know to search the attributes for these Toolboxes and pass requests for the tools on to them. (NOTE: depending on the implementation of idea 1 (above) it may be advantageous to have the ChainedContext hold on to requested tools as templates often use them multiple times + * the ChainedContext would know to search the attributes for these Toolboxes and pass requests for the tools on to them. (NOTE: depending on the implementation of idea 1 (above) it may be advantageous to have the ChainedContext hold on to requested tools as templates often use them multiple times. - - We could create a simple utility to help other classes retrieve tools, so they needn't all duplicate the code for finding the toolbox in the attributes and then requesting the tool from the toolbox... + * We could create a simple utility to help other classes retrieve tools, so they needn't all duplicate the code for finding the toolbox in the attributes and then requesting the tool from the toolbox... 3. SimplifiedToolboxXML: In line with the ideas above, we could cut out some repetition in toolbox.xml by better organizing it and using XML more appropriately. For instance, the [http://svn.apache.org/viewvc/velocity/tools/trunk/examples/simple/WEB-INF/toolbox.xml?revision=487337&view=markup toolbox.xml for the "simple" example] could be simplified further to something like: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools2Planning" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools2Planning The comment on the change is: create page to track and organize ideas for tools 2.x New page: == Ideas For VelocityTools 2.x == 1. TransparentOnDemandToolsLoading: Instead of a standard HashMap, the idea here is to have a Toolbox, perhaps inheriting HashMap, which will instantiate a tool from its tool-info only when the generic getter is called. This should be a quite interesting performance gain in some situations. We maybe need some attribute to have tools instantiated at toolbox initialization ('instantiate-on-load' ?). The Toolboxes may then pool or at least hold on to instantiated tools for subsequent requests from the template or from other parts of the webapp (see idea 2 below). 2. EasierToolAccessOutsideTemplates: Other objects in my webapp are often jealous of the VelocityViewServlet. They also would like to use some of the tools. Session scoped tools can be reached via the session, but it's not the case for application or request scoped tools. To achieve this, there would be two things to do: - create a separate Toolbox for each scope and store it in the attributes of the corresponding servlet API object (request->!ServletRequest, session->!HttpSession, application->!ServletContext). - the ChainedContext would know to search the attributes for these Toolboxes and pass requests for the tools on to them. (NOTE: depending on the implementation of idea 1 (above) it may be advantageous to have the ChainedContext hold on to requested tools as templates often use them multiple times - We could create a simple utility to help other classes retrieve tools, so they needn't all duplicate the code for finding the toolbox in the attributes and then requesting the tool from the toolbox... 3. SimplifiedToolboxXML: In line with the ideas above, we could cut out some repetition in toolbox.xml by better organizing it and using XML more appropriately. For instance, the [http://svn.apache.org/viewvc/velocity/tools/trunk/examples/simple/WEB-INF/toolbox.xml?revision=487337&view=markup toolbox.xml for the "simple" example] could be simplified further to something like: this is bar. 4. FactorOutBasicVelocityViewStuff: This would create a better basis for bring the [http://velocity.apache.org/engine/devel/veltag.html Veltag] into the project as a sibling of the VelocityViewServlet. 5. SupportAlternateToolboxConfiguration: Not everyone likes XML. I'd like us to make Toolbox management pluggable with provided support for configuration via properties file as well as XML, and i want it to be easier to configure and manage in Java as well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools -- * [http://velocity.apache.org/tools/devel/ Project Website] * [http://www.jajakarta.org/velocity/tools/ Project Website in Japanese] * [http://svn.apache.org/viewcvs.cgi/velocity/tools/trunk/ ViewCVS/SVN] + * VelocityTools2Planning - ideas for the next major version Contributed Code and Examples - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Trivial Update of "ContributedCode" by MichaelGuymon
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGuymon: http://wiki.apache.org/velocity/ContributedCode -- * MultiUberspect -- an Uberspector that can dispatch introspection tasks to custom Uberspectors on a per-class basis * LuceneDocumentUberspect -- An Uberspect for Lucene Documents that works with the above class * JythonUberspect -- An uberspect for handling Jython (Java Python) objects - * ["JRubyUberspect"] -- An Uberspect for JRuby: [http://sprocket.slackworks.com/wiki/published/JRubyUberspect info] [http://sprocket.slackworks.com/wiki/published/Slackocity project] + * ["JRubyUberspect"] -- An Uberspect for JRuby: [http://wiki.sprocket.slackworks.com/instiki/published/JRubyUberspect info] [http://wiki.sprocket.slackworks.com/instiki/published/Slackocity project] == Custom Directives == * ["XPath"] -- XPath evaluating directive, by VladimirKirichenko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityWhitespaceGobbling" by MichaelGiroux
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGiroux: http://wiki.apache.org/velocity/VelocityWhitespaceGobbling The comment on the change is: Describe a new option to set whitespace processing per #setindent directive -- * VelocityWhitespaceGobbleAll * VelocityWhitespaceGobbleNone * VelocityWhitespaceGobbleStructuredTemplates + * VelocityWhitespaceGobbleSetindentDirective The History of the Debate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityWhitespaceGobbleSetindentDirective" by MichaelGiroux
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGiroux: http://wiki.apache.org/velocity/VelocityWhitespaceGobbleSetindentDirective The comment on the change is: Proposal for new #setindent directive New page: For the most part, I want my templates to be readable and I use indenting to accomplish that. The indenting of the template has nothing to do with the desired output. For example, a simple template to generate a Java class might look like this: {{{ import com.myco.MyClass; public Class AnotherClass { #foreach ($t in $types) #if ($t.name.contains("_") Integer $t.name = 0; #if ($t.type == "static") // ignore static type $t.name #end #end #end } }}} This template should produce something like: {{{ import com.myco.MyClass; public Class AnotherClass { Integer v_1 = 0; Integer v_2 = 0; // ignore static type s_0 } }}} Note that the indentation of the Integer statements and the // ignore .. comment are the same even though they have different amounts of leading whitespace in the template. Given that each line of the nested blocks within template are indented further to improve readability, there is no good way for Velocity to know what I really want it to do. There would need to be some marker in the template to indicate where indentation should be set for subsequent lines. The same template can be modified slightly to indicate how to indent lines. {{{ import com.myco.MyClass; public Class AnotherClass { #setindent ## a new setindent directive #foreach ($t in $types) #if ($t.name.contains("_") Integer $t.name = 0; #if ($t.type == "static") // ignore static type $t.name #end #end #end } }}} In this example, a #setindent directive specifies the starting location for all subsequent lines. Velocity would use the whitespace before the #setindent directive as the amount to indent any subsequent text that is emitted. This strategy assumes that all leading whitespace would be ignored, and indentation would be controlled exclusively by the #setIndent directives. I realize that whitespace processing is much more complicated that indentation processing alone. This proposal only addresses how velocity could be enhanced to control indentation of generated text. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityWhitespaceGobbleSetindentDirective" by MichaelGiroux
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGiroux: http://wiki.apache.org/velocity/VelocityWhitespaceGobbleSetindentDirective -- This strategy assumes that all leading whitespace would be ignored, and indentation would be controlled exclusively by the #setIndent directives. - I realize that whitespace processing is much more complicated that indentation processing alone. This proposal only addresses how velocity could be enhanced to control indentation of generated text. + I realize that whitespace processing is much more complicated that indentation processing alone. This proposal only addresses how velocity could be enhanced to control indentation of generated text. Other approaches can be reviewed at VelocityWhitespaceGobbling. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityWhitespaceGobbleSetindentDirective" by MichaelGiroux
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by MichaelGiroux: http://wiki.apache.org/jakarta-velocity/VelocityWhitespaceGobbleSetindentDirective The comment on the change is: Revise specification of #setindent based on mailing list suggestion -- + {{{ + March 9, 2007 - revised description of proposed #setindent directive. + Based on comments in mailing list, the directive would specify an amount of indentation. + }}} For the most part, I want my templates to be readable and I use indenting to accomplish that. The indenting of the template has nothing to do with the desired output. For example, a simple template to generate a Java class might look like this: {{{ import com.myco.MyClass; @@ -33, +37 @@ {{{ import com.myco.MyClass; public Class AnotherClass { + #set ($indent = 4) - #setindent ## a new setindent directive + #setindent($indent) ## a new setindent directive - #foreach ($t in $types) + #foreach ($t in $types) - #if ($t.name.contains("_") + #if ($t.name.contains("_") - Integer $t.name = 0; + Integer $t.name = 0; - #if ($t.type == "static") + #if ($t.type == "static") - // ignore static type $t.name + // ignore static type $t.name + #end + void set${t.name}(Integer v) { + #set ($indent = $indent + 4) + #setindent($indent) + // some code within the method block + #set ($indent = $indent - 4) + #setindent($indent) + } #end #end - #end } }}} - In this example, a #setindent directive specifies the starting location for all subsequent lines. Velocity would use the whitespace before the #setindent directive as the amount to indent any subsequent text that is emitted. + In this example, a #setindent directive specifies the amount of whitespace to inject at the start of each line of generated text and the template is managing a variable ($indent) to keep track of the indentation amount. This strategy assumes that all leading whitespace would be ignored, and indentation would be controlled exclusively by the #setindent() directives. - This strategy assumes that all leading whitespace would be ignored, and indentation would be controlled exclusively by the #setIndent directives. - + This approach requires the template to manage an indentation variable ($indent) and execute #setindent directives. ''The template is pretty messy if there is not much text being generated.'' It would be nice if #setindent managed an internal variable and allowed the template to adjust the variable using absolute, increment and decrement values: + {{{ + #setindent(4) ## set indentation at 4 spaces + #setindent(+4) ## increment indentation by 4 spaces + #setindent(-4) ## decrement indentation by 4 spaces + }}} + + This would result in a template like this: + {{{ + import com.myco.MyClass; + public Class AnotherClass { + #setindent(4) ## set indentation at 4 spaces + #foreach ($t in $types) + #if ($t.name.contains("_") + Integer $t.name = 0; + #if ($t.type == "static") + // ignore static type $t.name + #end + void set${t.name}(Integer v) { + #setindent(+4) ## add 4 spaces to current indentation + // some code within the method block + #setindent(-4) ## remove 4 spaces from current indentation + } + #end + #end + } + }}} + + I realize that whitespace processing is much more complicated that indentation processing alone. This proposal only addresses how velocity could be enhanced to control indentation of generated text. Other approaches can be reviewed at VelocityWhitespaceGobbling. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "Velocity15ReleaseNotes" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/Velocity15ReleaseNotes The comment on the change is: removed "not complete" note about documentation. -- === Other Notes === - * The documentation has been significantly improved. Please note that many but not all new features are written up. + * The documentation has been significantly improved, with new articles on getting started and on building webapps. * !VelocityServlet is now officially deprecated. Please use [http://jakarta.apache.org/velocity/tools/view/ VelocityViewServlet] from the VelocityTools subproject instead. * !VelocityFormatter is also deprecated. Please use the various formatting tools in the VelocityTools subproject. * An optional Maven build is now available. However, ant remains the primary build tool. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "IntelliJSyntaxHighlighting" by jeffblack
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by jeffblack: http://wiki.apache.org/velocity/IntelliJSyntaxHighlighting -- Contributed by Dennis Lundberg (dennisl AT apache DOT org). + IDEA must be shutdown prior to the next step, or else the template file will be deleted. + Put the text below in a file called {{{VelocityTemplateLanguage.xml}}} - and save that file in IDEA's {{{config/filetypes/}}} directory. + and save that file in IDEA's {{{config/filetypes/}}} directory. This directory will be under your + username home directory, not the IDEA install directory. '''{{{VelocityTemplateLanguage.xml}}}''' {{{ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "VelocityTools2Planning" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools2Planning The comment on the change is: update to reflect progress so far -- == Ideas For VelocityTools 2.x == - 1. TransparentOnDemandToolsLoading: Instead of a standard HashMap, the idea here is to have a Toolbox, perhaps inheriting from !HashMap, which will instantiate a tool from its tool-info only when the generic getter is called. This should be a quite interesting performance gain in some situations. We maybe need some attribute to have tools instantiated at toolbox initialization ('instantiate-on-load' ?). The Toolboxes may then pool or at least hold on to instantiated tools for subsequent requests from the template or from other parts of the webapp (see idea 2 below). + 1. TransparentOnDemandToolsLoading: Instead of a standard HashMap, the idea here is to have a Toolbox, which will instantiate a tool from its tool-info only when the generic getter is called. This should be a quite interesting performance gain in some situations. If it seems useful, we could add a special attribute to force a tool to be instantiated at toolbox initialization ('instantiate-on-load' ?). The Toolboxes may then pool or at least hold on to instantiated tools for subsequent requests from the template or from other parts of the webapp (see idea 2 below). (STATUS: done except for the 'instantiate-on-load' attribute, but all needs testing) 2. EasierToolAccessOutsideTemplates: Other objects in my webapp are often jealous of the VelocityViewServlet. They also would like to use some of the tools. Session scoped tools can be reached via the session, but it's not the case for application or request scoped tools. To achieve this, there would be a few things to do: - * create a separate Toolbox for each scope and store it in the attributes of the corresponding servlet API object (request->!ServletRequest, session->!HttpSession, application->!ServletContext). + * create a separate Toolbox for each scope and store it in the attributes of the corresponding servlet API object (request->!ServletRequest, session->!HttpSession, application->!ServletContext). (STATUS: done) - * the ChainedContext would know to search the attributes for these Toolboxes and pass requests for the tools on to them. (NOTE: depending on the implementation of idea 1 (above) it may be advantageous to have the ChainedContext hold on to requested tools as templates often use them multiple times. + * the !ViewToolContext (successor of !ChainedContext) will search the attributes for these Toolboxes and pass requests for the tools on to them. (STATUS: done) - * We could create a simple utility to help other classes retrieve tools, so they needn't all duplicate the code for finding the toolbox in the attributes and then requesting the tool from the toolbox... + * We could create a simple utility to help other classes retrieve tools, so they needn't all duplicate the code for finding the toolbox in the attributes and then requesting the tool from the toolbox... (STATUS: not done) 3. SimplifiedToolboxXML: In line with the ideas above, we could cut out some repetition in toolbox.xml by better organizing it and using XML more appropriately. For instance, the [http://svn.apache.org/viewvc/velocity/tools/trunk/examples/simple/WEB-INF/toolbox.xml?revision=487337&view=markup toolbox.xml for the "simple" example] could be simplified further to something like: {{{ + + + + this is bar. - + - + + - - - - this is bar. }}} + (STATUS: done, but needs testing) - 4. FactorOutBasicVelocityViewStuff: This would create a better basis for bring the [http://velocity.apache.org/engine/devel/veltag.html Veltag] into the project as a sibling of the VelocityViewServlet. + 4. FactorOutBasicVelocityViewStuff: This would create a better basis for bring the [http://velocity.apache.org/engine/devel/veltag.html Veltag] into the project as a sibling of the VelocityViewServlet. (STATUS: mostly done) - 5. SupportAlternateToolboxConfiguration: Not everyone likes XML. I'd like us to make Toolbox management pluggable with provided support for configuration via properties file as well as XML, and i want it to be easier to configure and manage in Java as well. + 5. SupportAlternateToolboxConfiguration: Not everyone likes XML. I'd like us to make Toolbox management pluggable with provided support for configuration via properties file as well as XML, and i want it to be easier to configure and manage in Java as well. (STATUS: done, but needs testing)
[Velocity Wiki] Update of "VelocityTools2Planning" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/VelocityTools2Planning The comment on the change is: add some notes/plans for how & where to keep backward compatibility with 1.x -- 5. SupportAlternateToolboxConfiguration: Not everyone likes XML. I'd like us to make Toolbox management pluggable with provided support for configuration via properties file as well as XML, and i want it to be easier to configure and manage in Java as well. (STATUS: done, but needs testing) + 6. Simplify the package structure of VelocityTools. There are a lot of sub-packages that seem redundant or unnecessary. I'd like to shift things about as much as possible to reduce that. (STATUS: partly done) + + == Backwards Compatibility For VelocityTools 2.x == + + 1. Basic user interfaces - these are things that people use directly without extending + * Our tools - the biggest thing here is the tools themselves. we shouldn't make users have to change their templates at all. we might consider finding some way to provide deprecation notices for things we'd like to change, but i don't think there's many places we'll need to do that. in the meantime, the most we may do is move packages, add setup() methods, and put deprecated subclasses with init() and configure() support in the old tool locations. (STATUS: nothing to be done yet) + * Custom tools - the trick will be to support the init() and configure() methods. Not sure how this will work, but i'm pretty determined to find a way. (STATUS: not done yet) + * Servlets - A lot of people directly use the VVS and VLS. So, while i've moved them to a new package, there are deprecated subclasses at their old location to make this a seamless transition for these folks. (STATUS: done) + * toolbox.xml - We need to create a !FactoryConfiguration that can translate the old xml configuration format to fit the new tool management structure. This should not be too difficult. The trickier part is where we should automatically check for the old format (probably in the deprecated VVS and deprecated VLS, at least). Some thought may need to be put into this. Anyway, the goal is to not force people to update their configurations right away. (STATUS: not done yet) + * Logging stuff - The old !CommonsLog-!LogSystem bridges are deprecated and now extend their successors, the !CommonsLog-!LogChute implementations. I now think that CommonsLogLogChute belongs in Engine, not Tools, but it will have to have a copy here until at least the Engine 1.6 release. Also, !ServletLogger is deprecated and extends its successor, ServletLogChute. For all of these, the transition should be seamless for users also using Engine 1.5. (STATUS: done) + * !WebappLoader - This has been deprecated and now extends its successor, !WebappResourceLoader, which is better named and has logging improvements to match those of the other loaders in Engine 1.5. Again, upgrading to 2.x should not break anything for users also using Engine 1.5. (STATUS: done) + + 2. Common extension points - places where people extend the tools, servlets + * Servlet subclasses - we need to support this as much as possible. (STATUS: partly done) + * Tool subclasses that change init() or configure() - if we meet all the goals in #1 above, then this should happen automatically for the most part. we just need to leave our init() and configure() methods in place, so that calls to super.init() or super.configure() do not fail. + + 3. Advanced API users - those that use tool management without using the servlets (e.g. Spring MVC or "standalone" toolbox users) + * !ViewContext users - can use deprecated one at old location for now (STATUS: done) + * !ChainedContext users - !ChainedContext can extend !ViewToolContext, but what to do about setToolbox()? (STATUS: not done) + * XML!ToolboxManager users - may be possible to hack up a version that reads old toolbox.xml format, and returns a Map of initialized tools for getToolbox(initData), but that initData part is tricky. partial support is probably the best we can do here, unless we leave all the old code intact and just deprecate it. + * !ServletToolboxManager users - similar situation to that of XML!ToolboxManager, but worse. again, probably a choice between partial integration with new infrastructure or else leaving both infrastructures side-by-side with one deprecated. + + 4. Anyone else that digs further into the tool management API for 1.x - Unless we decide to only deprecate the old tool management infrastructure, these people shouldn't upgrade until they're ready to make a lot of changes. :) + - To unsubscribe, e-mail: [EMAIL
[Velocity Wiki] Update of "RoadMap" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/RoadMap -- * Allow macros to be defined in files loaded with #parse [http://issues.apache.org/jira/browse/VELOCITY-281 VELOCITY-281] (WGH) * New directive #evaluate [http://issues.apache.org/jira/browse/VELOCITY-509 VELOCITY-509] (WGH) * Move Texen and Anakia to become separately released subprojects [http://issues.apache.org/jira/browse/VELOCITY-522 VELOCITY-522] (WGH) + * Auto-magically support most List methods on array objects, so template authors can ignore the difference. + * As much as possible, support Iterable in #foreach ([https://issues.apache.org/jira/browse/VELOCITY-379 VELOCITY-379]) and varargs in method calls. (other suggestions for critical issues to include? leave initials if you are enthused enough to drive the issue) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "RoadMap" by NathanBubna
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/velocity/RoadMap -- * Allow macros to be defined in files loaded with #parse [http://issues.apache.org/jira/browse/VELOCITY-281 VELOCITY-281] (WGH) * New directive #evaluate [http://issues.apache.org/jira/browse/VELOCITY-509 VELOCITY-509] (WGH) * Move Texen and Anakia to become separately released subprojects [http://issues.apache.org/jira/browse/VELOCITY-522 VELOCITY-522] (WGH) - * Auto-magically support most List methods on array objects, so template authors can ignore the difference. + * Auto-magically support most List methods on array objects, so template authors can ignore the difference [http://issues.apache.org/jira/browse/VELOCITY-533 VELOCITY-533]. - * As much as possible, support Iterable in #foreach ([https://issues.apache.org/jira/browse/VELOCITY-379 VELOCITY-379]) and varargs in method calls. + * As much as possible, support Iterable in #foreach ([https://issues.apache.org/jira/browse/VELOCITY-379 VELOCITY-379]) and varargs in method calls ([http://issues.apache.org/jira/browse/VELOCITY-534 VELOCITY-534]). (other suggestions for critical issues to include? leave initials if you are enthused enough to drive the issue) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "PoweredByVelocity" by Jacklondon Chen
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by Jacklondon Chen: http://wiki.apache.org/velocity/PoweredByVelocity -- ||[http://scriptella.javaforge.com Scriptella ETL]||Scriptella is an open source ETL(Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows the use of SQL or another scripting language suitable for the data source to perform required transformations. Scriptella [http://scriptella.javaforge.com/docs/api/scriptella/driver/velocity/package-summary.html provides built-in support] for Velocity templates in ETL files|| ||[http://www.springframework.org Spring Framework]||Spring is a layered Java/J2EE application framework, based on code published in Expert One-on-One J2EE Design and Development by Rod Johnson (Wrox, 2002). Specifically, it is a complete, lightweight container providing centralized, automated configuration and wiring of your application objects. It includes a flexible MVC web application framework which is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI.|| ||[http://tammi.sourceforge.net/ Tammi]||Tammi is a Java component based development framework and run-time container for applications supporting web browsers, mobile terminals and/or Swing based user interfaces.|| - ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb provides unit test for whole request process without J2EE server, easy layout for web pages, simple O/R mapping using ANSI/ISO SQL, native support for design pattern named as TRANSACTION_PER_REQUEST, uniform success/fail page.|| + ||[http://velocityweb.sourceforge.net/ VelocityWeb]|| VelocityWeb is a zero-configuration web application framework for J2EE. It provides new technology for developing/unit testing without J2EE server.It uses Velocity HTML template files as view layer and Apache Common DBUtils as DAO layer following design pattern named as TRANSACTION_PER_REQUEST.|| ||[http://sourceforge.net/projects/webwork/ WebWork]||WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks. WebWork now supports Velocity with their 1.0 release.|| ||[http://www.ztemplates.org/ ztemplates]|| web framework with java 1.5 - uses object injection, annotations , generics and reflection - support for templating, data binding, form validation (with Ajax/DWR), security, search-engine friendly urls and i18n - gui components like tree and tabbed pane - supports Apache Velocity, JSP and other technologies for rendering webpages.|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Velocity Wiki] Update of "Velocity15ReleaseNotes" by WillGlassHusain
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Velocity Wiki" for change notification. The following page has been changed by WillGlassHusain: http://wiki.apache.org/velocity/Velocity15ReleaseNotes -- * There remain various subtle escaping bugs * Macros cannot be defined in one file and included with #parse in another. See MacroIssues for more information. + * If you call VelocityEngine.evaluate() (or use the RenderTool) from within a macro and a #foreach loop, you will not be able to access the loop variable. See [https://issues.apache.org/jira/browse/VELOCITY-504 Velocity-285]. + * In order to run "ant test" with ant 1.6.x, you will need to copy the junit.jar into /lib. Otherwise, please upgrade to ant 1.7 (which access the junit jar from within the Velocity classpath). === Other Notes === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]