Deprecated API

Deprecated Classes

com.jcorporate.expresso.services.test.ActionTestServlet
since v5.6, no longer compatible with Struts 1.1

com.jcorporate.expresso.services.dbobj.DBObjImpl
since Expresso 5.3 [never used]

com.jcorporate.expresso.core.security.filters.ISO_8859_1_eForum
As of Expresso 5.0.4 Eforum itself can do its own filtering now.

com.jcorporate.expresso.core.dbobj.LOBSupport
since Expresso 5.3 the ways it worked on LOBs wasn't remotely efficient and has been replaced by the implementation in com.jcorporate.expresso. core.dataobjects.jdbc.LOBField

com.jcorporate.expresso.core.logging.Log
Since Expresso 4.0

com.jcorporate.expresso.core.logging.LogHandler
As of Expresso 5.6 This has not been used since Log4j was integrated with Expresso.

com.jcorporate.expresso.ext.regexp.RE
since v5.6, use jakarta oro

com.jcorporate.expresso.ext.regexp.RECompiler
since v5.6, use jakarta oro

com.jcorporate.expresso.ext.regexp.REProgram
since v5.6, use jakarta oro

com.jcorporate.expresso.core.jsdkapi.ServletAPI2_1Session
since 5.6, Servlet 2.1 is not supported

com.jcorporate.expresso.ext.dbobj.SingleDBUserInfo
10/4/2004 functionality can be handled by DefaultUserInfo with DBOTHERMAP method to map a table to a context

com.jcorporate.expresso.ext.regexp.StringCharacterIterator
since v5.6, use jakarta oro

Deprecated Interfaces

com.jcorporate.expresso.ext.regexp.CharacterIterator
since v5.6, use jakarta oro

Deprecated Exceptions

com.jcorporate.expresso.ext.regexp.RESyntaxException
since v5.6, use jakarta oro

Deprecated Methods

com.jcorporate.expresso.core.dbobj.Schema.add(Job)
See the addJob(Class) method instead since Expresso 5.6

com.jcorporate.expresso.core.dbobj.Schema.add(String, String, String, String)
since 3/04; use addSetup() instead

com.jcorporate.expresso.core.controller.ControllerResponse.addError(String, String)
7/04 v5.5 expresso uses only one property name, the default; use addError(String errmsg) instead

com.jcorporate.expresso.core.controller.ErrorCollection.addError(String, String)
7/04 v5.5 since expresso uses only one property name, use addError(String errmsgkey) instead; if you want args/params for template replacement, use addError(key, (Object)replacementParam) Creation date: (8/29/00 2:43:13 PM) author Adam Rossi, PlatinumSolutions

com.jcorporate.expresso.core.dbobj.MultiDBObject.assembleObject(String)
v. 5.5+; 9/04; use getDBObject() instead

com.jcorporate.expresso.services.test.ControllerTestCase.buildControllerResponse(Document)

com.jcorporate.expresso.services.test.ControllerTestCase.buildControllerResponse(WebResponse)

com.jcorporate.expresso.core.servlet.CheckLogin.checkLogin(HttpServletRequest, HttpServletResponse)
use other checkLogin(request, forcedb); 9/04 v.5.5+

com.jcorporate.expresso.core.servlet.CheckLogin.checkLogin(HttpServletRequest, HttpServletResponse, ServletConfig)
use other checkLogin(request, forcedb); 9/04 v.5.5+

com.jcorporate.expresso.core.servlet.CheckLogin.checkLogin(HttpServletRequest, HttpServletResponse, ServletConfig, String)
use other checkLogin(request, forcedb); 9/04 v.5.5+

com.jcorporate.expresso.core.controller.State.equals(Object)
use direct comparison of state name instead. this algorithm which allows 2 kinds of objects is ugly, and no longer used in expresso as of 5/04, v.5.5.1 LAH

com.jcorporate.expresso.services.test.ActionTestServlet.getActionMappings()
For the Struts 1.1 do not use this method

com.jcorporate.expresso.core.dbobj.DBObjectDef.getAllFields()
use getAllFieldsMap instead

com.jcorporate.expresso.core.dbobj.DBObjectDef.getAllKeys()
Use getAllKeysMap or getAllKeysIterator instead

com.jcorporate.expresso.core.controller.ControllerRequest.getAttribute(String)
v5.5, 4/2004; use getAttrib() instead, and cast to string

com.jcorporate.expresso.services.controller.dbmaint.DynamicCmd.getCurrentDBObj()
Since Expresso 5.1 Use getDataObject() for compatibility with AutoDBObject, JoinedDataObject, etc. Will be removed in Expresso 5.2

com.jcorporate.expresso.core.controller.State.getDBController()
4/04 v5.5 use getController and cast.

com.jcorporate.expresso.core.controller.ControllerRequest.getDBName()
10/2004 v.5.6 use getDataContext instead

com.jcorporate.expresso.core.dbobj.Schema.getDBName()
Use getDataContext() instead. Since v.5.5

com.jcorporate.expresso.core.dbobj.DBObject.getDBName()
since Expresso 5.1 Use getDataContext() instead

com.jcorporate.expresso.core.security.UserInfo.getDBName()
since 5.6, use getDataContext() instead

com.jcorporate.expresso.core.security.UserInfo.getField(String)
Use the direct getLoginName, getEmail, getPassword, etc. methods instead

com.jcorporate.expresso.core.security.MapBasedUserInfo.getField(String)
Use the direct getLoginName, getEmail, getPassword, etc.

