I've seen this happen when multiple versions of the library are being
loaded into memory. CF/Java SHOULD pick the one loaded with the
Javaloader, but doesn't always. I've seen this happen when multiple
versions of POI have been dropped in CF's lib folder as well. When stuff
like this happens, I w
Interesting. Since I'm using the same code on two different systems and getting
the same results - is there any way I can see what is loaded in memory
currently?
-Mike
On Nov 24, 2011, at 7:46 AM, Dawn Hoagland wrote:
> I've seen this happen when multiple versions of the library are being loa
Ajas, here are some thoughts that may help:
The changing port
--
As for the port "changing all the time", that is normal behavior. Adobe
chose to implement things such that the "public" port for the debugger does
change, while the "private" port (specified in the admin, or on
Mike, you can see the classes and libraries loaded within CF using the
“Settings Summary” page of the CF admin, which has two fields: “CF Server Java
Class Path” and “Java Class Path”, each listing all the classes and
jars/libraries. This is quite different from the “java and jvm” page of the
A
I did note in your java loader code that you're loading all of the jars in
that subdirectory. Any chance you have multiple versions of POI there?
Looking over the java docs, try this:
*org.apache.poi.POIXMLProperties.CoreProperties.getRevision()*
On Thu, Nov 24, 2011 at 11:48 AM, Mike Staver
Thanks Charlie and Dawn. I definitely have just one version of poi in that
folder at a time. I typically load up those jars in the onApplicationStart in
the application.cfc. However, in the example I provided I'm doing everything in
one place. I will see what I can find on the java loader forums