You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Rene Gielen (JIRA)" <ji...@apache.org> on 2007/08/15 00:38:35 UTC

[jira] Updated: (WW-1695) Annotation based action configuration fails in porlet environment

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

Rene Gielen updated WW-1695:
----------------------------

    Attachment: myportlet.zip

Attached is a portlet based on Nils' embedded pluto example, against 2.0.9. The IndexAction for edit mode was modified to support a result configured by annotation, pointing to /foo.jsp if you enter foo in the first textbox.

When run with embedded pluto (mvn jetty:run), everything works fine.

But if you build a war and deploy it to Liferay 4.3.0, the portlet does not get initialized, instead it falls into an infinite loop after files were copied successfully.

After all, it seems not to be an issue of the annotation in particular, but rather the zero config plugin. Even without using the annotation, simply configuring actionPackages parameter causes the broken deployment.

I wonder if this could be a classloader issue....

> Annotation based action configuration fails in porlet environment
> -----------------------------------------------------------------
>
>                 Key: WW-1695
>                 URL: https://issues.apache.org/struts/browse/WW-1695
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Configuration, Portlet Integration
>    Affects Versions: 2.0.4
>         Environment: Liferay 4.2.1
>            Reporter: Rene Gielen
>            Assignee: Rene Gielen
>             Fix For: 2.1.0
>
>         Attachments: myportlet.zip
>
>
> Annotation based configuration for actions seems to fail at least in my portlet environment (Liferay 4.2.1), resulting in infinite loop while scanning for action classes in configured packages. Had no time to dig deeper yet, but the issue is reproducible

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