CONTENT NOT ALLOWED IN PROLONG

HI,
I AM doing simple file2file senario in SXMB_MONI its showing redflag and i tested the source code in testing its showing the following error
CONTENT NOT ALLOWED IN PROLONG
Regards,
Prasad

Hi Prasad,
It seems that your input payload is not correct. Take the input payload and test it in Message mapping. Check What error you are getting there. Also in test tab of message put manually the data your are getting in input payload. Check if it execute successfully. If yes then problem is with the input payload. If not then issue with data.

Similar Messages

How to resolve Content not allowed in prolog with PDF files

We are using PI 7.1 to read a file and using ASMA get the file name and pass it to a target mapping and call a web service with the file name.
We have a scenario that reads a PDF file as Binary form a folder. Our mapper uses ASMA to get the file name and folder of the
file to map to the target.
Testing in mapper works fine except for the ASMA does not function (known issue).
At runtime we drop a file and it is picked up as expected BUT from SXMB_MONI we see the following:
Runtime exception occurred during application mapping com/sap/xi/tf/_MM_FileNotification_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.
This error does not happen all the time either. When it appears it is typically only the first time a file is mapped and on subsequent retries it processes normally. In dev we have shown that PI seems to get stuck on a few initial files u2013 process properly on the first retry and then at some point has no issues and will process files very fast.
u201CContent not allowed in prologu201D at least from an XML perspective is related to characters appearing before the xml file declaration:
<?xml version="1.0".encoding="UTF-8"?>
If chars appear before this you get this error in Java parsers. This could be related but we do not have control over how PI parsed the file content and puts into XML messages inside the mapper as we do nothing with the file content.
The same file will go through randomly with this exception on multiple drops. Sometimes it gets processed properly and sometime it doesnu2019t u2013 but in dev it u201Calwaysu201D gets processed properly on the automatic retry. It does not seem to matter what PDF we drop in there either.
Our tyoes look something like this:
Source:
DT_FILE - xsd:hexBinary
Target:
FilePath - xsd:String
I have tried with DT_FILE as xsd:base64Binary with the same results...
We use a UDF to get the file name from ASMA as follows:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");
String ourSourceFileName = conf.get(key1);
String ourSourceDirName = conf.get(key2);
//conf.put(key1, ourSourceDirName + "/" + ourSourceFileName);
return ourSourceDirName + "
ToProcess
" + ourSourceFileName;
Edited by: Carey Bingham on May 26, 2010 12:24 AM

> Is using a custom adapter module the standard way to handle files when we do not want the content?
I would rather say this is a feasible solution
> If so does anyone have generic code that we can use for the purposes of simply monitoring a file and passing the file name/folder out implemented as modules already?
The questio is. What do you want to do with this information?
Here is a sample code written for a specific purpose, you can adapt this to your needs:
http://wiki.sdn.sap.com/wiki/display/XI/AdapterModulePI7.0SetAttachmentName
> Is this a known workaround to get around the "content not allowed in prolog" issue?
At least it is known by me

I am getting the following error: Unable to authenticate the package: B_SPACE_NUTRITION.itmsp ERROR ITMS-9000: "OPS/ibooks.ncx(5): element "content" not allowed yet; missing required element "navLabel"" at Book (MZItmspBookPackage)

I am getting the following error when attempting to deliver my iBooks Author book package via iTunes Producer: "
Unable to authenticate the package: B_SPACE_NUTRITION.itmsp
ERROR ITMS-9000: "OPS/ibooks.ncx(5): element "content" not allowed yet; missing required element "navLabel"" at Book (MZItmspBookPackage)"
I understand that there's something wrong with the TOC file (.ncx), but I have tried everything and nothing seems to work. Every section of the TOC is labeled, so not sure why the navLabel issue is happenening.
Any help is GREATLY appreciated! Thank you.

Similar issues looks like. Are you using a template other than those in iBooks Author? That's what I did, and that was definitely part of the issue.
After digging through .ibooks code for hours and still not seeing the problem, I decided to reach out to one of the Apple epub conversion affiliates in iTunes Connect. They said they could repair the file without a problem, started working on it, only to come back a week later and say they couldn't work on .ibooks or .iba files yet.
So, in complete frustration, I decided to transfer my content page by page from the blank template I downloaded from a vendor online to one of the "textbook" templates in IBA. This was a long process as I had to unlock and clear out the formatting of the template. But, once that was done and content was transferred over, all was good. I submitted/delivered the same content and preview book within the new template and it went right through the first time (all metadata was exactly the same as well).
Now, the iBookstore approval waiting process begins!
Good luck!

