Hello, are there any new recommendations to this topic?
Setting Introsepctor.setBeanInfoSearchPath(new String[0]) doesn't help. The BeanSerializer respectively the Introspector still tries to load a BeanInfo for each class. Providing empty BeanInfo-implementations as suggested in the posting below is a painful workaround. Thanks, Thomas Thread taken from the axis-user-mail-archive From "Keith Hatton" <[EMAIL PROTECTED]> Subject RE: Class/resource loading with applet killing performance Date Tue, 24 Aug 2004 08:29:32 GMT Hi Mark, For #3, you can call the following to turn off most of the BeanInfo behaviour. java.beans.Introspector.setBeanInfoSearchPath(new String[0]); Another possibility for #3 and #1 is just to provide empty implementations of the BeanInfo and _Helper classes. This is a pain but I haven't seen any better alternatives. Keep us posted if you find more! Keith -----Original Message----- From: Priest, Mark [mailto:[EMAIL PROTECTED] Sent: 23 August 2004 15:53 To: '[EMAIL PROTECTED]' Subject: Class/resource loading with applet killing performance Hello, We are having an issue with the Axis client that was reported about a year ago. We are using Axis in an applet and we want to minimize the number of things that the class loader is loading since each attempt to load a class or other resource that is not in the jar files we provide causes a GET request to the web server, which burns up a lot of bandwidth. There are three types of things that the Axis runtime is trying to load that are causing us performance problems: 1. _Helper classes. We don't use any _Helper classes but Axis tries to find them anyway 2. ResourceBundle Strings. We don't use logging on the client so we don't care to load the ResourceBundles 3. BeanInfo classes. We don't use any BeanInfo classes and just want the default behavior Is there any way to turn off the Axis runtime features that try to load classes and other resources for the three technologies above? It would significantly improve performance for us if these GET requests could be eliminated. There are about 84 such requests right now, with many duplicate requests for the same resource (see attached access log snippet). I included the message from last year below. Thanks, Mark List: axis-user Subject: non existing Helper class requests! From: Janis_Olekss () exigengroup ! lv Date: 2003-07-24 7:42:23 [Download message RAW] This is a multipart message in MIME format. --=_alternative 002A5549C2256D6D_= Content-Type: text/plain; charset="us-ascii" Hi, I have a "problem"! We have developed application which uses axis SOAP to access Genesys (telephony) statistics and made this as an applet. All the necessary stuff is included into .jar file which is downloaded, initialized and after that applications starts working. BUT (there is allways a catch) We have problem with additional traffic which appears on each applet initialization step when axis starts to seek different Helper classes and some kind of BeanInfo classes. As the classes are not present (ofcourse) in the .jar applet engine sends a ton of requests to server. The requests makes big traffic load and is not acceptable to our customer. We are trying to switch off the Helper class requests, but no success. So may be you could help? The requests looks something like this HTTP: R Port-8080 GET /ica/jars/mycompany/services/session/EventValueTypeType_Helper.class HTTP/1.1 HTTP: R Port-8080 GET /ica/jars/mycompany/services/session/ParameterBeanInfo.class HTTP/1.1 HTTP: R Port-8080 GET /ica/jars/mycompany/services/session/StatisticValueBeanInfo.class HTTP/1.1 abd there are more! Der Austausch von Nachrichten mit o.a. Absender via e-mail dient ausschließlich Informationszwecken. Rechtsgeschäftliche Erklärungen dürfen über dieses Medium nicht ausgetauscht werden. Correspondence with a.m. sender via e-mail is only for information purposes. This medium is not to be used for the exchange of legally-binding communications.
