Project deploy JDK version.

We want to develop a PCJ bean for oracle forms using Jdev 10.1.3.3.
But it is not reached from forms 10.1.2.2. Java bean is not found error occurs.
Then we want to import java class into forms following error ocuurs.
exception occurs: java.lang.UnsupportedClassVersionError: gorev/Formse (Unsupported major.minor version 49.0)
We think it is a bug because of Jdeveloper JDK version.
We tried the same code with Jdev 10.1.2.2 and it works properly.
So we want to compile the same project using JDK 1.4 from Jdev 10.1.3.3.
is it possible to compile a project with older JDK versions.
How?
Thanks.

Ali,
I told you how to do that...
Create a new J2SE definition for 1.4
Then change your project properties to use that J2SE definition. Your other projects will continue to use 1.5.
Or am I misunderstanding your question?

Similar Messages

Java JDK versions and compilation levels

Hi,
I have a question about differents java versions and the compilance level. As far as I know, if I am developing an application, for example a swing application or a JSF web project, that will be deployed to run in a JVM 1.6, I must compile my code with similar JDK, in this case, I must compile my code with a 1.6 JDK.
But, for example, can I use JDK 1.7 with compilance level 1.6 to run code under 1.6 virtual machine?
Suppose a JSF web project compiled with JDK 1.7 and source level 1.6 can be deployed on a tomcat that run in a 1.6 VM?
If that is correct, I think that I should always get the last JDK version installed in my computer and choose the different compilance level (example 1.4, 1.5, 1.6 or 1.7) to compile my code based on the target JVM, is that correct?
Thanks for your help, regards.

kerule wrote:
If my project will be executed on a JVM 1.4, I must have installed in my computer a JDK 1.4 and the project must be compiled with 1.4 JDK
If my project will be executed on a JVM 1.6, I must have installed in my computer a JDK 1.6 and the project must be compiled with 1.6 JDK
If my project will be executed on a JVM 1.7, I must have installed in my computer a JDK 1.7 and the project must be compiled with 1.7 JDK
Correct?Yes, and NO: the problem with what you said is "must be". If you compile with 1.7, but use objects that are backwardly compatible with 1.4, then it will work in 1.4 onward, but if you use features of 1.7 that are not compatible or possibly not available in 1.4, then you will not run in 1.4.
Your statements:
If my project will be executed on a JVM 1.4, I must have installed in my computer a JDK 1.4 and the project must be compiled with 1.4 JDK
If my project will be executed on a JVM 1.6, I must have installed in my computer a JDK 1.6 and the project must be compiled with 1.6 JDK
If my project will be executed on a JVM 1.7, I must have installed in my computer a JDK 1.7 and the project must be compiled with 1.7 JDKare safe, except where/if inconsistancies exist between versions.

How to downgrade my JDeveloper 11.1.2.4.0's project to earlier version for EM, Webcenter compatibility

Greetings,
its been 4 months now im working on JDeveloper 11.1.2.4.0 with jsf 2.0 on weblogic standalone server.
I finally finish my big project, but now i want to use EM & Webcenter functionalities that works only at JDeveloper 11.1.1....
I don't want to start my project all over again so i was hoping there is a way to downgrade my project to earlier version of JDeveloper
that also supports earlier version of jsf (jsf is the library that messing up everything, specially EM, since jsf 2.0 is not supported)
will be thankful if you got any suggestions, steps or tutorial to downgrade my project so it can be used and deployed properly on 11.1.1.. JDeveloper
so i can use EM & Webcenter.

I just spend 6 hours at work, with no luck, managed to downgrade it, atleast jsf wise, but i got tons of errors every time i fix one. I should not mention the design mixup, just functionalities.
The next version will support the old versions of BI, Webcenter, EM etc or it will come along with new versions?
And did you hear how soon will be out? alteast in how many weeks to know what will be my next move.
thanks.

Setting different JDK versions for Different webapp in Tomcat

Hi All,
I have 2 web-applications in Tomcat 5. Now for Java I have j2sdk1.4.2 & j2sdk1.3..
Now One of my application needs j2sdk1.4.2 while other can run only with
j2sdk1.3.. (This is an old project & there are java class package norms - like every class should be in a package to import it now. But earlier it was not strict).
Means this is absoulte for me to run one application with version 1.3 while other with 1.4.
But I can set Java_Home env. varibale only once. How can I tell my each web-application to take thier own jdk version in compiling & running.
Is this allowed in J2EE/Web-Containers.
Please suggest if there is any such setting which makes it possible.
THanks you all in advance...
Manoj :confused:

