I have a legacy app and I have to update struts 2.3 to struts 2.5. I have followed the migration instructions here (https://cwiki.apache.org/confluence/display/WW/Struts+2.3+to+2.5+migration) but I am getting the following error in Weblogic:
org.apache.struts2.dispatcher.DefaultDispatcherErrorHandler - Exception occurred during processing request: Cannot find definition named '/menu.tiles'
According to the migration instructions above, I only have to change the DOCTYPE in my struts.xml and tiles.xml files.
I tried the solution here (org.apache.tiles.definition.NoSuchDefinitionException: Cannot find definition named 'addCustomer.tiles') but that didn't work.
Any ideas?
All, I found this on stack overflow and it solved my issue. I am posting the answer so the next guy doesn't spend days looking for the answer.
The accepted answer from the link below solved my problem. *Note - I am working with Weblogic 12.4
Runtime exception while upgrading to struts 2.5.17
Related
We have recently upgraded a project from grails version 2.3.11 to 2.5.5. In the process the webflow plugin was updated from 2.0.8.1 to 2.1.0.
To controll webflow I use the g:link tag, like this:
<g:link event="foo">Foo action</g:link>
Before the update, the link url was correctly build, and looked like this:
/fooaction/superflow?execution=e1s2&_eventId=foo
Since the update, the link is missing the execution parameter, and resolves like this: /fooaction/superflow?_eventId=foo
This can be fixed, by changing the links, like this:
<g:link event="foo" params="${[execution: params.execution]}">Foo action</g:link>
But this can not be a solution. I searched the web and seem to be the only one having this problem. Which indicates I made a mistake in the configuration. Maybe someone can enlighten me, what I could have missed.
I found a link on github, stating This works with <= Grails 2.4.4 but not with Grails >= 2.4.5. The execution param is missing. Is this a bug which have not been fixed ever since?
Thank you very much.
I recently updated my grails project from 2.0.4 to 2.3.6, which is giving some errors while saving a form which contains multipart data (file attachments),
Its giving me the error for the file attachment fields like rejected value: grails.validation.ValidationException: Validation Error(s) occurred during save():
And its giving me the error in Requestmap.groovy as well, below is the error
Requestmap.url.unique.error
In version 2.0.4, its working fine without any errors.
How to resolve these issues?
Grails documentation contains tips on updating from one version to another. In your case you are making a large jump so you may have to refer to the following:
Upgrade from versions previous to 2.2
Upgrade from 2.2 to 2.3
Both issues you have are validation errors. You can see the validation errors in detail by executing:
Requestmap requestmap = new Requestmap([...])
requestmap.validate()
println requestmap.errors
You can find additional details about validation errors in the docs.
Update: The Question is Still Open, any reviews, comments are always welcome
As I already know lot QA's in stackoverflow regarding my topic, but most of them are closed and not properly answered.
Question 1) Steps for Migrating Rails 2.3.5 to Rails 3.x.x
Question 2) PitFalls and Traps
Question 3) Error Prone & Painfull Migration Phases
Note: I need Real Answers,Stuffs,Reviews and Suggestions are welcome, from those who involved in project migration from Rails 2.x.x to Rails 3.x.x
This has been answered in another question, How to update rails 2.3.10 to 3.x
But here is what I learned from an attempt at upgrading. Have to try again since the first attempt failed.
One of the most useful things I found in it was this plugin.
https://github.com/rails/rails_upgrade/blob/master/README
That would answer 1) with the steps for upgrading.
Also, it is a lot easier to upgrade to 3.0 than to 3.1 or 3.2. 3.0 -> 3.1 breaks a lot of stuff.
The suggestion is to do 2.3 -> 3.0 -> 3.1 -> ... all separately
2) named scopes like they are used in 2.3 don't work with 3.x - they have to be replaced with the Rails 3 version of scopes. For me the most annyoing things are some gems which haven't been upgraded to use Rails 3, so I have to figure out a replacement or throw them out. Also Rails 3 insists on marking all the text I output from helpers and from every other place than views as unsafe, which is really annoying. I can't remember now what we did to fix that.
3) Everything is very painful with upgrading Rails.
Edit: I found this presentation today, seems very informative, http://www.slideshare.net/crnixon/rails-3-7983843
I have upgraded my grails app from 1.3.7 to 2.0.1. I had few static (gsp but not using any controllers) pages using standard layout under "grails-app\views\" . These files were working fine prior to upgrade. But after upgrade, I get 404 error. Only index.gsp is working if I give root path ie. "http://localhost:8080/myapp/". But if I specify "http://localhost:8080/myapp/index.gsp", I get 404 error.
I assume this is something to do with grails filters in 2.0.1. But i couldn't figure it out yet. DO anyone have experienced any similar issue?
This was a security risk and directly linking to GSPs was disallowed in 2.0 - see http://jira.grails.org/browse/GRAILS-7542 and http://grails.1312388.n4.nabble.com/Direct-linking-to-gsp-in-Grails-2-0-td4228929.html for a discussion and examples of how to use URL mappings to link to GSPs.
I am working in Rails 3. If I run my application in IE8, I am getting the following error:
"Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience."
I tried few technical solutions but they didn't work.
Afterwards I removed prototype.js and the error was removed. If I include prototype.js again, the error gets displayed again.
Strange! What could be the solution?
give a try to Prototype 1.7RC3, it fixed a problem for me. Maybe it will help you too.