gmane.comp.jakarta.velocity.devel

Re: [GSoC 2012] Scope of the JSR 223 API coverage in implementation

Dishara Wijewardana — 2012-05-16T15:05:31


Sure, I will start.
Thanks

Re: Out-of-memory with #parse in #foreach

Nathan Bubna — 2012-05-16T13:37:12

Yeah, i think this is worth filing a bug report.  It's great that
things work correctly with caching on, but it still sounds like
something is funky there.

On Wed, May 16, 2012 at 2:03 AM, Marnix Bindels
<Marnix.Bindels< at >zorgttp.nl> wrote:

Re: [GSoC 2012] Scope of the JSR 223 API coverage in implementation

Claude Brisson — 2012-05-16T12:07:54

I started a page on the wiki:

  http://wiki.apache.org/velocity/VelocityScriptingApi

it will be more convenient than the dev list. Feel free to
change its whole structure.


  Claude

On Sun, 13 May 2012 01:13:45 +0530
Dishara Wijewardana <ddwijewardana< at >gmail.com> wrote:

Out-of-memory with #parse in #foreach

Marnix Bindels — 2012-05-16T09:03:45

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 <loader>.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

Re: [GSoC 2012] Scope of the JSR 223 API coverage in implementation

Dishara Wijewardana — 2012-05-12T19:43:45

On Sun, May 13, 2012 at 12:15 AM, Dishara Wijewardana <
ddwijewardana< at >gmail.com> wrote:


We also have to add a new class called ScriptEngineManager who is
responsible of managing engine related stuff,(which also recommends from
the spec)
This will allow users to maintain a global scope of attributes visible in
all ScriptEngines,

Re: [GSoC 2012] Scope of the JSR 223 API coverage in implementation

Dishara Wijewardana — 2012-05-12T18:45:14

On Mon, May 7, 2012 at 10:10 PM, Dishara Wijewardana <
ddwijewardana< at >gmail.com> wrote:


  ScriptContext - already a discussed in detail (which methods directly
supports, and which need to implement)



   ScriptEngineInfo -  This can be implemented from loading the info from a
property file.

Re: [VOTE] Velocity Master 1 Release Quality

Nathan Bubna — 2012-05-11T16:28:49

On Fri, May 11, 2012 at 12:45 AM, Antonio Petrelli
<antonio.petrelli< at >gmail.com> wrote:

Yeah, those are good points.  Definitely don't want to release the
master for all community changes.

Re: [VOTE] Velocity Master 1 Release Quality

Antonio Petrelli — 2012-05-11T07:45:33

2012/5/11 Claude Brisson <claude< at >renegat.net>:

Good points.
It's no problem to change it, after all it's a matter of minutes.
If anyone has a different opinion, I would cancel the vote and modify
the master pom accordingly.

Antonio

Re: [VOTE] Velocity Master 1 Release Quality

Claude Brisson — 2012-05-11T07:38:56

I see that team members informations are in both places: in the
master pom, and in the site pom (which does not depend on the master,
perfect). I'd be in favour of removing them from the master pom, for
several reasons:

1. it's redundant, and it better belongs to the site (oh and by the way
it isn't up to date, as Will is still mentioned as the PMC Chair)

2. we're not gonna release a new master (which implies new releases for
each and every subproject) each time we have a new committer, so if we
keep this information here, it will quickly become out-of-date

But I'm maybe missing something...


  Claude

On Thu, 10 May 2012 11:24:05 -0700
Nathan Bubna <nbubna< at >gmail.com> wrote:

Re: [VOTE] Velocity Master 1 Release Quality

Nathan Bubna — 2012-05-10T18:24:05

+1

On Thu, May 10, 2012 at 11:18 AM, Antonio Petrelli
<antonio.petrelli< at >gmail.com> wrote:

Re: [VOTE] Velocity Master 1 Release Quality

Antonio Petrelli — 2012-05-10T18:18:54

2012/5/10 Antonio Petrelli <antonio.petrelli< at >gmail.com>:

+1
Antonio

[VOTE] Velocity Master 1 Release Quality

Antonio Petrelli — 2012-05-10T18:18:15

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

Fwd: Fwd: Does Apache already have access to JSR 223 TCK

Nathan Bubna — 2012-05-10T17:46:24

---------- Forwarded message ----------
From: Daniel Kulp <dkulp< at >apache.org>
Date: Thu, May 10, 2012 at 10:16 AM
Subject: Re: Fwd: Does Apache already have access to JSR 223 TCK
To: board< at >apache.org
Cc: Nathan Bubna <nbubna< at >apache.org>, private< at >bsf.apache.org

On Thursday, May 10, 2012 09:56:47 AM Nathan Bubna wrote:

Would need to go to jcp-open< at >apache.org

That said, the answer is "no, we don't currently have it except as part of
the full J2EE TCK suite."  The jsr223 page says:

 - The JSR 223 TCK source will be made available at no extra charge to J2EE
licensees.

Thus, I'm a little surprised it's not made available from our java partner
download page. (just checked)  Not quite sure how to get access though.
That will require some more investigation.

Dan

--
Daniel Kulp
dkulp< at >apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Fwd: Does Apache already have access to JSR 223 TCK

Nathan Bubna — 2012-05-10T16:58:19

Do ya'll know the answer to this?

---------- Forwarded message ----------
From: Dishara Wijewardana <ddwijewardana< at >gmail.com>
Date: Thu, May 10, 2012 at 9:50 AM
Subject: Does Apache already have access to JSR 223 TCK
To: Velocity Developers List <dev< at >velocity.apache.org>, Claude Brisson
<claude< at >renegat.net>

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).

--
Thanks
/Dishara

Does Apache already have access to JSR 223 TCK

Dishara Wijewardana — 2012-05-10T16:50:30

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).

[GSoC 2012] Scope of the JSR 223 API coverage in implementation

Dishara Wijewardana — 2012-05-07T16:40:22

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*

Re: Problem when building velocity trunk

Dishara Wijewardana — 2012-05-07T15:44:56


Great,
I was going through the spec and gathering points for my first task.(sketch
a class diagram of the classes that going to implement of jsr 223 spec).
I also looked in to the sun implementation on JSR 223 on top of velocity,
and there was only Engine and the Factory implementation.


Regards,

Re: Problem when building velocity trunk

Dishara Wijewardana — 2012-05-05T16:49:32


Hi Claude,
I tried this but failed to build as the trunk pom points to an old snapshot
version of the master.
I created a JIRA[1] and attached the fixed pom as a patch .

With this change I was able to successfully build the velocity trunk code
with tests.

[1] - https://issues.apache.org/jira/browse/VELOCITY-824

[ANNOUNCE] Velocity Master 1 test build available (take 2)

Antonio Petrelli — 2012-05-05T12:42:55

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

[ANNOUNCE] Velocity Master 1 test build available

Antonio Petrelli — 2012-05-02T18:17:56

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

Re: Problem when building velocity trunk

Antonio Petrelli — 2012-05-02T12:30:05

2012/5/2 Claude Brisson <claude< at >renegat.net>



No, it's not this way especially if you think about version numbering.
velocity-engine-parent has its version, velocity-tools-parent too. What if
you release velocity-engine-parent various times? Should you release the
other dependent subprojects?
Instead, velocity-master will have a very slow-paced release plan, in other
words it will be released only when strictly needed (e.g. the first
version, or change in PMC/committers).



Sure, I will try to create a test build this evening (CET).

Antonio