We're running into similar problems with existing custom java
classes as we move to MX7. *It may be a bug*. It _appears_ that the
MX7 java class loader does not behave as expected - it certainly
behaves differently than in MX6. To reproduce the 500
java/package/name error, try placing your custom java classes in
the WEB-INF/classes directory. This also occurs when you place your
jar file in the WEB-INF/lib directory. If you look at the exception
log, you will see a java.lang.NoClassDefFoundError, which tells me
that the class was not correctly or fully loaded. The class loader
appears to load the class - no ObjectInstantiationException - yet
throws the NoClassDefFoundError exception when invoking _some_
methods. The problem is difficult to isolate because _some_ class
methods work while others do not, throwing the
NoClassDefFoundError.
The workaround I have found so far is to jar up the classes
and place it in the CFusionMX7/lib directory and restart the
server. This is how we have our production servers configured
anyway. This is an obvious problem for development as the
CFusionMX7/lib is not a dynamic class loading directory and any
changes made to classes therein require a server restart to be
effectuated.
In short, and I plan to start another thread, is that
the /WEB-INF/classes and WEB-INF/lib directories do not load
classes as expected in CFMX 7.
Adobe, please correct me if I am missing something.
Thanks,
Bill