http://blog.gmane.org/gmane.comp.jakarta.velocity.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16911 <pre>Hi all, As per Claude's suggestion, I have interpreted the JSR 223 with inline UML and please find the following. This is to review this before adding to the wiki.Please add anything missing or need to correct before adding to wiki for the first time. ScriptEngine *------* ScriptContext *------ ** Namespace *------* Scope * ----- ** Attributes *------* Reader *------* Writer ScriptEngineInfo *------* ScriptEngineFactory *------ ** ScriptEngine HttpScriptContext * IS-A* ScriptContext Namespace *IS-A* java.util.Map </pre> Dishara Wijewardana 2012-05-17T18:19:16 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16907 <pre>Hi all, I was testing a template collection that uses #parse inside some #foreach, which worked all fine inside eclipse but crashed when used in the stand-alone application running with a low heap setting with an OutOfMemoryError: Java heap space. I was able overcome this by setting the &lt;loader&gt;.resource.loader.cache to "true". Still I wanted to let you know about this as it may be an indicator of a resource management issue of sorts anyway. The parsed resource is constant, with caching off it gets reported as found and loaded by the ResourceManager for each iteration (some 6000 times in the example). I understand that without caching it gets loaded every time, but why do the previously loaded instances keep occupying memory? Perhaps by design: with proper caching in place, this is not an issue. If not and you're interested: let me know whether I should file a bug report/send in the examples. Thanks, Marnix </pre> Marnix Bindels 2012-05-16T09:03:45 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16899 <pre>The Velocity Master 1 test build has been available since 5th May 2012. Distribution: * https://repository.apache.org/content/repositories/orgapachevelocity-027/org/apache/velocity/velocity-master/1/velocity-master-1-source-release.zip Maven 2 staging repository: * https://repository.apache.org/content/repositories/orgapachevelocity-027/ If you have had a chance to review the test build, please respond with a vote to release it or not: -1: Leave at test build +1 Release it Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s. Antonio </pre> Antonio Petrelli 2012-05-10T18:18:15 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16896 <pre>Hi all, I saw some mail archives that Apache BSF has requested/had intention for requesting for the JSR 223 TCK. If they have that from Apache point of view, I think we can also use that. It is really helpful when implementing the spec. (specially if the TCK code is available, it is very efficient in implementing it). </pre> Dishara Wijewardana 2012-05-10T16:50:30 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16895 <pre>Hi all, I am starting this thread to keep track of the API scope of this implementation which we going to cover. All together, JSR 223 API has two main packages. Will continue updating the thread. And any ideas, thoughts are welcome.!! *javax.script* *Interfaces * Compilable Invocable Namespace ScriptContext ScriptEngine - already discussed in detail ScriptEngineFactory - already discussed in detail ScriptEngineInfo *javax.script.http * *Interfaces* * * *HttpScriptContext* *HttpScriptRequest* *HttpScriptResponse* </pre> Dishara Wijewardana 2012-05-07T16:40:22 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16892 <pre>Sorry I forgot to close the staging repository. Here is the correct announcement. The test build of Velocity Master 1 is available. No determination as to the quality of Velocity Master 1 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build. Distribution: * https://repository.apache.org/content/repositories/orgapachevelocity-027/org/apache/velocity/velocity-master/1/velocity-master-1-source-release.zip Maven 2 staging repository: * https://repository.apache.org/content/repositories/orgapachevelocity-027/ A vote regarding the quality of this test build will be initiated within the next couple of days. Antonio </pre> Antonio Petrelli 2012-05-05T12:42:55 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16891 <pre>The test build of Velocity Master 1 is available. No determination as to the quality of Velocity Master 1 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build. Distribution: * https://repository.apache.org/service/local/repositories/orgapachevelocity-027/content/org/apache/velocity/velocity-master/1/velocity-master-1-source-release.zip Maven 2 staging repository: * https://repository.apache.org/service/local/repositories/orgapachevelocity-027/content/ A vote regarding the quality of this test build will be initiated within the next couple of days. Antonio </pre> Antonio Petrelli 2012-05-02T18:17:56 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16887 <pre>Hi to all, I am trying to build velocity trunk from [1] . But it fails when try to build from trunk level. It fails with unresolvable parent. This trunk root pom points to a velocity-master artifact. Or I am I building a wrong source code ? [1] - http://svn.apache.org/repos/asf/velocity/engine/trunk/ </pre> Dishara Wijewardana 2012-05-01T18:09:59 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16882 <pre>Hi Claude and all, I am really ecstatic that my proposal in GSoC 2012 for Apache Velocity got accepted. I would like to dedicate my time and end this project in a high and contribute to Velocity. Thank you Apache Velocity. And special thanks goes to Claude for guiding me with the project proposal and etc. </pre> Dishara Wijewardana 2012-04-23T19:10:27 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16863 <pre>Hi, I know I'm a little bit late for GSoC project discussion. I'm terribly sorry if I selected a wrong method to contact Velocity team. I am interested in work upon issue https://issues.apache.org/jira/browse/VELOCITY-706 for a couple of reasons, they are: 1) I use Velocity at work and this feature would be great to have. 2) I am a student and I'd love to participate in GSoC to get some experience and to make something useful for the community. So, please tell me if I can help with that. I have nearly 2 years experience in field of Java SE and less in EE. My job is Java software developer and currently I study to get a Master's degree in "applied math and IT". I use Velocity as user and I'm very exited about its development. </pre> Constantine N 2012-03-26T20:02:10 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16862 <pre>Hi all, I am a student who likes to take part in GSoC 2012 and I am really interested in implementing a JSR spec which is always an interesting task to do. . I think this implementation will give a better value addition to Velocity as it has a industry standard support in back_end and will allows JSR 223 clients who likes Velocity to migrate without much effort I am willing to contribute this wonderful project idea (which as since last couple of years as seems) and continue the contribution further on Velocity. Hi Vincent, I couldn't reach to the links you provided in the JIRA[1] regarding this idea. I think the content has been removed . Hi Thomas, But I went through the specification and also downloaded the doc. Is it expected to implement the whole spec. I mean making VELOCITY a 100% compliant of JSR 223 ? It will be great if I can get to know the scope of the project and some more detail regarding the $subject so that I can understand the project in nutshell. (i.e is it expected to test the whole i</pre> Dishara Wijewardana 2012-03-25T15:38:29 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16861 <pre>Hi, I am Gayashan Amarasinghe, a 3rd year Computer Science &amp; Engineering undergraduate from University of Moratuwa, Sri Lanka. I would like to participate in GSoC 2012 with Apache Velocity Project. I am interested in the idea of integrating Google Chart Tools [1] listed in issues. This is my first attempt at GSoC. So i would be really glad if i could get some pointers to start understanding the code base and the project. I really like working with Google tools and libraries and i think it would be pretty cool if we can get Google chart tools to be integrated with web applications. [1] https://issues.apache.org/jira/browse/VELTOOLS-96 Thank you in advance. </pre> Gayashan Amarasinghe 2012-03-23T15:46:01 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16859 <pre>Hi Team, Can you please forward me the Requirement doc and the Source code of Anakia project. Thanks &amp; regards, Ahshan M.d </pre> ahshan md 2012-03-22T15:24:40 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16857 <pre>Hey devs. Looks like we only need to tag our issues with "gsoc2012" (in the Labels field) to have them listed on the "GSoC 2012 Tasks" page: https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12319270 I tagged some of them, maybe you have other ideas. Claude </pre> Claude Brisson 2012-03-22T14:23:26 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16854 <pre>foreach support for Closeable Iterator -------------------------------------- Key: VELOCITY-820 URL: https://issues.apache.org/jira/browse/VELOCITY-820 Project: Velocity Issue Type: Improvement Components: Engine Reporter: Robert Fuller Priority: Minor Attachments: foreach.diff would be nice if #foreach would do close the iterator if it implements Closeable. This will allow better resource management when using foreach to do things like run sql queries, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Robert Fuller (Created) (JIRA 2012-03-15T16:55:38 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16849 <pre>Maven pom.xml which uses JavaCC to generate Parser files for Velocity --------------------------------------------------------------------- Key: VELOCITY-819 URL: https://issues.apache.org/jira/browse/VELOCITY-819 Project: Velocity Issue Type: Improvement Components: Engine Affects Versions: 2.x Reporter: Jarkko Viinamäki This patch is meant for the new Velocity 2.0 Maven based build. Currently the problem is that it is difficult to generate new Parser source files if the Parser.jjt files is changed. This patch automates the whole process. The patch adds support for two command line arguments: To generate new Parser source files after you have changed the main/parser/Parser.jjt, use command line switch: mvn -Dparser.create=true package To generate new AST Node source files after you have done major changes to the parser (new nodes/directives), use command line switch: mvn -Dparser.create=true -Dparser.nodefiles=true pac</pre> Jarkko Viinamäki (Created) (JIRA 2012-03-13T17:48:38 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16846 <pre> [ https://issues.apache.org/jira/browse/VELTOOLS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13224527#comment-13224527 ] Christopher Schultz commented on VELTOOLS-126: ---------------------------------------------- Here's a stab at a patch. I'm not sure exactly at which level a configuration option should be put (ErrorsTool, ActionMessagesTool, or MessageResourcesTool), so any suggestions would be appreciated. Here's the meat of the patch (against 2.0.x, but I think trunk is identical): Index: src/main/java/org/apache/velocity/tools/struts/StrutsUtils.java =================================================================== --- src/main/java/org/apache/velocity/tools/struts/StrutsUtils.java(revision 1238717) +++ src/main/java/org/apache/velocity/tools/struts/StrutsUtils.java(working copy) &lt; at &gt;&lt; at &gt; -26,6 +26,7 &lt; at &gt;&lt; at &gt; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpSession; +import org.apache.commons.lang.StringEscapeUtils; import</pre> Christopher Schultz (Commented) (JIRA 2012-03-07T17:32:57 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16845 <pre> [ https://issues.apache.org/jira/browse/VELTOOLS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13224501#comment-13224501 ] Christopher Schultz commented on VELTOOLS-126: ---------------------------------------------- ErrorsTool now uses StrutsUtils.errorMarkup whose code looks a little different: String message; while (reports.hasNext()) { message = null; ActionMessage report = (ActionMessage)reports.next(); if (resources != null &amp;&amp; report.isResource()) { // TODO: VELTOOLS-126 - XSS vulnerability here // TODO: unless we HTML-escape some stuff message = resources.getMessage(locale, report.getKey(), report.getValues()); } results.append(prefix); if (message != null) { results.append</pre> Christopher Schultz (Commented) (JIRA 2012-03-07T16:54:57 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16844 <pre> [ https://issues.apache.org/jira/browse/VELOCITY-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarkko Viinamäki resolved VELOCITY-741. --------------------------------------- Resolution: Won't Fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jarkko Viinamäki (Resolved) (JIRA 2012-03-07T16:49:00 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16841 <pre>ValidatorTool generates invalid XHTML even when in XHTML mode ------------------------------------------------------------- Key: VELTOOLS-152 URL: https://issues.apache.org/jira/browse/VELTOOLS-152 Project: Velocity Tools Issue Type: Bug Components: VelocityStruts Affects Versions: 2.0 Reporter: Christopher Schultz Assignee: Christopher Schultz When using the validator tool in XHTML mode, the main "validate" method emits code like this: function validateMyForm(form) { if (bCancel) return true; else { var formValidationResult; formValidationResult = validateInteger(form) &amp;&amp; validateRequired(form) &amp;&amp; validateMaxLength(form) &amp;&amp; validateMask(form) &amp;&amp; validateIntRange(form); return (formValidationResult == 1); } Note the use of bare "&amp;" characters, which is not valid XHTML. Most web browsers will ignore this little quirk unless they are in XML parsing mode (usually enabled by setting the conte</pre> Christopher Schultz (Created) (JIRA 2012-03-06T16:12:59 http://comments.gmane.org/gmane.comp.jakarta.velocity.devel/16839 <pre>Case-insensitive matching ${object.methodName} == ${object.methodname} == ${object.methodName} ---------------------------------------------------------------------------------------------- Key: VELOCITY-818 URL: https://issues.apache.org/jira/browse/VELOCITY-818 Project: Velocity Issue Type: New Feature Components: Engine Affects Versions: 1.7 Reporter: Mark S I thought I would share the following code with the Apache Velocity community. Currently there is no easy way for Velocity to do a case-insensitive match on a property or method. Below is my implementation to achieve this. VelocityContext velocityContext = new VelocityContext(); { context.put( "aNumericValue", "1234567890" ); } | If String template = | Then String evaluatedTemplate = | | ${aNumericValue} | 1234567890 | | ${anumericvalue} | 1234567890 | | ${</pre> Mark S (Created) (JIRA 2012-02-10T16:44:59 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.jakarta.velocity.devel