Solved

XML parsing/writing to file with DocType

Posted on 2004-04-29
7
1,989 Views
Last Modified: 2013-11-23
Hi Experts,

I am parsing a web.xml document and setting some values then writing the file back to the file system. When I write the document to the file system the DocType remote URL dtd is being resolved and content inserted into the resulting file. All I want is to parse the xml set a couple values and write the xml back to file with the DocType preserved instead of being resolved and content included. Below is my code snipet.

DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(new File(new File(workDirectory, "WEB-INF"), "web.xml"));

//Set a couple values...

// Use a Transformer for output                              
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer();
DOMSource source = new DOMSource(document);
OutputStream out = new BufferedOutputStream(new FileOutputStream(new File(new File  (workDirectory, "WEB-INF"), "web.xml")));
StreamResult result = new StreamResult(out);
transformer.transform(source, result);
out.close();


I have tried to set the TranformerFactory.setURIResolver(null) with no change in the result and am not sure what this is supposed to do. I also used the root document node when constructiong the DOMSource but that just removes the DocType from the resulting xml and I want to maintain the original.

The parser being used is Xerces.

Thanks,

Greg
0
Comment
Question by:greghess
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 7

Expert Comment

by:maheshexp
ID: 10950433
document .getDoctype(); //gives DocType


DocumentType class

http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/DocumentType.html
0
 

Author Comment

by:greghess
ID: 10953727
Thanks for your comment,

My problem is not accessing the DocType node but having the DocType preserved when I write the document to file. What is hapening when I write the document to file is that the DocType is being resolved rather than just included in the xml.

The source xml has the DocType:

<!DOCTYPE web-app
  PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
  "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">

After parsing and writing to file the DocType now looks like:

<!--
Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
Palo Alto, CA  94303, U.S.A.  All rights reserved.
 
This product or document is protected by copyright and distributed
under licenses restricting its use, copying, distribution, and
decompilation.  No part of this product or documentation may be
reproduced in any form by any means without prior written authorization
of Sun and its licensors, if any.  

Third party software, including font technology, is copyrighted and
licensed from Sun suppliers.

Sun, Sun Microsystems, the Sun Logo, Solaris, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
and other countries.

All SPARC trademarks are used under license and are trademarks
or registered trademarks of SPARC International, Inc.
in the U.S. and other countries. Products bearing SPARC
trademarks are based upon an architecture developed by Sun Microsystems, Inc.

PostScript is a registered trademark of Adobe Systems, Inc.

 
Federal Acquisitions: Commercial Software - Government Users Subject to
Standard License Terms and Conditions.


 
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
INVALID.

_________________________________________________________________________
Copyright 1999 Sun Microsystems, Inc.,
901 San Antonio Road, Palo Alto, CA  94303, Etats-Unis.
Tous droits re'serve's.
 

Ce produit ou document est prote'ge' par un copyright et distribue' avec
des licences qui en restreignent l'utilisation, la copie, la distribution,
et la de'compilation.  Aucune partie de ce produit ou de sa documentation
associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
bailleurs de licence, s'il y en a.  

