[ 
http://jira.magnolia-cms.com/browse/BLOSSOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Duffey updated BLOSSOM-1:
--------------------------------

    Attachment: is-available-annotation-patch-v2.txt

Please use this patch.  @IsAvailable method signatures are now a bit more 
flexible and can accept zero, one or two parameters in any order:

info.magnolia.module.templating.Template (The template being checked)
info.magnolia.core.cms.Content (Content node for page in AdminCentral)

 Some examples:

@IsAvailable
public boolean isAvailable() { return true; }

 @IsAvailable
 public boolean isAvailable(Content node) { ... }

 @IsAvailable
 public boolean isAvailable(Template template, Content node) { ... }

If an unknown parameter type is found on an @IsAvailable annotated method then 
an error is logged and the template will not be available.

> Template annotation should allow specifying "class"
> ---------------------------------------------------
>
>                 Key: BLOSSOM-1
>                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-1
>             Project: Magnolia Blossom Module
>          Issue Type: New Feature
>            Reporter: Tobias Mattsson
>            Assignee: Tobias Mattsson
>            Priority: Minor
>             Fix For: 1.1.1
>
>         Attachments: blossom-template-class-patch.txt, 
> is-available-annotation-patch-v2.txt, is-available-annotation-patch.txt
>
>
> Transferred from Sourceforge
> Original description:
> Magnolia templates support a node named "class" that contains the fully 
> qualified class name to be instantiated for that particular template. This is 
> useful, for example, if you want to override the default isAvailable() method.
> The Blossom @Template annotation should allow specifying this value and 
> subsequently configuring it on the blossom generated template.
> Followup comments:
> Good suggestion, though even cooler would be to have isAvailable() directly
> on the controller.
> For now you can subclass DefaultBlossomTemplateRegistry and overload
> writeTemplateDefinition() to add the custom properties that you need.
> Replace <blossom:configuration /> with
> <bean class="se.issi.magnolia.module.blossom.BlossomConfiguration">
> <property name="templateRegistry">
> <bean class="some.package.MyCustomTemplateRegistry" />
> </property>
> </bean>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to