|
DO NOT REPLY [Bug 13600] - Problem with pre-defined java.naming.provid: msg#00219jakarta.avalon.phoenix.devel
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=13600>. 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=13600 Problem with pre-defined java.naming.provider.url donaldp@xxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |LATER ------- Additional Comments From donaldp@xxxxxxxxxx 2002-10-27 08:44 ------- At the moment the MX4J does not create a JNDI nameservice if you don't specify it and doesn't need it if the rmi adaptor is not enabled by default. Thus if you don't need to manage phoenix via RMI then you can just leave those sections commented out. In particular you may want to look at the default configuration defined at http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-avalon-phoenix/src/conf/kernel.xml?rev=1.26&content-type=text/plain which allows the http adaptor but does not enable the RMI adaptor (and thus the RMI name service is not required). |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Block context as shared source of block related information: 00219, Peter Donald |
|---|---|
| Next by Date: | Lifecycle methods - order of calling: 00219, Paul Hammant |
| Previous by Thread: | Re: Excalibur ClassLoader Component in Phoenixi: 00219, Peter Donald |
| Next by Thread: | Re: DO NOT REPLY [Bug 13600] - Problem with pre-defined java.naming.provider.url: 00219, Ulrich Mayring |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |