PutValue and getValue deprecated???

I'm using jdev 3.2 and have been getting the following warnings:
Warning: method putValue(java.lang.String, java.lang.Object)in interface javax.servlet.http.HttpSession has been deprecated.
When I check the documentation for HttpSession, those methods are not listed as being deprecated, and they are not listed on the deprecation list either.
So...are they or are they not deprecated????

The methods are deprecated in Servlet api 2.2.

Similar Messages

PutValue and getValue are deprecated...

session.putValue("paramName","value")
and
session.getValue("paramName")
are deprecated.
Do you know what functions I can use to replace them?

Use session.setAttribute(String, Object) and session.getAttribute(String).
-Navin

ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance

Hi friends,
i am trying to install BIW 3.0b (win-2000, oracle 9.2.0.1.0 (patch 9.1.0.4.1)& j2sdk 1_4_1)
while installing database instance i am getting this problem.
INFO 2007-09-26 15:57:09
Copying file C:/SAPinst ORACLE KERNEL/keydb.xml to: C:/SAPinst ORACLE KERNEL/keydb.1.xml.
INFO 2007-09-26 15:57:09
Creating file C:\SAPinst ORACLE KERNEL\keydb.1.xml.
INFO 2007-09-26 15:58:14
Processing of host operation t_HostInfo_SHARED succeeded.
INFO 2007-09-26 15:58:35
The 'saploc' share exists at directory 'E:\usr\sap'. Choosing drive E: as SAP System drive.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.XML.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:26
Copying file C:/SAPinst ORACLE KERNEL/DBSIZE.XML to: C:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/DDLORA.TPL to: DDLORA.TPL.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DDLORA.TPL.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
INFO 2007-09-26 16:00:33
Removing file C:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:02:00
Package table created
PHASE 2007-09-26 16:02:10
SAP Business WareHouse
PHASE 2007-09-26 16:02:10
SAP Web Application Server
PHASE 2007-09-26 16:02:10
Request common parameters of SAP System
PHASE 2007-09-26 16:02:10
Create operating system accounts
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1004 ACCOUNTNAME=biwdev\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1005 ACCOUNTNAME=biwdev\SAP_BWD_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1006 ACCOUNTNAME=biwdev\SAP_BWD_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1007 ACCOUNTNAME=ORA_BWD_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1008 ACCOUNTNAME=ORA_BWD_OPER ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1009 ACCOUNTNAME=biwdev\bwdadm ACCOUNTTYPE=USER DESCRIPTION=SAP System Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,biwdev\Users,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1010 ACCOUNTNAME=biwdev\SAPServiceBWD ACCOUNTTYPE=USER CONDITION=YES DESCRIPTION=SAP System Service Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1844237615-963894560-725345543-1009' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeServiceLogonRight SeNetworkLogonRight' to account 'biwdev\SAPServiceBWD' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'biwdev\bwdadm' on host 'biwdev'!
INFO 2007-09-26 16:02:18
Evaluating all 'tNT_RegistryEntries' table rows succeeded.
INFO 2007-09-26 16:02:19
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:20
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:22
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:23
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:53
Creating directory E:\oracle\BWD\sapdata1\system_1.
INFO 2007-09-26 16:02:53
Creating file system node E:\oracle\BWD/sapdata1\system_1 with type DIRECTORY succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.ORA to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.ORA with type FILE to E:\oracle\ora92\database\initBWD.ora succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.SAP to: E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.SAP with type FILE to E:\oracle\ora92\database\initBWD.sap succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.DBA to: E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.DBA with type FILE to E:\oracle\ora92\database\initBWD.dba succeeded.
INFO 2007-09-26 16:02:55
Processing of all file system node operations of table tORA_ServerConfig_FORMS succeeded.
INFO 2007-09-26 16:02:57
Processing of adapt operation tORA_ServerConfig succeeded.
INFO 2007-09-26 16:02:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:02
Moving file E:/oracle/ora92/database/initBWD.ora to: orig_init_ora_tmp.txt.
INFO 2007-09-26 16:03:02
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:03:02
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
INFO 2007-09-26 16:03:02
'E:\oracle\ora92/bin/oradim -new -sid BWD -STARTMODE auto' returned with '20'.
INFO 2007-09-26 16:03:04
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-09-26 16:03:13
CJS-00084 SQL Statement or Script failed. Error Message: ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance started.
ERROR 2007-09-26 16:03:13
FJS-00012 Error when executing script.
Please let me know, what was tha problem.
Regards,
satish

I suggest you upgrade your Oracle installation to 9.2.0.7 or 9.2.0.8 and then try again.
Markus

Obsolete and/or deprecated

