Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>@ViewScoped</code> beans are stored in HTTP session. Any objects which are stored in the HTTP session needs to implement <a href="http://java.sun.com/javase/6/docs/api/java/io/Serializable.html" rel="nofollow noreferrer"><code>Serializable</code></a>. See also <a href="https://stackoverflow.com/questions/4832386/jsf-managed-bean-causing-java-io-notserializableexception-during-tomcat-deployme">JSF managed bean causing java.io.NotSerializableException during Tomcat deployment</a> and <a href="https://stackoverflow.com/questions/2294551/java-io-writeabortedexception-writing-aborted-java-io-notserializableexception">java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException</a>.</p> <p>The <code>NotSerializableException</code> is usually self-explaining since it mentions the full qualified name of the class which needs to be serialized as well, but can't be since it doesn't implement <code>Serializable</code>. </p> <p>However, in this particular case the name seems to indicate an autogenerated class, most likely autogenerated by the EJB container and thus completely out of your control.</p> <p>I've never seen this problem before and Google also doesn't seem to give much about this problem. Based on the stacktrace you're using Glassfish v3, so I'd suggest to post an <a href="https://glassfish.dev.java.net/servlets/ProjectIssues" rel="nofollow noreferrer">issue</a> about that. In the meanwhile your best bet is probably to set the JSF view state saving to the server side instead.</p> <hr> <p><strong>Update</strong>: a similar problem in MyFaces suggests a JSF impl specific issue of using wrong classloader during deserialization. Upgrading the JSF impl should solve the problem: <a href="https://stackoverflow.com/questions/7761622/ejb-in-viewscoped-managedbean-causes-java-io-notserializableexception">@EJB in @ViewScoped @ManagedBean causes java.io.NotSerializableException</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. PO@EJB in @ViewScoped managed bean causes java.io.NotSerializableException
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO@EJB in @ViewScoped managed bean causes java.io.NotSerializableException
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, thank you for your answer, actually the "view-state saving" was set to "CLIENT" I didn't realise that since the web.xml file was automatically generated by the IDE. However I thought "client state saving" was the way to go, but from what I can see if i want to use @ViewScoped managed-beans I need to either change it to "server state saving" or make all my EJB and ManagedBeans implement serializable which I think is a bit complicated....
      singulars
      1. PO
      1. USufasoli
    2. COThere you have the IDE for. To autogenerate code. You only have to understand what the IDE does and how to use it properly :) I'd personally just get rid of the client side state saving. Server memory is cheaper than network bandwidth and the user experience will be more improved when the HTTP data transfer goes faster.
      singulars
      1. PO
      1. USBalusC
    3. COyeah! thank you VERY VERY much, you and your articles have saved me a lot of time once again!
      singulars
      1. PO
      1. USufasoli
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload