java.beans.PropertyVetoException

Error creating default request document from schema; cause was DOM002 Illegal character

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web6

  • via Oracle Community by 3004, 1 year ago
    Error creating default request document from schema; cause was DOM002 Illegal character
  • via Oracle Community by 3004, 1 year ago
    Error creating default request document from schema; cause was DOM002 Illegal character
  • Stack trace

    • java.beans.PropertyVetoException: Error creating default request document from schema; cause was DOM002 Illegal character at com.bea.adapter.cci.DocumentInteractionSpecImpl.vetoableChange(DocumentInteractionSpecImpl.java:120) at com.bea.adapter.dbms.cci.InteractionSpecImpl.vetoableChange(InteractionSpecImpl.java:139) at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:225) at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:142) at com.bea.adapter.cci.InteractionSpecImpl.fireChangeEvent(InteractionSpecImpl.java:194) at com.bea.adapter.cci.DocumentInteractionSpecImpl.setRequestDocumentDefinition(DocumentInteractionSpecImpl.java:51) at com.bea.wlai.ApplicationViewDeploymentInfo.replicateDocumentDefinitionsIntoDocumentInteractionSpecs(ApplicationViewDeploymentInfo.java:111) at com.bea.wlai.ApplicationViewDeploymentCache.applicationViewDeployed(ApplicationViewDeploymentCache.java:156) at com.bea.wlai.ApplicationViewDeploymentCache.onMessage(ApplicationViewDeploymentCache.java:121) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1806) at weblogic.jms.client.JMSSession.execute(JMSSession.java:1765) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.