Is there a way to override the security manager class - "JaasSecurityManager" (I need to disable caching), like it was in the old jboss versions (through jboss-service.xml).
Thanks a lot!
Related
I am having an application build on grails 2.2.4. I need to update it to grails 4.0.8 Can i upgrade directly. As i checked from various sources, i need to jump first from 2.2.4 to 3.x then thereafter 3.x to 4.x. Please suggest me optimum way to do this upgrade.
Similar to other question about Grails upgrades
Major version upgrades in Grails are rarely trivial. I'd suggest starting a new app in the target version, and migrating classes/functionalities.
In Grails framework, the effort required to update your application depends on multiple factors, such as:
The standard practices. For instance, the persistence stuff in the Grails services instead of controller or domains itself.
The underline plugins your application depends on. You would need to update to the latest version of the plugin, or in some case find an alternative approaches as the plugin may longer be maintained, or there maybe better ways of doing it. For instance, we had some custom plugin for multi-tenancy back when I started with Grails, But now, GORM has great support for multi-tenancy.
I personally think you should directly jump from Grails 2 to Grails 4 by creating a new application, and then move your source code. But, first you need to identify all the variables such as plugins or libraries.
I have a Struts web application which I want to migrate from JBoss server 4.3 to JBoss 7.1.
Can anyone tell me what things do I need to consider while migrating application to newer version like connection pooling, EJB compatibility, etc., which is dependent on JBoss server?
Since jboss 7 changed their class loading scheme you at first place consider to configure the class path to include only required libraries not loaded by the server. Everything else should be fixed separately because Struts framework doesn't have a reference to relayed problems.
I have several applications created with grails 1.2.2. I need to modify one of these applications to work with multiple datasources. It seems that my best option is to upgrade to a new version of grails. I'm worried that trying to go straight to grails 3 will cause major issues, but am not sure which versions to step through if I'm going to upgrade gradually. Any advice? I apologize for this being so open ended.
The first info about support for multiple databases in official docs exists in version 2.0.0:
http://docs.grails.org/2.0.0/guide/conf.html#multipleDatasources
Check out this guide for upgrade:
http://docs.grails.org/2.0.0/guide/gettingStarted.html#upgradingFromPreviousVersionsOfGrails
I am using Grails 2.3.3 and IntelliJ ultimate 12.1.6 on my Vista 32 machine.
I used grails command line to create a new app and then added spring security and spring security ui. My BuildConfig.groovy plugins section contains
compile ":spring-security-core:2.0-RC2"
compile ":spring-security-ui:1.0-RC1"
I ran
grails s2-quickstart
grails s2ui-override auth
grails s2ui-override register
My generated RegisterController looks like this:
class RegisterController extends grails.plugin.springsecurity.ui.RegisterController {
}
the grails.plugin is red and unresolved and no matter what I try I can't get IntelliJ to resolve grails.plugin
Grails compiles and runs the app without issue, and if I override methods I find in the source code for the spring ui RegisterController they are correctly wired in to the app, but I can't even compile from intell and I can't get intellij to help me override code.
I thought maybe creating the project outside of IntelliJ was an issue so I created a new Grails project using the IntelliJ interface, the plugins still do not resolve.
I tried adding the plugins as runtime with no success.
I have spent the afternoon and evening researching this with no success. There are questions similar to this with major versions 10 and 11 of IntelliJ but nothing current, so I am resolved to asking for help to get IntelliJ to recognize the Grails plugin classes. I can post an entire small sample project if necessary.
Thanks.
Dave
I often have this issue when I place a new plugin into my BuildConfig.groovy, but not typically when I add a jar dependency.
I resolve it by doing the following in the menu: Tools > Grails > Synchronize Grails Settings
You can tell whether or not a plugin is synchronized in IDEA by navigating in the Project view to grails-app > target > work > plugins. Each synchronized plugin with have a tiny blue square over the bottom right corner of the directory icon. If it doesn't have that icon, it isn't synchronized with IDEA properly.
Using IntelliJ 13.1.5 and Grails 2.4.3 with Maven there is an issue with 2 different groovy-all jars being pulled in by the IDE.
The way to resolve it is to go to Module Settings and under both the project and projectGrialsPlugins modules modify the User Grails library entry. Click the edit button(pencil) and remove the groovy-all.2.3.3.jar from the project.
Remember if you close the project and reopen it those settings may need to be reapplied.
We would like to create a completely new service using JBoss 7.1 with modern technologies
such as JPA, Java EE 6, etc....
Alas, we have a legacy system running on a JBoss 4.2.2 that is definitely NOT portable to JBoss 7. The old system will have to access the new system, i.e. call methods via RMI.
Unfortunately, that is not possible out of the box:
JBoss 7 does not support the old JNP protocol anymore that was usually used in JBoss 4 for JNDI lookups.
(See https://docs.jboss.org/author/display/AS71/JNDI+Reference)
We cannot just add the new JARs needed for the new protocol to, say, default/lib, because this will cause version conflicts (logging, e.g.) and simply does not work.
I see two possible solutions, which are both complicated and error-prone:
We add a new Deployment to JBoss 4 that is packaged with all
necessary libraries to access JBoss 7 using and try to use JBoss'
class loader magic in jboss-app.xml to make it work.
We retrofit the old JNP server which can be found in jnpserver.jar
as a new JBoss 7 module.
In both cases we would have to bind a Bridge/Adapter object to the JNDI context via JNP that forwards all requests.
Does anyone have experiences in bridging the gap (rather a snake pit in fact) between JBoss 4 to JBoss 7 or a better idea?
Thanks in advance.
Markus
Make your life easier and use web services between them as this will also avoid and classloader / serialization hell