[ 
https://issues.apache.org/jira/browse/WW-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662601#comment-13662601
 ] 

Stefan Reich commented on WW-4055:
----------------------------------

Hi Lukasz,
I am slammed at work, so I didn't have time to finish and test the fix based on 
your suggestion.

One thing that I noticed that could be different from other people's 
deployments. We package our web app as an ear file, and in the 
weblogic-application.xml descriptor, at the EAR level, we configure 
org.apache.* and all subpackages to be resolved from our WEB-INF/lib directory.

Sorry, no ETA yet. My first fix works fine, though.
                
> Convention plugin doesn't find any Action classes in EAR deployment on 
> Weblogic 10 and 12
> -----------------------------------------------------------------------------------------
>
>                 Key: WW-4055
>                 URL: https://issues.apache.org/jira/browse/WW-4055
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Convention
>    Affects Versions: 2.3.14
>            Reporter: Stefan Reich
>             Fix For: 2.3.15
>
>         Attachments: PackageBasedActionConfigBuilder.patch
>
>
> The weblogic container versions 10, 11 and 12 has a peculiar way of deploying 
> ear and war files. 
> It unpacks the ear and war file, and jars up the contents of WEB-INF classes 
> into a new file: WEB-INF/lib/_wl_cls_gen.jar. After that, all content from 
> WEB-INF/classes is deleted.
> The consequence is that the classloader will return a URL to the 
> WEB-INF/classes directory when the plugin is searching for annotated classes, 
> but it will be empty, so this plugin would never find any Action classes.
> I have a patch that has been verified to work on Weblogic 10 and 12.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to