jacquard 1.10.14 by The Web Engineering Factory and Toolworks

Deprecated API

Deprecated Classes
uk.co.weft.htform.Button
          see ActionWidget 
uk.co.weft.domutil.ContextElement
          The use of this class is deprecated because most current DOM implementations won't handle nodes they didn't create. Sad, but there it is - if you use this your code will be at best fragile and unportable. Use ContextElmentGenerator instead. 
uk.co.weft.exceptionhandler.SourceForgeExceptionHandler
          does not work yet. 
uk.co.weft.domutil.TranslatingContextElement
          The use of this class is deprecated because most current DOM implementations won't handle nodes they didn't create. Sad, but there it is - if you use this your code will be at best fragile and unportable. Use ContextElmentGenerator instead. 
 

Deprecated Fields
uk.co.weft.htform.Form.actionExecutedToken
          use ACTIONEXECUTEDTOKEN 
uk.co.weft.domutil.DocPage.chosenGeneratorMagicToken
          use CHOSENGENERATORMAGICTOKEN 
uk.co.weft.htform.TableWrapperForm.confirmDeletionToken
          use CONFIRMDELETIONTOKEN 
uk.co.weft.htform.Form.contextMenuMagicToken
          use CONTEXTMENUMAGICTOKEN 
uk.co.weft.htform.Form.cssHelp
          use CSSHELP 
uk.co.weft.htform.Form.cssPrompt
          use CSSPROMPT 
uk.co.weft.dbutil.ConnectionPool.dbPassMagicToken
          use DBPASSMAGICTOKEN 
uk.co.weft.dbutil.ConnectionPool.dbUrlMagicToken
          use DBURLMAGICTOKEN 
uk.co.weft.dbutil.ConnectionPool.dbUserMagicToken
          use DBUSERMAGICTOKEN 
uk.co.weft.htform.TableWrapperForm.deletedToken
          use DELETEDTOKEN 
uk.co.weft.dbutil.Context.endOfCommentMagicToken
          there should be no need to use this 
uk.co.weft.htform.Servlet.localeMagicToken
          use LOCALEMAGICTOKEN 
uk.co.weft.htform.Form.onloadFunctionToken
          use ONLOADFUNCTIONTOKEN 
uk.co.weft.htform.Servlet.outputStreamMagicToken
          use OUTPUTSTREAMMAGICTOKEN 
uk.co.weft.htform.Servlet.redirectMagicToken
          use REDIRECTMAGICTOKEN 
uk.co.weft.htform.Servlet.requestMagicToken
          use REQUESTMAGICTOKEN 
uk.co.weft.htform.Servlet.responseMagicToken
          use RESPONSEMAGICTOKEN 
uk.co.weft.htform.Form.selectedWidgetSetMagicToken
          use SELECTEDWIDGETSETMAGICTOKEN 
uk.co.weft.htform.Servlet.servletMagicToken
          use SERVLETMAGICTOKEN 
uk.co.weft.htform.Servlet.sessionMagicToken
          use SESSIONMAGICTOKEN 
uk.co.weft.dbutil.Context.startOfCommentMagicToken
          there should be no need to use this 
uk.co.weft.htform.TableWrapperForm.storedToken
          use STOREDTOKEN 
uk.co.weft.htform.TableWrapperForm.storeFailToken
          use STOREFAILEDTOKEN 
uk.co.weft.htform.Page.titleMagicToken
          use TITLEMAGICTOKEN 
uk.co.weft.htform.Form.validationWhingeToken
          use VALIDATIONWHINGETOKEN 
 

Deprecated Methods
uk.co.weft.dbutil.Currency.coerceToDouble()
          this isn't really safe because of possible rounding errors 
uk.co.weft.dbutil.Context.comment(String)
          don't use this. Write to your log instead if you have one; otherwise write to standard error (which is what this now does) 
uk.co.weft.htform.ResultFormatter.composeActionURL(Context)
          use composeActionURL( Context, Context) 
uk.co.weft.dbutil.TableDescriptor.drop(Context, Object)
          use drop( Context) instead. 
uk.co.weft.dbutil.TableDescriptor.fetch(Context, Object)
          use fetch( Context) instead. Returns a positive integer if successful; if exactFetchCount is true, the number of matching rows. 
uk.co.weft.dbutil.ColumnDescriptor.formatForInsert(Context)
          this has actually never worked as advertised and is wrong - probably for all purposes - but it has been in the toolkit so long that it is possible that some applications out there depend on its wrong behaviour, so this has not been corrected. If you are using it, consider formatForSelect( Context) instead. 
uk.co.weft.dbutil.ColumnDescriptor.formatForMatch(Context)
          use #formatForMatch(Context,boolean) 
uk.co.weft.dbutil.CharacterColumnDescriptor.formatForMatch(Context)
          use formatForMatch( Context,boolean) 
uk.co.weft.htform.Form.generate(Context)
          this is the future, but it isn't finished yet; expect some changes to the interface definition and XML 