Org.xml.sax error content not allowed in prolog

Hi,
I am running Jetty 6.x on SUSE and there is a webapp called pyjasper i am trying to run on it. the context maps fine and it displays the content however, when i use the applet in the webapp to create a report (.jasper) it gives me a org.xml.sax Parse exception: content not allowed in prolog.
A little part of the error is pasted below:
generating report /tmp/pyJasper/compiled-reports/6390c37d0ea810c7fae3e647c2f86817.jasper
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:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.commons.digester.Digester.parse(Digester.java:1647)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:239)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:226)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:214)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
2010-03-04 09:15:59.073::WARN: /pyJasper/jasper.py
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:243)
at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:226)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:214)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:168)
at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:152)
at net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
I am guessing this is some sort of an error in xml parsing. I found couple of solutions on sun java forums but none of them worked for me. Right now I am trying to figure out whether this is being caused by the applet or the java itself.
Apparently other people who use this applet do not have a problem and they have the exact same files as me. So I am not sure what exactly is causing tihs problem. Bit of a noob.
Any help would be greatly appreciated.
THANK YOU VERY MUCH!!!! :)

Hi thanks you very much for the reply.
In my message I forgot to mention that I edited my prologs to "<?xml version = "1.0" encoding = "UTF-8"?>" and the jetty.xml that has the server configuration has:
<?xml version = "1.0" encoding = "UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
I apologize for the clarity of my message. I meant to say that I was wondering whether the problem is with the xm files that java has, or the xml files that are in the pyjasper package that I downloaded?
I also checked for byte order mark using hex editor to see if those six characters were in front of my xml files. None of the files in the pyjasper package had the BOM so that solution did not work.
Is there something wrong with the above xml prolog?
I have been reading tons of different posts and stuf trying to figure this out for the past month but juts cannot seem to get it to work.
Thanks.

Anyone know how to fix this error: RROR ITMS-9000: "OPS/ibooks.ncx(5): element "content" not allowed yet

Trying to publish an iBook and having major problems at the last step. Here is my error message:
Apple's web service operation was not successful
Unable to authenticate the package: B_SPACE_NUTRITION.itmsp
ERROR ITMS-9000: "OPS/ibooks.ncx(5): element "content" not allowed yet; missing required element "navLabel"" at Book (MZItmspBookPackage)
Any advice???

Similar issues looks like. Are you using a template other than those in iBooks Author? That's what I did, and that was definitely part of the issue.
After digging through .ibooks code for hours and still not seeing the problem, I decided to reach out to one of the Apple epub conversion affiliates in iTunes Connect. They said they could repair the file without a problem, started working on it, only to come back a week later and say they couldn't work on .ibooks or .iba files yet.
So, in complete frustration, I decided to transfer my content page by page from the blank template I downloaded from a vendor online to one of the "textbook" templates in IBA. This was a long process as I had to unlock and clear out the formatting of the template. But, once that was done and content was transferred over, all was good. I submitted/delivered the same content and preview book within the new template and it went right through the first time (all metadata was exactly the same as well).
Now, the iBookstore approval waiting process begins!
Good luck!

Content not allowed problems

On posting a reply to this thread ...
which study guides are good for 10g oca?
Yes this thread
which study guides are good for 10g oca?
I seemed to get a lot of content not allowed unless I split to several posts.
Evidently it is a not that I am restricted to one hyperlink per post ( I thoight it might be that)
Anyone any thoughts ... or am I just having a crazy moment?

