2013/10/30 Greuel, Jim :
> I don't know about the 10 times easier, but we'll see what we can do.
I mean you have a real case and as you've probably noticed I'm
adjusting my solution to your very simple example ;-) You can always
extend the example to help me grasp as much as possible :-)
Regards
I don't know about the 10 times easier, but we'll see what we can do.
Jim
On Tue, Oct 29, 2013 at 1:02 PM, Lukasz Lenart wrote:
> 2013/10/29 Greuel, Jim :
> > Our real app has numerous cases where the URL namespace doesn't match the
> > Java package structure. I was hoping we could make this w
2013/10/29 Greuel, Jim :
> Our real app has numerous cases where the URL namespace doesn't match the
> Java package structure. I was hoping we could make this work without
> restructuring the application and/or modifying URLs. Is this something
> that is fixable, i.e., should I submit a jira tick
Our real app has numerous cases where the URL namespace doesn't match the
Java package structure. I was hoping we could make this work without
restructuring the application and/or modifying URLs. Is this something
that is fixable, i.e., should I submit a jira ticket, or do I need to just
bite the
The problem is with @Namespace annotation in HelloWorldAction which
doesn't play well with init-param actionPackages. Simple move
HelloWorkAction to package org.apache.struts.helloworld.test and set
actionPackages tp org.apache.struts.helloworld and remove @Namespace
annotation.
Regards
--
Łukas
Thanks Lukasz. Yes, setting defaultParentPackage fixes the problem for the
sample app, but my real app has multiple custom struts packages, so I can't
specify a single default that works in all cases.
Jim
> In 2.0.11 the Codebehind plugin was just a UnknownHandler ;-)
> Try add this:
> va
gt; enough to make migration to the Conventions plugin costly). The app makes
> use of the @ParentPackage, @NameSpace and @Result annotations. The
> @ParentPackage annotation seems to no longer work after the migration.
>
> Before submitting a bug report, I thought I'd check to se
On Sep 25, 2010, at 7:33 AM, Jason Ferguson wrote:
> Can the @ParentPackage annotation accept more than one argument (i.e. both
> "struts-default" and "json-default")?
IIRC, json-default extends struts-default, so that shouldn't be an issue...
-Dale
I'm using the JSON plugin to manage my actions that require JSON response as
well as the convention plugin. However, I've Googled until my eyes were
about to find out and couldn't find the answer to this question:
Can the @ParentPackage annotation accept more than one argument (i.
eł Wielgus.
2010/7/14 JP Cafaro :
I'm using struts 2 with convention plugin. The convention plugin page
states for the ParentPackage annotation, "To apply this annotation to all
actions in a package (and subpackages), add it to package-info.java." I
have two packages, my-default
states for the ParentPackage annotation, "To apply this annotation to all
> actions in a package (and subpackages), add it to package-info.java." I
> have two packages, my-default and my-secure. I have a package called
> actions.secure and in it I have a package-info.java wit
I'm using struts 2 with convention plugin. The convention plugin page
states for the ParentPackage annotation, "To apply this annotation to
all actions in a package (and subpackages), add it to
package-info.java." I have two packages, my-default and my-secure. I
have a
12 matches
Mail list logo