Content Holders Not Allowing Text Styling

I'm new to B.C. and am really enjoying the new services I can use. I published my design from Muse to BC and enabled content editing within B.C. however text was not editible within "Site Editor". Support said that this may be because of the way my html conflicted with B.C. so I decided to use content holders. This addresses my needs for the most part however when I publish the site to B.C. many of the text stylings don't display in the live view (though they do display in the design view). The font type, color seem to work however bullets, indents bold talic and a few others do not.
My html isn't exotic at all however I thought this might be the problem. So, just for an experiment I tried a new content holder with just one word that was bolded and sure enough that didn't render as bold either.
Am I missing something or is this a bug?

I just used the visual editor so i suppose its inline styles. I also tried a simple bold tag on a single word and even that did not work

Similar Messages

"Content is not allowed in prolog" with SOAP Attachment

I'm writing an application using SAAJ that sends a soap message to a servlet which responds with some information, including HTML which the client application will display. The HTML has to go into a SOAP attachment so the tags won't get confused with XML.
I had the whole thing working with plain text sending within a normal node, and I only switched a few lines to make that text an attachment with HTML instead, but now I'm getting the exception "Content is not allowed in prolog" on the Client side when it tries to create the envelope from the SOAPMessage.
Code for building answering SOAPMessage with attachment (Servlet to Client)
     public static SOAPMessage buildXML(Message newMessage){
          SOAPMessage msg = null;
          try {
               MessageFactory msgFactory = MessageFactory.newInstance();
               msg = msgFactory.createMessage();
               // Create an envelope in the message
               SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
               msg.setProperty(SOAPMessage.WRITE_XML_DECLARATION, "true");
               msg.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "UTF-8");
               //Get hold of the the body
               SOAPBody body = envelope.getBody();
               SOAPElement soap_message = body.addChildElement("MESSAGE");
               if (newMessage.message_type != null){
                    SOAPElement soap_message_type = soap_message.addChildElement("MESSAGETYPE");
                    soap_message_type.addTextNode(newMessage.message_type);
               if (newMessage.questionID != 0){
                    SOAPElement soap_questionID = soap_message.addChildElement("QUESTIONID");
                    soap_questionID.addTextNode("" + newMessage.questionID);
               if (newMessage.username != null){
                    SOAPElement soap_username = soap_message.addChildElement("USERNAME");
                    soap_username.addTextNode(newMessage.username);
               if (newMessage.password != null){
                    SOAPElement soap_password = soap_message.addChildElement("PASSWORD");
                    soap_password.addTextNode(newMessage.password);
               if (newMessage.message_text != null){
                    AttachmentPart soap_message_text = msg.createAttachmentPart("<html><body>" + newMessage.message_text + "</body></html>", "text/html");
                    soap_message_text.setContentId("MESSAGETEXT");
                    msg.addAttachmentPart(soap_message_text);
                    //SOAPElement soap_message_text = soap_message.addChildElement("MESSAGETEXT");
                    //soap_message_text.addTextNode(newMessage.message_text);
               if (newMessage.sampleString != null){
                    SOAPElement soap_password = soap_message.addChildElement("SAMPLESTRING");
                    soap_password.addTextNode(newMessage.sampleString);
               SOAPElement tmpEl;
               for (int i=0; i<newMessage.numArrayUsed; i++){
                    tmpEl = soap_message.addChildElement("SAMPLEINT");
                    tmpEl.addTextNode("" + newMessage.sampleInt);
               msg.saveChanges();
          } catch (Exception e) {
               e.printStackTrace();
          return msg;
You can see in the area where it adds MESSAGETEXT there are two clients commented out which work. The three lines above it are what changed to make it an attachment instead.
Code in Client for recieving reply from Servlet
SOAPMessage reply = connection.call(soap_msg, endpoint);
System.out.println("\nReceived reply from: " + endpoint);
reply.writeTo(System.out);
System.out.println("");
reply_msg = ProcessXML.parse(reply);This is the console output:
Edit: These forums seem to be inserting an extra > before the <?xml version="1.0" encoding="UTF-8"?> line, but it doesn't exist in the code I'm pasting
Received reply from: http://localhost:8080/kuj/CaseStudyServlet
------=_Part_2_371807.1137465625031
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><MESSAGE><MESSAGETYPE>deliverquestion</MESSAGETYPE><QUESTIONID>1</QUESTIONID><USERNAME>zac</USERNAME></MESSAGE></SOAP-ENV:Body></SOAP-ENV:Envelope>
------=_Part_2_371807.1137465625031
Content-Type: text/html
Content-Id: MESSAGETEXT
<html><body>This is an Array sort Question. You will be given 10 random integers and you must sort and return them in the order of greatest to least.</body></html>
------=_Part_2_371807.1137465625031--
ERROR: 'Content is not allowed in prolog.'
17-Jan-2006 02:40:25 com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
SEVERE: SAAJ0511: Unable to create envelope from given source
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:
     at com.sun.xml.messaging.saaj.soap.EnvelopeFactory.createEnvelope(EnvelopeFactory.java:111)
     at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(SOAPPart1_1Impl.java:39)
     at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:98)
     at com.zacwittedesign.xml.ProcessXML.realParse(ProcessXML.java:32)
     at com.zacwittedesign.xml.ProcessXML.parse(ProcessXML.java:26)
(snip)And this is the beginning of the code for extracting the info from the SOAPMessage on the Client side:
private static Message realParse(SOAPMessage msg){
          Message newMessage = new Message();
          try {
               SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
               SOAPBody body = envelope.getBody();
(snip)It dies on SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
Does anyone know what I'm doing wrong?

I suppose I should also include the bit where the Servlet actually SENDs the resulting SOAPMessage
SOAPMessage msg = ProcessXML.buildXML(outMessage);
// try to send it
try {
     response.setContentType("text/xml");
     msg.writeTo(response.getOutputStream());

Org.xml.sax.SAXParseException: Content is not allowed in prolog Error

Hello,
this is pratap.<br>
i was trying rules using decision tables with 'call charges' example<br>.
after filling the text fields i am getting an error org.xml.sax.SAXParseException: Content is not allowed in prolog<br>.
Can any one please tell me what are the reasons for this error and how to correct it<br>.
thank you.

Problem solved.There was some problem in xml file i corrected it and it worked.Sorry for asking silly question.

[Fatal Error] :1:1: Content is not allowed in prolog.

I'm trying to compare an XML file to an XSLT generated file from that XML file, and when I run the the class as a JUnit Test, I get the following:
[Fatal Error] :1:1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
     at org.custommonkey.xmlunit.XMLUnit.buildDocument(XMLUnit.java:352)
     at org.custommonkey.xmlunit.XMLUnit.buildDocument(XMLUnit.java:339)
     at org.custommonkey.xmlunit.XMLUnit.buildControlDocument(XMLUnit.java:283)
     at org.custommonkey.xmlunit.Diff.<init>(Diff.java:116)
     at org.custommonkey.xmlunit.examples.MyXMLTestCase.testXSLTransformation(MyXMLTestCase.java:70)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at junit.framework.TestCase.runTest(TestCase.java:164)
     at junit.framework.TestCase.runBare(TestCase.java:130)
     at junit.framework.TestResult$1.protect(TestResult.java:106)
     at junit.framework.TestResult.runProtected(TestResult.java:124)
     at junit.framework.TestResult.run(TestResult.java:109)
     at junit.framework.TestCase.run(TestCase.java:120)
     at junit.framework.TestSuite.runTest(TestSuite.java:230)
     at junit.framework.TestSuite.run(TestSuite.java:225)
     at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Any ideas?

In my experience, "Content is not allowed in prolog" usually means your XML file is stored in the UTF-8 encoding with a BOM. Java's UTF-8 Charset doesn't recognize the UTF-8 BOM; it decodes it and passes it along like any other character, then the XML parser chokes on it.
To get rid of the BOM you can open the XML file in a text editor and (depending on the editor) either (1) save the file as UTF-8 without BOM, or (2) switch to hexadecimal and delete the first three bytes (EF, BB, BF).

"Content is not allowed in trailing section" error in JAXP 1.1

Hi All,
I'm trying to write parse XML using JAXP 1.1. I've given input to parser as shown in below code.
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser parser = factory.newSAXParser();
parser.parse(new File(args[0], handler);this worked for me. But I've tried to pass java.io.InputStream reference to the overloaded parse() method of SAXParser class, it throwed the following exception
org.xml.sax.SAXParseException: Content is not allowed in trailing section.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at CMMCompareHelper.main(CMMCompareHelper.java:234)I'm using JAXP 1.1 with J2SE 1..4.2. My requirement is that I get the XML as a String and I've tried to convert it to java.io.ByteArrayInputStream and passed to the SAXParser. It din't work. Code I've written to do this is shown below:
FileInputStream in = new FileInputStream(new File(args[0]));
byte[] buf = new byte[512];
ByteArrayOutputStream byteOut = new ByteArrayOutputStream();
while(in.read(buf) != -1){
    byteOut.write(buf);
InputStream newCMMStream = new ByteArrayInputStream(byteOut.toByteArray());
SAXParser parser = factory.newSAXParser();
parser.parse(newCMMStream, handler);          Am I doing something wrong?
Thanks in advance for any help in this regard.
Satya

Hi Satya,
XML file is suppose to be read as text. Instead of using Byte Streams, use Character Streams or String store
Eventually, the XML data must be processed as text. If it is fed to parser as a binary-stream, parser will try to interpret bytes with default-runtime character-set. This may lead to corruption of data if the bytes are interpreted in incorrect charcter-set (ex UNICODE, ASCII) or were decoded ( UTF-8, UTF-16) incorrectly from file at the first place.
Also, we need to ensure that the character-array/stream being fed does not have any garbage due to overallocation of store (array size). The "Content not allowed in the trailing section" error most probably comes due to this.
If the underlying file to be read is normal ASCII text file, allocating a character array/buffer to the size of the file is good enough. You may also specify UTF-8 as the character-set as UTF-8 subsumes ASCII. Considering the3 file is a simple ASCII text file, here is a code that might provide a valid feed to the parser.
File file = new File(args[0]);
Reader fileReader = new BufferedReader(new FileReader(file));
char[] buffer = new char[file.length()]; \\the length of buffer should be exactly equal to number of bytes in the ASCII text file
fileReader.read(buffer);
CharArrayReader characterStream = new CharArrayReader(xmlstring.toCharArray());
InputSource is = new InputSource(characterStream);
//feed this input source to the parser.
In-case the file is not ASCII and the number bytes != number of characters, you cannot just allocate a character buffer of size file-length. You may have to employ some scheme to allocate just accurate size buffer and read everything into it.. A quick dirty scheme could be
char[] buffer = new char[very-large]; \\the length of buffer should be exactly equal to number of bytes in the ASCII text file
fileReader.read(buffer);
buffer = (new String(buffer).trim()).toCharArray();
Hope this helps !! :)
Regards,
Simar SIngh

[Fatal Error] jstl::1:1: Content is not allowed in prolog.

I use Tomcat 5.5, Eclipse 3.0, JSTL 1.1 and the following jsp doesnt work on my system, it comes the error:
[Fatal Error] jstl::1:1: Content is not allowed in prolog.
farben.jsp:
<%@ page language="java" contentType="text/html" %>
<%@ taglib prefix="c" uri="/WEB-INF/tld/c.tld" %>
<%@ taglib prefix="x" uri="/WEB-INF/tld/x.tld" %>
<%@ taglib uri="/WEB-INF/tld/struts-html.tld" prefix="html" %>
<%@ taglib uri="/WEB-INF/tld/struts-bean.tld" prefix="bean" %>
<%
     System.out.println("farben 0");
     try { String seite = request.getAttribute("seite").toString();
     //String seite = session.getAttribute("seite");
%>
<% if(seite.length() > 0) { %>
     <c:set var="hnr"><%=seite.substring(0,3)%></c:set>
     <% System.out.println("farben 1"); %>
     <c:set var="mnr"><%=seite.substring(3,6)%></c:set>
<% System.out.println("farben 2"); %>
     <c:set var="snr"><%=seite.substring(6,9)%></c:set>
<% System.out.println("farben 3"); %>
     <c:set var="stufe"><%=session.getAttribute("stufeID")%></c:set>
     <% System.out.println("farben 4"); %>
     <c:set var="rolle"><%=session.getAttribute("rolleID")%></c:set>
     <% System.out.println("farben 5"); %>
     <c:import url="/xml/Menue.xml" var="xmlmenue">
     </c:import>
     <% System.out.println("farben 6"); %>
     <x:parse varDom="farben" doc="$(xmlmenue)" />
     <% System.out.println("farben 7"); %>
     <c:set var="name"><x:out select="$farben//hauptmenue[@hnr=$hnr]/@hnr"/></c:set>
     <c:set var="farbe1"><x:out select="$farben//hauptmenue[@hnr=$hnr]/farbe[@nummer='f1']"/></c:set>
     <c:set var="farbe2"><x:out select="$farben//hauptmenue[@hnr=$hnr]/farbe[@nummer='f2']"/></c:set>
     <c:set var="farbe3"><x:out select="$farben//hauptmenue[@hnr=$hnr]/farbe[@nummer='f3']"/></c:set>
#menue , #${name} {
     background-color: ${farbe1};
     color: #ffffff;
.aktiv1 , #untermenue {
     background-color: ${farbe2};
.aktiv2 , #menue a:hover{
     color: #000000;
     background-color: ${farbe3};
     <x:forEach select="$farben//hauptmenue[contains(@stufe,$stufe)and contains(@rolle,$rolle)]">
          .hmenue #<x:out select="@hnr"/>:hover { background-color: <x:out select="farbe[@nummer='f1']"/> }
     </x:forEach>
<%           }
          } catch (Exception ex) {%>
#menue {
     background-color: #ffffff;
<% } %>
if i change <x:parse varDom="farben" doc="$(xmlmenue)" /> in <x:parse varDom="farben" doc="<test>test</test>" /> it works without error, what can i do ?

It may be that your source includes some XML that is escaped during parsing. Try this (it worked for me)
<x:parse varDom="farben" ><c:out value="$(xmlmenue)" escapeXml="false"/></x:parse>c:out is from java.sun.com/jstl/core

Content is not allowed in Prolog error while configuring File to Mail

Hi Expert,
I have a scenario where I have to pick up a file from FTP using sender File adapter and send this file as an attachment using Receiver Mail adapter.
There are 3 requirements :
1) File name of the attachment in the Mail should be same as the File picked from FTP.
2) The Mail content should be "Please find attached the <Filename> for your reference.
i.e The content has to be dynamic
3) Subject of the Mail should be dynamic e.g : Apple_<Filename>
I am facing the following issues :
1. Since single File is picked up,the file is going as an payload and not as an attachment.As a result when i am doing message mapping,i am getting the error saying "Content is not allowed in prolog" in SXMB_MONI or Runtime workbench.
2. Since we have dynamic requirements, i have to Use "Use Mail Package" option.It implies that i have to use Message Mapping.But if i use Message Mapping,i get the error "Content is not allowed in prolog".
I understand that most of the experts would ask me to write UDF's, but if i use UDF i am getting the "Content is not allowed in prolog" error.
Thanks
Saurabh

Hi Saurabh
Try using PayloadSwapBean:
http://help.sap.com/saphelp_nw70/helpdata/en/6b/4493404f673028e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/2e/bf37423cf7ab04e10000000a1550b0/content.htm
"Content is not allowed in prolog" could be caused by some encoding issue.
Regards,
Giuseppe

Org.xml.sax.SAXParseException: Content is not allowed in prolog.

Hi All,
Currently i m doing some practice on JSTL and following few examples from this link http://java.sun.com/developer/technicalArticles/javaserverpages/faster/
while doing xml-ex1.jsp
This is xml-ex1.jsp code
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="x" uri="http://java.sun.com/jstl/xml" %>
<html>
<head>
<title>JSTL Support for XML</title>
</head>
<body bgcolor="#FFFFCC">
<h3>Books Info:</h3>
<c:set var="xmltext">
<books>
<book>
<title>Book Title A</title>
<author>A. B. C.</author>
<price>17.95</price>
</book>
<book>
<title>Book Title B</title>
<author>X. Y. Z.</author>
<price>24.99</price>
</book>
</books>
</c:set>
<x:parse xml="${xmltext}" var="output"/>
<b>The title of the first book is</b>:
<x:out select="$output/books/book[1]/title"/>
<br>
<b>The price of the second book</b>:
<x:out select="$output/books/book[2]/price"/>
</body>
</html>
While running jsp page i m getting follwing error
SEVERE: Servlet.service() for servlet jsp threw exception
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
     at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
     at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseInputSource(ParseSupport.java:227)
     at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseInputSourceWithFilter(ParseSupport.java:193)
     at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseReaderWithFilter(ParseSupport.java:199)
     at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseStringWithFilter(ParseSupport.java:206)
     at org.apache.taglibs.standard.tag.common.xml.ParseSupport.doEndTag(ParseSupport.java:138)
     at org.apache.jsp.jsp.xml_002dex1_jsp._jspx_meth_x_parse_0(org.apache.jsp.jsp.xml_002dex1_jsp:152)
     at org.apache.jsp.jsp.xml_002dex1_jsp._jspService(org.apache.jsp.jsp.xml_002dex1_jsp:70)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at
NOTE :- I m using Tomcat 5.5.14 .
Please help me out how to resolve this problem
Thanks & Regards
Rupesh Kumar

From what I understand, it has nothing to do with your JSP and all to do with the XML it's supposed to parse. It sounds malformed. Check the first tag.

Error: content is not allowed in prolog

I get this error:
Severity Description Resource In Folder Location Creation
Time Id
2 Configuration error encountered on line 2, column 1:
'Content is not allowed in prolog.' FlexWebFluorine August 5, 2007
8:47:24 PM 408
when I create an empty FDS based project in FlexBuilder. Here
are the first two lines of the MXML file:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml">
(Forum mangles that entry but it is the standard one created
by FlexBuilder)
Any ideas?

Are you using any other editor? Some put leading, invisible
characters in the file that cause this message.
Tracy

Trying to create a pdf with jasper - Content is not allowed in prolog

hi all,
Im trying to create a pdf file with jasper reports but i get this error message:
29/11/2007 16:52:03 org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:899)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
     at org.apache.commons.digester.Digester.parse(Digester.java:1666)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.loadXML(JRPrintXmlLoader.java:151)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.load(JRPrintXmlLoader.java:103)
     at net.sf.jasperreports.view.JRViewer.loadReport(JRViewer.java:1376)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:243)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:214)
     at net.sf.jasperreports.view.JasperViewer.<init>(JasperViewer.java:140)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:397)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:328)
     at br.com.abril.contratos.Gerar.geraRelatorio(Gerar.java:38)
     at br.com.abril.contratos.Gerar.main(Gerar.java:47)

cause of the error:
After some extensive research on the web, it is found that that you are using an UTF-8 encoded file with byte-order mark (BOM). Java doesn't handle BOMs on UTF-8 files properly, making the three header bytes appear as being part of the document. UTF-8 files with BOMs are commonly generated by tools such as Window's Notepad. This is a known bug in Java, but it still needs fixing after almost 8 years...
There are some hexadecimal character at the begining of the file, which is giving error"content not allowed in prolog". No solution is provided for this till now.
Example: suppose your file start with <?xml version="1.0" encoding="utf-8"?>. you will see this in a editor. But if you open this file with any hexadecimal editor you will find some junk character in the start of the file.that is causing the problem
solution:
1) convert your file into a string and then read the file from the forst character that in my case the first character will be "<".so the junk character will not be there in the string and then again convert it into a file.
2) some people are able to solve this problem by changing the "utf-8" to "utf-16". remember only in some case. some times this problem also exits in "utf-16" file.
3) some are able to solve this problem by changing the LANG to US.en.
4) If the first three bytes of the file have hexadecimal values EF BB BF then the file contains a BOM.so you can also handle by your own.
5)Download a hexadecimal editor and remove the BOM.
6) In case you are not able to think furthe then please to more research in internet may be you find some other solution to this problem. But These solution are some type of hack not exactly a solution.

