[
https://issues.apache.org/struts/browse/TILES-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Petrelli updated TILES-469:
-----------------------------------
Description: 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. (was: In a non-portlet environment, if you try to load
PortletTilesRequestContextFactory, all subsequent calls using Velocity cause a
NoClassDefFoundError, searching for a class in Portlet API.)
Affects Version/s: 2.1.3
Summary: Other integrations do not work if portlet support is
loaded (was: Velocity integration does not work if portlet support is loaded)
> 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-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.
