I have an application deployed on WAS 6.1 (without future pack). This application contains a JAX-WS client for a JAX-WS Web Service. Is this architecture possible? Considering that WAS 6.1 uses JAVA 1.5?
I encountered a lot of problems...like missing jars, and incompatible java version.
Can anyone say to me which are the jax-ws jars I need?
We did this for a while with Axis 2 under WAS 6.1 without the Web Services Feature Pack. That is, we deployed Axis 2 jars in the web application's WEB-INF/lib. It did work, but had some performance and resource issues at the time. Thus, we decided to install the (free) Feature Pack, and that made everything work easier and better.
Also, though, don't forget that WebSphere 6.1 goes out of service this month.
As to the incompatible Java version from Java 1.5, JAX-WS can work with Java 1.5, but I have no idea whether your particular code needs Java 6.
Related
I have an old Vaadin 7 application, and I'm trying to upgrade the Spring Boot version from 1.5.22.RELEASE to 2.0.9.RELEASE. I keep running into errors. Should this even work? I can't find any documentation about the version compatibility.
Edit:
The errors are along the lines of java.lang.NoClassDefFoundError: org/springframework/boot/bind/RelaxedPropertyResolver due to the various API changes between the Spring versions.
The official Vaadin Spring Boot add-on 1.2.x branch that is meant to be used with Vaadin 7 only seems to support Spring Boot 1.5. The 3.x branch of the add-on for current Vaadin 8 versions apparently works with both, but those changes haven't been backported to the older branch and the newer branch doesn't work with Vaadin 7. Applying the Spring Boot Migration Guide to my project itself doesn't do the trick thanks to the add-on incompatibility.
Unfortunately not, Vaadin 7 is only compatible up to Spring Boot 1.5. If you want to use Spring Boot 2.x, you have three options:
Upgrade your project to use Vaadin 8 (compatible with both Spring Boot 1.5 and 2.x), see migration guide for details. In most cases this is fairly straightforward with the help of the compatibility classes. It's probably a good idea to do the Vaadin version upgrade first, and only upgrade Spring Boot version after the application is already running on Vaadin 8 (that way it's easier to figure out which upgrade to blame if there are any problems). However, it should be noted that the free support of Vaadin 8 will end in February 2022 already, although the commercial extended support will be available for 10 more years after that.
Create a new Vaadin 14 project (only compatible with Spring Boot 2.x, the starter app generated by start.vaadin.com is Spring Boot based by default), purchase a Vaadin subscription that includes Multiplatform Runtime which allows you to use Vaadin 7 classes from within Vaadin 14, and insert your old views into the new project with the help of the MPR wrappers. Remember to leave out your old Vaadin 7 Spring add-on, and to use the new one that is wired through Flow Servlet instead. This option requires a bit more initial effort (and the subscription), but gives you a leg up to continue converting your project to a pure Vaadin 14 version later on.
Upgrade your project fully to Vaadin 14 (or higher, but that's the newest LTS version at the moment). The migration guide is from Vaadin 8 up, so you might need to consult the Vaadin 7 to Vaadin 8 migration guide as well for some features. This is a significantly bigger jump than from Vaadin 7 to Vaadin 8 since the whole client-side handling was rewritten after Vaadin 8, but gives you right away access to the newer bells and whistles, you'll have several more years of free support available, and upgrading from Vaadin 14 to the next LTS version in turn should be a smaller step again.
What are the jar files I need to use spring expression language in my web app?
This web app itself is not based on Spring. I would like to use the 4.0.1 version. Is spring-expression-4.0.1.RELEASE.jar alone enough?
I assume you need the expression and the core jar. Try with expression only and add core if something still is missing.
And you should consider using 4.1 or even 4.2, 4.1 is available and has no higher requirements than 4.0. 4.2 is scheduled to be released in only a few weeks, so you could start with the already available RC2 and go to final very soon.
I'm very new to server side programming, and I want to develop something by using java and Spring framework. I'm working in Android technology for the last two years and I'm very much familiar with Java and Eclipse IDE.
Can anyone provide me links to some useful tutorials and examples?
Which IDE will be more suitable for me? Eclipse or Netbeans?
Thanks in advance...
I think Eclipse is more suitable, Because you already know about Eclipse(Eclipse is used for android projects).
http://static.springsource.org/spring/docs/3.0.0.RELEASE/spring-framework-reference/html
http://static.springsource.org/docs/Spring-MVC-step-by-step/
It's a very vague question but I'll give you my opinion:
Learn Java EE - this includes:
JSP/JSF
Servlets
Web
EJB 3
Build an application using these technologies and only after you familiarize yourself with it, only then start using spring. Spring is using a lot of theses technologies behind the scenes and it is important to understand what is going on
Regarding eclipse vs netbeans - I'm a huge fan of eclipse and i think it is a great tool however netbeans has better integration with Glassfish (sun/oracle application server) and better GUI tools. so it is really a matter of taste.
As for web/application servers:
Tomcat is a great server to start with, but since it is a web server it does not support EJB.
For using EJB you'll need an application server like Jboss or glassfish.
I'd start with tomcat and then move to glassfish.
What IDEs are you used to? I recommend that you use STS - Spring Tool Suite, which is an Eclipse based IDE maintained by SpringSource. Alternatively, the IntelliJ IDEA Ultimate also provide good support for Spring projects.
Its quite a while since I started learning Java EE (I come from Rails world).
I'd like to test create a simple blog to test these:
- Hibernate, JPA
- Spring with MVC
- JSF and routing
- Struts 2
- Eclipse and local test (modify, reload, check changes)
- Tomcat, Jboss or Jetty
- An administration area (Session)
- Maven
I've a basic knowledge of each of those but as soon as I spend tons of time installing stuff and, somehow, I manage to resolve all inconveniences there is ALWAYS something that goes wrong (installation, tutorial obsolete, should I work with Spring IDE, MyEclipse, Jboss Application Server or regular Eclipse?, tons of random errors, each tutorial asking for random dependencies, each showcase).
QUESTION
How do you create quickly a startup project with these components?
You go with some Maven archetype? If so which one?
What I'd like is something I can download or build equipped out of the box with all above mentioned components. To name a few:
- railswizard.org, youvegotrails.com, railsboost.com/templates/new
SIDE QUESTION
Currently I'm following this great series, can you suggest some more like this:
- http://www.youtube.com/user/koushks?feature=gb_p13n_ch_rec
All the above components in a single project? That makes no sense; Spring MVC, Struts 2, and JSF would rarely be combined in the same project.
Each web framework has demo applications, what's wrong with those? There are archetypes for at least some combinations, although I'm not sure it's not better to put them together yourself.
Without knowing what kind of issues/errors you're getting, it's impossible to help. Maven should be taking care of most/all dependency issues. You shouldn't be spending much time installing anything by hand except maybe an app container.
IMO you're better off asking specific, actionable questions, and start with each specific technology and build up an application, rather than trying to integrate everything at once--a sure recipe for frustration.
For starting with a simple Java EE application, a good point to start is just downloading a Java EE 6 implementation.
Those are offered by various parties, which might be confusing at first. It's however just like there isn't the One and Only C compiler, but there are many and they all compile the same standard C.
For Java EE 6, obvious choices are GlassFish 3.1.2, JBoss AS 7.1, TomEE. (just pick one, at this stage it doesn't matter much which one you'll use).
Java EE 6 is a full stack solution. It's a single download and you don't necessarily need to install any other libraries. It comes with an MVC framework (JSF), an ORM solution (JPA), dependency injection (CDI), business logic support (EJB) and then some.
As for the IDE, NetBeans has a particular good default integration for GlassFish (can even be downloaded as one bundle), but for Eclipse it's not that difficult either. You need to download the Java EE edition of Eclipse and after starting it, go to Help -> Eclipse Marketplace, search for "GlassFish" and install the "GlassFish Server Plugin".
See also Minimal 3-tier Java EE app, without any XML config for a very minimal example to get started and JSF 2.0 tutorial with Eclipse and Glassfish for a very detailed one including instructions how to exactly setup the IDE.
What I'd like is something I can download or build equipped out of the box with all above mentioned components. To name a few:
http://appfuse.org/display/APF/Home
Appfuse will take you through the initial setup of a maven built spring based web application with hibernate included.
If you come from the rails world you might also look into Spring Roo which tries to borrow from Ruby i'm told. The primary focus of roo is to stand up all of the technology you've listed above quickly.
I want to start a my first Java EE project. I have read a lot that springMVC framework is a good choice (never used though)
My earlier experience with java is not much. only some small app development using Netbeans. so I have some experience using Netbeans.
But I see that I can start a Java EE project in Netbeans. so what kind of framework netbeans is using underneath.
PS: My understanding of framework (e.g. SpringMVC) is that you follow rule of framework to configure your app. and then framework take care or linking your View, controller and model.
so if i am using netbeans, do i need to take care of linking of my MVC by myself?
I see that I can start a Java EE project in Netbeans. so what kind of framework netbeans is using underneath.
Hmm... Nothing. NetBeans is just an IDE and let you use whatever framework you want: JSF 2.0, Wicket, Struts 2, Stripes, Spring MVC, your own poison. Of course, one could say that NetBeans promotes (and supports) JSF 2.0 but this doesn't mean you can't use another framework, just add the required libraries to your project.
In any case, Spring MVC is just one options amongst others and is not an absolute requirement to write Java EE applications. Some Java EE applications don't even have a web interface actually. And believe it or not, you can write Java EE application - especially Java EE 6 applications - without Spring :)