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
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 a legacy grails app running on 1.3 on Java 6 with tomcat 6.
We need to upgrade to java 8 on tomcat 8.
Is it possible to upgrade grails version from 1.3 to 2.4.5.
Lot of compilation issues and some of the holder classes are missing.
Please suggest.
The easiest way we've found to upgrade between incompatible versions of Grails is to create a new application in the new version, and migrate the services/controllers/src directories into the new application.
You will need to keep in mind various changes (like the Holders classes you mentioned, which are now part of Holders in grails.util.Holders, iirc). Also, you'll probably need to upgrade any plugins you use to newer 2.4.x-compatible versions as well (specifically spring-security, etc.)
It's not an easy task, but it can be done. We've migrated from 1.x to 2.x before, and from 2.2 to 2.4, and we're currently migrating to 3.x. BTW, since you're migrating, perhaps moving to 3.x would be a better move?
Good luck!
Yesterday I tried to create a Vaadin project as described under https://vaadin.com/framework/get-started
I did it that way because the current eclipse plugin doesn't support greating Vaadin 8 projects.
Then I imported the project using Eclipse Import->Existing Maven Projects.
THis worked almost fine - only when starting the project using "Debug on Server" the Browser cannot connect to the application, although the application seems to be loaded.
When using mvn clean install and deploying the war manually this works.
What is missing there? Is there currently a good way of using Vaadin 8 with Eclipse?
Apparently this is more of an eclipse configuration question.
The context root can be changed using the projects Properties->Web Project Settings.
I would already use Vaadin together with spring-boot. On spring site they do have also a nice initializer tool to create your project: https://start.spring.io/ (Vaadin 8 is already used)
Also very helpful: http://vaadin.github.io/spring-tutorial/
The big advantage of using spring for me is the dependency injection, which simplifies the project setup.
I just started learning Apache ISIS. I have configured the application and imported into Eclipse(Mars). Can anyone tell me how I can run the application from eclipse.
The main thing you need to do is to set up the DataNucleus enhancer. There's details and a screencast here
We have found that the DN enhancer can be a little unreliable on larger projects, which was one of the reasons as developers we ended up moving to using IntelliJ (community edition is fine). YMMV.
Within an IDE you run the app using the org.apache.isis.WebServer helper class (it's just a wrapper around jetty).
HTH