Upgrading legacy JSF 1.x to JSF 2.3.6 trying to figure out best course action.
This is my old line of code that I would like to now how to change it correctly in JSF 2.3
<a4j:status for="assignInventoryRegion" stopText="" startText="Request under process" startStyle="color:green"/>
Related
I'm trying to migrate Easygrid plugin from 2.X to 3.X
I have an error that can not resolve:
In version 2.X the Class DefaultGrailsControllerClass had a method "registerMapping", but in version 3.X of the same class this method does not exist any more.
The question is: What method I can use of the new version (3.X) class?
Please note that I can not understand very much all the Easygrid plugin code, because I am not the author.
Thanks
I am upgrading my application from Grails version 2.3.7 to version 3.2.2. My JSPs and other content like CSS and images all had to move from the old location of "web-app" to the new location of "src/main/resources/". Now, however, my JSPs will not load like they did before. For instance, my index page has always been http://hostname/app-name/homepage.jsp, and that always loaded just fine in Grails 2.x. Maybe there is just a configuration missing or something, does anyone have a suggestion. I have read the upgrade documentation, but have not found an answer to my problem.
As Grails 3 uses Spring Boot there is no default context. So your application should be served under http://hostname:port.
You can change it back to the previous URL as suggested in How do you change the application name in Grails 3?
Need of help.
I am new to Grails,
My question is How to do db-reverse-engineer.?
I did it in Grails 2.5.1 but I am struggling with Grails 3.1.0.M2 version.
Thanks in advance.
There's no plugin for Grails 3. I started to convert the older one but it's more work than I was expecting because it has to work with Hibernate 4, and the old plugin only works with Hibernate 3.
But the generated files wouldn't be any different in Grails 3 than in Grails 2 since GORM has stayed rather consistent. Since the plugin is only used at build time, and often only once or at most a few times, I recommend that you configure a Grails 2 app with the same database config settings and using the plugin there, then moving the generated files to your Grails 3 app.
On the Spring Security Core plugin GitHub repo, I see that Graeme on May 21st upped the required version of Grails from 2.0 to 2.3 before the RC4 version was released a couple of months later, but I don't see any explanation for why. Was it mismatched dependencies, bug reports, etc?
I run a 2.2.4 app, and I would prefer not to upgrade at this point just to get the latest RC of spring security core. I understand if the upgrade to 3.2.0.RELEASE of spring security caused mismatched dependencies with older versions of Grails since I've run into the same issues before.
This originally came up due to a pull request on the spring security OAuth2 provider plugin that I maintain. The pull request upped the required version to 2.3, and the requester pointed me to the RC4 release of core as the reason.
Thanks for the good works as always!
It's pure speculation on my part, but as far as I can tell, it has to do with the getNamespace() method introduced in the UrlMappingInfo interface in Grails 2.3.
The Spring Security Core plugin's class AnnotationFilterInvocationDefinition does check if it's dealing with Grails 2.3 or higher before it attempts to call getNamespace(), but in its current state it causes a compilation error (due to the missing method).
I suppose the class could resort to using the reflection API to get around this, making it possible to lower the requirement to Grails 2.2.0 (or keep it at 2.0.0)
String namespace = null;
try {
Method m = mapping.getClass().getDeclaredMethod("getNamespace", null);
namespace = (String)m.invoke();
} catch(NoSuchMethodException e) { ... }
I am looking for a solution which can help me to use <rich:placeholder> in jsf2.0 and richfaces 3.0.0
Do you have any proposals?
The error message:
<rich:placeholder> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: placeholder
<rich:placeholder> was added to RichFaces in 4.3 version, if you want to use it you'll have to update. (Which you should do anyway, RF 3.0.0 is very, very old)