find and solve || findandsolve.com
Please wait.....

Welcome back.






Before Read Terms of use

This XML file does not appear to have any style information associated with it




This XML file does not appear to have any style information associated with it. The document tree is shown below.

In my local computer this is working fine.When i have deveployed in live then this types of issue has been occured.


Answer


Option 1.

Any website want to sitemap file created by Sitemap Automator is called an XML Sitemap file. XML is a way of marking up a file to give the text meaning.Does not appear to have any style information associated means that the XML document can be displayed to you in your web browser with fancy font styling.The XML sitemap file is for search engines only it doesn't want to any types of styling.So as you can see, there is nothing to worry about.

Option 2.

You will get this message in the client side when the client (the web browser) for some reason interprets the HTTP response content representing a HTML document as text/xml instead of text/html and the parsed XML tree doesn't have any XML-stylesheet. In other words, the web browser parsed the retrieved HTTP response content as XML instead of as HTML due to a missing or incorrect HTTP response content type.

In case of JSF/Facelets files which have the default extension of .xhtml, that can in turn happen if the HTTP request hasn't invoked the FacesServlet and thus it wasn't able to parse the Facelets file and generate the desired HTML output based on the XHTML source code. Firefox is then merely guessing the HTTP response content type based on the .xhtml file extension which is in your Firefox configuration apparently by default interpreted as text/xml.

You need to make sure that the HTTP request URL, as you see in browser's address bar, matches the <url-pattern> of the FacesServlet as registered in webapp's web.xml, so that it will be invoked and be able to generate the desired HTML output based on the XHTML source code. If it's for example *.jsf, then you need to open the page by /some.jsf instead of /some.xhtml. Alternatively, you can also just change the <url-pattern> to *.xhtml. This way you never need to fiddle with virtual URLs.

More information stackoverflow

Another link Click here


Sundar  Neupane

Sundar Neupane

I like working on projects with a team that cares about creating beautiful and usable interfaces.

Comments



Report Response