We Keep Coding

Configuration Issue In Spring MVC setup

I am setting a project for Spring MVC but it seems to hold some issue.
while configuring I am Tomcat-7 and JRE 1.8 but due to this project is not setting up.
Earlier when I was learning Spring Core JRE 1.8 was not an issue it was automatically getting configured. But now while building MVC project it is generating below problem, it say's
"Faceted Project problem(Java Version Mismatch)"
and is this happening when i am not using this Apache Tomcatv7 is being loaded along with JRE1.7
[1: this image I have manually changed the JRE1.8]
https://drive.google.com/open?id=1JNEoP8_Yb79-2dGGFm3EaZKI5uHjj5RB
[2: But still on selecting Apache Tomcat JRE1.7 is being loaded]
https://drive.google.com/open?id=1SVlL1h7rF9kspYNnUe70O5Y3NYalBtQ2
I therefore want to use JRE1.8 for configuring the project, but it seems Apache Tomcat version is Generating problem.
So do I need to upgrade the version of Tomcat??

For your first statement :
In offcial page of Tomcat it says that Tomcat 7.x is compatible
with JDK-6 and higher version of JDK. So JDK 8 should not give an
issue with it.
I think the main reason could be, different versions of Java in compiler and in project facets. The Java facet version needs to always match the java compiler compliance level.
If you want to use Java compiler level as 1.8, then you should upgrade tomcat runtime envionment to java 8 and also change the project facets to 1.8.
Java 7 at the runtime and java 8 at compile time, this combination will not work. this would be worked for vice versa.
You can change Java runtime as follows :
1. select Apache> Tomcat 7 Server
2. Configure Runtime Environments
3. On this screen there is a pulldown labeled JREs.
4. You should find your JRE listed. If not use the Installed JRE button.
5. Select the desired JRE. Click the FINISH button.
Hope this solves your problem. Do upvote if this has helped a tiny bit :)

What version of AXIS2 shipped with Websphere 8.5.5.2?

I just want to know the inputs for below questions.
what version of AXIS2 will come with Websphere 8.5.5.2?
Where can i see the version details of AXIS2 jars shipped with WAS 8.5.5.2?
My code actually compiled with AXIS2 1.6.1 and deployed the same in WAS 8.5.5.2. I am getting below classcast exceptions. What could your suggestions to resolve this issue. I thought there is problem with different versions of axis2 while compiling and deploying. I am not able to know what version of axis2 shipped with websphere 8.5.5.2.
Approaches I have used.
1) Part of code which uses Axis was compiled against AXIS2 1.6.1 version and generated war was deployed in WAS 8.5.5.2 with no libraires in WAR. Got classNotFoundException for org.apache.axiom.util.stax.XMLStreamWriterUtils. Added org.apache.axis2.jar located in plugins in shared libraries and attached to my server war module level. Then class cast exception came.
2) Part of code which uses Axis was compiled against AXIS2 1.6.1 and generated war was deployed in WAS 8.5.5.2 with org.apache.axis2.jar under WEB-INF/libraires in WAR. Then class cast exception came.
Calling getRendererRef(): renderer Type=[OutInRenderer]
WSRenderer I Start:
WSRenderer E Unable to perform rendering due to exception (java.lang.ClassCastException: org.apache.axiom.util.stax.xop.XOPEncodingStreamWriter incompatible with org.apache.axiom.ext.stax.datahandler.DataHandlerWriter)
WSRenderer E stacktrace=org.apache.axiom.util.stax.XMLStreamWriterUtils.internalGetDataHandlerWriter(XMLStreamWriterUtils.java:71)
org.apache.axiom.util.stax.XMLStreamWriterUtils.writeDataHandler(XMLStreamWriterUtils.java:134)
3) Kept Parent_LAST option in WAS 8.5.5.2 for server war which results plenty of errors related to parsers and other. Application stopped working because of many classcast and incompatible issues.
Any inputs are appreciable...

The code in the WebSphere runtime is not based on an official release of Apache Axis2, but on a fork created from a development version. Your only option to use Axis2 on WebSphere is to configure your application with parent last class loading. To make this work you need to remove from your application all the JARs containing APIs that must be loaded from the server runtime, such as the servlet API and various XML APIs.

Is It Possible To Use The IBM WebSphere JAX-WS Runtime To Generate Web Services In Eclipse 4.x?

