Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-321
Here is an overview of the issue:
-
I'm not 100% sure I understand the current app client jndi handling,
but my impression is that jndi lookup pulls the read only context back
from the server.
Is there some reason the read-only-context is not packed into the app
client configuration so that no lookup communication to the server
Project: Apache Geronimo
Status: Resolved, Closed (4 items)
Updated In Last: Week (7 days)
** New Feature
* [GERONIMO-292] Add gerneric security realm
** Bug
* [GERONIMO-321] Overwriting web.xml with upgraded in-memory version
** Task
* [GERONIMO-311] Tomcat GBean for starting/stoping
That has already been fixed in the source tree.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Sep 23, 2004, at 2:04 PM, Dondi Imperial wrote:
Hello everyone. I'm new here so please be gentle if I am wrong :). I
think there is a bug in
Hi all,
I was trying to run an application on geronimo. While starting the
server I got the following exception.
java.sql.SQLException: Io exception: JNDI Package
failurejavax.naming.NotContextException: Not an instance of DirContext
at
I committed a partial implementation of the ability to include module
vendor dds directly in a geronimo-application.xml. This seems to work
for connectors but the app-client, jetty, and openejb module builders
aren't updated yet. Dain and I will be working on updating the rest of
these in