Pplsft compIntf adapter: "XML Error: 1:1: Content is not allowed in prolog"

Hi All,
I am using the peoplesoft component interface adapter in IDM 5.5 and IDM 6.0.
I configured the adapter, tested it successfully and enterred the details to create and provision a user to peoplesoft.
But whenever I click on the save button in the end of the creation wizard I get this error:
com.waveset.util.WavesetException: An error occurred adding user 'FX600859' to resource 'PeopleSoft Component Interface'. com.waveset.util.XmlParseException: XML Error: 1:1: Content is not allowed in prolog.I know the prolog is something about the first two lines and BOM and all - but this is like a really fresh install of IDM ( I tried and experienced the same error on both v 5.5 and 6.0) and have checked almost all the files which might be related to the user creation process.......... the error does not say which object has the defective prolog if at all..
I have also enabled trace for a lot of classes (incrementally of course since I failed to get any info from the earlier traces..) Here are the classes/ methods that I have set show trace on:
com.waveset.adapter.ResourceAdapterBase#createAccounts
com.waveset.util.XmlParseException
com.waveset.util.XmlUtil
com.waveset.util.XmlParser
com.waveset.adapter.PeopleSoftCompIntfcAdapter
com.waveset.object.GenericObject
com.waveset.adapter.ResourceAdapterBase
All have a level of 4..... (the most verbose)
here is the trace output:
20060302 15:53:58.286 http-8080-Processor3(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:58.286 http-8080-Processor3(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:58.286 http-8080-Processor3(0x017050f5) ResourceAdapterBase#getFeatures() Info
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Object PUBLIC 'waveset.dtd' 'waveset.dtd'>
<Object>
<Attribute name='account'>
    <Object>
      <Attribute name='CASE_INSENSITIVE_IDS' value='account.CASE_INSENSITIVE_IDS'/>
      <Attribute name='CREATE' value='account.CREATE'/>
      <Attribute name='DELETE' value='account.DELETE'/>
      <Attribute name='DISABLE' value='account.DISABLE'/>
      <Attribute name='ENABLE' value='account.ENABLE'/>
      <Attribute name='EXCLUDE' value='account.EXCLUDE'/>
      <Attribute name='ITERATOR' value='account.ITERATOR'/>
      <Attribute name='LIST' value='account.LIST'/>
      <Attribute name='LOGIN' value='account.LOGIN'/>
      <Attribute name='PASSWORD' value='account.PASSWORD'/>
      <Attribute name='UPDATE' value='account.UPDATE'/>
    </Object>
</Attribute>
</Object>
20060302 15:53:58.286 http-8080-Processor3(0x017050f5) ResourceAdapterBase#getFeatures() Exit returned= { account={ DISABLE=account.DISABLE, DELETE=account.DELETE, CASE_INSENSITIVE_IDS=account.CASE_INSENSITIVE_IDS, UPDATE=account.UPDATE, EXCLUDE=account.EXCLUDE, PASSWORD=account.PASSWORD, ENABLE=account.ENABLE, LIST=account.LIST, LOGIN=account.LOGIN, ITERATOR=account.ITERATOR, CREATE=account.CREATE } }
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getUser() Entry no args
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Entry arg1=user=User:600859
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Exit returned= FX600859
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getUser() Info Getting identity FX600859
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Entry no args
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data host== com.waveset.object.ResourceAttribute@1d6fad7
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data host== chslx07.corp.fedex.com
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getOptionalStringResAttrVal() Data port== 18100
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data User== com.waveset.object.ResourceAttribute@ee5d13
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data User== IBCMGR
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Password== com.waveset.object.ResourceAttribute@1209d56
20060302 15:53:58.286 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Password== 88AF52E54FD71942:549D63D0:1098ECAEC1A:-7FFD|QS8v8QpqGTI=
20060302 15:53:58.396 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Info Successful connection with ISession psft.pt8.joa.Session@30380
20060302 15:53:58.396 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Exit void
20060302 15:53:58.396 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:58.396 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:58.396 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getComponentInterface() Info Fetching compIntfcName 'USER_PROFILE'
20060302 15:53:58.546 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getComponentInterface() Info Successfully got compIntfcName 'USER_PROFILE
20060302 15:53:58.546 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.setProperty {UserID,FX600859}
20060302 15:53:58.546 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: null
20060302 15:53:58.546 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.setProperty
20060302 15:53:58.546 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.invokeMethod {Get, {} }
20060302 15:53:58.656 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: [java.lang.Boolean] = false
20060302 15:53:58.656 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.invokeMethod
20060302 15:53:58.656 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Info Disconnecting from ISession psft.pt8.joa.Session@30380
20060302 15:53:58.656 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getUser() Exit void
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getFeatures() Entry no args
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getFeatures() Info
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Object PUBLIC 'waveset.dtd' 'waveset.dtd'>
<Object>
<Attribute name='account'>
    <Object>
      <Attribute name='CASE_INSENSITIVE_IDS' value='account.CASE_INSENSITIVE_IDS'/>
      <Attribute name='CREATE' value='account.CREATE'/>
      <Attribute name='DELETE' value='account.DELETE'/>
      <Attribute name='DISABLE' value='account.DISABLE'/>
      <Attribute name='ENABLE' value='account.ENABLE'/>
      <Attribute name='EXCLUDE' value='account.EXCLUDE'/>
      <Attribute name='ITERATOR' value='account.ITERATOR'/>
      <Attribute name='LIST' value='account.LIST'/>
      <Attribute name='LOGIN' value='account.LOGIN'/>
      <Attribute name='PASSWORD' value='account.PASSWORD'/>
      <Attribute name='UPDATE' value='account.UPDATE'/>
    </Object>
</Attribute>
</Object>
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getFeatures() Exit returned= { account={ DISABLE=account.DISABLE, DELETE=account.DELETE, CASE_INSENSITIVE_IDS=account.CASE_INSENSITIVE_IDS, UPDATE=account.UPDATE, EXCLUDE=account.EXCLUDE, PASSWORD=account.PASSWORD, ENABLE=account.ENABLE, LIST=account.LIST, LOGIN=account.LOGIN, ITERATOR=account.ITERATOR, CREATE=account.CREATE } }
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#createAccounts() Entry arg1=num users: 1
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#startConnectionWrapper() Entry no args
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Entry no args
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data host== com.waveset.object.ResourceAttribute@1d6fad7
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data host== chslx07.corp.fedex.com
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getOptionalStringResAttrVal() Data port== 18100
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data User== com.waveset.object.ResourceAttribute@ee5d13
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data User== IBCMGR
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Password== com.waveset.object.ResourceAttribute@1209d56
20060302 15:53:58.666 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Password== 88AF52E54FD71942:549D63D0:1098ECAEC1A:-7FFD|QS8v8QpqGTI=
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Info Successful connection with ISession psft.pt8.joa.Session@158473e
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Exit void
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#startConnectionWrapper() Exit void
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#realCreate() Entry no args
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Entry arg1=user=User:600859
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Exit returned= FX600859
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#realCreate() Info Creating identity FX600859
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:58.776 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getComponentInterface() Info Fetching compIntfcName 'USER_PROFILE'
20060302 15:53:58.997 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#getComponentInterface() Info Successfully got compIntfcName 'USER_PROFILE
20060302 15:53:58.997 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.setProperty {UserID,FX600859}
20060302 15:53:58.997 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: null
20060302 15:53:58.997 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.setProperty
20060302 15:53:58.997 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.invokeMethod {Create, {} }
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: [java.lang.Boolean] = true
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.invokeMethod
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#setCIFromWSUSer() Entry arg1=600859
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#setCIFromWSUSer() Info Setting user 'User:600859'
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Entry arg1=user=User:600859
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Exit returned= FX600859
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.setProperty {EmailAddress,[email protected]}
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: null
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.setProperty
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info
Begin JOA method USER_PROFILE.setProperty {SymbolicID,COEDEV}
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info --Returned: null
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#invoke() Info End JOA method USER_PROFILE.setProperty
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttr() Data Read/Write Component Interface Name== com.waveset.object.ResourceAttribute@f2f973
20060302 15:53:59.618 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getRequiredResAttrVal() Data Read/Write Component Interface Name== USER_PROFILE
20060302 15:53:59.628 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#realCreate() Exit void
20060302 15:53:59.628 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Entry arg1=user=User:600859
20060302 15:53:59.628 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#getIdentity() Exit returned= FX600859
20060302 15:53:59.628 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#createAccounts() Info
==> com.waveset.util.WavesetException:
==> com.waveset.util.XmlParseException: XML Error: 1:1: Content is not allowed in prolog.
20060302 15:53:59.638 Provisioning for Configurator(0x017050f5) PeopleSoftCompIntfcAdapter#connect() Info Disconnecting from ISession psft.pt8.joa.Session@158473e
20060302 15:53:59.638 Provisioning for Configurator(0x017050f5) ResourceAdapterBase#createAccounts() Exit voidNow what I see is that the error is generated as an exception in the class/method: ResourceAdapterBase#createAccounts()
but I have not been able to get any deeper than that....
Can someoe please help me in resolving this issue.. or is there someway I can dig deeper.. to maybe understand which file / object is causing the error??
Thanks and best regards,
Anoop

Hi Anoop / Ilayarajan,
Could you please post the solution for this error. When I provision a user to PeopleSoft, I am getting similar error: com.waveset.util.WavesetException: An error occurred adding user "userID' to resource 'PeopleSoft Component Interface'. com.waveset.util.XmlParseException: XML Error: 1:1: Content is not allowed in prolog.
Thanks
User_idm

[Fatal Error] :1:2: Content is not allowed in prolog.

I am trying to parse input stream i amgetting this error please help me
[Fatal Error] :1:2: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
     at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
     at it.Test.DomParserExample.parseXmlFile(DomParserExample.java:90)
     at it.Test.DomParserExample.getParsedXml(DomParserExample.java:50)
     at it.sella.dbu.helper.DaoHelper.parseClobData(DaoHelper.java:28)
     at it.Test.ClobTest.getRequestView(ClobTest.java:122)
     at it.Test.ClobTest.main(ClobTest.java:30)
Exception in thread "main" java.lang.NullPointerException
     at it.Test.DomParserExample.parseDocument(DomParserExample.java:104)
     at it.Test.DomParserExample.getParsedXml(DomParserExample.java:52)
     at it.sella.dbu.helper.DaoHelper.parseClobData(DaoHelper.java:28)
     at it.Test.ClobTest.getRequestView(ClobTest.java:122)
     at it.Test.ClobTest.main(ClobTest.java:30)
Message was edited by:
raj25amigo

Thanks buddy ..it was a malformed XML i missed out a tag

XML loader and UTF-16 - throws Content is not allowed in prolog

Hi,
Our ECC system is updated to unicode system recently. Now the iDoc downloaded from ECC is having a tag <?xml version="1.0" encoding="utf-16"?>.
The XML Loader in the transaction throws an exception "Cannot perform action on XML document Content is not allowed in prolog. Exception: [Content is not allowed in prolog.]". If I change the encoding manually as "utf-8" and executing the transaction, it is working fine.
Please let me know how to solve the issue.
Thanks,
Raman N

Where should I enhance the webservice to make it able to handle zipped XML documents? Shouldn't take the AXIS library take care of this automatically?
This is the web.xml document I use.
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>
NDW2</display-name>
<servlet>
<display-name>
Apache-Axis Servlet</display-name>
<servlet-name>AxisServlet</servlet-name>
<servlet-class>
org.apache.axis.transport.http.AxisServlet</servlet-class>
</servlet>
<servlet>
<display-name>
Axis Admin Servlet</display-name>
<servlet-name>AdminServlet</servlet-name>
<servlet-class>
org.apache.axis.transport.http.AdminServlet</servlet-class>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/servlet/AxisServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>*.jws</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AxisServlet</servlet-name>
<url-pattern>/services/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>AdminServlet</servlet-name>
<url-pattern>/servlet/AdminServlet</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
</web-app>

Sorry, this content is not allowed - absolutely puzzled - how to resolve?

Hi all,
I tried to start a new thread today - put a lot of effort into the question - good
English, code (with tags) tested - basically no problems - forum SQL and PL/SQL
There were absolutely no offensive words, nor indeed could what I wrote
be construed as anyway offensive (in fact I positively acknowledged another
poster's contributions).
When I try to post "jive" (more like "hive" - the kind that itches) refuses
to accept my post and I get the message - "Sorry, this content is not allowed"
I tried to edit bits, move bits around, but to no avail.
What can I do to resolve this issue? Is it common?
Any ideas, references, URL's ideas, whatever appreciated.
Paul...

Billy Verreynne wrote:
There is a list of banned words on OTN to counter spam. A bone of contention
that has been raised and discussed numerous times here.
Do not use sales pitch words - like disc0unt. What about b0nus? Or pr1ce?
Do not use words that refers to articles of clothing like sho3s or j3ans.And if one is writing an app for the garm3nt industry?
Is it a frustration? You betcha. I've complained bitterly about it. But the OTN admins seem
convinced that to counter spam, regular posters and valid postings have to feel the pain. :-(V. annoying - it's not like the volume of traffic is huge... I know that I've been told before that
the current version of hive is not going anywhere - but for the (apparently) vapourware
that is the new forum software could have a "rep" status and obviously those who use
obscenities will be "chaparoned" until they mend their ways...
<rant>
It's a bit sad that the world's second largest s/w company can't have a semi-decent
configurable forum system - it also says much about their attitude to the volunteers
who give of their time and effort on these fora - I've had much more help here than
I've ever got off metalink - or whatever they're calling it these days. Furthermore
it strikes me that it would be a good showcase for Apex - another pet rant is that
the sample apex apps that were available are no longer there, despite the web
site saying that they would appear - and that's a good three years now...
Anyway, another cross to bear...
</rant>
On a more positive note, I've criticised Oracle from time to time and have had
cross words with some fellow posters and have never had a post deleted or
a thread that I started locked.
Anyway, keep up the good work on PL/SQL and SQL and Database-General.
Paul...

Set Content Copying: Not allowed in Adobe forms

We have developed an adobe form, non interactive form, which has scanned signatures, incorporated as images, of authorized personnel.
But we found that these signatures (images) can be copied by standard copy (Ctr+c).
After a brief study we could find out that we need to set the Content Copying as Not allowed, in document properties, as one of the possible solution, but we are unable to do so.
Could you please suggest a way out as to how do we set Content Copying: Not allowed, in the document properties, of the PDF document.

Thank you for your view.
The XML equivalent of the Adobe form, designed, has a tag <PDF security> which has "copy content" set as 1. The possible solution to my problem is to set the copy content to zero or a value which deactivates the copy content. But even though we set the value to zero, the moment we activate the form it reset itself to 1. Could you please elaborate on this one?

Content Holders Not Allowing Text Styling

Similar Messages

Maybe you are looking for