Prashant,
Thx for your response.
I have executed the od -c command on my xml file and do not see any
empty lines before the prolog:
# od -c JMS.properties
0000000 < ? x m l v e r s i o n = " 1
0000020 . 0 " e n c o d i n g = " U T
0000040 F - 8 " ? > < J M S P r o p e r
0000060 t i e s x m l n s = " h t t p
0000100 : / / l u c e n t . c o m / G R
0000120 I P P / j m s P r o p e r t i e
0000140 s " x m l n s : x s i = " h t
0000160 t p : / / w w w . w 3 . o r g /
0000200 2 0 0 1 / X M L S c h e m a - i
0000220 n s t a n c e " \n x s i : s c
0000240 h e m a L o c a t i o n = " h t
0000260 t p : / / l u c e n t . c o m /
0000300 G R I P P / j m s P r o p e r t
0000320 i e s J M S _ p r o p e r t i
0000340 e s . x s d " > \n < S Y S T E
Lydie
-----Original Message-----
From: Prashant
Sent: Tuesday, October 17, 2006 15:18
To: j-users@xxxxxxxxxxxxxxxxx
Subject: Re: Getting SAX Exception Content is not allowed in prolog.
when using my code on Unix platform
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.NeBiJMSO
> utgoingGatewayManager"</JMS_OUTGOING_GATEWAY_MANAGER_CLASS>
>
> <JMS_INCOMING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSIncomingG
> ateway"</JMS_INCOMING_GATEWAY_CLASS>
>
> <JMS_OUTGOING_GATEWAY_CLASS>"com.lucent.lws.nebilight.NeBiJMSOutgoingG
> ateway"</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_SU
> CCESS_DOCUMENT>
> <RESPONSE_ON_ERROR_DOCUMENT>"BD:ErrorReport_L_0.5"</RESPONSE_ON_ERROR_
> DOCUMENT>
> <NOTIFICATION_DOCUMENT>"BD:ExecutionStatus_L_1.0"</NOTIFICATION_DOCUME
> NT>
> <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!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: j-users-help@xxxxxxxxxxxxxxxxx
|
