commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11479] New: - [discovery] Never instantiates service if not cached?
Date Mon, 05 Aug 2002 19:32:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11479>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11479

[discovery] Never instantiates service if not cached?

           Summary: [discovery] Never instantiates service if not cached?
           Product: Commons
           Version: Nightly Builds
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Sandbox
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: Joe@Germuska.com


I hope I haven't totally missed the boat here, but I just started working with the "commons-
proper" version of "discovery" (which needs to be added as a bugzilla component, btw).

"find" was returning null, although I understood the API to say that it would throw an 
exception if it couldn't find the requested implementation class.  So looking at Discovery,

it seems as if version 1.8 never goes through the process where it instantiates the service

if it doesn't find it in the cache.  This seems like such a low-level problem that I'm afraid

I'm misinterpreting it, but the attached patch (a) works and (b) makes more sense, so I'm

putting it in.  Please set me straight if I'm confused.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message