You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by "Decoker, Lydie (Lydie)" <de...@lucent.com> on 2006/10/17 14:51:53 UTC
Getting SAX Exception Content is not allowed in prolog. when using my code on Unix platform
Hi!
When executing my Java code (using Xerces parser), everything is ok.
When I use the same code with the same xml files (except the path local)
on a Unix platform , I got: SAX Exception Content is not allowed in
prolog.
My xml file:
<JMSProperties xmlns="http://lucent.com/GRIPP/jmsProperties"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://lucent.com/GRIPP/jmsProperties
JMS_properties.xsd">
<SYSTEM_NAME>WFM014</SYSTEM_NAME>
<INSTANCE_ID>INTF_TEST</INSTANCE_ID>
<XSLT_FILE>"/servernet/wfm/lucent/LUplat/nbi/xsltemplates/jms-wfm.xsl"</
XSLT_FILE>
<CATALOG>"/servernet/wfm/lucent/LUplat/config/JMSCatalog.xml"</CATALOG>
<JMS_OUTGOING_GATEWAY_MANAGER_CLASS>"com.lucent.lws.nebilight.NeBiJMSOut
goingGatewayManager"</JMS_OUTGOING_GATEWAY_MANAGER_CLASS>
<JMS_INCOMING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSIncomingGat
eway"</JMS_INCOMING_GATEWAY_CLASS>
<JMS_OUTGOING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSOutgoingGat
eway"</JMS_OUTGOING_GATEWAY_CLASS>
<JMS_SESSION_TRANSACTED/>
<JMS_SESSION_ACKMODE/>
<CONNECTION_FACTORY>"myConnectionFactory"</CONNECTION_FACTORY>
<PROVIDER_URL>"tcp://135.87.9.11:3035"</PROVIDER_URL>
<INITIAL_CONTEXT_FACTORY>"org.exolab.jms.jndi.InitialContextFactory"</IN
ITIAL_CONTEXT_FACTORY>
<JMSMessageConsumption>asynchronously</JMSMessageConsumption>
<OUTGOING_SELECTION_FIELD>MessageType</OUTGOING_SELECTION_FIELD>
<RESPONSE_ON_SUCCESS_DOCUMENT>"BD:OrderResponse_L_1.0"</RESPONSE_ON_SUCC
ESS_DOCUMENT>
<RESPONSE_ON_ERROR_DOCUMENT>"BD:ErrorReport_L_0.5"</RESPONSE_ON_ERROR_DO
CUMENT>
<NOTIFICATION_DOCUMENT>"BD:ExecutionStatus_L_1.0"</NOTIFICATION_DOCUMENT
>
<IncomingGateways>
<IncomingGateway>
<QueueName QueueType="Queue">QueueName3</QueueName>
</IncomingGateway>
<IncomingGateway>
<QueueName QueueType="Queue">QueueName3</QueueName>
</IncomingGateway>
</IncomingGateways>
<OutgoingGateways>
<OutgoingGateway>
<QueueName QueueType="Queue">QueueName4</QueueName>
<OutgoingSelectionFieldValue>"BD:OrderResponse_L_1.0"</OutgoingSelection
FieldValue>
</OutgoingGateway>
<OutgoingGateway>
<QueueName QueueType="Queue">QueueName4</QueueName>
<OutgoingSelectionFieldValue>"BD:ErrorReport_L_0.5"</OutgoingSelectionFi
eldValue>
</OutgoingGateway>
</OutgoingGateways>
</JMSProperties>
Any suggestion on the root cause of this issue?
Thx!
Re: Getting SAX Exception Content is not allowed in prolog. when
using my code on Unix platform
Posted by Prashant <pr...@pramati.com>.
Verify if you have empty lines before prolog[1].
Sometimes i find the "annotated" XML specification[2] more friendly.
[1]:http://www.w3.org/TR/2000/REC-xml-20001006#sec-prolog-dtd
[2]:http://www.xml.com/axml/testaxml.htm
-Prashant
Decoker, Lydie (Lydie) wrote:
> Hi!
>
> When executing my Java code (using Xerces parser), everything is ok.
> When I use the same code with the same xml files (except the path
> local) on a Unix platform , I got: SAX Exception Content is not
> allowed in prolog.
>
> My xml file:
>
> <JMSProperties xmlns="http://lucent.com/GRIPP/jmsProperties"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://lucent.com/GRIPP/jmsProperties
> JMS_properties.xsd">
> <SYSTEM_NAME>WFM014</SYSTEM_NAME>
> <INSTANCE_ID>INTF_TEST</INSTANCE_ID>
> <XSLT_FILE>"/servernet/wfm/lucent/LUplat/nbi/xsltemplates/jms-wfm.xsl"</XSLT_FILE>
> <CATALOG>"/servernet/wfm/lucent/LUplat/config/JMSCatalog.xml"</CATALOG>
> <JMS_OUTGOING_GATEWAY_MANAGER_CLASS>"com.lucent.lws.nebilight.NeBiJMSOutgoingGatewayManager"</JMS_OUTGOING_GATEWAY_MANAGER_CLASS>
> <JMS_INCOMING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSIncomingGateway"</JMS_INCOMING_GATEWAY_CLASS>
> <JMS_OUTGOING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSOutgoingGateway"</JMS_OUTGOING_GATEWAY_CLASS>
> <JMS_SESSION_TRANSACTED/>
> <JMS_SESSION_ACKMODE/>
> <CONNECTION_FACTORY>"myConnectionFactory"</CONNECTION_FACTORY>
> <PROVIDER_URL>"tcp://135.87.9.11:3035"</PROVIDER_URL>
> <INITIAL_CONTEXT_FACTORY>"org.exolab.jms.jndi.InitialContextFactory"</INITIAL_CONTEXT_FACTORY>
> <JMSMessageConsumption>asynchronously</JMSMessageConsumption>
> <OUTGOING_SELECTION_FIELD>MessageType</OUTGOING_SELECTION_FIELD>
> <RESPONSE_ON_SUCCESS_DOCUMENT>"BD:OrderResponse_L_1.0"</RESPONSE_ON_SUCCESS_DOCUMENT>
> <RESPONSE_ON_ERROR_DOCUMENT>"BD:ErrorReport_L_0.5"</RESPONSE_ON_ERROR_DOCUMENT>
> <NOTIFICATION_DOCUMENT>"BD:ExecutionStatus_L_1.0"</NOTIFICATION_DOCUMENT>
> <IncomingGateways>
> <IncomingGateway>
> <QueueName QueueType="Queue">QueueName3</QueueName>
> </IncomingGateway>
> <IncomingGateway>
> <QueueName QueueType="Queue">QueueName3</QueueName>
> </IncomingGateway>
> </IncomingGateways>
> <OutgoingGateways>
> <OutgoingGateway>
> <QueueName QueueType="Queue">QueueName4</QueueName>
>
> <OutgoingSelectionFieldValue>"BD:OrderResponse_L_1.0"</OutgoingSelectionFieldValue>
> </OutgoingGateway>
> <OutgoingGateway>
> <QueueName QueueType="Queue">QueueName4</QueueName>
>
> <OutgoingSelectionFieldValue>"BD:ErrorReport_L_0.5"</OutgoingSelectionFieldValue>
> </OutgoingGateway>
> </OutgoingGateways>
> </JMSProperties>
> Any suggestion on the root cause of this issue?
>
> Thx!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org