java.lang.Object
mill.forum.Forum
- Direct Known Subclasses:
- SimpleForum
- public abstract class Forum
- extends java.lang.Object
forumURI
public java.lang.String forumURI
month
public int month
year
public int year
id_forum
public long id_forum
id
public long id
isJustEntered
public boolean isJustEntered
jspPage
public mill.port.InitPage jspPage
isDebug
private static boolean isDebug
isProduction
private static boolean isProduction
Forum
public Forum()
Forum
public Forum(javax.servlet.http.HttpServletRequest request,
javax.servlet.http.HttpServletResponse response,
mill.port.InitPage jspPage)
throws ForumException
getNameTable
public abstract java.lang.String getNameTable()
getNameIdSequence
public abstract java.lang.String getNameIdSequence()
getNameThreadSequence
public abstract java.lang.String getNameThreadSequence()
getForumMessage
public abstract ForumMessage getForumMessage(mill.db.DBconnect db__,
long id__)
throws ForumException
dbg
private static void dbg(java.lang.String s)
dbg
private static void dbg(java.lang.String s,
int level)
setCookie
public static void setCookie(javax.servlet.http.HttpServletRequest request,
javax.servlet.http.HttpServletResponse response)
getIdThread
public long getIdThread(long id_main__)
throws ForumException
finalize
protected void finalize()
throws java.lang.Throwable
- Description copied from class:
java.lang.Object
- Called on an object by the Virtual Machine at most once,
at some point after the Object is determined unreachable
but before it is destroyed. You would think that this
means it eventually is called on every Object, but this is
not necessarily the case. If execution terminates
abnormally, garbage collection does not always happen.
Thus you cannot rely on this method to always work.
For finer control over garbage collection, use references
from the
java.lang.ref package.
Virtual Machines are free to not call this method if
they can determine that it does nothing important; for
example, if your class extends Object and overrides
finalize to do simply super.finalize().
finalize() will be called by a java.lang.Thread that has no
locks on any Objects, and may be called concurrently.
There are no guarantees on the order in which multiple
objects are finalized. This means that finalize() is
usually unsuited for performing actions that must be
thread-safe, and that your implementation must be
use defensive programming if it is to always work.
If an Exception is thrown from finalize() during garbage
collection, it will be patently ignored and the Object will
still be destroyed.
It is allowed, although not typical, for user code to call
finalize() directly. User invocation does not affect whether
automatic invocation will occur. It is also permitted,
although not recommended, for a finalize() method to "revive"
an object by making it reachable from normal code again.
Unlike constructors, finalize() does not get called
for an object's superclass unless the implementation
specifically calls super.finalize().
The default implementation does nothing.
getThreads
public java.lang.String getThreads()
throws ForumException
getFirstMonthInYear
public java.lang.Integer getFirstMonthInYear()
throws ForumException
getListYears
public java.lang.String getListYears()
throws ForumException
getListMonths
public java.lang.String getListMonths()
throws ForumException
getMessagesInThread
public java.util.Vector getMessagesInThread()
throws ForumException
getStartMessages
public java.lang.String getStartMessages()
throws ForumException
getCurrentMessage
public ForumMessage getCurrentMessage()
throws ForumException
getMessages
public java.lang.String getMessages(long id__,
long id_thread__,
long curr_level__,
long id_main__)
throws ForumException
addMessage
public long addMessage(javax.servlet.http.HttpServletRequest request,
long id_thread__,
long id_main__)
throws ForumException
- return id of added message
JAVADOC | 
SOURCE | 
DOWNLOAD | NESTED | FIELD | CONSTR | METHOD