Hi there,
I have recently installed Oracle 10g using DBCA. I then ran some scripts to utilise our internal application that runs on Oracle 9i. After shutting down the instance and restarting it, I get the following error:
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Has anyone any ideas on how to locate this parameter? The alert log did not give me much info.
Regards
Ciara

Thanks for that, the list of deprecated values are as follows. Do I simply set them to false/0 to get rid of the error on startup?
NAME
lock_name_space
buffer_pool_keep
buffer_pool_recycle
max_commit_propagation_delay
remote_archive_enable
log_archive_start
parallel_server
parallel_server_instances
fast_start_io_target
logmnr_max_persistent_sessions
serial_reuse
NAME
max_enabled_roles
global_context_pool_size
plsql_compiler_flags
sql_trace
parallel_automatic_tuning
drs_start
Regards
Ciara

Obsolete and/or deprecated parameter(s) specified for plsql_compiler_flags

Hi All,
After upgrading the from 10.2.0.1 to 10.2.0.4 on linux. I am getting ORA-32004: obsolete and/or deprecated parameter(s) specified error for plsql_compiler_flags.
in alert log says
Deprecated system parameters with specified values:
plsql_compiler_flags
End of deprecated system parameter listing
Could you please help me how to fix this problem.
Thanks

Thank you Pavan and oradba.
even after changing to
ALTER SYSTEM SET plsql_compiler_flags = 'NATIVE' SCOPE=SPFILE;
ALTER SYSTEM SET plsql_code_type = "NATIVE" SCOPE=SPFILE;
still I am getting same error. Could you please help me to fix this problem.
Thanks

What reason ORA-32004: obsolete and/or deprecated parameter(s) specified ?

Hi
ORA-32004: obsolete and/or deprecated parameter(s) specified
Whenever i changed my test database from noarchive log mode to archive log mode, after i changed ,i startup database the above error occured.
following steps i do it,
SQL> archive log list;
Database log mode           No Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
Change your database No Archive mode to Archive mode
Your Database must in mount stage
SQL>shutdown immediate
SQL>startup mount
SQL> archive log list;
Database log mode           No Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
SQL> alter database archivelog;
Database altered.
SQL> archive log list;
Database log mode           Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
SQL>alter database open;
SQL>archive log list
Database log mode           Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence      0
Next log sequence           0
Current log sequence           0
Automatic archival – Disable (the database archive mode but automatic
archival disable
So datas not archive.you must enable the automatic archival)
SQL>archive log start; (session level only enabled not instance level)
SQL> archive log list;
Database log mode           Archive Mode
Automatic archival           Enable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
If you want set instance level you change in parameter file
SQL>show parameter log_archive_start
Name                    Type           Value
log_archive_start boolean      FALSE
SQL>alter system set log_archive_start=true scope=spfile
System altered.
SQL>shut immediate
SQL>startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
Database open.
sql>
But i resolved the problem
I want know the reason why the above error occured
database version : 10g
os : xp ( my laptop) Not office database
Regards
S.Azar
DBA

>
SQL>alter system set log_archive_start=true scope=spfile
System altered.
SQL>shut immediate
SQL>startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
>
Precisely that parameter LOG_ARCHIVE_START is obsolete in 10g. You also don't need to enable the archiving with
archive log start
Simply changing into archive mode also brings up archiver processes since 10g :-)
Kind regards
Uwe
http://uhesse.wordpress.com

Session.putValue() and session.setAttribute

do I have to use session.putValue() before using session.setAttribute() and session.getAttribute() ?
becuase I have one JSP page include one form (action=TheSameJspFile.JSP) several Submit bottuns each Bottun has its Value.
in the JSP I request the submit value and depends on it doing stuff ...
each Value I have to get and to set a session Attribute, if I want to putValue it will delete the old value.
how can I solve this?

You need to store something in the session before you can retrieve it.
So, you need to do a setAttribute() to place something in the session. Then you use getAttribute() to retrieve it. DO NOT use putValue as it is deprecated and has been replaced by setAttribute(). DO NOT use getValue() as it is deprecated and has been replaced by getAttribute().

ORA-32004: obsolete and or deprecated parameter

Oracle 11.1.7.0:
When I startup the db I get ORA-32004. There is no trace of which parameter is obsolete in alert logs. Neither do I see that parameter in v$obsolete_parameter. How can I look at what that parameter is?

I found it in alert log. Since it was one parameter I didn't see it clearly in the logs. This parameter was user_dump_dest. I reset this parameter. But we have a requirement to set this parameter becaus current filesystem doesn't have enough space. How can I set this so that the destination can be on different volume than $ORACLE_HOME?

ORA-32004: obsolete and/or deprecated parameter(s) specified

Error at startup in Oracle Database 10g
Which parameter should i set
Thanks

Please make sure if SPFILE contains the parameter "log_archive_start=TRUE". If yes this should be removed as this is obsolete in 10g. Don't edit the SPFILE with note pad. You may have to recreate the file using "CREATE SPFILE FROM PRILE;"

Deprecated HttpSession.putValue vs HttpSession.setAttribute

I have written a number of servlets that track and manage a user using HttpSession. I have been trying to attach the user profile (a class I wrote that contains simple info like name, age...) to the HttpSession with the setAttribute method. When I get my HttpSession back on the next Servlet I use the getAttribute method only to have my Servlet killed at that line of code ie, after session.getAttribute( "my_attribute") the Servlet stops executing code.
When I use the deprecated putValue and getValue, everything works just fine.
Does anyone have a solution to this one? Thanks in advance for any assistance.

I believe you need to cast anything you pull back out of the session, else it comes out as a generic Object.

Jdev3.2 and ias: not compatible?

Jdev3.2 support servlet2.2 api.and ias use apache jserver,which only support servlet 2.0.So our application can't run on ias when
we update from jdev3.1 to jdev3.2 .But it was well on jdev3.2.
for example ,with jdev3.2 ,we use session.putValue and getValue to record something,but the session is lost on ias.But it was fine with jdev3.1. So we use Servlet 2.2 api:session.setAttrubute,but it can't run on ias.
How to slove it? urgent
regards

We have tried the ias9i for nt.And the problem is still there:sessionsetAttribute can not run.
And we know that ias9i still use the jserver ,which just support servlet 2.0 and apache team said they would not update it.
What's the problem?
I am using the apache+tomcat.And it is fine.

Obsolete and deprecated parameters

Hi,
we got the error when i start the istance.
SQL> STARTUP
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 75498852 bytes
Database Buffers 88080384 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
How to find which parameters are obsolete and/or deprecated?

user3266490 wrote:
Hi,
we got the error when i start the istance.
SQL> STARTUP
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 75498852 bytes
Database Buffers 88080384 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
How to find which parameters are obsolete and/or deprecated?Hi
Check
http://azardba.blogspot.com/2009/08/ora-32004-obsolete-andor-deprecated.html
Regards
Azar
DBA

Subsequent acquistion and deprecation

Hi,
This is Amar i hava a issue regards deprecation.
for ex: on 01.01.2007 on asset is capitised by1000 and the deprecation is calculated 10% that is 100.
for the same asset subsequent acquisation is 500 on 01.06.2007. but the deprecation is taking for the full year means 12 month. but my clint want to deprecation for the subsequent acquisation is form the posting date. is it possialbe are not. if any on know please let me konw.
Regards,
Amar.

Hi pankaew,
i think u r not understand my problem, he purchased one asset on 01.01.2007, for the same asset he added some value on the middle of the year. if we run the deprecation it is calculate for the full year deprecation for subsequent accusation asset aslo. but my client want to calculate the deprecation for the subsequent vacation for the posting date on words.
EX:on 01.01.2007 asset capitalization 1000.
for the same asset some amount is added(means subsequent accusation) on 05.01.2007 is 200
now Deprecation calculate is going like that. 1200/10=120
but my cline wat to =1000/10 =100
and =200/10 =20*8/12 =13.33
now total dep for asset is = 100+13.33 =113.33

Deprecated methods/classes

Does anyone know if, for the SUN Certified Web Component Developer exam, you are tested on the deprecated classes and methods e.g. HttpSession.putValue(), HttpSession.getValue() etc?

No they are not in the test

Session object question put vs. putValue vs. setAttribute?

I have the following code:
<%@ page import="java.util.*" %>
<jsp:useBean id="EducationBean" class="java.util.Hashtable" scope="session" />
<%
String swCurrFileName = "swcontrol.jsp";
Enumeration params = request.getParameterNames();
while (params.hasMoreElements()) {
String name = (String)params.nextElement();
EducationBean.put(name, request.getParameter(name));
%>
My question is I can't find any documentation on the put command, whats the difference between 'put', and 'putValue', and 'setAttribute'? When I try using the 'putValue' or 'setAttribute' command I get errors.
What I'm trying to do is store form values in a session object across several pages, and on the last page display all the form values from the previous pages.

the object you are calling put on is a java.util.Hashtable. put places an object into the table to be keyed off of another object. In your case, your key is the variable name and the object to be stored is your parameter from that name.
the putValue and setAttribute are methods on the session object. They both do the same action as above, but are for HttpSession objects. putValue is deprecated and you should be using setAttribute, but most WebServers have putValue() pointing to the setAttribute() method. hope this helps.

PutValue and getValue deprecated???

Similar Messages

Maybe you are looking for