velocity 2 jar in maven repository

[jmeter tea]

Hello,

I was expecting to download velocity 2 jar from the link:
https://repo1.maven.org/maven2/org/apache/velocity/velocity/
But only until velocity 1.7 exists there.
Should version 2 be uploaded to this url or should it be found elsewhere?

Re: Setting context value from template broken in 2.0

[Claude Brisson]

On 05/12/2017 23:46, Veit Guna wrote:


Hi.

I just gave 2.0 a testdrive and some issues occurred to me.

a) Until 1.7 I could use

#set($subject = "Hey Buddy")

To pass back context values to the caller (java code). I could simply
get it from the Map:

contextMap.get("subject");

Now this doesn't work anymore. The key is not contained in the context
after the template has been processed.
Is this by intention? Is there another way of passing back values from
the template?


It does work with this following code:

VelocityContext context = new VelocityContext();
template.merge(context, output);
/* template contains #set($suject = "hello there") */
System.out.println("subject = " + context.get("subject"));

Ok, I saw your second email. Well, anyhow, the behavior should still be 
the same.

Note that you can turn it off with:

template.provide.scope.control = true


b) org.springframework.ui.velocity.VelocityEngineFactoryBean doesn't
work anymore if configured like this:



or this (leaving it out completely results in the same):



Spring uses an old ResourceLoader for classpath scanning (can be fixed
by using velocitys own). Also it uses
the old *Chute logger class. Both resulting in appropriate exceptions
not finding matching classes.

As Spring announced to drop Velocity Support with 5, this is maybe not a
topic for you guys anymore.


On the contrary, they just don't want to maintain the Velocity 
integration themselves, which means we should host the few glue classes 
here. Adapting the org.springframework.ui.velocity pakage for 2.0 should 
be trivial, we're just waiting for someone to contribute it.


Regards,

  Claude


But it would have been nice to keep these classes for a while to not
break existing projects .

So let's forget about b). Does anyone has a clue about a)?

Cheers
Veit




-
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org




On 05/12/2017 23:46, Veit Guna wrote:

Hi.

I just gave 2.0 a testdrive and some issues occurred to me.

a) Until 1.7 I could use

#set($subject = "Hey Buddy")

To pass back context values to the caller (java code). I could simply
get it from the Map:

contextMap.get("subject");

Now this doesn't work anymore. The key is not contained in the context
after the template has been processed.
Is this by intention? Is there another way of passing back values from
the template?

b) org.springframework.ui.velocity.VelocityEngineFactoryBean doesn't
work anymore if configured like this:



or this (leaving it out completely results in the same):



Spring uses an old ResourceLoader for classpath scanning (can be fixed
by using velocitys own). Also it uses
the old *Chute logger class. Both resulting in appropriate exceptions
not finding matching classes.

As Spring announced to drop Velocity Support with 5, this is maybe not a
topic for you guys anymore.
But it would have been nice to keep these classes for a while to not
break existing projects :).

So let's forget about b). Does anyone has a clue about a)?

Cheers
Veit




-
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org

strict mode but ignore null

[Veit Guna]

Hi.

I would like to setup Velocity so that invalid (=unknown)
properties/methods are throwing an exception, but null values shouldn't.
And that per default.
I know that I could use quiet references, but I would have to think
about everytime, whether it could be null or not. Or use it all the time,
which I would like to avoid - since I'm lazy :).

I activated strict mode which fails on unknown properties/methods -
which is good.

But it also fails on something like

$valid.nullPropertyToObject.validproperty

What I would like is, that it doesn't fail because of
nullPropertyToObject being null.

My basic idea around this is, to spot real errors like unknown
properties during tests.
I don't really care about actual null values/references - these should
be rendered empty in case of null during runtime.

In my tests I assert, that the rendering basically works (all
properties/methods exist) and values are properly filled.
But I don't want (ever) to fail only because one property is null during
runtime.

Is this somehow possible?

I just upgraded to 2.0 hoping that this is handled more flexible now.

Cheers
Veit





-
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org