Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 26 Members of 3082 |
| Forum: Seam Users |
 |
18. Jul 2008, 16:16 CET | Link |
When Seam is initialized when JBoss starts up and there is a seam.properties file in the resources folder for the WAR/EAR, Seam scans the EAR/WAR for classes marked with the @Name annotation so that they will be available for run-time processing like when they are referenced in JSF EL.
example:
2008-07-18 07:06:18,367 INFO [org.jboss.seam.Component] Component: hotelBooking, scope: CONVERSATION, type: STATEFUL_SESSION_BEAN, class: org.jboss.seam.example.booking.HotelBookingAction, JNDI: jboss-seam-booking/HotelBookingAction/local
So in this case, the hotelBooking component lives
in the conversation context of that particular user session.
In terms of memory allocation, what/where exactly is a context (whether it's session, conversation, page, business process, etc.)? Is it a place in the JVM heap? How can I find out the details of this? thx.
3 Replies: | |||
|---|---|---|---|
All in memory when the Seam lifecycle is active, but back by:
* Session - provided by servlet API, so memory * conversation - stored in session * page - stored in JSF UIViewRoot (so either serialized to the form or in the session) * business process - by jBPM, so persisted via hibernate * application - in memory |
|||
what do you mean when you say Current reading list: Effective Java, 2nd ed.; Java Power Tools; Ubuntu Linux Toolbox |
|||
Current reading list: Effective Java, 2nd ed.; Java Power Tools; Ubuntu Linux Toolbox