com.jcorporate.expresso.core.dbobj.DBObjectDef.getFieldList()
Use getFieldListArray or getFieldListIterator instead

com.jcorporate.expresso.core.db.DBConnection.getFields(String)
Use getFieldsMap() instead

com.jcorporate.expresso.core.dbobj.DBObject.getIndexArray()
since 5.6, Use ((DBObjectDef)getMetaData()).getIndexArray() instead

com.jcorporate.expresso.core.dbobj.DBObjectDef.getKeyFieldList()
Use getKeyFieldArray instead

com.jcorporate.expresso.core.misc.ConfigManager.getMapping(String, String)
this method is now deprecated and does no anything since Struts 1.1 ConfigManager.getActionConfig(String moduleName, String controllerName, String stateName )

com.jcorporate.expresso.services.test.ControllerTestCase.getNodes(Document, String)

com.jcorporate.expresso.core.controller.State.getOptionalParameters()
3/5/04 v5.5 Use getOptionalParametersList instead

com.jcorporate.expresso.core.dataobjects.DataField.getOriginalValue()
8/04 v.5.5 do not expose this cache Retrieve the last original value if the data has changed. Will return null if isChanged() is false

com.jcorporate.expresso.core.dataobjects.jdbc.JoinedDataField.getOriginalValue()
8/04 v.5.5 do not expose this cache

com.jcorporate.expresso.core.controller.Controller.getSchemaHierarchy()
7/04; v5.5. just name changed. see getSchemaStack

com.jcorporate.expresso.core.controller.DBController.getString(String, Object[], ControllerRequest)
The getString method from ControllerRequest should be used in *all* cases - this method is not reliable, as the same DBController instance is shared between users.

com.jcorporate.expresso.core.dbobj.Schema.getTests()
Since Expresso 5.6 Tests have been separated from the main code base.

com.jcorporate.expresso.core.controller.State.getUser()
3/5/04 use ControllerRequest getUid() instead.

com.jcorporate.expresso.ext.dbobj.SingleDBUserInfo.getUserName()
Since Expresso 5.5; use getFullName() instead to avoid confusion with login name

com.jcorporate.expresso.services.dbobj.DefaultUserInfo.getUserName()
Since Expresso 5.5; use getFullName() instead to avoid confusion with login name

com.jcorporate.expresso.core.db.DBConnection.getWildCards()
9/04, v5.5+ use DBConnectionPool.getDefaultWildCards() instead

com.jcorporate.expresso.core.db.DBConnection.getWildCardsList()
9/04, v5.5+ use DBConnectionPool.getDefaultWildCards() instead

com.jcorporate.expresso.core.dbobj.DBObject.isMultiValued(String)
since 5.6, use getJDBCMetaData().isMultiValued(String)

com.jcorporate.expresso.core.dbobj.DBObject.isReadOnly(String)
since 5.6, use getJDBCMetaData().isReadOnly(String)

com.jcorporate.expresso.core.dbobj.DBObject.isSecret(String)
since 5.6, use getJDBCMetaData().isSecret(String)

com.jcorporate.expresso.core.dbobj.DBObject.isVirtual(String)
since 5.6, use getJDBCMetaData().isVirtual(String)

com.jcorporate.expresso.ext.struts.taglib.ControllerUtils.nestedProperty(PageContext, String, String)
use nestedProperty(PageContext, name, property, checkExists) instead

com.jcorporate.expresso.core.misc.CurrentLogin.newInstance(String, String, String, String, long, int)
use other newInstance instead; 9/04 v.5.5+

com.jcorporate.expresso.core.dbobj.Schema.otherSetup(String)
5.5+; 10/04. use otherSetup(log, dbcontext) instead

com.jcorporate.expresso.services.test.ControllerTestCase.parseResponse(WebResponse)

com.jcorporate.expresso.services.test.ActionTestServlet.processActionForm(ActionMapping, HttpServletRequest)
For the Struts 1.1 do not use this method

com.jcorporate.expresso.services.test.ActionTestServlet.processActionPerform(Action, ActionMapping, ActionForm, HttpServletRequest, HttpServletResponse)
For the Struts 1.1 do not use this method

com.jcorporate.expresso.core.servlet.DBServlet.requireLogin(HttpServletRequest, HttpServletResponse, String)
does nothing but return false;

com.jcorporate.expresso.core.dbobj.DBObject.saveBinaryField(String, byte[])
since Expresso 5.6. Use LobField directly or com.jcorporate.expresso.services.dbobj.MediaDBObject for BLOB storage since they all require much less memory as well as provides more dynamic database support.

com.jcorporate.expresso.core.controller.State.saveErrors(ErrorCollection)
3/4/04 [v5.5] Use response.saveErrors instead.

com.jcorporate.expresso.core.controller.ControllerRequest.setAttribute(String, String)
v5.5, 4/2004; use setAttrib() instead

com.jcorporate.expresso.core.dbobj.Schema.setDBName(String)
Since Expresso 5.6 Use setDataContext(String) instead.

com.jcorporate.expresso.core.dbobj.DBObject.setFilterClass(Class)
use setFilterClass(Filter)

com.jcorporate.expresso.core.controller.ControllerResponse.validate(ValidationSet, ErrorCollection)
See ControllerRequest.validateDBObject instead....

Deprecated Constructors

com.jcorporate.expresso.core.misc.CurrentLogin(String, String, String, String, long, int)
use newInstance() instead; 9/04 v5.5+