E
Eric
I have a web application class file that added a static variable from
v1 to v2. Version 2 code is a subset of Version 1 with v2 overwriting
duplicates.
version 1 - The mfr gets set on context initialization via
context.setAttribute("mfr", new ManufacturerClass()).
SessionMgr implements java.io.Serializable
public ManufacturerClass getMfr() {
return
(ManufacturerClass)getHttpSession().getServletContext().getAttribute("mfr");
}
version 2 - The mfr gets set during context initialization via a static
call SessionMgr.setMfr(new ManufacturerClass())
SessionMgr implements java.io.Serializable
private static ManufacturerClass mfr;
public ManufacturerClass getMfr() {
return mfr;
}
Command line javac points to the same javac that Jbuilder points to..
jdk version 1.5.0_06-b05.
When I compile v1 and v2 from command line, I have no compile or
runtime errors.
When I compile v1 and v2 from Jbuilder, I have no compile errors, but
during runtime the first time I try to call SessionMgr.getMfr(), I get
an IncompatibleClassChangeError.
My question is, what does Jbuilder do during compilation to interfere
with ManufacturerClass and/or SessionMgr versus what a command line
compile would do?
v1 to v2. Version 2 code is a subset of Version 1 with v2 overwriting
duplicates.
version 1 - The mfr gets set on context initialization via
context.setAttribute("mfr", new ManufacturerClass()).
SessionMgr implements java.io.Serializable
public ManufacturerClass getMfr() {
return
(ManufacturerClass)getHttpSession().getServletContext().getAttribute("mfr");
}
version 2 - The mfr gets set during context initialization via a static
call SessionMgr.setMfr(new ManufacturerClass())
SessionMgr implements java.io.Serializable
private static ManufacturerClass mfr;
public ManufacturerClass getMfr() {
return mfr;
}
Command line javac points to the same javac that Jbuilder points to..
jdk version 1.5.0_06-b05.
When I compile v1 and v2 from command line, I have no compile or
runtime errors.
When I compile v1 and v2 from Jbuilder, I have no compile errors, but
during runtime the first time I try to call SessionMgr.getMfr(), I get
an IncompatibleClassChangeError.
My question is, what does Jbuilder do during compilation to interfere
with ManufacturerClass and/or SessionMgr versus what a command line
compile would do?