XML-comments not allowed in IDOC_AAE-Adapter?

Hi,
we have a File to IDOC scenario and are using the IDOC_AAE adapter for sending IDOCs to the SAP system.
In our mapping we have added some comments into the XML-IDOC-structure.
By sending the document to the SAP-system we are getting the following error:
MP: exception caught with cause
com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to
idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character
encountered within IDocXML for type <INVOIC01>:
state=READING_FIELD_STARTTAG, charPosition=872, lineNumber=23, columnNumber=14,
invalidChar=U+0021,
sourceSnippet=...RCY>^~~~<KUNDEUINR>DEXXXXXXX</KUNDEUINR>^~~~<BSART>INVO</BSART>^~~~^~~... ^
The problem seems to be the <!-- - Tag in the structure.
But the ! (U+0021) is a correct XML 1.0 character. I don't know why the IDOC-XML parser throws this exception.
Does anybody have an idea what the problem is?
When we remove the comments the IDOC could be sent successfully to the SAP system.
Are only IDOC-specific characters allowed here, no comments and no other XML-specific characters and structures?
This would be very strange.
Thanks for your answer.
Regards
Thorsten

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

Similar Messages

Comments Not allowed?

Hello freinds,
I have installed Adobe LiveCycle designer 8.2 in my windows 7 machine, i opened a brand new pdf and entered contact details, then am trying to write comments, but, when i saw its peoperties, i noticed that COMMENTS: NOT ALLOWED under security tab!! Pls. let me know how i can enable and so that i can write comments.
Thank you

Hi Srinivas,
Just to add my bit to the discussion, which is the same as what George and Chuck are saying.
The issue is that the form is opening in the free Adobe Reader (even if opening in a browser, the Reader is still being used). As a result certain functionality is not available.
For example, if the form is not Reader Enabled, then users with Reader will not be able to add comments to the form.
Even if the form is Reader Enabled, if the form was originally saved as a Dynamic XML Form (in the LiveCycle Designer save-as dialog), then you will not be able to add comments.
When working with forms that are created in LiveCycle Designer, you can only add comments where the form was originally saved as a Static PDF Form in the save-as dialog.
Here is a summary. I suspect that your form is in Option 2, that is the form is not Reader Enabled and is opened in Reader.
http://assure.ly/etkFNU.
In addition there is a long discussion here: http://forums.adobe.com/message/2686010#2686010
Hope that helps,
Niall

Commenting not allowed after emailing pdfs

I am fairly new to acrobat. I am trying to save illustrator files as pdfs in order for clients to comment with stickies on the file. No matter what security settings I use after emailing the files my document settings change.... comments not allowed....???

Wired_Bob wrote:
The option to allow commenting is checked and the document is saved replacing the first exported doc.
I guess that part of your terminology is confusing. What do you mean by "checked".
To be sure we're on the same page, by "checked" you mean after opening in Acrobat you went to Comments>Enable for commenting and analysis in Adobe Reader, correct?
The reason I ask is because if you open it in Acrobat and go to File>Properties and see that commenting is "allowed", that still doesn't mean that it is enabled for Reader users.

Commenting Not allowed, even in docs I create Reader 8.1.1

I cannot comment or bring up the comment menu in any document in Reader 8.1.
I do not know what happened. And this is true for at least 2 computers in my house. We have Acrobat 6 installed as a PDF Creator. But even in documents I create and have no security enabled, the Reader 8.1 tells me the document has "commenting" - "not allowed." I have tried everything I can think of, even un-installing reader and then installing a fresh copy, but the reader still does not allow me to make comments,
Any ideas?

Good morning all,
I believe the following information may be helpful, I came across this issue this morning and found that this works:
Once you have completed your file in Acrobat Professional you need to open the "Comments" tab menu and choose "Enable for commenting and analysis in Reader" option.
This will save your file again and once opened in Reader the commenting functions will be enabled.
Why this is so when all security options in the Professional File are show 'allowed' is beyond my comprehension.
Hope it helps.
Cheers.

405 Method Not Allowed -- XI AS2 Adapter error

Hi All,
I am getting the folloeing error in AS2 Adapter "405 Method Not Allowed". Please let me know ablout the latest note etc to resolve the same as note no. 906435 is quite old and is unable to resolve the same.
Thanks in Advance.
With regards,
Gaurav

Is your computer directly connected to internet, or do you have make some proxy settings ?

Commenting Not Allowed