wouldn't matter if you could.
The package enforcement is NOT something from J2SDK 1.4 but from the version of Tomcat used.
Each Tomcat instance will use the same JVM for all webapps running inside it. You'll need a separate Tomcat instance of an older version for the older webapp (or better yet change it around to the new rules).

Target JDK version?

Hi, I'm trying to get a string out of a database via JDBC. When I compile my code with "1.3.0" as target JDK version in the project properties settings, the java.sql.ResultSetMetaData().getColumnType(int column) method says my string is of type OTHER and it comes out as '3003D0022003100...'.
When I compile with "Jdeveloper_1.2.2" as target JDK version, the java.sql.ResultSetMetaData().getColumnType(int column) method returns a type value that does not correspond to any of the 27 types defined in java.sql.Types. The string looks as it should though. Why is this? Does the Oracle compiler or JVM change som settings in the sun.jdbc.odbc.JdbcOdbcDriver that maes the string com out right? How do I do to get the string out as a string with the standars JVM (say when i access it via a JSP)?
/Fredrik
null

Fredrik,
You don't mention which driver version you're using. I know with 8.1.6, there was a classes12.zip for using JDBC with the JDK 1.2.x, and a classes111.zip for using JDBC with JDK 1.1.8 (I think).
I don't know that they even have a classes13.zip available, so your results may vary if using JDK 1.3. The internal JVM on the server uses JDK 1.2.
I recommend checking the Oracle8i JDBC Developer's Guide and Reference for the version of the database you're connecting to and see info is provided there about compatibility with different versions of the JDK.

Is it possible to alter JDK version used by OAS?

I'm using OAS 101202 and am currently having issues deploying an ear file that's been built by java 1.5. OAS 101202 only uses java 1.4.2_06. When i deploy my ear file I get the following java incompatibility error
java.lang.UnsupportedClassVersionError: org/apache/struts2/dispatcher/FilterDispatcher (Unsupported major.minor version 49.0)
The version of struts we're using requires 1.5.
Is it possible to get 101202 working with 1.5?
Thanks
Paul

