This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/11349] New: JNDI URL context factories not located correctly
- From: "gbenson at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jun 2003 11:54:46 -0000
- Subject: [Bug libgcj/11349] New: JNDI URL context factories not located correctly
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11349
Summary: JNDI URL context factories not located correctly
Product: gcc
Version: 3.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gbenson at redhat dot com
CC: gcc-bugs at gcc dot gnu dot org
In JNDI, you can set the property "java.naming.factory.url.pkgs" (usually
referenced as javax.naming.Context.URL_PKG_PREFIXES) to point to a package that
can create URL context factories. For example, if java.naming.factory.url.pkgs
was set to "com.redhat.foo", then URLs starting in "bar:" would be handled by
contexts created by the class com.redhat.foo.bar.barURLContextFactory.
libgcj is looking in the wrong place for these factories: in the above example
it would look in com.redhat.foo.barURLContextFactory. The attached patch fixes.