Adelle Hartley <[EMAIL PROTECTED]> writes:
> I'm looking at porting a library that was written for COM and .Net
> to work as a Python module, and was wondering whether it would be
> better to stick to the library's current naming convention so that
> the API is as similar as possible on each platf
Sorry, I meant to say "did something change" in the first sentence of this
request for help.
>
> Hi,
> Did somebody change in Resin 3.1.7a for mod_caucho.so except what is noted in
> changelog? The same resin.conf works fine for jsp pages with previous
> versions of Resin 3.1 but it looks like
Hi,
Did somebody change in Resin 3.1.7a for mod_caucho.so except what is noted in
changelog? The same resin.conf works fine for jsp pages with previous versions
of Resin 3.1 but it looks like mod_caucho even does not try to connect to Resin
in 3.1.7a and JSP simply outputs source code of the sc
Hi,
we are running Resin-Pro 3.1.7a on a Sun Solaris 10 Box with
successfully compiled JNI Code, but since upgrading from 3.1.6 our log
files are growing with Exceptions like this:
==> debug.log <==
[2008.09.15 18:28:18.328] [WebApp: ] WARNING
(com.caucho.util.ThreadPool) java.lang.Unsatisfied
Scott,
Just taking a quick look at the snapshots, and it seems like the Pro war
file build script seems to be leaving out the javamail jar. I presume
this is because the name changed, since the updated activation.jar is
still there.
The OS version of the zip has the javamail-141.jar in them, bu
Hi Scott,
I need to recompile win32 src to platform AMD64.
Other projects recompiled successfully except project "resin".
Visual Studio generated three errors complaining that
"Java_com_caucho_boot_JniProcess_getMaxFd"
"Java_com_caucho_boot_JniProcess_setMaxFd"
symbols not found.
I double checke