I'm attempting to generate a JAX-WS server top down (from a WSDL) for the IBM WebSphere v7 runtime using Eclipse Kepler. The problem I'm running into is that I simply cannot select the web service runtime to be IBM WebSphere JAX-WS, there is no option for it. I've installed the WebSphere Application Server Developer Tools plugin for Kepler and configured the runtime in Eclipse to be the runtime installed on my system. I can also compile applications against the WAS 7 runtimes and deploy them to a WAS 7 server, so it would appear the runtimes are available.
The biggest thing that's frustrating me is that the option is available in Eclipse Indigo (3.x). To make sure there wasn't something awry with my work space or install in any way, I downloaded fresh copies of both versions of Eclipse, started with fresh work spaces, and installed the WAS 7 plugin on both versions from the marketplace. Eclipse 3.x gives me the option, but 4.x does not.
Now, I know these plugins are different versions. The version provided by the marketplace for Eclipse 4.x is 8.5.5011.v20131031_0202 while the version for 3.x is 8.5.1002.v20130402_2058, which based on the version number appears to be about 7 months older. This leads me to my question, is it possible to use the IBM WebSphere JAX-WS runtime to generate web services in Eclipse 4.x anymore? I've tried searching the web all I can but have found no mention of this ability being removed from the plugin. I've even found other SO posts that make it seem like this once was available for Eclipse 4.x, but maybe no longer is with the latest version of the plugin (this linked question is over a year old). Does anyone know the answer to this. Is it no longer possible to do this, or is it actually possible by some other means that that you could share please?

Apparently this is fixed now (see https://www.ibm.com/developerworks/community/forums/html/topic?id=29712397-fdfd-41be-8668-ada56447711a). The version of the plugin didn't change, but it sounds like there was an update to the plugin that fixed a bug.

JSF 2.0 + axis2 integration is it possible?

Is it possible to implement axis2 in an JSF 2.0 project ?? it seems I cannot do that because it pops up an error saying : javaserver faces 2.0 requires dynamic web module 2.5, and axis2 requires dynamic module 2.2 or 2.3 does anyone have any solution please ??

I just tried this on MyEclipse 10.7.1 and had no problem. I just added JSF capabilities to the web project (right click on the project and go to MyEclipse->Add JSF Capabilities, selecting 2.0. Then I set the Axis2 runtime in the preferences (I have an old Axis2 1.5.4 runtime). Then I went to the preferences page you showed, for the project, and added Axis2. I got no errors. For the Axis2 runtime preferences page, you need to have the WTP Extras enabled (Window->Preferences->General->Capabilities->Advanced then open MyEclipse Standard Tools and select WTP Extras before clicking OK).
I'm not sure if the release of MyEclipse is significant but, if you're not on the latest (10.7.1) it would probably be a good idea to update your installation first.

Problem whille adding project into the websephere 6.1

I am using IBM web-sphere 6.1 as a application server and eclipse as IDE. so i have one project name as MobileBank.ear which contain deployment descriptor file which has one module name as amsejb.jar which is ejb project and some jar files. so while adding MobileBank.ear into the server i am getting the following error " Web-Sphere v6.0 only supports J2EE 1.2, 1.3, and 1.4 Enterprise applications." due to this error i am not able to deploy my ear can anyone guide me please... also MobileBank.ear contains web project though i am not able to add the ear. Kindly Guide me...
Thanks in advance...
Vinod

I am using IBM web-sphere 6.1 ... Web-Sphere v6.0 only supports ... Are you sure you are using WAS 6.1 ?? May be this is what causing the problem

Well, 6.1 really doesn't support more than 1.4 and you're attempting to use newer versions.. You should
Edit the project facets in the project properties to utilize older versions
Not select 6.0 when generating the project as the target. That is used for the remote deployment etc. Eclipse does not really support 6.1/7.x deployment so please generate the generic projects instead.

i deleted the EAR folder ,created new Enterprise Application Project and added all project in that . error got resolved .

I am using WAS 7.0
U need to change the WebSphere Application Server version under Coniguration section while creating a project in Eclipse/RAD.
Then Dynamic Web module version will get changed from 3.0 to 2.5

While creating a dynamic web project,
-- On entering the "project name"
-- we have an option to check "Add project to EAR"
-- Enter the EAR name
-- choose the EAR version on of these - 1.2, 1.3, 1.4 and 5.0
On doing this, we would be able to add the EAR to WAS (I have been using v7)