Paul Clapham wrote:I remember those forums from 10 or 15 years ago -- you could access them from your e-mail client, you could read the posts and responses which showed up in the natural tree structure in your mail reader, and you could respond to a post in your mail reader, which would result in an e-mail being sent to the forum and showing up in the tree structure for that thread. It had a four-letter acronym which I'm failing to remember right now, but the name "newsgroup" comes into my mind for some reason.
Rob Spoor wrote:javaee-web-api is a subset of javaee-api that has some packages omitted. Although I am surprised to see that for version 6, javax.jms, javax.xml.messaging javax.xml.registry are the only packages present in javaee-api and not in javaee-web-api. The difference is a bit larger in version 7 (where apparently javax.mail and a few other packages have been removed from javaee-web-api).
Ulf Dittmer wrote:Would the point be that you can submit posts via mail? JForum had that capability originally, but we deliberately did not turn it on. (Not that it ever supported singling out forums to my knowledge.)
It's already possible to be notified whenever a new post is made in any particular forum.
K. Tsang wrote:I'm not sure if this is correct. I think for remote JNDI, the lookup code should look like:
Tim Holloway wrote:Annotating an application-scope bean as Singleton is redundant. By definition, there's only one instance of it per application.
The problem here is that although your property is only coded once and for a single user, its get method has side-effects.
JavaBeans in general and specifically JSF backing beans should not have side-effects in their get/set methods. A get method for a property might be invoked 5 or 6 times in the course of a single request/response cycle.
The way around this is to back up the get/set methods by an actual instance variable (property item) and have the get/set methods set or retrieve that variable's value.
For a read-only property such as this one, the backing property variable can be initialized either in a @Postconstruct method or by coding the "get" method to employ the variable as a cached item. That is, on the first call, retrieve the value from the database and set the variable, on subsequent calls just return the variable.