If you use a nightly build, be sure to get the newest, as I fixed a
bug yesterday.

On 11 Feb 2003 at 15:27, [EMAIL PROTECTED] wrote:

>
> Thanks for your answer.
> I was making a mistake, thinking that the compression was a new feature of
> HTTP 1.1. I just need compression, and do not have any interest in HTTP
> 1.1.
> According to your answer, I think that the nightly build is stable enough
> to be used in a production environment.
>
> Thanks,
>
>  Christophe
>
>
>
>
>
> [EMAIL PROTECTED] le 11/02/2003
> 15:19:28
>
> Veuillez répondre à [EMAIL PROTECTED]
>
> Pour : [EMAIL PROTECTED]
> cc :
>
> Objet :     Re: Java 1.4 SLOW
>
>
> Remember that 1.4 includes a copy of Crimson.  If you have been using
> a parser that is much faster, that could be the difference.  You can
> choose the parser that gets used by specifying the
> DocumentBuilderFactory.  Sun's docs for
> DocumentBuilderFactory#newInstance state
>
> >>>>
> Obtain a new instance of a DocumentBuilderFactory. This static method
> creates a new factory instance. This method uses the following
> ordered lookup procedure to determine the DocumentBuilderFactory
> implementation class to load:
>
> Use the javax.xml.parsers.DocumentBuilderFactory system property.
>
> Use the properties file "lib/jaxp.properties" in the JRE directory.
> This configuration file is in standard java.util.Properties format
> and contains the fully qualified name of the implementation class
> with the key being the system property defined above.
>
> Use the Services API (as detailed in the JAR specification), if
> available, to determine the classname. The Services API will look for
> a classname in the file META-
> INF/services/javax.xml.parsers.DocumentBuilderFactory in jars
> available to the runtime.
>
> Platform default DocumentBuilderFactory instance.
> <<<<
>
> On the server, you can specify the parser in web.xml with a parameter
> named XMLParser, the value of which is the class of the
> DocumentBuilderFactory.
>
> On 30 Jan 2003 at 17:57, Luke Galea wrote:
>
> > I am having a strange problem using 2.3.1 (or 2.2 or 2.1 for that
> > matter)..
> > When I run my soap client in 1.4 it is REALLY slow on the invoke
> > call.... The same code in 1.3 takes no more than 30 secs to run a series
> > of 20-30 calls.. In 1.4 it takes 5 minutes..
> >
> > Has anyone had this problem?
> >
> > Luke Galea
> > Software Development
> > BlueCat <http://www.bluecatnetworks.com/>  Networks
> > 905-762-5225
> >
> >
>
>
> Scott Nichol
>
> Do not reply directly to this e-mail address, as it is filtered to
> only receive e-mail from specific mailing lists.
>
>
>
>
>
>
>
>
>
>
>
>
> ----------------
> L'acces immediat aux meilleurs tarifs Air France et au billet electronique sur 
>http://www.airfrance.com
>
> For immediate access to the best Air France fares and to electronic tickets, visit 
>our website http://www.airfrance.com
>
> ----------------
> Les donnees et renseignements contenus dans ce message sont personnels, 
>confidentiels et secrets. Ce message est adresse a l'individu ou l'entite dont les 
>coordonnees figurent ci-dessus. Si vous n'etes pas le bon destinataire, nous vous 
>demandons de ne pas lire, copier, utiliser ou divulguer
cette communication. Nous vous prions de notifier cette erreur a l'expediteur et 
d'effacer immediatement cette communication de votre systeme.
> The information contained in this message is privileged, confidential, and protected 
>from disclosure. This message is intended for the individual or entity adressed 
>herein. If you are not the intended recipient, please do not read, copy, use or 
>disclose this communication to others; also please
notify the sender by replying to this message, and then delete it from your system.
>
>


Scott Nichol

Do not reply directly to this e-mail address, as it is filtered to
only receive e-mail from specific mailing lists.


Reply via email to