Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elda documentation: *Rendering with Velocity* #175

Open
jgrzebyta opened this issue Nov 17, 2016 · 2 comments
Open

elda documentation: *Rendering with Velocity* #175

jgrzebyta opened this issue Nov 17, 2016 · 2 comments
Labels

Comments

@jgrzebyta
Copy link

I found following errors in the documentation:

  1. Line 8 in the example code of VelocityRenderer:
api:variable [
     api:name "_resourceRoot"; 
     api:value "/myEldaApp"
   ];

If the user will not change default location of elda-assets that the resource name is "/elda-assets/".

  1. Line 12 the same place:
api:variable [
     api:name "_velocityPath"; 
     api:value "/var/lib/tomcat7/local-assets/velocity, /var/lib/tomcat7/elda-assets/velocity"
   ]

there should be before comma character in the api:value otherwise does not work.
Thus correct value is:

api:value "/var/lib/tomcat7/local-assets/velocity , /var/lib/tomcat7/elda-assets/velocity"
@ashleysommer
Copy link

I ran into a similar problem with 1.3.19
I fixed it (a hacky workaround) by defining
VELOCITY_PATH=",/velocity" environment variable.
You can see in the source here: https://github.com/epimorphics/elda/blob/master/elda-lda/src/main/java/com/epimorphics/lda/renderers/velocity/VelocityRendering.java#L224
It adds defaultVelocityRoot to the end of the search string, and defaultVelocityRoot comes from the VELOCITY_PATH environment variable.

It may not be exactly the same problem, as this, but that fixed it for me.

ehedgehog pushed a commit that referenced this issue Apr 18, 2017
@ehedgehog
Copy link
Contributor

I have been unable to reproduce the problem. Could you provide a
complete minimal example, please?

Chris

@ehedgehog ehedgehog added the bug label Apr 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants