thymeleaf / thymeleaf-itutorial Goto Github PK

Now Thymeleaf 2.1.2 has been released, maybe the interactive tutorial should be updated to this version, in order to not make it run on a snapshot (for 2.1.1, currently...)

I think we should try switching to Heroku (by moving http://itutorial.thymeleaf.org there) and see whether it correctly handles our traffic for this tutorial.

If after a time everything goes OK, the current paid hosting could be shut down.

At the about section, this can be read:

This interactive tutorial has been created by the Thymeleaf Team using great open source tools like:

• ACE web editor
• Adobe Source Code Pro font
• jQuery
• Spring Framework

Hmmm... and Thymeleaf? ;-)

Current version of the tutorial has only 10 exercises.

Previous version had 14 exercises, so there are 4 exercises which need to be adapted to the new tutorial.

The tutorial app breaks where upgrading to Thymeleaf 2.0.17 or higher.

The problem happens at parsing and executing the template.

With IE8, there are encoding problems in generated sources and dynamic view boxes, for example, when typing Ñ or € in the source code box.

Since the itutorial is hosted at Heroku no stats software is running.

We should configure some stats software in order to get some visitor's feedback, for example, any of the Heroku plug-ins to do it or Google Analytics.

As any arbitrary code can be invoked using SpringEL, a user of the tutorial could type something like

    <span th:text="${T(java.lang.System).exit(0)}">Bye bye</span>

This is a severe issue if you plan to publish the tutorial in some server but it is not a problem for the current installation in Google App Engine, as this commands are ignored (https://developers.google.com/appengine/docs/java/#javalangsystem)

Provide a method to automatically show if the user answer is correct, maybe using the Thymeleaf-testing framework.

When the user types a correct answer, a "Congratulations" message should pop up with a button to move to next exercise.

When a error raises, highlight in the editor the line with the error.

This should be possible to achieve using the getLineNumber() method of TemplateProcessingException class.

New lines are not shown in the Java code dialog (for example, when you want to see Product.java code).

The cause is a ACE JS Editor related issue:
ajaxorg/ace#1551

I am getting below error.I have tried with thymeleaf-spring3 version 2.0.18..Still facing same issue.Error i am getting while sending confirmation mail after check out
HTTP Status 500 - Request processing failed; nested exception is org.springframework.mail.MailPreparationException: Could not prepare mail; nested exception is org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "customer.firstName + ' ' + customer.lastName" (orderConfirmation-email:19).

Please let me know how to fix this.

Thanks
Mausumi

If we have problems with GAE limits we could implements some optimizations like:

• Using CDN for third-party resources (jQuery, ACE, fonts...).
• Do not use a request to show "static view" (do it directly from Javascript).
• Do not use org.springframework.web.servlet.i18n.SessionLocaleResolver but implement a stateless LocaleResolver (just using the request parameter 'locale')
• Split up the tutorial in 2 parts (2 instances of GAE).

Split up "Show solution" button into two buttons:

• "Show solution" which shows the solution without modifying the editor.
• "Apply solution" which pastes the solution into the editor.

Currently the "about" page that explains what the tutorial is and what technologies it was made with is only linked from the exercise pages.

It would be nice to have a link also from the main page.

When there is an already-in-context bean (like e.g. a "Product" instance in exercise 1) show its attribute name ("product") and a link to see the source code of the class.

Thymeleaf 2.1.4 has just been published, and it would be nice if the interactive tutorial was updated to this new version :)

Now Thymeleaf 2.1.3 has been released, the itutorial should be updated to make use of this new version.