QuieterSoySyntaxException when adding a form to my Confluence Blueprint

[Yaacov Weingarten]

Trying to create a Confluence blueprint and I am loosely following the Intermediate Tutorial supplied by Atlassian (all Tutorials seem to be using outdated syntax) and I copied their code into my plugin:

{template .page1Form}
 <form action="#" method="post" class="aui">
 <fieldset>
 <div class="field-group">
 <label for="vname">{getText('es.blueprint.form.label.title.vName')}</label>
 <input id="vname" class="text" type="text" name="vName">
 </div>
 </fieldset>
 </form>
{/template}

When I run (atlas-run) this plugin, I get the following error message:

 [INFO] [talledLocalContainer] com.atlassian.soy.impl.QuieterSoySyntaxException: Found error where declared syntax version 2.0 is not satisfied: In file /soy/enablements.soy:6, template ESPlugin.Blueprints.Enablements.page1Form: Tag {template .page1Form}: Template is missing SoyDoc.

Is this template missing some field?

Is there a reference with the updated syntax for adding these forms to the plugin (I obviously need to create a more extensive form for my plugin, and having a reference would be very helpful)?

[Andrew S]

Is it simply that your template has no documentation tag? This is required, as explained here. In your case, because your "page1form" template seems to take no parameters, it might look like this:

/**
 * Shows my nice form.
 */

I see that the tutorial page does contain such a tag. Although it looks like a mere comment, it's actually required by the Soy compiler.

[Yaacov Weingarten]

Thanx, but the full Soy code was/is the following (copied from the tutorial [except the name space]):

{namespace ESPlugin.Blueprints.Enablements}
/**
* A form that accepts a person's name
*/
 
{template .page1Form}
 <form action="#" method="post" class="aui">
 <fieldset>
 <div class="field-group">
 <label for="vname">{getText('es.blueprint.form.label.title.vName')}</label>
 <input id="vname" class="text" type="text" name="vName">
 </div>
 </fieldset>
 </form>
{/template}

[Yaacov Weingarten]

Found that the problem was apparently with the blank line between the javadoc comment and the template line. Not allowed to have whitespace in the beginning of these lines.