I have converted several scanned checklists to form fillable PDF's using Designer. After converting them to form fillable I have inserted several check box objects so that our employees (who all have Adobe Standard) can fill out the check lists and save them and insert the filled out checklists into work binders. On occassion they need the ability to add comments to a section of the checklist and they all know how to use the commenting features. On most of the forms I created commenting is alllowed however on the last two that I created "Commenting Allowed" is marked as no in the security settings and I can't get this to change.
The only thing that I can think of that I changed on these is that I might have selected "Preserve Appearance" instead of "Maintain Editablity" in step two of the New Form Assistant.
Is there any way to enable the commenting on these files? One of them is 90 pages long and took a long time to add all the checkboxes to.
Thanks

Try to save it as a static form. Here's the email from our tech team:
"If he did just have him save it as a static form. The issue becomes one of how do we know where to put the comments if the page/section doesnt exist."
Mike
Mike Potter
Adobe Enterprise Developer Relations

V15 XML Loader Access To Path Not Allowed

We are just starting to test our V15 sandbox system that has just been upgraded. We have a transaction that works fine in our older environment (V12.2) but the same transaction fails in V15. The first sequence in the transaction is an XML Loader that tries to load and XML configuration file from the local MII server where the transaction is running. The action fails with a Access to path /directoryNameHere/fileNameHere.xml is not allowed error.
As far as we can tell, all of the filesystem/OS level permissions (Linux in our case) are the same as they are in our old environment.
Other than file/directory permissions, any ideas why this might fail? Has anything changed in V15 that would potentially impact this?
We are not specifying a Credential Store alias (listed as optional).
Thank you,
Mike

At some point a 'Default File Path' parameter was added as a system property and it's value may be causing your issue.
System Properties - SAP Manufacturing Integration and Intelligence - SAP Library
Default File Path
DefaultFilePath
The path on the file system (along with the subfolders) used to store files that need to be accessed by the following workbench actions for read/write operations:
File I/O
CreateDirectory
CreateZipArchive
DeleteFile
GetFileList
WriteFile
FTPInput
FTPOutput
ADS Printing
E-Mail
Send Mail
Read Mail
LoggingXML Tracer
Web
HTMLSaver
XMLSaver
TextSaver
ImageSaver
HTMLLoader
XMLLoader
TextLoader
ImageLoader
Note
Access to the files under the previous path (and the subfolders) will be lost if the path is changed.
If the path is empty, you can access the file system, provided the file system provides read/write permissions. The same holds good for prior releases.

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:1: Content is not allowed in prolog. ..XML READ ERROR

