-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting wrong path when trying to use logic forwardTo #733
Comments
I think that a better solution is to get the superclass of the weld proxy I don't know why this issue haven't happened until now... Chico Sokol On Wed, Aug 6, 2014 at 12:35 AM, astronauta [email protected]
|
…ause of proxified class name
Yes, I was late in this issue :-) The solution in that PR is fine for me. Chico Sokol On Wed, Aug 6, 2014 at 12:25 PM, astronauta [email protected]
|
thank you @csokol |
I think it was not happening before because it's not always necessary to proxify a controller. Maybe only if you use CDI interceptors, maybe for |
Closed by #734. Thank you @adolfoweloy to help us. |
This issue is related to 4.1.0-RC2-SNAPSHOT version of VRaptor4.
When trying to invoke a forwardTo as result.forwardTo(this).form(), I'm getting an error message that says "Resource not found". That's happening because of wrong path resolving inside DefaultLogicResult.java. The code below, shows the usage of forwardTo that leads to this wrong behavior.
Take a look at the code snippet that starts at line 113 inside DefaultLogicResult.java:
When resolver.pathFor returns the path, the path is resolved as follows:
The real path should be:
Instead of trying to change code inside DefaultLogicResult.java, I made some change at DefaultPathResolver.extractControllerFromName as follows:
Using such change, I've got my version working as I was expecting. I ran all unit tests using mvn test and got no errors.
I think that is an issue, and maybe someone knows a better solution than I gave.
The text was updated successfully, but these errors were encountered: