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.
Related
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.
It seems like this questions should be easy but the installation requirements for Grails (http://www.grails.org/Installation) haven't been updated in 2 years. Does anyone know for sure is Grails 2.3 will run on JDK 8?
As noticed by heikkim this ticket which is now closed suggests that support for Java 8 will start on Grails 2.4:
http://jira.grails.org/browse/GRAILS-11063 (title: Java 8 support)
Tried an app (built on v2.3.7) on JDK 8 and hit a road block with database-migration plugin while compiling the app. If that particular plugin is commented out then everything looks good during compilation.
Running the app (with a sample controller) throws an error related to withFormat method from grails-plugin-mimetypes. Looking into it.
Raised an improvement defect for grails-database-migration plugin. I think this may not be required as well but making grails JDK8 compatible might need changes in grails-core. However, I have not checked with latest milestone build for Grails 2.4 which might already be taking care of those compatibility issues.
hello I made one applicattion(WEB API MVC4 which connect with SQL server) using framework 4.5, in my IIS express run fine but I try publish in other server which uses framework 4.0, my applicattion not run ?
I change in properties of my application works with framework 4.0 and in my IIS express run fine but other server not run.
I can't upload version framework in the other server.
thanks for the asnwers and sorry for my english I'm learning
Maybe you have changed target framework attribute in your web application that isn't sufficient to deploy. In your codes you may use libraries that require .net 4.5 while you only have changed the setting. About running this in your iis express must say that your system by default supports .net 4.5 while your app says i need only .net 4.0. So .net 4.5 related parts will be compiled and executed on local server and no ambiguous thing is here.
Running .NET4.5 based app on .NET4 machine is not supported. Simply because .NET4.5 is a super set of .NET4. Everything that's built for .NET4 works on .NET4.5 but not the other way around. If you are using Visual Studio 2012, you can change TargetFramework (in project properties) to .NET Framework 4, this will ensure that your app is built for .NET4.
--Varun
(.NET Framework Team)
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