Hi I am developing an application where it will read xml elements from the http site (http://www.w3schools.com/Xml/note.xml) and display in my program using DOM. while executing its giving CONTENT IS NOT ALLOWED IN PROGRAM below error. but when i am use coded xml in program itself as comment as shown in program its giving correct value. I need to read from http not from coded xml in the program. its immediate please help me out.
[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 SimpleXML1.main(SimpleXML1.java:34)
import javax.xml.parsers.*;
import org.xml.sax.InputSource;
import org.w3c.dom.*;
import java.io.*;
public class SimpleXML1 {
public static void main(String arg[]) {
String xmlRecords = "http://www.w3schools.com/Xml/note.xml";
/* String xmlRecords =
" <note>" +
" <to>John</to>" +
" <from>Manager</from>" +
" <heading>XML Program</heading>" +
" <body>Simple XML</body>" +
"</note>";*/
try {
DocumentBuilderFactory dbf =
DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
InputSource is = new InputSource();
is.setCharacterStream(new StringReader(xmlRecords));
Document doc = db.parse(is);
NodeList nodes = doc.getElementsByTagName("note");
for (int i = 0; i < nodes.getLength(); i++) {
Element element = (Element) nodes.item(i);
NodeList from = element.getElementsByTagName("from");
Element line = (Element) from.item(0);
Node child1 = line.getFirstChild();
CharacterData cd = (CharacterData) child1;
System.out.println(cd.getData());
catch (Exception e) {
e.printStackTrace();
}

chrisacess wrote:String xmlRecords = "http://www.w3schools.com/Xml/note.xml";
/* snip */
is.setCharacterStream(new StringReader(xmlRecords));
Is that really how you're trying to read the online XML document? Because I don't see anything that makes a connection to the site. All you're doing is trying to parse the string "http://www.w3schools.com/Xml/note.xml" is if it were XML.
ps, That "Content not allowed in prolog" error message is worse than useless IMO. They might as well say "It didn't work" for all the good does.

Clear text value not allowed for credentials in config.xml

I am in the process of migrating our J2EE application from Weblogic 8.1 to Weblogic 10 MP1 and have converted config.xml to the new schema. When starting up in production mode, I see the following error which causes the server to shutdown:
<Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: In production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean>
In 8.1 it seems that it would fill in the credentials based on the username and password in boot.properties so it was possible for our installation program to leave these entries blank. However, when starting in 10.0 it doesn't do this. Below is an excerpt from config.xml.
<security-configuration>
<name>xyz</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xsi:type="wls:default-role-mapperType"></sec:role-mapper>
<sec:authorizer xsi:type="wls:default-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:user-lockout-manager></sec:user-lockout-manager>
<sec:security-dd-model>Advanced</sec:security-dd-model>
<sec:combined-role-mapping-enabled>false</sec:combined-role-mapping-enabled>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted></credential-encrypted>
<web-app-files-case-insensitive>os</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>true</compatibility-connection-filters-enabled>
<enforce-strict-url-pattern>false</enforce-strict-url-pattern>
</security-configuration>
Is anyone else trying to do this?
Henry

Hi henry,
While running a particular instance in the production mode(wls 10.x),prior to upgrading the domain you need to upgrade the security provider(all the mbeans ) you use in the previous versions and later on if you follow the domain upgrade you may find a solution for this issue...

As a new Macbook Pro user I was saddened to find that the feature of using keywords in iPhoto '11 does not allow showing same under each photo. I understand this was available in earlier versions. Any comments?

As a new Macbook Pro user I was saddened to find that the feature of using keywords in iPhoto '11 does not allow showing same under each photo. I understand this was available in earlier versions. Any comments?

Against TOU which you "agreed" to in order to post in these user to user forums. If you want to "suggest" something to Apple, do so in the Product Feedback area.

Whitespace is not allowed at this location. Error while running CP using RDF with XML

Hi All,
I am using RDF report with output type as XML. It have following parameters:
1. Organization Name,
2. Invoice No From
3. Invoice No To
4. Date From
5. Date To
I had developed an RTF and registered that in Oracle Applications. The output comes in Excel file.
When I used to run report using Invoice Number From and Invoice Number To the report is giving normal excel output.
But when I am running using parameters Date From and Date To then XML output is coming after viewing output in CP Output button.
I downloaded that xml file. It is invalid as in the last of xml file it is showing following error message
"Whitespace is not allowed at this location".
Please let me know how can I resolve this problem.
Thanks in advance..
Regards
Sandip

my xml file looks like this....

<XX_ITEM_LOADING>
<LIST_G_BLANKET_NUMBER>
    <G_BLANKET_NUMBER>
      <CUSTOMER>SPS PVT LTD</CUSTOMER>
      <INVOICE_NO>17356</INVOICE_NO>
      <INVOICE_DATE>20-JUL-13</INVOICE_DATE>
      <BUYER_REF>56780YP</BUYER_REF>
      <ITEM_DESCRIPTION>XXCSD</ITEM_DESCRIPTION>
      <NUM_OF_BEANS></NUM_OF_BEANS>
      <CARIRER></CARIRER>
      <SHIP_METHOD_CODE>UK568</SHIP_METHOD_CODE>
      <MODE_OF_TRANSPORT>ROAD</MODE_OF_TRANSPORT>
      <ASSEABLE_VALUE>1134534</ASSEABLE_VALUE>
      <QUANTITY>149</QUANTITY>
      <SOLD_TO>SPS PVT LTD</SOLD_TO>
      <TAN_NO></TAN_NO>
      <ST_REG_NO>943481</ST_REG_NO>
      <EC_CODE></EC_CODE>
      <TERMS>30 NET</TERMS>
      <CUST_PO_NUMBER></CUST_PO_NUMBER>
      <DESTINATION>LONDON</DESTINATION>
      <CP_DAYS>3</CP_DAYS>
    </G_BLANKET_NUMBER>
XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Whitespace is not allowed at this location. Error processing resource 'file:///C:/Users/sys/Downloads/cp_output_date_range....
      <SOLD_TO>DKSP TECHNOLOGIES & ENGG(A DIV. OF PARROT SYSTEM LTD.)</SOLD_TO>
_METHOD_CODE>

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.

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.

Acrobat Reader 9.0 PDF - Commenting property "Not Allowed"

Hi,
I saved a document in Illustrator as PDF but unfortunately the Commenting property is set to "Not Allowed" and I cannot mark-up the file in Acrobat Reader. What is strange is all properties are set to "Allowed" when I open the same document in Acrobat Pro!
Can I do anything in Illustrator or Acrobat Reader in order to have this Commenting property set to "Allowed"?
For info, I am using Illustrator CS2 and Acrobat Reader 9.0
Cheers!

This is normal. Reader cannot normally add comments.
HOWEVER, a file can be prepared in Acrobat Pro (See the Comments menu)
so Reader can add comments. This locks out certain other things: read
the warning carefully.
Aandi Inston

XML-comments not allowed in IDOC_AAE-Adapter?

Similar Messages

Maybe you are looking for