user999999 wrote:
is there a link where they are compared? last time I used ucertify, but I was disappointed, as in ucertify I was scoring around 95% whereas in the real exam I just about passed.The Oracle Approved Practice Test supplier (Kaplan IT) is here: [http://www.oracle.com/global/us/education/certification/sts.html]
Transcender and Selftestsoftware may use some or even a lot of the same material .... Basically you pay a bit more for Transcender compared to Selftestsoftware and you get a little more.
I have never used them myself but understand them to be of good quality.
see: [http://blogs.oracle.com/certification/2009/12/0099.html]
A lot of practice test suppliers source back to the same dodgy material and should be avoided ... see http://blogs.oracle.com/certification/2009/05/the_route_you_choose.html
Ucertify is certainly regarded by http://www.certguard.com as a legitimate supplier (ucertify.com = SAFE ... checked at tiem of post), and they sometimes offer exams the official suppliers do not. Several comments I have seen indicate SOME of their material is not of the highest quality and may not stress you as much as the real exam. That said they appear to taking trouble to produce original material and get exams quickly to market, and seem to price competively when necessary. They may well be trying to improve there precieved quality issues in the marketplace.
( I apologise for many splits in this reply ... I have had a lot of content not allowed).
Edited by: bigdelboy on 12-Jan-2010 03:49 As one can see ... I have managed to integrate the messages I have used previously and managed to post them to this forum. I did have a few network issues at the time of the last post so perhaps that was it .... perhaps I am gong a insane after all. I don't believe I had removed anything significant. But perhaps I am wrong.

Problem with Exception - "Content not allowed in Prolog"

I was using org.w3c.dom package to handle all my XML data in JDK 1.4.1 environment. Recently, I have upgraded my Java version to JDK 1.5. When I run my code, while parsing the XML data, it is throwing an Exception - "Content not allowed in Prolog". I know that this Exception is because the XML data does not contain xml declaration in prolog.
But, I have the code that queries the database and builds the records in XML format. The sample XML is as follows.
<list>
<row>
<fld1>Val1</fld1>
<fld2>Val2</fld2>
</row>
<row>
<fld1>Val3</fld1>
<fld2>Val4</fld2>
</row>
</list>
I want to know why the JVM is validating for XML declaration? Why can't it continue parsing the XML in case it is well formed? Is there any way so that I can skip this validation?
Please reply. I am in a big trouble because, in case some changes are required, I need to implement in many places of my API.

The isELIgnored flag just fixes this page.
If you want to use EL on your pages a better solution is to update your web.xml file:
EL Expressions in JSP2.0 containers:
In order to evaluate EL expressions, your web.xml file must be up to date.
If web.xml states that it is version 2.3 or less, then EL evaluation is disabled by default for backwards compatibility.
So if your web.xml starts with this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>Replace it with this
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app 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"
version="2.4">
Cheers,
evnafets

Note : Content Not Allowed Message

I am trying to post a message regarding a problem I have with windows 7 and Reports builder dates formats. I keep getting "content not allowed"?????

Thanks for the encouragement to persevere . . .
the culprit was:
f<colon>facetapparently an eff cannot appear alone or followed by a colon
Edited by: lili5059 on Feb 27, 2011 2:40 PM

Content not allowed in prologue

Anyone ever have this problem? WebLogic 8.1. Tried using latest xalan/xerces.
Also Saxon. Seems like the xml reader is broken.
The files I'm using for xml/xsl are trivial, and work in both xmlspy and saxon.
None of the fixes work so far(check for whitespace or extraneous characters
etc).
Here's the exceptions, followed by the test case. Thanks in advance.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.jav
a:349)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
l.java:630)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXPar
ser.java:1189)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.jav
a:349)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
l.java:630)
Here is a sample xml.xslt, followed by the java code to invoke it:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes"/>
<xsl:param name="someparam">futureParameter</xsl:param>
<xsl:template match="/wermdoc">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="reqlines">
<table width="100%" border="1" cellspacing="0" cellpadding="0">
<tr bgcolor="#44FF44">
<td>Type</td>
<td>Status</td>
<td>Dept ID</td>
<td>Acct</td>
<td>Name</td>
<td>Item ID</td>
<td>Description</td>
<td>Qty</td>
<td>UOM</td>
<td>Price</td>
<td>Ext. Net Price</td>
<td>Due Date</td>
</tr>
<xsl:apply-templates/>
</table>
</xsl:template>
<xsl:template match="reqline">
<tr>
<xsl:apply-templates/>
</tr>
</xsl:template>
<xsl:template match="text()">
<td>
<xsl:value-of select="." />
</td>
</xsl:template>
</xsl:stylesheet>
<?xml version="1.0" encoding="UTF-8"?>
<wermdoc>
<reqlines>
<reqline>
<h_req_type>PO</h_req_type>
<req_status>C</req_status>
<deptid>003072</deptid>
<account>50221</account>
<name1>A A OFFICE EQUIPMENT CO INC</name1>
<h_itm_id_inv_id>1</h_itm_id_inv_id>
<itm_descr>1</itm_descr>
<qty_req>1</qty_req>
<unit_of_measure>EA</unit_of_measure>
<price_req>1</price_req>
<extended_net_price>1</extended_net_price>
<due_dt>2003-08-26 00:00:00.0</due_dt>
</reqline>
</reqlines>
</wermdoc>
String stylesheet = request.getParameter("XS");
String requestDoc = request.getParameter("DOC");
String resultDoc = "NO INPUT";
if ( stylesheet != null && requestDoc != null ) {
try {
// System.setProperty("javax.xml.transform.TransformerFactory",
// "com.icl.saxon.TransformerFactoryImpl");
// System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
// "com.icl.saxon.om.DocumentBuilderFactoryImpl");
StringWriter swriter = new StringWriter();
Transformer trans;
TransformerFactory factory = TransformerFactory.newInstance();
DocumentBuilderFactory dfactory =
DocumentBuilderFactory.newInstance();
dfactory.setNamespaceAware(true);
DocumentBuilder docBuilder = dfactory.newDocumentBuilder();
Document doc = docBuilder.parse(new File(stylesheet));
trans =
factory.newTransformer(new StreamSource(new File(stylesheet)));
trans.transform(
new StreamSource(new StringReader(requestDoc)),
new StreamResult(swriter));
resultDoc = swriter.toString();
} catch (Exception e) {
e.printStackTrace(System.out);
end of message.

Thanks Bruce! Saved the code to a project.
Put another way the problem was this:
"trans.transform(new StreamSource(new StringReader(requestDoc))"
Should've been simply "trans.transform(new StreamSource(requestDoc)".
My confusion was introduced through cut-n-paste and of course StringReader
doesn't care if what it reads is simply a filename rather than the contents
of the file. That wouldn't have happened with your code...
Bruce Stephens <[email protected]> wrote:
>
Hi Rich,
It seems to me that encoding has always been java's Achilles heel :-)
Try the attached code and see if it works for you.
Thanks,
Bruce
Rich Kucera wrote:
Anyone ever have this problem? WebLogic 8.1. Tried using latestxalan/xerces.
Also Saxon. Seems like the xml reader is broken.
The files I'm using for xml/xsl are trivial, and work in both xmlspyand saxon.
None of the fixes work so far(check for whitespace or extraneouscharacters
etc).
Here's the exceptions, followed by the test case. Thanks in advance.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.jav
a:349)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
l.java:630)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXPar
ser.java:1189)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.jav
a:349)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
l.java:630)
Here is a sample xml.xslt, followed by the java code to invoke it:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes"/>
<xsl:param name="someparam">futureParameter</xsl:param>
<xsl:template match="/wermdoc">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="reqlines">
<table width="100%" border="1" cellspacing="0" cellpadding="0">
<tr bgcolor="#44FF44">
<td>Type</td>
<td>Status</td>
<td>Dept ID</td>
<td>Acct</td>
<td>Name</td>
<td>Item ID</td>
<td>Description</td>
<td>Qty</td>
<td>UOM</td>
<td>Price</td>
<td>Ext. Net Price</td>
<td>Due Date</td>
</tr>
<xsl:apply-templates/>
</table>
>> </xsl:template>
<xsl:template match="reqline">
<tr>
<xsl:apply-templates/>
</tr>
</xsl:template>
<xsl:template match="text()">
<td>
<xsl:value-of select="." />
</td>
</xsl:template>
</xsl:stylesheet>
<?xml version="1.0" encoding="UTF-8"?>
<wermdoc>
<reqlines>
<reqline>
<h_req_type>PO</h_req_type>
<req_status>C</req_status>
<deptid>003072</deptid>
<account>50221</account>
<name1>A A OFFICE EQUIPMENT CO INC</name1>
<h_itm_id_inv_id>1</h_itm_id_inv_id>
<itm_descr>1</itm_descr>
<qty_req>1</qty_req>
<unit_of_measure>EA</unit_of_measure>
<price_req>1</price_req>
<extended_net_price>1</extended_net_price>
<due_dt>2003-08-26 00:00:00.0</due_dt>
</reqline>
</reqlines>
</wermdoc>
String stylesheet = request.getParameter("XS");
String requestDoc = request.getParameter("DOC");
String resultDoc = "NO INPUT";
if ( stylesheet != null && requestDoc != null ) {
try {
// System.setProperty("javax.xml.transform.TransformerFactory",
// "com.icl.saxon.TransformerFactoryImpl");
// System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
// "com.icl.saxon.om.DocumentBuilderFactoryImpl");
StringWriter swriter = new StringWriter();
Transformer trans;
TransformerFactory factory = TransformerFactory.newInstance();
DocumentBuilderFactory dfactory =
DocumentBuilderFactory.newInstance();
dfactory.setNamespaceAware(true);
DocumentBuilder docBuilder = dfactory.newDocumentBuilder();
Document doc = docBuilder.parse(new File(stylesheet));
trans =
factory.newTransformer(new StreamSource(new File(stylesheet)));
trans.transform(
new StreamSource(new StringReader(requestDoc)),
new StreamResult(swriter));
resultDoc = swriter.toString();
} catch (Exception e) {
e.printStackTrace(System.out);
end of message.import java.io.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.*;
public class testcode {
public static void main(String[] args) throws Exception {
try {
FileInputStream fis = new FileInputStream( "theData.xml" );
InputStreamReader ir = new InputStreamReader(fis , "UTF-8");
BufferedReader br = new BufferedReader(ir);
Source source = new javax.xml.transform.stream.StreamSource( br );
StringWriter swriter = new StringWriter();
Transformer trans;
TransformerFactory factory = TransformerFactory.newInstance();
trans = factory.newTransformer(new StreamSource(new File("stylesheet.xslt")));
trans.transform( source, new StreamResult(swriter));
String resultDoc = swriter.toString();
System.out.println("OK: " + resultDoc);
} catch (Exception e) {
e.printStackTrace(System.out);

Content not allowed?

First time posting in the Compressor forum. Or trying to anyway. I have a very basic question, but the system is not allowing me to post it, saying I have included content in my post that is not permitted. This is not helpful.
What content would that be? I'm not using explicatives.

Nice workaround.
Did you complete the entries in the Job Action pane?
BTW, try not to take the "censor" personally; it's merely an algorithm making all these calls…and missed calls. Agree it's very aggravating not to be able to reach a live person to over-ride the software.
Russ

"Content not allowed in Prolog" XML error while using RemoteSession API

Hi,
I am trying to create a view by using a RemoteSession object CREATED on the RPC URL of Sun Identity Manager. Here is the code I am trying out.
try
URL url = new URL ("http","localhost",8080,"/idm/servlet/rpcrouter2");
System.out.println (url.toString());
RemoteSession _remoteSession = new RemoteSession
(url,Constants.CONFIGURATOR, new EncryptedData
("configurator"));
System.out.println ("Remote session is "+_remoteSession);
GenericObject view = _remoteSession.createView ("Role",null);
System.out.println ("View is "+view);
catch (MalformedURLException male){
     male.printStackTrace ();
catch (WavesetException wes){
     wes.printStackTrace ();
catch (Exception e){
     e.printStackTrace ();
When this line is called,
GenericObject view = _remoteSession.createView ("Role",null);
The code throws the following exception.
[java] http://localhost:8080/idm/servlet/rpcrouter2
[java] Remote session is com.waveset.session.RemoteSession@1cbda0a
[java] com.waveset.util.XmlParseException: XML Error: 1:1: Content is not a
llowed in prolog.
[java] at com.waveset.util.XmlParser.wrapException(XmlParser.java:886)
[java] at com.waveset.util.XmlParser.parseString(XmlParser.java:519)
[java] at com.waveset.util.XmlUtil.parseString(XmlUtil.java:440)
[java] at com.waveset.session.RemoteSession.getResultObject(RemoteSessi
on.java:1028)
[java] at com.waveset.session.RemoteSession.rpc(RemoteSession.java:995)
[java] at com.waveset.session.RemoteSession.callx(RemoteSession.java:92
3)
[java] at com.waveset.session.RemoteSession.call(RemoteSession.java:907
[java] at com.waveset.session.RemoteSession.call(RemoteSession.java:893
[java] at com.waveset.session.RemoteSession.call(RemoteSession.java:880
[java] at com.waveset.session.RemoteSession.call(RemoteSession.java:869
[java] at com.waveset.session.RemoteSession.createView(RemoteSession.ja
va:753)
[java] at com.sun.idm.idmx.myspefiles.MyRemoteApiUsage.createAndProvisi
onUser3(MyRemoteApiUsage.java:496)
[java] at com.sun.idm.idmx.myspefiles.MyRemoteApiUsage.demoBasicProvisi
oning(MyRemoteApiUsage.java:475)
[java] at com.sun.idm.idmx.myspefiles.MyRemoteApiUsage.runDemo(MyRemote
ApiUsage.java:656)
[java] at com.sun.idm.idmx.myspefiles.MyRemoteApiUsage.main(MyRemoteApi
Usage.java:670)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
Is this a known issue in the SDK ? If I construct my own XML and populate a GenericObject, _remoteSession.checkinView (view) does not have any problem in checking in the view. The exception is thrown irrespective of the view id I use , i.e. IDMXUser, User, Role etc.
Thanks,
Srinivas

Hi Srini,
Have you solved this problem. If yes then can you help me with the solution?
Thanks!

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.

"Restrictions Do Not Allow Explicit Content"???

Downloaded a few podcasts yesterday. Listened to one of them on the ride home last night (from my iPhone, after syncing). Tried to pick up where I left off this morning, and these particular podcasts are "grayed out" and, when tapped, say "Content Not Allowed. Restrictions do not allow explicit content". I checked my iTunes preferences (Parental), nothing is checked, no restrictions. These are the very same podcasts I was listening to 12 hours ago! And they play fine on my computer, within iTunes. Just won't play on the iPhone after syncing. And it's just these podcasts (Start Up by Alex Blumberg -- far from explicit or pornographic). All the others are playing fine on the iPhone.
Any ideas?

I do not understand why APPLE is making it Rocket Science to protect our kids from this por-nography through their Store.
I have been in a dialgue with APPLE now for 2 weeks about the APP's that continue to come up, and researching further their podcasts also. They continue, as recommended here, to suggest that you complain to the a feedback link that, unfortunately, ends with a thank you and we will not be contacting you personally about this.
My suggestion is that you go to one of their 24 hour response links, here is one! (http://www.apple.com/support/itunes/contact.html?form=app_store&topic=App%20Stor e&subtopic=Downloading%20and%20updating%20Applications) and complain there. It is their respondsibility to manage their content.
The other suggestion is to notify everyone you know of your issue with APPLE and encourage them to also notify APPLE!
Everyone that I have notified is equally dissatisfied with APPLE.
Shame, we have to go so far to get APPLE to do what's right!

Content is not allowed in the Prolog

Hi All,
I am getting this error while trying to run my Spring based app in the browser
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 2 in XML document from ServletContext resource [/WEB-INF/applicationContext.xml] is invalid; nested exception is org.xml.sax.SAXParseException: Content is not allowed in prolog.
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:359)
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303)
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280)
     org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131)
     org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147)
     org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124)
     org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92)
     org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101)
     org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389)
     org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324)
     org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244)
     org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187)
     org.springframework.web.context.ContextLoaderServlet.init(ContextLoaderServlet.java:82)
     javax.servlet.GenericServlet.init(GenericServlet.java:261)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:158)
     org.apache.catalina.startup.Embedded.start(Embedded.java:1030)
     com.sun.enterprise.web.WebContainer.start(WebContainer.java:490)
     com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:506)
     com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:54)
     com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
root cause
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:266)
     org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:206)
     org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76)
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351)
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303)
     org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280)
     org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131)
     org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147)
     org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124)
     org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92)
     org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101)
     org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389)
     org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324)
     org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:244)
     org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187)
     org.springframework.web.context.ContextLoaderServlet.init(ContextLoaderServlet.java:82)
     javax.servlet.GenericServlet.init(GenericServlet.java:261)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
     java.security.AccessController.doPrivileged(Native Method)
     javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
     org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:158)
     org.apache.catalina.startup.Embedded.start(Embedded.java:1030)
     com.sun.enterprise.web.WebContainer.start(WebContainer.java:490)
     com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:506)
     com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:54)
     com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:324)
     org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)here is my xml file which is throwing the error
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<bean id="aquofusionController" class="org.aquosine.aquofusion.controller.AquofusionController"/>
<bean id="urlMapping" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="mappings">
<props>
<prop key="/hello.htm">aquofusionController</prop>
</props>
</property>
</bean>
</beans>please help as i am breaking head over this for last two days.

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.

"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

CONTENT NOT ALLOWED IN PROLONG

Similar Messages

Maybe you are looking for