I have some really bad experiences with changing the jdk version, but you can install one next to the AS and then do some config magic in server.xml (if I'm correct) to point to the new java compiler. For the exact syntax you have to search the docs though (it was something like javac-$RANDOM_WORD_I_FORGOT )

JRC R2 and JDK Versions

Hi,I use Crystal Report XI R2 JRC on a Web App. My application works fine (included all actions with the crystal viewer) with this configuration : -Application Server : WAS Express 5.0 - OS : Windows - platform : Intel - JDK : 1.4My application does'nt work fine (some actions with the crystal viewer - button next page, export PDF, etc... return an error 500) with this new configuration : -Application Serveur : WAS 6.1 - OS: Linux Red Hat AS4 Updated 4 - Platform : Iseries - JDK : 1.5 This is the error description : Error 500: LinkageError while defining class: com.crystaldecisions.Utilities.LengthLimitedDataInputStream Could not be defined due to: com.crystaldecisions.Utilities.c This is often caused by having a class defined at multiple locations within the classloader hierarchy. Other potential causes include compiling against an older or newer version of the class that has an incompatible method signatureIf somebody can help me or knows this problem (jdk version ?) with JRC R2, Thanks, Jerome. 

On our support site we have a document of supported platforms for various Operating systems,Â including Linux.Â In the Application server table, it lists the following configurations:
Application ServersÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â JDK
[] OAS 10G Rel.2 (10.1.2)Â Â Â Â Â 1.4.2_x Tomcat 5.0.27Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 1.4.2_08+ [] WebLogic 8.1 SP4Â Â Â Â Â Â Â Â Â Â Â 1.4.2_x WebSphere 5.1.0.4Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 1.4.1_x [**] WebSphere 5.1.1.0Â Â Â Â Â Â Â 1.4.2_x
WebSphere 6.0.0.2Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 1.4.2_x
I would also suggest reviewing the platforms document
[http://support.businessobjects.com/communityCS/TechnicalPapers/boe_xi_r2_supported_platforms_linux.pdf | http://support.businessobjects.com/communityCS/TechnicalPapers/boe_xi_r2_supported_platforms_linux.pdf]
InÂ your case it would seem that the issue is related to the platform you are trying to deploy on.Â Â
Usually the solution is to deploy on something that is on the supported list; it is one less thing that gets in the way of a successful solution.Â One thing you might try, is recompiling the JARS using the newer JDK, thisÂ is not a guarunteed solution but has been known to work in the past.Â
I do recommend, as a member of Developer Support, that you have a supported configuration, that way ifÂ you find any bugs with the product, we have an escalation path to fixing them.Â
Merry Enns
Technical Resource, Developer Support
Business Objects

Which JDK version is required for NWDS v 7.01.07

Hi,
Can someone point me in the right direction to find out whcih JDK version is required for NWDS v 7.01.07.
I currently have j2sdk1.4.2_19 installed but I am getting a build error when creating a new project from ESS of:
No 'default' JDK defined, will use running VM.
The TARGET variable for the shortcut and JAVA_HOME env variables are set.
The JRE_SRCROOT variable in NWDS is empty.
Regards,
Rob

In NWDS set default JDK version.
Windows - preferences - java Installed JREs
Select chk box for JRE you want.
Hope this helps.

SSIS Project Deployment : Getting error "query the operation_messages view for the operation identifier"

Hello,
I have developed SSIS package and using Project Deployment Model.
I have created a Folder under the SSISDB in Integration Services Catalog.
Then, Right click on the Project folder and Deploy Project, Selected the .ispac file and clicked Deploy.
It gives me below error.
Can anyone please help me on this?
I tried deploying it several times but getting the same error message. I searched for forums and tried below things:
http://capstonebi.blogspot.in/2012/09/ssis-2012-deployment-frustrations.html
http://thinknook.com/ssis-2012-deployment-error-the-project-or-operation-records-do-not-exist-2012-08-03/
Thank you,
Mittal.

Hi Mittal,
If we want to find more information about this error, we should execute the query below under SSISDB catalog in SQL Server Management Studio, then expand the message column to see the detail error message:
select * from catalog.operation_messages
where operation_id=100155
Generally, the issue always be caused by a timeout for big projects, this is a known issue. The workaround for this issue is create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
Besides, it can also be caused by other issues. For example, if the package includes an Attunity Oracle connection, but the deployed environment doesn’t install the Attunity connectors. For more details, please see:
http://www.sqlservercentral.com/Forums/Topic1587793-2799-1.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How are you tracking deployed software versions for traceability?

I am curious how others are tracking deployed software versions in automated test environments.
I am working on a medical device tester and we have a somewhat inefficient method for keeping track of all version numbers. I would like to know what tools are available to automate tracking version throughout a project, from build to viewing later. Or, what methods are typical in this type of environment.
Essentially, we need to be able to say at any given moment what software version is running at 3 remote locations on several deployed systems.
For simply automating the process of viewing the version number programmatically, I found this, but we've had issues with it:
http://digital.ni.com/public.nsf/allkb/D45E3A1E694815AD86257173005CFD36
This solution requires a "separate" installer to get the .NET framework onto the target PC. Also, it doesn't work (to my knowledge) with the Help>>About window.
Comments?
Dan Richards
Certified LabVIEW Developer

Dennis,
Thanks for replying. We are using SVN. The exact ECO process for this project is under construction as it is a relatively new project and deployments will be at our customer's site. We use JIRA for tracking specific change requests.
Here's an example of our basic process:
- Software changes made (according to JIRA tasks) and source code checked in
- Builds released per schedule with version numbers (from JIRA projects) hard-coded into the application
- Builds deployed at different locations & times
Here's what I'd like to see to improve things:
- Builds released with version numbers generated from one of the following:
   1. Loaded from JIRA release numbers - maybe auto-generated for reference by LabVIEW when building the application
   2. Part of a custom build launcher
         >> This would be a custom interface that runs functions like those in Application Builder palette while also sending version info
         >> Perhaps it could prompt the user for version info or read from something auto-generated.
- Builds should automatically make version numbers visible within the application (for example, LabVIEW has the Help>>About window)
- Build numbers should be programmatically/dynamically accessible without having to install an additional .NET framework that isn't listed in 'Additional Installers'
Curious if there are any tools that support these kinds of things. I am aware of Deploy by Wirebird Labs and Proligent by Averna, although I am lacking in knowledge about specific features.
Regards,
Dan
Dan Richards
Certified LabVIEW Developer

NWDS JDK version

Hi Team,
I am using Portal 7.4 sp4 and i want to modify one WD Java application running in that.
Now i am trying to install NWDS 7.31 SP 9 with JDK jdk-6u26-windows-i586.
My doubt is in the NWDS installation guide, its mentioned like...
Note: To deploy an application, the JDK version of NWDS and JVM version of application server should be same "
Now my JVM version in portal UNIX server is JVM 6 (SAP).
Can i go ahead with installtion of NWDS 7.31 SP 9 with JDK jdk-6u26-windows-i586 in my windows 32bit machine to modify the applications?
Please suggest.
Thanks in Advance
Regards,
Alex

Hi Alex
you can go ahead.
I think that comment tries to say only that the major version of the jdk/jre must be the same. E.g if on client you have 1.6 then on server the vm must be sapvm6 (and not say 5 or anything else). You said also very correctly that the jdk has to be 32 bit and the SP relation is also correct (731 nwds has +5 higher SP than 7.4 server)
Regards,
Ervin

JDK Version req for OIM 9.1.0.1 Installation

Hi,
As per Oracle's documentation, we need to use JDK 1_4_2_15 for Oracle Identity Manager 9.1.0.1. Installation. In my machine when I checked Java Version it shows jdk 1.5_0_06. Is there any problem if I go with the default jdk version or I have to change it to 1.4.2_15. Please advise.
Regards,
CC

This is given in docs:
C:\>java -version
java version "1.5.0_06"
http://download.oracle.com/docs/cd/E14049_01/doc.9101/e14062/install_config_oc4j.htm#BGBJAAID

How to determine the JDK version required to use a jar?

Hi all.
I am using a hosted server that uses JDK 1.4.2 and I cannot upgrade the VM. I have been finding it extremely difficult to install web applications on this server since I find that after installing the app, the web server complains the bytecode used in the jar is newer than the VM can understand (or it complains that the app uses JEE servlet or JSP methods it cannot find).
To compound the problem, only about 25% of the sites I've visited that provide jars for download mention the minumum JDK version required to use them. (Some do not mention any system requirements at all besides 'requires Java and a Java application server').
Do any of you know of any tools that can analyze a jar and determine the bytecode version it uses?
(Another helpful tool would be one that can determine the minimum JEE APIs required to run a web app..., but that's probably wishful thinking :)).
Thanks for your help.
Michael N. Christoff

The major/minor version of the class file is the way to go.
Also, it's not necessary to write a separate program to get to those. javap prints them out when being passed the -v flag.
Note, however that "JDK version" is not a correct term, as I can create 1.4-compatible class files with a Java 6 JDK (by passing the -target flag to javac). Those won't look any different than .class files written with a 1.4 JDK.

BOE XI 3.1 jdk version

<h4> Hi,
Is JDK1.6 supported for BOE XI 3.1 application server?
According to platform requirements for linux (page 7) it seems that Tomcat 5.5 , jdk 1.5.0_xx is supported.
Of course in the same document there's also written: </h4>
Application Server Incremental Release Support Policy
Specified application servers versions have been successfully tested by Business Objects. Incremental releases of the specified versions defined by the last number in the application server name will be supported as they are made available, but may not have been tested by Business Objects. Exceptions in support will be documented.
JDK Version Support Policy
JDK major versions are specified to ensure the use of correct version when there are multiple choices provided
by the vendor. Business Objects tests and supports any _xx release installed with a given application server.
<h4>
So must I assume that Tomcat 6 and jdk 1.6.0_xx is supported?
Thanks,
Fabbio
</h4>
Edited by: fabbio on Sep 14, 2009 6:17 PM

With service pack 2 tomcat 6.0 is now supported but you will need to add it as 5.5 still comes packaged with the product. JDK 1.6 was not tested with tomcat per the [supported platforms for XI 3.1 SP2|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/402db6eb-845d-2c10-a38c-aafde85ec769&overridelayout=true]
If using other web/apps that support 1.6 (weblogic or websphere) then 1.6 can be used.
Regards,
Tim

How to change weblogic 10.3 's JDK version

I installed weblogic 10.3 and its default JDK version is 1.6.0_05, but I want to update the JDK to 1.6.0_18, how should I do it?
I tried to create a new domain and in "JDK Selection", I select option "Other JDK",path is "C:\Program Files (x86)\Java\jre6", but when start admin server, error "you wrongly used \Java\jre6 "(Which is translated from Japanese).
How should I do?

Hi,
Please refer to the Post: http://weblogic-wonders.com/weblogic/2010/09/03/why-and-how-oracle-jrockit/
If you want to use a Different Version of Sun JDK then please change the JAVA_VENDOR=Sun as well....in the folowing Image:
http://weblogic-wonders.com/weblogic/wp-content/uploads/2010/09/setting_JAVA_JOME_In_script.jpg
Example : (setDomainEnv.cmd) for WINDOWS OS
set JAVA_HOME=C:\myJDKs\jdk1.6.0_18
set JAVA_VENDOR=Sun
=-- = = = = = =-- = = = = = =-- = = = = = =-- = = = = =
Just in case if you still face the same problem then do the following:
In your Windows OS box...
RightClick on MyComputer ---> Advanced(Tab)---> Envirunment Variables (Button)---->User Variables (Section) add a new variable:
Variable Name : PATH
Variable Value : C:\myJDKs\jdk1.6.0_18;%PATH%;
OK
Just to verify this now open a fresh command prompt and then Just run the following command:
java -version
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic(WebLogi Wonders Are Here)

Project deploy JDK version.

Similar Messages

Maybe you are looking for