topic Re: problem with ftl template. in Alfresco Archive

problem with ftl template.

need — Sun, 09 Oct 2011 18:44:15 GMT

Hi all,I have a problem with a dashlet 3.4d with Alfresco Share. I have followed many tutorials but I can not solve my problem. Let me explain.I created Alfresco webscripts makes me a search for all documents that have a certain aspect. and return a json and it works if I access the page http://loca

Re: problem with ftl template.

jordiv — Mon, 10 Oct 2011 07:31:39 GMT

It seems that your modelli variable isn't a list.
Have you tried printing its value?

Cheers,
Jordi.

Re: problem with ftl template.

need — Mon, 10 Oct 2011 07:48:27 GMT

no i don't have printed this variable? How can i print the variable in file log for example?

Thanks

Re: problem with ftl template.

need — Mon, 10 Oct 2011 07:52:04 GMT

the instructions var data = connector.call("let/modelli") what it returns? And in what format?

Re: problem with ftl template.

scouil — Mon, 10 Oct 2011 08:14:42 GMT

Or it could just be that connector.call("let/modelli"); fails (doesn't return with a 200 status).
In this case you enter in the "else" where model.modelli is assigned the string "zzzzzz" which converts into a freemarker.template.SimpleScalar.
I'm not sure what you're trying to do with this but, even in the "else", model.modelli should be an array or your html template will fail.

Re: problem with ftl template.

need — Mon, 10 Oct 2011 08:18:34 GMT

Ok I printed the variable (modelli) in the dashlet and i see zzzz, then it means that the state of the remote call is not 200. How can I fix this?

I have to change something in the connection string? (Let / modelli)?

Thank a lot.

Re: problem with ftl template.

jordiv — Mon, 10 Oct 2011 09:03:39 GMT

Try using get instead of call and put a "/" at the beginning:


var data = connector.get("/let/modelli");
‍‍‍

It this doesn't work you can check what status code are you getting from your webscript.

Cheers,
Jordi.

Re: problem with ftl template.

scouil — Mon, 10 Oct 2011 09:14:17 GMT

To begin with, data.status doesn't directly returns the code but a ResponseStatus object ( http://wiki.alfresco.com/wiki/Surf_Platform_-_Freemarker_Template_and_JavaScript_API#ResponseStatus ).
So you should do

if (data.status.code == 200)‍

instead of

if (data.status == 200)‍

But I would advise you to return the response in the modelli whatever the code is:

var connector = remote.connect("alfresco");
var data = connector.call("let/modelli");
var result = eval('(' + data + ')');
model.modelli = result;
‍‍‍‍‍

and handle the display in your html template


<#if modelli.status.code == 200>
    <table>
         <#list modelli.response["modelli"] as mod>
            <tr>
               <td><b>Name</b></td><td>${mod.name}</td>
            </tr>
            <tr>
            <td><b>Link</b></td><td><a href="${url.context}${mod.link}?guest=true">${url.context}${mod.link}</a></td>
            </tr>
         </#list>
    </table>
<#else>
    Error ${modelli.status.code}: <br />
    ${modelli.status.message}
</#if>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I haven't tested it so it might be full of syntax errors but I hope you get the point.

Re: problem with ftl template.

need — Mon, 10 Oct 2011 09:23:11 GMT

ok i ok I found the problem that did not entry in the IF block. I had to put a slash at the beginning of the string let / models (/ let / templates /).

But now I can print var data is returned: {"modelli" : [ {"name" : "consulente.xls", "link" : "\/alfresco\/d\/d\/workspace\/SpacesStore\/b632375f-e6a1-40e2-a2ee-dd858a4f8dc2\/consulente.xls", } ] }

Now how do I access from ftl template at variable name and link variable?

Thanks at all.

Re: problem with ftl template.

scouil — Mon, 10 Oct 2011 09:33:10 GMT

Hum… I'm OK to help when you're stuck but don't expect us to do your whole job.
How about you give it a try on your own and come back posting here if you're actually stuck? I bet you'll get it to work with the first thing you'll try.

Re: problem with ftl template.

need — Mon, 10 Oct 2011 12:25:09 GMT

ok thanks and sorry,

I tried the solution suggested by you and in your template gave me modelli.status not definied (I understand why), however, to go forward I removed the if block (the template) and in dashlet displays data correctly.

But now I have another problem that I can not fix, every time I add a new aspect to me is this error:

Error Message: 09100001 Failed to execute script 'classpath*:alfresco/web-extension/site-webscripts/org/alfresco/components/dashlets/getmodel.get.js': 09100000 SyntaxError: missing ] after element list (file:/C:/Alfresco/tomcat/shared/classes/alfresco/web-extension/site-webscripts/org/alfresco/components/dashlets/getmodel.get.js#3(eval)#5)‍

and this exception

Exception: org.mozilla.javascript.EcmaError - SyntaxError: missing ] after element list (file:/C:/Alfresco/tomcat/shared/classes/alfresco/web-extension/site-webscripts/org/alfresco/components/dashlets/getmodel.get.js#3(eval)#5)‍

and this is my js controller file


var connector = remote.connect("alfresco");
var data = connector.get("/let/modelli");
var result = eval('(' + data + ')');
model.result = result;
‍‍‍‍‍‍

If i refresh the page http://127.0.0.1:8080/alfresco/service/let/modelli see correctly

{"modelli" : [
        {"name" : "consulente.xls",
         "link" : "\/alfresco\/d\/d\/workspace\/SpacesStore\/b632375f-e6a1-40e2-a2ee-dd858a4f8dc2\/consulente.xls",
        }
        {"name" : "doc1.doc",
         "link" : "\/alfresco\/d\/d\/workspace\/SpacesStore\/1019756f-4624-4ee7-8095-c78f57209560\/doc1.doc",
        }
]
}‍‍‍‍‍‍‍‍‍

Thanks all.

Re: problem with ftl template.

scouil — Mon, 10 Oct 2011 12:44:19 GMT

I actually never used the remote API so I don't really know how to use it.
Removing the "if" block works as long as the "remote.call" returns the expected result but you should find a way to retrieve and handle the errors.

Your current error is due to an error in your JSON syntax.
First:
You only got comas as long as the attribute isn't the last one in the object. e.g.

{"first":1,  //here is a coma
 "last":2    //no coma
}‍‍‍

so none of your "link" attributes shouldn't end with a coma since these are the last attributes of the object.

Second:
In an array, the objects should, once again, be separated by comas. e.g.

{"myArray": ["first":1,
                   "last":2} , //here is a coma
                  {"first":1,
                    "last":2}  //no coma (last object of the array)
                   ]‍‍‍‍‍

Considering these rules, your json output should be:


{"modelli" : [
        {"name" : "consulente.xls",
         "link" : "\/alfresco\/d\/d\/workspace\/SpacesStore\/b632375f-e6a1-40e2-a2ee-dd858a4f8dc2\/consulente.xls"
        },
        {"name" : "doc1.doc",
         "link" : "\/alfresco\/d\/d\/workspace\/SpacesStore\/1019756f-4624-4ee7-8095-c78f57209560\/doc1.doc"
        }
]
}
‍‍‍‍‍‍‍‍‍‍‍

Re: problem with ftl template.

need — Mon, 10 Oct 2011 13:10:18 GMT

Thank you for your immense availability,

use alfresco recently, I find it a powerful, yet extremely complex at the beginning to start to understand its mechanisms for the development and customization, this is because around documentation very scattered and not always updated.

Even with this discussion I'm learning a lot and is very useful for me to understand certain mechanisms.

Now I ask you an opinion, you think to do what I'm doing (view in a dashlets all docs who have a particular aspect), it is conceptually wrong to use the method I'm using? Is there any other method more effective to do this? I use this method because the documentation I found online seemed the only valid for my problem.

Re: problem with ftl template.

scouil — Mon, 10 Oct 2011 13:24:33 GMT

I'm usually more of an online-doc guy but for Alfresco, starting with books was an awesome plus.
I particularly liked Alfresco Developer guide by Jeff Potts (who's now the head of Alfresco community).

About what you're doing, I don't know all your needs so I can't really tell you but my advice would be to stick with alfresco's default UI.
If you start developing your own UI, your users will keep on asking for new features until your dashlet is no longer maintainable.
Alfresco Share's default interface is nice and powerful.
So before trying to develop your own alfresco share through an ecosystem of dashlets, have a look at what Alfresco can do out of the box.

Good luck,