pluginDirectory cannot be null
I am running Chainsaw using the supplied batch file, and am getting the dreaded "pluginDirectory cannot be null, yada yada" error message on loading Chainsaw. Here is my setup: C:\bin\chainsaw>dir Volume in drive C has no label. Volume Serial Number is C400-7795 Directory of C:\bin\chainsaw 08/29/2006 04:04 PM . 08/29/2006 04:04 PM .. 03/02/2006 01:49 PM 351 chainsaw.bat 03/02/2006 01:49 PM 361 chainsaw.sh 03/02/2006 01:49 PM71,406 jakarta-oro-2.0.6.jar 03/02/2006 01:49 PM88,173 jmdns.jar 03/02/2006 01:49 PM 356,733 log4j-1.3alpha-7.jar 03/02/2006 01:49 PM 806,086 log4j-chainsaw-2.0alpha-1.jar 03/02/2006 01:49 PM33,080 log4j-optional-1.3alpha-7.jar 03/02/2006 01:49 PM35,028 log4j-oro-1.3alpha-7.jar 03/02/2006 01:49 PM 9,072 log4j-smtp-1.3alpha-7.jar 03/02/2006 01:49 PM22,306 log4j-xml-1.3alpha-7.jar 03/02/2006 01:49 PM 6,022 log4j-zeroconf.jar 03/02/2006 01:49 PM 265,396 xstream-1.1.2.jar 12 File(s) 1,694,014 bytes 2 Dir(s) 46,276,349,952 bytes free C:\bin\chainsaw>chainsaw C:\bin\chainsaw>java -Dorg.apache.commons.logging.Log=org.apache.commons.loggin .impl.Log4JLogger -classpath jakarta-oro-2.0.6.jar;jmdns.jar;log4j-1.3alpha-7.j r;log4j-chainsaw-2.0alpha-1.jar;log4j-optional-1.3alpha-7.jar;log4j-oro-1.3alph -7.jar;log4j-smtp-1.3alpha-7.jar;log4j-xml-1.3alpha-7.jar;log4j-zeroconf.jar;xs ream-1.1.2.jar org.apache.log4j.chainsaw.LogUI Using font=Arial Wanting to add a row, but GUI not initialized, waiting... Writing MRU ->C:\Documents and Settings\bmanica\.chainsaw\mru.xml C:\bin\chainsaw> So everything conceivable seems to be taken care of by the batch file. Here is the configuration file I am using... http://jakarta.apache.org/log4j/"; debug="true"> What am I missing about why this isn't working? -- C. Benson Manica ataru(at)sdf.lonestar.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is it possible to e-mail all logging related to a specific thread?
Hi all, I have to face this problem. I have a product (servlet+webservices)that uses Log4j and I got a new requirement. The system sends a mail when an application exception is thrown, now I'm asked to include all the logging information generated since the servlet started processing the request. There is an further requirement to separate logging info based on the logger name but I suspect that once I found a solution for the first requirement this should be easy to solve. Does anyone knows if is it possible to satisfy such requirement (i.e to grad all logging requests emitted by a thread since a certain date)? My initial thought was to implement a custom appender able to separate thread information (via ThreadLocal for example) and then get the info from this appender to compose the email, but I'm not sure this is the rigth way. Thanks in advance, Giovanni -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to e-mail all logging related to a specific thread?
How much data could that be? On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: Hi all, I have to face this problem. I have a product (servlet+webservices)that uses Log4j and I got a new requirement. The system sends a mail when an application exception is thrown, now I'm asked to include all the logging information generated since the servlet started processing the request. There is an further requirement to separate logging info based on the logger name but I suspect that once I found a solution for the first requirement this should be easy to solve. Does anyone knows if is it possible to satisfy such requirement (i.e to grad all logging requests emitted by a thread since a certain date)? My initial thought was to implement a custom appender able to separate thread information (via ThreadLocal for example) and then get the info from this appender to compose the email, but I'm not sure this is the rigth way. Thanks in advance, Giovanni -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Staufferhttp://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to e-mail all logging related to a specific thread?
I estimate some around 50kb of logging (I took the number extracting a subset of lines from the file containing the logs). The logging info could be cleared as the invocation ends (via an explicit call) and we have about 100 concurrent executions. Thanks, Giovanni How much data could that be? On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: Hi all, I have to face this problem. I have a product (servlet+webservices)that uses Log4j and I got a new requirement. The system sends a mail when an application exception is thrown, now I'm asked to include all the logging information generated since the servlet started processing the request. There is an further requirement to separate logging info based on the logger name but I suspect that once I found a solution for the first requirement this should be easy to solve. Does anyone knows if is it possible to satisfy such requirement (i.e to grad all logging requests emitted by a thread since a certain date)? My initial thought was to implement a custom appender able to separate thread information (via ThreadLocal for example) and then get the info from this appender to compose the email, but I'm not sure this is the rigth way. Thanks in advance, Giovanni -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to e-mail all logging related to a specific thread?
You could maybe make an appender that adds the event to the MDC and then have your email appender include the MDC. Be sure to clear the MDC at the end of the request. That seems like it might be the easiest solution but someone else might have a better idea. On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: I estimate some around 50kb of logging (I took the number extracting a subset of lines from the file containing the logs). The logging info could be cleared as the invocation ends (via an explicit call) and we have about 100 concurrent executions. Thanks, Giovanni > How much data could that be? > > On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: >> Hi all, >> I have to face this problem. I have a product >> (servlet+webservices)that >> uses Log4j and I got a new requirement. The system sends a mail when an >> application exception is thrown, now I'm asked to include all the >> logging information generated since the servlet started processing the >> request. There is an further requirement to separate logging info based >> on the logger name but I suspect that once I found a solution for the >> first requirement this should be easy to solve. >> Does anyone knows if is it possible to satisfy such requirement (i.e to >> grad all logging requests emitted by a thread since a certain date)? >> My initial thought was to implement a custom appender able to separate >> thread information (via ThreadLocal for example) and then get the info >> from this appender to compose the email, but I'm not sure this is the >> rigth way. >> Thanks in advance, >> Giovanni >> -- >> Giovanni Cuccu >> CUP 2000 Spa >> Via del Borgo di S. Pietro, 90/c - 40126 Bologna >> e-mail: [EMAIL PROTECTED] >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Staufferhttp://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JDBCAppender & Sun App Server
I've looked through the archives and haven't really found an answer to my problem. I'm logging to a MySQL database using the JDBCAppender. I've written practically no custom code on top of the log4j module, just a loading and unloading of the configuration, and I'm really not having too many problems with the log4j itself. BTW: I'm using 1.2.13 I think that my Appserver is disconnecting the connection to the database and my guess is that log4j is unable to re-establish the connection. I'm probably just being dense on what I should be doing, but I thought someone else out there might have already experienced this and found a fix for it. Error: Error while cleaning up ManagedConnection javax.resource.ResourceException: The isolation level for this connection could not be retrieved at com.sun.gjc.spi.ManagedConnection.cleanup(ManagedConnection.java: 197) at com.sun.enterprise.resource.AbstractConnectorAllocator.cleanup (AbstractConnectorAllocator.java:82) at com.sun.enterprise.resource.PoolManagerImpl.putbackResourceToPool (PoolManagerImpl.java:349) at com.sun.enterprise.resource.PoolManagerImpl.resourceErrorOccurred (PoolManagerImpl.java:333) at com.sun.enterprise.resource.LocalTxConnectionEventListener.connectionErr orOccurred(LocalTxConnectionEventListener.java:58) at com.sun.gjc.spi.ManagedConnection.connectionErrorOccurred (ManagedConnection.java:588) at com.sun.gjc.spi.ManagedConnectionFactory.matchManagedConnections (ManagedConnectionFactory.java:194) at com.sun.enterprise.resource.AbstractConnectorAllocator.matchConnection (AbstractConnectorAllocator.java:93) at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResour ce(IASNonSharedResourcePool.java:392) at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource (IASNonSharedResourcePool.java:355) at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource (IASNonSharedResourcePool.java:250) at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool (PoolManagerImpl.java:211) at com.sun.enterprise.resource.PoolManagerImpl.getResource (PoolManagerImpl.java:172) at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnectio n(ConnectionManagerImpl.java:258) at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection (ConnectionManagerImpl.java:193) at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection (ConnectionManagerImpl.java:122) at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:70) at com.sun.dashboards.admin.ProductListingModel.getProductListing (ProductListingModel.java:61) at com.sun.dashboards.admin.ProductListingAction.execute (ProductListingAction.java:44) at org.apache.struts.action.RequestProcessor.processActionPerform (RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process (RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java: 1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:747) at javax.servlet.http.HttpServlet.service(HttpServlet.java:860) at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java: 249) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute (SecurityUtil.java:282) at org.apache.catalina.security.SecurityUtil.doAsPrivilege (SecurityUtil.java:165) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:257) at org.apache.catalina.core.ApplicationFilterChain.access$000 (ApplicationFilterChain.java:55) at org.apache.catalina.core.ApplicationFilterChain$1.run (ApplicationFilterChain.java:161) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:263) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:551) at org.apache.catalina.core.StandardContextValve.invokeInternal (StandardContextValve.java:225) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:173) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:551) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:161) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:551) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java: 933) at com.sun
Re: Is it possible to e-mail all logging related to a specific thread?
I do not use an email appender, but a java method.If I correctly understand your proposal I have to write a custom appender anyway ,i.e. standard log4j distribution does not provide a solution for my problem, is it right? Giovanni Cuccu You could maybe make an appender that adds the event to the MDC and then have your email appender include the MDC. Be sure to clear the MDC at the end of the request. That seems like it might be the easiest solution but someone else might have a better idea. -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to e-mail all logging related to a specific thread?
How do you send emails right now? I can't think of a way to do this without writing an appender. I think the SMTPAppender send some of the logs before the error but probably not exactly what you want. On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: I do not use an email appender, but a java method.If I correctly understand your proposal I have to write a custom appender anyway ,i.e. standard log4j distribution does not provide a solution for my problem, is it right? Giovanni Cuccu > You could maybe make an appender that adds the event to the MDC and > then have your email appender include the MDC. Be sure to clear the > MDC at the end of the request. That seems like it might be the > easiest solution but someone else might have a better idea. > -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Staufferhttp://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to e-mail all logging related to a specific thread?
I send mail using a custom class. my code looks like: try { . }catch (Exception e) { String content=//create mail body basing on contxt info and exception Mailer.sendMail(content); } sendMail spawns a thread in order to do an async send. I looked at SMTP appender and it seems that it works accumulating messages in a buffer and then sending the email if a class implementing TriggeringEventEvaluator returns true. If so this a very good point to start since I can reuse the buffer (changing its recycling buffer) and the trigger logic. Thanks a lot, Giovanni How do you send emails right now? I can't think of a way to do this without writing an appender. I think the SMTPAppender send some of the logs before the error but probably not exactly what you want. On 8/30/06, Giovanni Cuccu - CUP2000 <[EMAIL PROTECTED]> wrote: I do not use an email appender, but a java method.If I correctly understand your proposal I have to write a custom appender anyway ,i.e. standard log4j distribution does not provide a solution for my problem, is it right? Giovanni Cuccu > You could maybe make an appender that adds the event to the MDC and > then have your email appender include the MDC. Be sure to clear the > MDC at the end of the request. That seems like it might be the > easiest solution but someone else might have a better idea. > -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Giovanni Cuccu CUP 2000 Spa Via del Borgo di S. Pietro, 90/c - 40126 Bologna e-mail: giovanni.cuccu _at_ cup2000.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fixing pluginDirectory
(I'm trying a different tack on this question, because I feel certain that there is a simple answer to my problem and it is driving me insane.) When I run Chainsaw, I get this error: pluginDirectory cannot be null, and it must exist and must be readable, using the normal Classloader What exactly is the pluginDirectory? How do I set it up? Will the receivers I define in the chainsaw configuration XML work when I do? How can I figure out what value is being used as the pluginDirectory that causes this error? -- C. Benson Manica ataru(at)sdf.lonestar.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Fixing pluginDirectory
Some receivers available via Chainsaw have third party jar dependencies (for example: DBReceiver, CustomSQLDBReceiver, VFSLogFilePatternReceiver). Chainsaw is available via Web Start, and to support those receivers with third party jar dependencies, we needed to provide a mechanism to load those classes. The mechanism we chose was to create a custom classloader which can load classes from any jar in the $user.dir/.chainsaw/plugins directory. To use a receiver with third party jar dependencies: - define the receiver in your Chainsaw config file (see an example from Chainsaw's Welcome tab) - launch Chainsaw - check the 'ok to remove security manager' box in Chainsaw's application-wide preferences screen - point the 'automatic configuration URL' application-wide preference to your Chainsaw config file's URL - exit Chainsaw - copy third party jar dependencies to $user.dir/.chainsaw/plugins - launch Chainsaw Scott -Original Message- From: C. Benson Manica [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 11:12 AM To: log4j-user@logging.apache.org Subject: Fixing pluginDirectory (I'm trying a different tack on this question, because I feel certain that there is a simple answer to my problem and it is driving me insane.) When I run Chainsaw, I get this error: pluginDirectory cannot be null, and it must exist and must be readable, using the normal Classloader What exactly is the pluginDirectory? How do I set it up? Will the receivers I define in the chainsaw configuration XML work when I do? How can I figure out what value is being used as the pluginDirectory that causes this error? -- C. Benson Manica ataru(at)sdf.lonestar.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: pluginDirectory cannot be null
LogFilePatternReceiver can only load regular text log files, not XML-based log files. To load XML-based load files, you can use the 'file-load log4j file' menu, or pull the source for Log4j 1.3, build it and use org.apache.log4j.xml.LogFileXMLReceiver (not yet available from the Web Start distribution - will be available after the next log4j 1.3 alpha release). Scott Deboy Principal Engineer COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -Original Message- From: Christopher Benson-Manica [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 6:33 AM To: log4j-user@logging.apache.org Subject: pluginDirectory cannot be null I am running Chainsaw using the supplied batch file, and am getting the dreaded "pluginDirectory cannot be null, yada yada" error message on loading Chainsaw. Here is my setup: C:\bin\chainsaw>dir Volume in drive C has no label. Volume Serial Number is C400-7795 Directory of C:\bin\chainsaw 08/29/2006 04:04 PM . 08/29/2006 04:04 PM .. 03/02/2006 01:49 PM 351 chainsaw.bat 03/02/2006 01:49 PM 361 chainsaw.sh 03/02/2006 01:49 PM71,406 jakarta-oro-2.0.6.jar 03/02/2006 01:49 PM88,173 jmdns.jar 03/02/2006 01:49 PM 356,733 log4j-1.3alpha-7.jar 03/02/2006 01:49 PM 806,086 log4j-chainsaw-2.0alpha-1.jar 03/02/2006 01:49 PM33,080 log4j-optional-1.3alpha-7.jar 03/02/2006 01:49 PM35,028 log4j-oro-1.3alpha-7.jar 03/02/2006 01:49 PM 9,072 log4j-smtp-1.3alpha-7.jar 03/02/2006 01:49 PM22,306 log4j-xml-1.3alpha-7.jar 03/02/2006 01:49 PM 6,022 log4j-zeroconf.jar 03/02/2006 01:49 PM 265,396 xstream-1.1.2.jar 12 File(s) 1,694,014 bytes 2 Dir(s) 46,276,349,952 bytes free C:\bin\chainsaw>chainsaw C:\bin\chainsaw>java -Dorg.apache.commons.logging.Log=org.apache.commons.loggin .impl.Log4JLogger -classpath jakarta-oro-2.0.6.jar;jmdns.jar;log4j-1.3alpha-7.j r;log4j-chainsaw-2.0alpha-1.jar;log4j-optional-1.3alpha-7.jar;log4j-oro- 1.3alph -7.jar;log4j-smtp-1.3alpha-7.jar;log4j-xml-1.3alpha-7.jar;log4j-zeroconf .jar;xs ream-1.1.2.jar org.apache.log4j.chainsaw.LogUI Using font=Arial Wanting to add a row, but GUI not initialized, waiting... Writing MRU ->C:\Documents and Settings\bmanica\.chainsaw\mru.xml C:\bin\chainsaw> So everything conceivable seems to be taken care of by the batch file. Here is the configuration file I am using... http://jakarta.apache.org/log4j/"; debug="true"> What am I missing about why this isn't working? -- C. Benson Manica ataru(at)sdf.lonestar.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Re: Chainsaw stops receiving events after a while
Sorry, haven't seen that. Socket timeout related? Do you have the same problem with the log4j 1.2.8 version of Chainsaw? -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of BoD Sent: Tuesday, August 29, 2006 1:42 AM To: log4j-user@logging.apache.org Subject: Re: Chainsaw stops receiving events after a while I didn't find a solution yet. Has anybody ever seen the same problem? (Sorry to insist). Thank you for your help! BoD BoD a écrit : > Hi! > > I've been using chainsaw for a few days now, and I'm experiencing a > problem. > After not using my application for a while (+/- 1 hour) chainsaw stops > receiving (or at least it stops displaying) events. If I quit my > application and restarts it, then it starts receiving them again. > > I didn't see any exception in my application saying something about not > being able to log. > > I used to use Lumbermill, an application similar to Chainsaw, and never > had a similar problem. > > Is there any configuration parameter that enables a timeout or something > like that? > > My application uses log4j v1.2.8, could that be the source of the problem? > > Thank you very much for your help! > > BoD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fixing pluginDirectory
On Wed, Aug 30, 2006 at 12:02:31PM -0700, Scott Deboy wrote: > > The mechanism we chose was to create a custom classloader which can load > classes from any jar in the $user.dir/.chainsaw/plugins directory. Ah, I didn't catch until now the existence of that directory. I appreciate you pointing it out, but I find it surprising that the plugins directory isn't created automatically, which would have saved me the effort of hunting for it since I do not actually need that capability. I also think it would be helpful for the non-observant (such as myself) to get some descriptive text concerning the .chainsaw directory on the web page - as it is, it is only mentioned in passing deep within the Distribution notes, where it is easily missed. > - check the 'ok to remove security manager' box in Chainsaw's > application-wide preferences screen If I may ask, why is this step necessary for using third-party plugins? The warning that is popped up when this box is checked makes it clear that it isn't to be checked lightly. -- C. Benson Manica ataru(at)sdf.lonestar.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fixing pluginDirectory
If I may ask, why is this step necessary for using third-party plugins? The warning that is popped up when this box is checked makes it clear that it isn't to be checked lightly. Apache projects are not allowed to ship non-Apache jars as part of a distribution, unless the license for those 3rd party jars is compatible with the ASL, in at least one case for some receiver stuff the license is not compatible. We are forced to ask you to download that yourself, and install it somewhere, in this case, the .plugins directory. To throw a 2nd spanner in the works, Java Web Start classloading rules dictate that only classes loaded from the same classloader that loaded the Webstart app are valid (and need to be signed by the same certificate). The only way around this was to disable the built-in security manager.Since there is a slim possibility of 'rogue' code causing you problems if it was loaded we felt obligated to inform you of the potential problem.The warning is probably written more on the scary side than necessary, but I felt that it would be better to err on the side of caution. If you can suggest some better phrasing, we'll happily consider changing it. You have some valid points about clarity of information (and quantity), which we will take on board. I didn't think the error mentioned about the .plugin directory not being found would be 'fatal' to you, Chainsaw should just keep on trucking (with the caveat that some of the Receiver types wouldn't be available). cheers, Paul Smith smime.p7s Description: S/MIME cryptographic signature