Bug 11349 - JNDI URL context factories not located correctly
Summary: JNDI URL context factories not located correctly
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: libgcj (show other bugs)
Version: 3.3
: P2 normal
Target Milestone: 3.3.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-27 11:54 UTC by Gary Benson
Modified: 2005-07-23 22:49 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Fix (245 bytes, patch)
2003-06-27 11:57 UTC, Gary Benson 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Benson 2003-06-27 11:54:44 UTC 
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.
Comment 1 Gary Benson 2003-06-27 11:57:09 UTC 
Created attachment 4290 [details]
Fix
Comment 2 Tom Tromey 2003-06-30 20:42:24 UTC 
I've put the fix on the trunk, and also into 3.3
and classpath.  thanks