uk.co.weft.htform.WidgetSet.generate(Document, Context)
          this method is not yet stable, may change in future. 
uk.co.weft.htform.Widget.generateAttributes(Element)
          use generateAttributes(Element,Context) instead. 
uk.co.weft.domutil.ResultSetGenerator.generateRS(Document, Context, Contexts, String)
          use generateRS( Document, Contexts, String, String, int, int) instead 
uk.co.weft.dbutil.Context.getConnection(String, String, String)
          this is really horribly bad design. You should use ConnectionPool.getConnection() instead. 
uk.co.weft.htform.Page.getHeadIncludeURL(URL, Context)
          replaced with getHeadIncludeURL(String,Context) which is able to fix up relative URLs 
uk.co.weft.dbutil.Context.getKeys()
          probably better to use keys() 
uk.co.weft.htform.FormLayout.getPrompt(Context, Widget)
          use Widget.getPrompt( Context) 
uk.co.weft.maybeupload.MaybeUploadRequestWrapper.getRealPath(String)
          As of Version 2.1 of the Java Servlet API, use ServletContext.getRealPath(java.lang.String) instead. 
uk.co.weft.alert.Watcher.getResource(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.htform.Servlet.getResource(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.htform.ResourceConsumer.getResource(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.alert.Watcher.getResourceString(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.htform.Servlet.getResourceString(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.htform.ResourceConsumer.getResourceString(String, Context)
          i18n code is still experimental and the only call I commit to supporting in the longer term is grs(String,Context) 
uk.co.weft.htform.Page.getStylesheet(Context)
          probably better to use getStylesheets(Context) 
uk.co.weft.htform.Page.getTitle()
          use getTitle( Context) in preference 
uk.co.weft.dbutil.Context.getValue(String)
          probably better to use get() 
uk.co.weft.alert.Watcher.grs(String)
          use grs(String,Context) 
uk.co.weft.htform.Servlet.grs(String)
          use grs(String,Context) 
uk.co.weft.htform.ResourceConsumerImpl.grs(String)
          use grs(String,Context) 
uk.co.weft.htform.ResourceConsumer.grs(String)
          use grs(String,Context) 
uk.co.weft.domutil.DocumentGeneratorImpl.init(ServletConfig)
          From Jacquard 2.0, a ServletConfig won't be passed. Specialise init( Context) instead. 
uk.co.weft.htform.Servlet.init(ServletConfig)
          Forms now work both as Servlets and DocumentGenerators; in Jacquard 2.0 they will act primarily as DocumentGenerators. ServletConfig may not be available to a DocumentGenerator (e.g. when it isn't called from a Servlet). So it's better ( more general) to specialise init( Context) than init( ServletConfig). If you do the former your forms will work whether or not they're called from Servlets; if the latter only when called from Servlets. 
uk.co.weft.maybeupload.MaybeUploadRequestWrapper.isRequestedSessionIdFromUrl()
          As of Version 2.1 of the Java Servlet API, use MaybeUploadRequestWrapper.isRequestedSessionIdFromURL() instead. 
uk.co.weft.dbutil.JDBCAuthenticator.isSecret(String)
            
uk.co.weft.dbutil.Authenticator.isSecret(String)
          use getFeatures( token) instead 
uk.co.weft.htform.ResultFormatter.layout(Context)
          not thread safe. Use layout( data, context). 
uk.co.weft.htform.ResultFormatter.layoutFirst(Context)
          no non-deprecated replacement at present. 
uk.co.weft.htform.FormLayout.layoutWidget(Context, Widget, Stack)
          maintained for backwards compatibility only; use layoutWidgets(WidgetSet,Context) instead. 
uk.co.weft.htform.FormLayout.layoutWidgets(WidgetSet, Context, Stack)
          maintained for backwards compatibility only; use layoutWidgets(WidgetSet,Context) instead. 
uk.co.weft.amazon.AmazonDescriptor.match(Context)
          use match( Context,boolean) 
uk.co.weft.dbutil.TableDescriptor.match(Context)
          use match( Context,boolean) 
uk.co.weft.dbutil.DataStoreDescriptor.match(Context)
          use #match(Context,boolean) 
uk.co.weft.dbutil.Contexts.match(Context)
          use match( Context, boolean) 
uk.co.weft.dbutil.TableDescriptor.match(Context, boolean, Connection)
          may become protected in future releases 
uk.co.weft.dbutil.TableDescriptor.match(Context, Connection)
          may be dropped in future releases 
uk.co.weft.dbutil.TableDescriptor.match(Context, Vector)
          use match( Context,Vector,boolean) 
uk.co.weft.dbutil.TableDescriptor.match(Context, Vector, boolean, Connection)
          experimental; may be withdrawn 
uk.co.weft.dbutil.TableDescriptor.match(Context, Vector, Connection)
          will become protected in future releases 
uk.co.weft.dbutil.Context.merge(Dictionary)
          the Dictionary class is obsolete; use merge(Map) instead. 
uk.co.weft.htform.Widget.onloadRequest()
          use onloadRequest( Context) instead 
uk.co.weft.domutil.TranslatingContextElement.populate(Document, String, Context)
            
uk.co.weft.htform.TableWrapperForm.populateForm(Object, Context)
          specialise fetch( Context) instead. 
uk.co.weft.dbutil.Context.putValue(String, Object)
          probably better to use put() 
uk.co.weft.dbutil.Context.releaseConnection(Connection, boolean)
          setting dontCloseStatements to true may be associated with connection pool leaks: use with great caution. 
uk.co.weft.dbutil.ConnectionPool.releaseConnection(Connection, boolean)
          setting dontCloseStatements to true may be associated with connection pool leaks: use with great caution. 
uk.co.weft.htform.Widget.scriptRequest()
          use scriptRequest( Context) instead 
uk.co.weft.htform.Widget.setType(String)
          use appropriate sub-class instead. 
uk.co.weft.dbutil.TableDescriptor.store(Context, Object)
          use store( Context) instead. 
uk.co.weft.htform.Servlet.storeOnSession(Context, String, String)
          still experimental; may not be supported in future 
uk.co.weft.htform.WithExceptionHandlerServlet.whinge(ServletOutputStream, Exception)
          use whinge(ServletOutputStream,Exception,Context,boolean) 
uk.co.weft.htform.Servlet.whinge(ServletOutputStream, Exception)
          you really, really ought to be passing a context 
uk.co.weft.htform.WithExceptionHandlerServlet.whinge(ServletOutputStream, Exception, Context)
          use whinge(ServletOutputStream,Exception,Context,boolean) 
 

Deprecated Constructors
uk.co.weft.htform.HTMLTextAreaWidget(String, String, String, int, int, boolean)
          dont't use the hardwrap flag, use wrap instead 
uk.co.weft.maybeupload.MaybeUploadRequestWrapper(HttpServletRequest)
          do not use. Not supported. Will be withdrawn soon. If you have any code which uses this class directly, please keep it up to date with maybeupload package. 
uk.co.weft.maybeupload.MaybeUploadRequestWrapper(HttpServletRequest, File, boolean, boolean)
          do not use. Not supported. Will be withdrawn soon. If you have any code which uses this class directly, please keep it up to date with maybeupload package. 
uk.co.weft.htform.ResultFormatter(Contexts, Calendar)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.htform.ResultFormatter(Contexts, Calendar, String, String)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.htform.ResultFormatter(Contexts, Calendar, String, String, String)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.htform.ResultFormatter(ResultSet, Calendar)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.htform.ResultFormatter(ResultSet, Calendar, String, String)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.htform.ResultFormatter(ResultSet, Calendar, String, String, String)
          not thread-safe. Use zero-arg constructor with init(). 
uk.co.weft.substitute.SubstitutionBuffer(File, File, Map)
          the default substitutable start and substitutable end markers have change to the 'at symbol', in line with Apache Ant's default markers. This is because our previous default markers were incompatible with XML. In view of this recent change you are strongly advised to explicitly specify your start and end markers in the mean time. 
uk.co.weft.substitute.SubstitutionBuffer(File, Map)
          the default substitutable start and substitutable end markers have change to the 'at symbol', in line with Apache Ant's default markers. This is because our previous default markers were incompatible with XML. In view of this recent change you are strongly advised to explicitly specify your start and end markers in the mean time. 
uk.co.weft.htform.TextAreaWidget(String, int, int, boolean)
          don't use the 'hardwrap' flag, use wrap instead 
uk.co.weft.htform.TextAreaWidget(String, String, String, int, int, boolean)
          don't use the 'hardwrap' flag, use wrap instead 
uk.co.weft.htform.TextAreaWidget(String, String, String, int, int, boolean, boolean)
          don't use the 'hardwrap' flag, use wrap instead 
uk.co.weft.domutil.TranslatingContextElement(Document, String, Context)
            
uk.co.weft.htform.Widget(Element)
          not expected to work yet 
uk.co.weft.htform.Widget(String, boolean)
          there are too many constructors for widgets, and this one will not be supported in Jacquard 2.0. Use setImmutable( boolean) instead 
uk.co.weft.htform.Widget(String, String, boolean)
          there are too many constructors for widgets, and this one will not be supported in Jacquard 2.0. Use setImmutable( boolean) instead 
uk.co.weft.htform.Widget(String, String, String, boolean)
          there are too many constructors for widgets, and this one will not be supported in Jacquard 2.0. Use setImmutable(boolean) instead 
uk.co.weft.htform.Widget(String, String, String, boolean, int)
          there are too many constructors for widgets, and this one will not be supported in Jacquard 2.0. Use setSize and setImmutable 
 


jacquard 1.10.14 by The Web Engineering Factory and Toolworks