[
http://jira.jboss.com/jira/browse/JBSEAM-1846?page=all ]
Gavin King closed JBSEAM-1846.
------------------------------
Resolution: Rejected
Definitely not a bug in Seam. Possibly a bug in EJB3. Log objects are Externalizable, so
their state should be correctly passivated.
Injected Logger is null after component passivation and activation
------------------------------------------------------------------
Key: JBSEAM-1846
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1846
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: Jboss 4.0.5
Suse Linux 10.2
Seam 1.2.1.GA
Reporter: Paul Pantages
Priority: Minor
When a component is passivated, then activated, the Log object is not properly restored;
it is null.
This occurs if the Log is not declared static.
E.g., define:
@Logger
private Log log;
@PrePassivate
public void prePasivate()
{
System.out.println("prePasivate()");
System.out.println("log is " + log );
}
@PostActivate
public void postActive()
{
System.out.println("postActive()");
System.out.println("log is " + log );
}
Let the component passivate, then re-activate. The println from the postActive() method
will show the log is null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira