Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
If devMode=false then our JBoss app server displays a similar 404 error page with the same error message. I don't know what exactly happens in the background but I would like to display a Struts action when page not found. On Mon, Sep 19, 2016 at 1:25 PM, Lukasz Lenart wrote: > 2016-09-19 13:24

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Lukasz Lenart
2016-09-19 13:24 GMT+02:00 Tamás Barta : > To avoid the "There is no Action mapped for namespace [/nosuchpackage] and > action name [nosuchaction] associated with context path []." pages. > > Dispatcher catches ConfigurationException and displays its default error > page. But this happens only in

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
To avoid the "There is no Action mapped for namespace [/nosuchpackage] and action name [nosuchaction] associated with context path []." pages. Dispatcher catches ConfigurationException and displays its default error page. On Mon, Sep 19, 2016 at 1:17 PM, Lukasz Lenart wrote: > 2016-09-19 13:08

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Lukasz Lenart
2016-09-19 13:08 GMT+02:00 Tamás Barta : > To answer my question and help others: I managed to handle every similar > problem by settings custom error handler: > > name="myHandler" class="mypackage.DispatcherErrorHandler" /> > Can you share more details? What was the reason as Struts pro

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
> It's a fallback, did you read this https://struts.apache.org/ docs/converting-application-from-codebehind-to-convention-plugin.html? Yes, but I don't understand which row is about it :) https://struts.apache.org/docs/namespace-configuration.html The Default Namespace part which made me underst

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
To answer my question and help others: I managed to handle every similar problem by settings custom error handler: On Mon, Sep 19, 2016 at 11:48 AM, Tamás Barta wrote: > It seems that it solves both problems if I set @Namespace("/") in every > action in the main package. The default

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Lukasz Lenart
2016-09-19 10:51 GMT+02:00 Tamás Barta : > Hi, > > Thank you for your answer. These two problems are very important for me on > my project. > >> Which action was returned? > > When I call http://myurl/anything/limit.action then LimitAction result is > returned. Any action in the main package can be

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
It seems that it solves both problems if I set @Namespace("/") in every action in the main package. The default "" namespace cause the problems. Now it seems that my only problem is that although I set "default-action-ref" it works if I call http://myurl/somethingnotexists.action But it won't wor

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
Hi, Thank you for your answer. These two problems are very important for me on my project. > Which action was returned? When I call http://myurl/anything/limit.action then LimitAction result is returned. Any action in the main package can be accessed in any url, for example: http://myurl/anythi

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Bruno Wintenberger
This make me think about the "struts.mapper.alwaysSelectFullNamespace" property. Take a look at this stackoverflow entry : http://stackoverflow.com/questions/8424215/struts-2-mapped-actions-working-with-any-url 2016-09-19 10:35 GMT+02:00 Lukasz Lenart : > 2016-09-19 9:59 GMT+02:00 Tamás Barta : >

Re: Trying to migrate to 2.5.2

2016-09-19 Thread Lukasz Lenart
2016-09-19 9:59 GMT+02:00 Tamás Barta : > Hi, > > I'm trying to migrate from 2.3 to 2.5.2 but I have two weird problem, both > were good in 2.3 so they are maybe problem of Convention plugin. > > Let's assume I have two actions: > > mypackage.actions.LimitAction > mypackage.actions.user.UserAction

Trying to migrate to 2.5.2

2016-09-19 Thread Tamás Barta
Hi, I'm trying to migrate from 2.3 to 2.5.2 but I have two weird problem, both were good in 2.3 so they are maybe problem of Convention plugin. Let's assume I have two actions: mypackage.actions.LimitAction mypackage.actions.user.UserAction In 2.3 : http://myurl/limit.action -> OK http://myurl