You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2009/09/29 17:59:49 UTC

[jira] Closed: (TILES-469) Other integrations do not work if portlet support is loaded

     [ https://issues.apache.org/struts/browse/TILES-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli closed TILES-469.
----------------------------------

    Resolution: Fixed

Checking if a class of the porlet API is present. If not, this problem is trapped and the PortletTilesRequestContextFactory ignored.

> Other integrations do not work if portlet support is loaded
> -----------------------------------------------------------
>
>                 Key: TILES-469
>                 URL: https://issues.apache.org/struts/browse/TILES-469
>             Project: Tiles
>          Issue Type: Bug
>          Components: tiles-core, tiles-portlet
>    Affects Versions: 2.1.3, 2.2.1
>         Environment: Servlet container
>            Reporter: Antonio Petrelli
>            Assignee: Antonio Petrelli
>             Fix For: 2.1.4, 2.2.1
>
>
> In a non-portlet environment, if you try to load PortletTilesRequestContextFactory, all subsequent calls using 2 or 3 parameters (like Velocity) cause a NoClassDefFoundError, searching for a class in Portlet API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.