could you configure public static void writeXml( Node n, OutputStream os ) throws TransformerException of org.apache.tomcat.util.DomUtil to trap TransformerFactoryConfigurationError http://cupi2.uniandes.edu.co/site/images/recursos/javadoc/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html#newTransformer%28javax.xml.transform.Source%29
it seems at minumum one of these conditions to be satisifed to properly newInstance the TransformerFactory ? Use the javax.xml.transform.TransformerFactory 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. The jaxp.properties file is read only once by the JAXP implementation and it's values are then cached for future use. If the file does not exist when the first attempt is made to read from it, no further attempts are made to check for its existence. It is not possible to change the value of any property in jaxp.properties after it has been read for the first time. 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.transform.TransformerFactory in jars available to the runtime. Platform default TransformerFactory instance. ? Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sun, 12 Sep 2010 16:01:26 +0200 > Subject: Re: Host Manager. > From: wesley.ache...@gmail.com > To: users@tomcat.apache.org > > Okay I'm most of the way to a solution but I wouldn't mind if someone > would take a look at a new WIP class and tell me what needs cleaning. > Its not quite functional. > > Anyone interested? > > On Fri, Sep 3, 2010 at 4:44 AM, Wesley Acheson <wesley.ache...@gmail.com> > wrote: > > Looked at that before not really convinced reworking that is easier > > than adding in an xml line or two via an xml writer. > > > > Willing to be convinced though. > > > > Wes > > > > On 9/3/10, Pid <p...@pidster.com> wrote: > >> On 02/09/2010 21:06, Caldarale, Charles R wrote: > >>>> From: Wesley Acheson [mailto:wesley.ache...@gmail.com] > >>>> Subject: Host Manager. > >>> > >>>> Is there is no documentation for the host-manager? > >>> > >>> Very little that I've found. You can learn a bit about it by looking at > >>> its WEB-INF/web.xml file. > >>> > >>>> If I remember correctly from this list it doesn't persist > >>>> its settings is that correct? > >>> > >>> Correct. > >>> > >>>> How many people would be interested in it persisting its > >>>> settings, by editing the appropriate files. > >>> > >>> I would be interested. Note that there's only one file to edit: > >>> conf/server.xml. > >>> > >>>> Is that in theory possible? > >>> > >>> It's all software... > >>> > >>>> to add the folder structure and the appropiate > >>>> context.xml files. > >>> > >>> That's not necessary - the conf/Catalina/[host]/... files are already > >>> created automatically as webapps are deployed under the new <Host>. Only > >>> conf/server.xml needs to be updated. > >>> > >>>> Would it interfere too badly with tomcat while > >>>> it was running? > >>> > >>> No, Tomcat only reads server.xml during startup. Whatever update > >>> mechanism is used must insure that the file is never in an unparsable > >>> state (e.g., don't update in place, instead create a new file and then > >>> rename it). > >> > >> May I gently steer you in the direction of the JMX API and the > >> Catalina:type=Server.Operations.storeConfig() command? > >> > >> Not sure it works very well at the moment, but if it did... > >> > >> p > >> > >>> - Chuck > >>> > >>> > >>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > >>> MATERIAL and is thus for use only by the intended recipient. If you > >>> received this in error, please contact the sender and delete the e-mail > >>> and its attachments from all computers. > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >>> For additional commands, e-mail: users-h...@tomcat.apache.org > >>> > >> > >> > > > > -- > > Sent from my mobile device > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