Le logiciel de'tenu par des tiers, et qui comprend la technologie
relative aux polices de caracte`res, est prote'ge' par un copyright
et licencie' par des fournisseurs de Sun.
 
Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,  
sont des marques de fabrique ou des marques de'pose'es de Sun
Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
 
Toutes les marques SPARC sont utilise'es sous licence et sont
des marques de fabrique ou des marques de'pose'es de SPARC
International, Inc. aux Etats-Unis et  dans
d'autres pays. Les produits portant les marques SPARC sont
base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.  

Postcript est une marque enregistre'e d'Adobe Systems Inc.
 
LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
--><!--
The web-app element is the root of the deployment descriptor for
a web application
--><!--
The icon element contains a small-icon and a large-icon element
which specify the location within the web application for a small and
large image used to represent the web application in a GUI tool. At a
minimum, tools must accept GIF and JPEG format images.
--><!--
The small-icon element contains the location within the web
application of a file containing a small (16x16 pixel) icon image.
--><!--
The large-icon element contains the location within the web
application of a file containing a large (32x32 pixel) icon image.
--><!--
The display-name element contains a short name that is intended
to be displayed by GUI tools
--><!--
The description element is used to provide descriptive text about
the parent element.
--><!--
The distributable element, by its presence in a web application
deployment descriptor, indicates that this web application is
programmed appropriately to be deployed into a distributed servlet
container
--><!--
The context-param element contains the declaration of a web
application's servlet context initialization parameters.
--><!--
The param-name element contains the name of a parameter.
--><!--
The param-value element contains the value of a parameter.
--><!--
The servlet element contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup element is
present, then the JSP should be precompiled and loaded.
--><!--
The servlet-name element contains the canonical name of the
servlet.
--><!--
The servlet-class element contains the fully qualified class name
of the servlet.
--><!--
The jsp-file element contains the full path to a JSP file within
the web application.
--><!--
The init-param element contains a name/value pair as an
initialization param of the servlet
--><!--
The load-on-startup element indicates that this servlet should be
loaded on the startup of the web application. The optional contents of
these element must be a positive integer indicating the order in which
the servlet should be loaded. Lower integers are loaded before higher
integers. If no value is specified, or if the value specified is not a
positive integer, the container is free to load it at any time in the
startup sequence.
--><!--
The servlet-mapping element defines a mapping between a servlet
and a url pattern
--><!--
The url-pattern element contains the url pattern of the
mapping. Must follow the rules specified in Section 10 of the Servlet
API Specification.
--><!--
The session-config element defines the session parameters for
this web application.
--><!--
The session-timeout element defines the default session timeout
interval for all sessions created in this web application. The
specified timeout must be expressed in a whole number of minutes.
--><!--
The mime-mapping element defines a mapping between an extension
and a mime type.
--><!--
The extension element contains a string describing an
extension. example: "txt"
--><!--
The mime-type element contains a defined mime type. example:
"text/plain"
--><!--
The welcome-file-list contains an ordered list of welcome files
elements.
--><!--
The welcome-file element contains file name to use as a default
welcome file, such as index.html
--><!--
The taglib element is used to describe a JSP tag library.
--><!--
The taglib-uri element describes a URI, relative to the location
of the web.xml document, identifying a Tag Library used in the Web
Application.
--><!--
the taglib-location element contains the location (as a resource
relative to the root of the web application) where to find the Tag
Libary Description file for the tag library.
--><!--
The error-page element contains a mapping between an error code
or exception type to the path of a resource in the web application
--><!--
The error-code contains an HTTP error code, ex: 404
--><!--
The exception type contains a fully qualified class name of a
Java exception type.
--><!--
The location element contains the location of the resource in the
web application
--><!--
The resource-ref element contains a declaration of a Web
Application's reference to an external resource.
--><!--
The res-ref-name element specifies the name of the resource
factory reference name.
--><!--
The res-type element specifies the (Java class) type of the data
source.
--><!--
The res-auth element indicates whether the application component
code performs resource signon programmatically or whether the
container signs onto the resource based on the principle mapping
information supplied by the deployer. Must be CONTAINER or SERVLET
--><!--
The security-constraint element is used to associate security
constraints with one or more web resource collections
--><!--
The web-resource-collection element is used to identify a subset
of the resources and HTTP methods on those resources within a web
application to which a security constraint applies. If no HTTP methods
are specified, then the security constraint applies to all HTTP
methods.
--><!--
The web-resource-name contains the name of this web resource
collection
--><!--
The http-method contains an HTTP method (GET | POST |...)
--><!--
The user-data-constraint element is used to indicate how data
communicated between the client and container should be protected
--><!--
The transport-guarantee element specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL. NONE means that the application does not require any
transport guarantees. A value of INTEGRAL means that the application
requires that the data sent between the client and server be sent in
such a way that it can't be changed in transit. CONFIDENTIAL means
that the application requires that the data be transmitted in a
fashion that prevents other entities from observing the contents of
the transmission. In most cases, the presence of the INTEGRAL or
CONFIDENTIAL flag will indicate that the use of SSL is required.
--><!--
The auth-constraint element indicates the user roles that should
be permitted access to this resource collection. The role used here
must appear in a security-role-ref element.
--><!--
The role-name element contains the name of a security role.
--><!--
The login-config element is used to configure the authentication
method that should be used, the realm name that should be used for
this application, and the attributes that are needed by the form login
mechanism.
--><!--
The realm name element specifies the realm name to use in HTTP
Basic authorization
--><!--
The form-login-config element specifies the login and error pages
that should be used in form based login. If form based authentication
is not used, these elements are ignored.
--><!--
The form-login-page element defines the location in the web app
where the page that can be used for login can be found
--><!--
The form-error-page element defines the location in the web app
where the error page that is displayed when login is not successful
can be found
--><!--
The auth-method element is used to configure the authentication
mechanism for the web application. As a prerequisite to gaining access
to any web resources which are protected by an authorization
constraint, a user must have authenticated using the configured
mechanism. Legal values for this element are "BASIC", "DIGEST",
"FORM", or "CLIENT-CERT".
--><!--
The security-role element contains the declaration of a security
role which is used in the security-constraints placed on the web
application.
--><!--
The role-name element contains the name of a role. This element
must contain a non-empty string.
--><!--
The role-link element is used to link a security role reference
to a defined security role. The role-link element must contain the
name of one of the security roles defined in the security-role
elements.
--><!--
The env-entry element contains the declaration of an
application's environment entry. This element is required to be
honored on in J2EE compliant servlet containers.
--><!--
The env-entry-name contains the name of an application's
environment entry
--><!--
The env-entry-value element contains the value of an
application's environment entry
--><!--
The env-entry-type element contains the fully qualified Java type
of the environment entry value that is expected by the application
code. The following are the legal values of env-entry-type:
java.lang.Boolean, java.lang.String, java.lang.Integer,
java.lang.Double, java.lang.Float.
--><!--
The ejb-ref element is used to declare a reference to an
enterprise bean.
--><!--
The ejb-ref-name element contains the name of an EJB
reference. This is the JNDI name that the servlet code uses to get a
reference to the enterprise bean.
--><!--
The ejb-ref-type element contains the expected java class type of
the referenced EJB.
--><!--
The ejb-home element contains the fully qualified name of the
EJB's home interface
--><!--
The ejb-remote element contains the fully qualified name of the
EJB's remote interface
--><!--
The ejb-link element is used in the ejb-ref element to specify
that an EJB reference is linked to an EJB in an encompassing Java2
Enterprise Edition (J2EE) application package. The value of the
ejb-link element must be the ejb-name of and EJB in the J2EE
application package.
--><!--
The ID mechanism is to allow tools to easily make tool-specific
references to the elements of the deployment descriptor. This allows
tools that produce additional deployment information (i.e information
beyond the standard deployment descriptor information) to store the
non-standard information in a separate file, and easily refer from
these tools-specific files to the information in the standard web-app
deployment descriptor.
-->

I believe that the transformer is fetching the dtd and putting the content(not sure why it is only the comments) into the file.

I want the original DocType to be preserved.

Thanks,

Greg
0
 
LVL 7

Expert Comment

by:maheshexp
ID: 10957114
document .getDoctype(); give the doctype of the ur original document, preserve or store it somewhere, and then write the DocType seperately when u write back your new XML file
0
[Live Webinar] The Cloud Skills Gap

As Cloud technologies come of age, business leaders grapple with the impact it has on their team's skills and the gap associated with the use of a cloud platform.

Join experts from 451 Research and Concerto Cloud Services on July 27th where we will examine fact and fiction.

 

Author Comment

by:greghess
ID: 10959956
Thanks for you comments,

Ok, I am with you, I really need a code sample. I am not sure how to implement that strategy.

Cheers,

Greg
0
 
LVL 7

Accepted Solution

by:
maheshexp earned 250 total points
ID: 10960853
0
 

Author Comment

by:greghess
ID: 10962791
Thanks that was what I was looking for :-).

Unfortunatly the problem I was trying to solve is related to the parsing of the document. Accepted answer. Please check my next question maybe you can help.

Cheers,

Greg
0
 
LVL 7

Expert Comment

by:maheshexp
ID: 10965242
thanks... :-)
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Go is an acronym of golang, is a programming language developed Google in 2007. Go is a new language that is mostly in the C family, with significant input from Pascal/Modula/Oberon family. Hence Go arisen as low-level language with fast compilation…
Introduction Since I wrote the original article about Handling Date and Time in PHP and MySQL several years ago, it seemed like now was a good time to update it for object-oriented PHP.  This article does that, replacing as much as possible the pr…
This video teaches viewers about errors in exception handling.
Video by: Mark
This lesson goes over how to construct ordered and unordered lists and how to create hyperlinks.
Suggested Courses

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question