[prev in list] [next in list] [prev in thread] [next in thread] 

List:       struts-dev
Subject:    [jira] [Updated] (WW-4238) ParentPackage change not rescanned ..causing incorrect parent package ass
From:       "Jim Greuel (JIRA)" <jira () apache ! org>
Date:       2013-11-26 15:14:38
Message-ID: JIRA.12677118.1383329365589.30917.1385478878961 () arcas
[Download RAW message or body]


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

Jim Greuel updated WW-4238:
---------------------------

    Attachment: helloworld-2_0_11.zip
                helloworld-2_3_15_1.zip

I've attached a code-behind sample app, based on the Struts HelloWorld example, that \
exhibits the behavior.  It creates and uses a custom struts package that makes use of \
the paramsPrepareParamsStack interceptor stack.  If I build and run with struts \
2.0.11, it works fine - the parameter interceptor is executed before the prepare \
interceptor.  If I build and run with struts 2.3.15.1, the parameter interceptor is \
not executed before the prepare interceptor - I get what appears to be the default \
interceptor stack instead of the paramsPrepareParamsStack, as though it is ignoring \
my @ParentPackage annotation.  Both 2.0.11 and 2.3.15.1 versions of the sample app \
are attached.

(I know the Codebehind plugin was deprecated long ago, but we have an old, large app \
running on Struts 2.0.11 that uses it.)

> ParentPackage change not rescanned ..causing incorrect parent package assignment
> --------------------------------------------------------------------------------
> 
> Key: WW-4238
> URL: https://issues.apache.org/jira/browse/WW-4238
> Project: Struts 2
> Issue Type: Bug
> Components: Annotations
> Environment: JDK 1.7.0.25
> Struts-2.3.4
> deployed to TC 7.0.37
> Reporter: Martin Gainty
> Priority: Minor
> Labels: ParentPackage
> Fix For: 2.3.17
> 
> Attachments: helloworld-2_0_11.zip, helloworld-2_3_15_1.zip
> 
> Original Estimate: 120h
> Remaining Estimate: 120h
> 
> I wanted to take observe behaviour of changing ParentPackage and here is the change \
> for org.apache.struts2.showcase.person.package-info.java within showcase app
> //All package assignments for showcase/person
> //will be changed to showcase/bogus
> //@ParentPackage("person")
> @ParentPackage("bogus")
> @Namespace("/person")
> package org.apache.struts2.showcase.person;
> import org.apache.struts2.convention.annotation.Namespace;
> import org.apache.struts2.convention.annotation.ParentPackage;
> No effect on behaviour
> it seems that any changes to org.apache.struts2.convention.annotation.ParentPackage \
> do not shift the interpretation from old package of "person" to new "bogus" package \
> Orginally reported by Jim Greuel USFWS



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[prev in list] [next in list] [prev in thread] [next in thread]