Jasper Parse Exception CRM HH Service
I am getting a parse exception for the line in jsps that include this file -> "/include/HeadInclude.jsp".
ated the following parse exception: org.apache.jasper.compiler.CompileException:
C:\Documents and Settings\I806232\Documents\SAP\workspace\40SP08\cfg\service\tm
p\app-root\include\HeadInclude.jsp(4,0) Bad file argument to include
The file exists but still I get this error during pre-compilation.
Any ideas?
This is the standard HH Service war file. Almost every jsp in it uses the include tag so it won't be a good idea to change this in all the jsps.
I checked the server.xml context path
<Context path="" docBase="webapps/me" crossContext="true" debug="0" reloadable="false"
/>
But this xml is not used during build time, is it? Is there anything missing from it. I dont see the HHService application context root in it..
Thanks
Similar Messages
-
Problem with JSF tags, org.apache.jasper.JasperException: Exception in JSP:
I am a beginner to JSF , I am getting the following error when I try to invoke using the following URL
http://localhost:8080/Loginjsf/
I have copied web.xml,faces-config.xml,index.jsp, userLogin.jsp and also the list of jars I am using.
java version I am using jdk1.5.0_14
tomcat version 5.5.25
JSF Version 1.1_01
---------------------------------------------------------------------this is the error------------------------------------------------------------------
exception
org.apache.jasper.JasperException: Exception in JSP: /index.jsp:7
4: </head>
5: <body>
6: </body>
7: <jsp:forward page="userLogin.jsp"></jsp:forward>
8: </html>
Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:451)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
org.apache.jasper.JasperException: Exception in JSP: /userLogin.jsp:15
12: </head>
13:
14: <body>
15: <f:view>
16: <h:form id="UserName">
17: <f:loadBundle basename ="com.demo.MessageBundle" var="bundle"/> <br>
18: <h:inputText></h:inputText>
Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:451)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
org.apache.jsp.index_jsp._jspService(index_jsp.java:50)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
javax.servlet.ServletException: Cannot find FacesContext
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:841)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:774)
org.apache.jsp.userLogin_jsp._jspService(userLogin_jsp.java:92)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
org.apache.jsp.index_jsp._jspService(index_jsp.java:50)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
javax.servlet.jsp.JspException: Cannot find FacesContext
javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:399)
com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)
org.apache.jsp.userLogin_jsp._jspx_meth_f_005fview_005f0(userLogin_jsp.java:107)
org.apache.jsp.userLogin_jsp._jspService(userLogin_jsp.java:82)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
org.apache.jsp.index_jsp._jspService(index_jsp.java:50)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
THE WEB.XML FILE I AM USING IS
The web.xml, faces-config.xml files which I am using ,
<?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>
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml</param-value>
</context-param>
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>true</param-value>
<description>
Set this flag to true if you want the JavaServer Faces
Reference Implementation to validate the XML in your
faces-config.xml resources against the DTD. Default
value is false.
</description>
</context-param>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<!--Tomcat 5 Workaround: Listener used to initialize JSF on startup-->
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
</web-app>
THE FACES-CONFIG.XML I AM USING
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config >
<application>
<view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
</application>
<managed-bean>
<managed-bean-name>UserBean</managed-bean-name>
<managed-bean-class>com.demo.bean.UserBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>userName</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
<managed-property>
<property-name>password</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
</managed-bean>
<navigation-rule>
<from-view-id>/userLogin.jsp</from-view-id>
<navigation-case><from-outcome>failure</from-outcome>
<to-view-id>/loginForm.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-action>success</from-action>
<to-view-id>/userLoginSuccess.jsp</to-view-id>
</navigation-case></navigation-rule>
<navigation-rule>
<from-view-id>/userLoginSuccess.jsp</from-view-id>
</navigation-rule>
<navigation-rule>
<from-view-id>/loginForm.jsp</from-view-id>
</navigation-rule>
</faces-config>
THE INDEX.JSP I AM USING
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
</head>
<body>
</body>
<jsp:forward page="userLogin.jsp"></jsp:forward>
</html>
THE USERLOGIN.JSP is
<%@ page language="java" pageEncoding="ISO-8859-1"%>
<%@ taglib uri="/WEB-INF/html_basic.tld" prefix="h"%>
<%@ taglib uri="/WEB-INF/jsf_core.tld" prefix="f"%>
<html>
<head>
<title>My JSF 'userLogin' starting page</title>
<!--
<link rel="stylesheet" type="text/css" href="styles.css">
-->
</head>
<body>
<f:view>
<h:form id="UserName">
<f:loadBundle basename ="com.demo.MessageBundle" var="bundle"/> <br>
<h:inputText></h:inputText>
<h:outputLabel value="UserName"></h:outputLabel>
<h:inputText></h:inputText>
<h:outputLabel for="Password" value="Password" id="Password"></h:outputLabel>
</h:form>
</f:view>
</body>
</html>
THE JAR FILES LOCATED AT tomcat-5.5\webapps\Loginjsf\WEB-INF\lib
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-logging.jar
el-api.jar
el-ri.jar
jsf-api.jar
jsf-facelets.jar
jsf-impl.jar
jstl.jar
standard.jar
It would be great if you could help me in resolving this problem, what is that I am doing wrong?Thanks for your suggestions, I updated the web.xml and index.jsp accordingly but this time I am getting a different kind of error as below
org.apache.jasper.JasperException: Exception in JSP: /index.jsp:6
3: <head>
4: </head>
5: <body>
6: <jsp:forward page="userLogin.faces"></jsp:forward>
7: </body>
8: </html>
Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:451)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
javax.servlet.ServletException: Error Parsing /userLogin.jsp: Error Traced[line: 1] The markup in the document preceding the root element must be well-formed.
javax.faces.webapp.FacesServlet.service(FacesServlet.java:202)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
org.apache.jsp.index_jsp._jspService(index_jsp.java:49)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
com.sun.facelets.FaceletException: Error Parsing /userLogin.jsp: Error Traced[line: 1] The markup in the document preceding the root element must be well-formed.
com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:234)
com.sun.facelets.compiler.Compiler.compile(Compiler.java:105)
com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197)
com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144)
com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:496)
com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
org.apache.jsp.index_jsp._jspService(index_jsp.java:49)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -
XML Parser Exception in Install of AIA 11.1.1.5 on SOA 11.1.1.5
I am attempting to install AIA Foundation Pack on a SOA domain and continually encounter an XML parsing exception error as the installer is attempting to install WSM security policies. Here are the key details:
AIA version = 11.1.1.5
SOA Suite = 11.1.1.5
WebLogic = 10.3.5
Operating System = Fedora14 (a home lab machine but I don't think this is an OS issue)
The error is encountered about 17 minutes into the lengthy process. Just before the error appears in the installation log, the following message appears indicating roughly what step is being performed:
[zip] Building zip: /opt/oraclemw/aia11115/aia_instances/dev1/tmp/aia_security_policies.zip
The core error messages are:
[exec] SEVERE: WSM-01605 XML parser exception
[exec] oracle.xml.parser.v2.XMLParseException: Expected 'EOF'.
[exec] at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
The python modules being executed by the WLST scripting tool at the time of the failure are:
[exec] Problem invoking WLST - Traceback (innermost last):
[exec] File "/opt/oraclemw/aia11115/Infrastructure/Install/AID/lib/py/importpolicy.py", line 29, in ?
[exec] File "/opt/oraclemw/oracle_common/common/wlst/wsmManage.py", line 719, in importRepository
[exec] File "/opt/oraclemw/oracle_common/common/wlst/lib/ora_util.py", line 51, in raiseScriptingException
[exec] OracleScriptingException: None
Finally, the outer XML files being used as input for the deployer that seems to be running at the time are:
/opt/oraclemw/aia11115/Infrastructure/Install/AID/AIAExecuteDriver.xml
with references to lines 221 and 64.
The problem occurs whether I try to use Java JDK 16.0.20 or JRockit R28.2.0 as the JRE when running the AIA installer. (The WebLogic domain is configured to use JRockit).
Any suggestions? Is there a library conflict being picked up between different releases of XercesImpl? I would hope there isn't actually a bad XML file in the AIA artifacts or WSM (Web Service Management) policies being deployed.HI
How this issue was resolved? Please explain in detail. I am facing the same issue.
Regards
Arun -
JmsAdapter DOM Parsing Exception handling
Hi,
I'm currently facing a problem with the behaviour of the Jms Adapter.
Whenever a JMS message is put in the queue and that message is not XML valid, the Jms Adapter (consumer) throw the exception "DOM Parsing Exception in translator Exception".
That's fine, I understand that the message was not well formed. But what is not fine is that the underlying BPEL is not instanciated : meaning I can't handle the exception properly.
Is there a way to force the Jms Adapter not to crash on the DOM Parsing for the BPEL to be instanciated (and then being able to handle the exception there) ?
Or is there a way to handle the error thrown by the Jms Adapter itself ? How ?
I think I do have a workaround to this if there is no better option (if both above questions cannot be answered) but I would rather not implement it since it will involve some extra steps / complexity.
> It would be to check the "native format opaque schema" option and then use a java embedded to decode the base64 into a string for eventually parsing it.
regards,
mathieuHi Mathieu,
The messages that error out before being posted to the service infrastructure are referred to as rejected messages. For example, the Oracle File Adapter selects a file having data in CSV format and tries to translate it to XML format (using NXSD). If there is any error in the translation, this message is rejected and are not be posted to the target composite.
You can create rejection handlers to handle message errors. Message errors include those that occur during translation, correlation ID mismatch and XML parsing after message reception.
Docs on how to do that are here...
http://docs.oracle.com/cd/E28280_01/integration.1111/e10231/life_cycle.htm#CIAIICJJ
Cheers,
Vlad -
Integration between B2B and ESB error (DOM Parsing Exception in translator)
Hello,
We have configured a circuit that has the objective of sending a message to B2B and then the ESB dequeues that message from the IP_IN_QUEUE.
The problem is that for some reason, the ESB cannot read message using the AQ Adapter object.
The error is the following:
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
The trace is the following:
ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:139) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1609) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1514) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1447) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1286) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:134) ... 8 more
The Payload is the following:
<?xml version="1.0" ?><OMG_O19 xmlns="urn:oracle:integration:b2b:C023D5B231EF45519AA3D9929B4990E1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.4" CreatedDate="2007-07-17T17:10:43" CreatedBy="ECXEngine_837" GUID="{D16D28B9-3821-4BCC-B4D9-0D92F8611BB5}"><Internal-Properties><Data-Structure Name="Message"><Lookup Name="MessageSendingApp">ALERT</Lookup><Lookup Name="MessageSendingAppUniversalID"></Lookup><Lookup Name="MessageSendingAppUniversalIDType"></Lookup><Lookup Name="MessageSendingFacility">CHVNG</Lookup><Lookup Name="MessageSendingFacilityUniversalID"></Lookup><Lookup Name="MessageSendingFacilityUniversalIDType"></Lookup><Lookup Name="MessageReceivingApp">RADIO</Lookup><Lookup Name="MessageReceivingAppUniversalID"></Lookup><Lookup Name="MessageReceivingAppUniversalIDType"></Lookup><Lookup Name="MessageReceivingFacility">CHVNG</Lookup><Lookup Name="MessageReceivingFacilityUniversalID"></Lookup><Lookup Name="MessageReceivingFacilityUniversalIDType"></Lookup><Lookup Name="MessageCode">OMG</Lookup><Lookup Name="TriggerEvent">O19</Lookup><Lookup Name="MessageStructure">OMG_O19</Lookup><Lookup Name="MessageVersion">2.4</Lookup><Lookup Name="InternatCodeID"></Lookup><Lookup Name="InternatCodeText"></Lookup><Lookup Name="InternatCodeSystem"></Lookup><Lookup Name="InternatCodeAlternateID"></Lookup><Lookup Name="InternatCodeAlternateText"></Lookup><Lookup Name="InternatCodeAlternateSystem"></Lookup><Lookup Name="InternationalVersionID"></Lookup><Lookup Name="InternationalVersionIDText"></Lookup><Lookup Name="InternationalVersionIDSystem"></Lookup><Lookup Name="InternationalVersionIDAlternateID"></Lookup><Lookup Name="InternationalVersionIDAlternateText"></Lookup><Lookup Name="InternationalVersionIDAlternateSystem"></Lookup><Lookup Name="Standard">HL7</Lookup><Property Name="MessageEncodingCharacters">^~\&</Property><Property Name="MessageSendingApp">ALERT</Property><Property Name="MessageSendingAppUniversalID"></Property><Property Name="MessageSendingAppUniversalIDType"></Property><Property Name="MessageSendingFacility">CHVNG</Property><Property Name="MessageSendingFacilityUniversalID"></Property><Property Name="MessageSendingFacilityUniversalIDType"></Property><Property Name="MessageReceivingApp">RADIO</Property><Property Name="MessageReceivingAppUniversalID"></Property><Property Name="MessageReceivingAppUniversalIDType"></Property><Property Name="MessageReceivingFacility">CHVNG</Property><Property Name="MessageReceivingFacilityUniversalID"></Property><Property Name="MessageReceivingFacilityUniversalIDType"></Property><Property Name="MessageDate">20070705161247+0000</Property><Property Name="MessageDateTimePrecision"></Property><Property Name="MessageSecurity"></Property><Property Name="MessageCode">OMG</Property><Property Name="TriggerEvent">O19</Property><Property Name="MessageStructure">OMG_O19</Property><Property Name="MessageControlID">1709</Property><Property Name="ProcessingID">P</Property><Property Name="ProcessingMode"></Property><Property Name="MessageVersion">2.4</Property><Property Name="InternatCodeID"></Property><Property Name="InternatCodeText"></Property><Property Name="InternatCodeSystem"></Property><Property Name="InternatCodeAlternateID"></Property><Property Name="InternatCodeAlternateText"></Property><Property Name="InternatCodeAlternateSystem"></Property><Property Name="InternationalVersionID"></Property><Property Name="InternationalVersionIDText"></Property><Property Name="InternationalVersionIDSystem"></Property><Property Name="InternationalVersionIDAlternateID"></Property><Property Name="InternationalVersionIDAlternateText"></Property><Property Name="InternationalVersionIDAlternateSystem"></Property><Property Name="SequenceNumber"></Property><Property Name="ContinuationPointer"></Property><Property Name="AcceptAckType"></Property><Property Name="AppAckType"></Property><Property Name="CountryCode"></Property><Property Name="CharacterSet"></Property><Property Name="LanguageID"></Property><Property Name="LanguageText"></Property><Property Name="LanguageSystem"></Property><Property Name="LanguageAlternateID"></Property><Property Name="LanguageAlternateText"></Property><Property Name="LanguageAlternateSystem"></Property><Property Name="AlternateCharacterSetSchema"></Property><Property Name="ConformanceStatementID"></Property><Property Name="MessageProfileNamespaceID"></Property><Property Name="MessageProfileUniversalID"></Property><Property Name="MessageProfileUniversalIDType"></Property><Property Name="DecimalSeparator"></Property><Property Name="ElementDelimiter">0x7c</Property><Property Name="ReleaseCharacter">0x5c</Property><Property Name="RepeatingSeparator">0x7e</Property><Property Name="SegmentDelimiter">0xd</Property><Property Name="SubcomponentDelimiter">0x26</Property><Property Name="SubelementDelimiter">0x5e</Property></Data-Structure></Internal-Properties><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>ALERT</HD.1></MSH.3><MSH.4><HD.1>CHVNG</HD.1></MSH.4><MSH.5><HD.1>RADIO</HD.1></MSH.5><MSH.6><HD.1>CHVNG</HD.1></MSH.6><MSH.7><TS.1>20070705161247+0000</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>OMG</MSG.1><MSG.2>O19</MSG.2><MSG.3>OMG_O19</MSG.3></MSH.9><MSH.10>1709</MSH.10><MSH.11><PT.1>P</PT.1></MSH.11><MSH.12><VID.1>2.4</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13></MSH><Extra-
PID><Extra-
PID.1 xsi:nil="true"></Extra-
PID.1><Extra-
PID.2 xsi:nil="true"></Extra-
PID.2><Extra-
PID.3><Extra-
PID.3.1>390971</Extra-
PID.3.1><Extra-
PID.3.2 xsi:nil="true"></Extra-
PID.3.2><Extra-
PID.3.3 xsi:nil="true"></Extra-
PID.3.3><Extra-
PID.3.4>CHVNG</Extra-
PID.3.4><Extra-
PID.3.5>NS</Extra-
PID.3.5></Extra-
PID.3><Extra-
PID.4 xsi:nil="true"></Extra-
PID.4><Extra-
PID.5><Extra-
PID.5.1>Santos</Extra-
PID.5.1><Extra-
PID.5.2>Paula</Extra-
PID.5.2><Extra-
PID.5.3>Cristina Silva Lopes</Extra-
PID.5.3></Extra-
PID.5><Extra-
PID.6 xsi:nil="true"></Extra-
PID.6><Extra-
PID.7>19720117000000+0000</Extra-
PID.7><Extra-
PID.8 xsi:nil="true"></Extra-
PID.8><Extra-
PID.9 xsi:nil="true"></Extra-
PID.9><Extra-
PID.10 xsi:nil="true"></Extra-
PID.10><Extra-
PID.11><Extra-
PID.11.1>R Bernardino Costa 358 Bl D Hab 04</Extra-
PID.11.1><Extra-
PID.11.2 xsi:nil="true"></Extra-
PID.11.2><Extra-
PID.11.3>Valadares</Extra-
PID.11.3><Extra-
PID.11.4 xsi:nil="true"></Extra-
PID.11.4><Extra-
PID.11.5>4405</Extra-
PID.11.5></Extra-
PID.11><Extra-
PID.12 xsi:nil="true"></Extra-
PID.12><Extra-
PID.13 xsi:nil="true"></Extra-
PID.13><Extra-
PID.14 xsi:nil="true"></Extra-
PID.14><Extra-
PID.15 xsi:nil="true"></Extra-
PID.15><Extra-
PID.16 xsi:nil="true"></Extra-
PID.16><Extra-
PID.17 xsi:nil="true"></Extra-
PID.17><Extra-
PID.18>7011588</Extra-
PID.18><Extra-
PID.19 xsi:nil="true"></Extra-
PID.19></Extra-
PID><Extra-
PV1><Extra-
PV1.1 xsi:nil="true"></Extra-
PV1.1><Extra-
PV1.2>URG</Extra-
PV1.2><Extra-
PV1.3><Extra-
PV1.3.1>1</Extra-
PV1.3.1><Extra-
PV1.3.2 xsi:nil="true"></Extra-
PV1.3.2><Extra-
PV1.3.3 xsi:nil="true"></Extra-
PV1.3.3><Extra-
PV1.3.4>CHVNG</Extra-
PV1.3.4></Extra-
PV1.3><Extra-
PV1.4 xsi:nil="true"></Extra-
PV1.4><Extra-
PV1.5 xsi:nil="true"></Extra-
PV1.5><Extra-
PV1.6 xsi:nil="true"></Extra-
PV1.6><Extra-
PV1.7 xsi:nil="true"></Extra-
PV1.7><Extra-
PV1.8 xsi:nil="true"></Extra-
PV1.8><Extra-
PV1.9 xsi:nil="true"></Extra-
PV1.9><Extra-
PV1.10 xsi:nil="true"></Extra-
PV1.10><Extra-
PV1.11 xsi:nil="true"></Extra-
PV1.11><Extra-
PV1.12 xsi:nil="true"></Extra-
PV1.12><Extra-
PV1.13 xsi:nil="true"></Extra-
PV1.13><Extra-
PV1.14 xsi:nil="true"></Extra-
PV1.14><Extra-
PV1.15 xsi:nil="true"></Extra-
PV1.15><Extra-
PV1.16 xsi:nil="true"></Extra-
PV1.16><Extra-
PV1.17 xsi:nil="true"></Extra-
PV1.17><Extra-
PV1.18>URG</Extra-
PV1.18><Extra-
PV1.19><Extra-
PV1.19.1>7088430</Extra-
PV1.19.1><Extra-
PV1.19.2 xsi:nil="true"></Extra-
PV1.19.2><Extra-
PV1.19.3 xsi:nil="true"></Extra-
PV1.19.3><Extra-
PV1.19.4>SONHO</Extra-
PV1.19.4></Extra-
PV1.19><Extra-
PV1.20 xsi:nil="true"></Extra-
PV1.20><Extra-
PV1.21 xsi:nil="true"></Extra-
PV1.21><Extra-
PV1.22 xsi:nil="true"></Extra-
PV1.22><Extra-
PV1.23 xsi:nil="true"></Extra-
PV1.23><Extra-
PV1.24 xsi:nil="true"></Extra-
PV1.24><Extra-
PV1.25 xsi:nil="true"></Extra-
PV1.25><Extra-
PV1.26 xsi:nil="true"></Extra-
PV1.26><Extra-
PV1.27 xsi:nil="true"></Extra-
PV1.27><Extra-
PV1.28 xsi:nil="true"></Extra-
PV1.28><Extra-
PV1.29 xsi:nil="true"></Extra-
PV1.29><Extra-
PV1.30 xsi:nil="true"></Extra-
PV1.30><Extra-
PV1.31 xsi:nil="true"></Extra-
PV1.31><Extra-
PV1.32 xsi:nil="true"></Extra-
PV1.32><Extra-
PV1.33 xsi:nil="true"></Extra-
PV1.33><Extra-
PV1.34 xsi:nil="true"></Extra-
PV1.34><Extra-
PV1.35 xsi:nil="true"></Extra-
PV1.35><Extra-
PV1.36 xsi:nil="true"></Extra-
PV1.36><Extra-
PV1.37 xsi:nil="true"></Extra-
PV1.37><Extra-
PV1.38 xsi:nil="true"></Extra-
PV1.38><Extra-
PV1.39 xsi:nil="true"></Extra-
PV1.39><Extra-
PV1.40 xsi:nil="true"></Extra-
PV1.40><Extra-
PV1.41 xsi:nil="true"></Extra-
PV1.41><Extra-
PV1.42 xsi:nil="true"></Extra-
PV1.42><Extra-
PV1.43 xsi:nil="true"></Extra-
PV1.43><Extra-
PV1.44>20070705154838+0000</Extra-
PV1.44><Extra-
PV1.45 xsi:nil="true"></Extra-
PV1.45><Extra-
PV1.46 xsi:nil="true"></Extra-
PV1.46><Extra-
PV1.47 xsi:nil="true"></Extra-
PV1.47><Extra-
PV1.48 xsi:nil="true"></Extra-
PV1.48><Extra-
PV1.49 xsi:nil="true"></Extra-
PV1.49><Extra-
PV1.50 xsi:nil="true"></Extra-
PV1.50><Extra-
PV1.51>V</Extra-
PV1.51><Extra-
PV1.52 xsi:nil="true"></Extra-
PV1.52></Extra-
PV1><Extra-
ORC><Extra-
ORC.1>NW</Extra-
ORC.1><Extra-
ORC.2><Extra-
ORC.2.1>19013</Extra-
ORC.2.1><Extra-
ORC.2.2>ALERT</Extra-
ORC.2.2></Extra-
ORC.2><Extra-
ORC.3 xsi:nil="true"></Extra-
ORC.3><Extra-
ORC.4 xsi:nil="true"></Extra-
ORC.4><Extra-
ORC.5>NW</Extra-
ORC.5><Extra-
ORC.6 xsi:nil="true"></Extra-
ORC.6><Extra-
ORC.7 xsi:nil="true"></Extra-
ORC.7><Extra-
ORC.8 xsi:nil="true"></Extra-
ORC.8><Extra-
ORC.9 xsi:nil="true"></Extra-
ORC.9><Extra-
ORC.10 xsi:nil="true"></Extra-
ORC.10><Extra-
ORC.11 xsi:nil="true"></Extra-
ORC.11><Extra-
ORC.12><Extra-
ORC.12.1>4292</Extra-
ORC.12.1><Extra-
ORC.12.2>Martinez</Extra-
ORC.12.2><Extra-
ORC.12.3>Cristina</Extra-
ORC.12.3></Extra-
ORC.12><Extra-
ORC.13 xsi:nil="true"></Extra-
ORC.13></Extra-
ORC><Extra-
OBR><Extra-
OBR.1>1</Extra-
OBR.1><Extra-
OBR.2><Extra-
OBR.2.1>19013</Extra-
OBR.2.1><Extra-
OBR.2.2>ALERT</Extra-
OBR.2.2></Extra-
OBR.2><Extra-
OBR.3 xsi:nil="true"></Extra-
OBR.3><Extra-
OBR.4><Extra-
OBR.4.1>10781</Extra-
OBR.4.1><Extra-
OBR.4.2>M<escape V="XE3"/>o direita, duas incid<escape V="XEA"/>ncias</Extra-
OBR.4.2><Extra-
OBR.4.3>CHVNG</Extra-
OBR.4.3></Extra-
OBR.4><Extra-
OBR.5 xsi:nil="true"></Extra-
OBR.5><Extra-
OBR.6 xsi:nil="true"></Extra-
OBR.6><Extra-
OBR.7 xsi:nil="true"></Extra-
OBR.7><Extra-
OBR.8 xsi:nil="true"></Extra-
OBR.8><Extra-
OBR.9 xsi:nil="true"></Extra-
OBR.9><Extra-
OBR.10 xsi:nil="true"></Extra-
OBR.10><Extra-
OBR.11 xsi:nil="true"></Extra-
OBR.11><Extra-
OBR.12 xsi:nil="true"></Extra-
OBR.12><Extra-
OBR.13 xsi:nil="true"></Extra-
OBR.13><Extra-
OBR.14 xsi:nil="true"></Extra-
OBR.14><Extra-
OBR.15 xsi:nil="true"></Extra-
OBR.15><Extra-
OBR.16><Extra-
OBR.16.1>4292</Extra-
OBR.16.1><Extra-
OBR.16.2>Martinez</Extra-
OBR.16.2><Extra-
OBR.16.3>Cristina</Extra-
OBR.16.3></Extra-
OBR.16><Extra-
OBR.17 xsi:nil="true"></Extra-
OBR.17><Extra-
OBR.18 xsi:nil="true"></Extra-
OBR.18><Extra-
OBR.19 xsi:nil="true"></Extra-
OBR.19><Extra-
OBR.20 xsi:nil="true"></Extra-
OBR.20><Extra-
OBR.21 xsi:nil="true"></Extra-
OBR.21><Extra-
OBR.22 xsi:nil="true"></Extra-
OBR.22><Extra-
OBR.23 xsi:nil="true"></Extra-
OBR.23><Extra-
OBR.24 xsi:nil="true"></Extra-
OBR.24><Extra-
OBR.25 xsi:nil="true"></Extra-
OBR.25><Extra-
OBR.26 xsi:nil="true"></Extra-
OBR.26><Extra-
OBR.27><Extra-
OBR.27.1 xsi:nil="true"></Extra-
OBR.27.1><Extra-
OBR.27.2 xsi:nil="true"></Extra-
OBR.27.2><Extra-
OBR.27.3 xsi:nil="true"></Extra-
OBR.27.3><Extra-
OBR.27.4>20070705161237+0000</Extra-
OBR.27.4></Extra-
OBR.27><Extra-
OBR.28 xsi:nil="true"></Extra-
OBR.28></Extra-
OBR><Extra-
NTE><Extra-
NTE.1>1</Extra-
NTE.1><Extra-
NTE.2 xsi:nil="true"></Extra-
NTE.2></Extra-
NTE><Extra-
DG1><Extra-
DG1.1>1</Extra-
DG1.1><Extra-
DG1.2 xsi:nil="true"></Extra-
DG1.2><Extra-
DG1.3><Extra-
DG1.3.1>9233</Extra-
DG1.3.1><Extra-
DG1.3.2>Contusao De Dedo Da Mao</Extra-
DG1.3.2><Extra-
DG1.3.3>ICD9</Extra-
DG1.3.3></Extra-
DG1.3><Extra-
DG1.4 xsi:nil="true"></Extra-
DG1.4><Extra-
DG1.5 xsi:nil="true"></Extra-
DG1.5><Extra-
DG1.6>D</Extra-
DG1.6></Extra-
DG1></OMG_O19>
I think that the problem should be because of the "Extra" (eg. <Extra-
PID.1 xsi:nil="true">) word that B2B puts in every tag.
The strange thing is that, this already worked until two days ago....
What could it be?
Thanks for your help.
Best Regards,
Nuno FernandesHello,
We have configured a circuit that has the objective of sending a message to B2B and then the ESB dequeues that message from the IP_IN_QUEUE.
The problem is that for some reason, the ESB cannot read message using the AQ Adapter object.
The error is the following:
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
The trace is the following:
ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:139) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1609) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1514) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1447) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1286) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:134) ... 8 more
The Payload is the following:
<?xml version="1.0" ?><OMG_O19 xmlns="urn:oracle:integration:b2b:C023D5B231EF45519AA3D9929B4990E1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.4" CreatedDate="2007-07-17T17:10:43" CreatedBy="ECXEngine_837" GUID="{D16D28B9-3821-4BCC-B4D9-0D92F8611BB5}"><Internal-Properties><Data-Structure Name="Message"><Lookup Name="MessageSendingApp">ALERT</Lookup><Lookup Name="MessageSendingAppUniversalID"></Lookup><Lookup Name="MessageSendingAppUniversalIDType"></Lookup><Lookup Name="MessageSendingFacility">CHVNG</Lookup><Lookup Name="MessageSendingFacilityUniversalID"></Lookup><Lookup Name="MessageSendingFacilityUniversalIDType"></Lookup><Lookup Name="MessageReceivingApp">RADIO</Lookup><Lookup Name="MessageReceivingAppUniversalID"></Lookup><Lookup Name="MessageReceivingAppUniversalIDType"></Lookup><Lookup Name="MessageReceivingFacility">CHVNG</Lookup><Lookup Name="MessageReceivingFacilityUniversalID"></Lookup><Lookup Name="MessageReceivingFacilityUniversalIDType"></Lookup><Lookup Name="MessageCode">OMG</Lookup><Lookup Name="TriggerEvent">O19</Lookup><Lookup Name="MessageStructure">OMG_O19</Lookup><Lookup Name="MessageVersion">2.4</Lookup><Lookup Name="InternatCodeID"></Lookup><Lookup Name="InternatCodeText"></Lookup><Lookup Name="InternatCodeSystem"></Lookup><Lookup Name="InternatCodeAlternateID"></Lookup><Lookup Name="InternatCodeAlternateText"></Lookup><Lookup Name="InternatCodeAlternateSystem"></Lookup><Lookup Name="InternationalVersionID"></Lookup><Lookup Name="InternationalVersionIDText"></Lookup><Lookup Name="InternationalVersionIDSystem"></Lookup><Lookup Name="InternationalVersionIDAlternateID"></Lookup><Lookup Name="InternationalVersionIDAlternateText"></Lookup><Lookup Name="InternationalVersionIDAlternateSystem"></Lookup><Lookup Name="Standard">HL7</Lookup><Property Name="MessageEncodingCharacters">^~\&</Property><Property Name="MessageSendingApp">ALERT</Property><Property Name="MessageSendingAppUniversalID"></Property><Property Name="MessageSendingAppUniversalIDType"></Property><Property Name="MessageSendingFacility">CHVNG</Property><Property Name="MessageSendingFacilityUniversalID"></Property><Property Name="MessageSendingFacilityUniversalIDType"></Property><Property Name="MessageReceivingApp">RADIO</Property><Property Name="MessageReceivingAppUniversalID"></Property><Property Name="MessageReceivingAppUniversalIDType"></Property><Property Name="MessageReceivingFacility">CHVNG</Property><Property Name="MessageReceivingFacilityUniversalID"></Property><Property Name="MessageReceivingFacilityUniversalIDType"></Property><Property Name="MessageDate">20070705161247+0000</Property><Property Name="MessageDateTimePrecision"></Property><Property Name="MessageSecurity"></Property><Property Name="MessageCode">OMG</Property><Property Name="TriggerEvent">O19</Property><Property Name="MessageStructure">OMG_O19</Property><Property Name="MessageControlID">1709</Property><Property Name="ProcessingID">P</Property><Property Name="ProcessingMode"></Property><Property Name="MessageVersion">2.4</Property><Property Name="InternatCodeID"></Property><Property Name="InternatCodeText"></Property><Property Name="InternatCodeSystem"></Property><Property Name="InternatCodeAlternateID"></Property><Property Name="InternatCodeAlternateText"></Property><Property Name="InternatCodeAlternateSystem"></Property><Property Name="InternationalVersionID"></Property><Property Name="InternationalVersionIDText"></Property><Property Name="InternationalVersionIDSystem"></Property><Property Name="InternationalVersionIDAlternateID"></Property><Property Name="InternationalVersionIDAlternateText"></Property><Property Name="InternationalVersionIDAlternateSystem"></Property><Property Name="SequenceNumber"></Property><Property Name="ContinuationPointer"></Property><Property Name="AcceptAckType"></Property><Property Name="AppAckType"></Property><Property Name="CountryCode"></Property><Property Name="CharacterSet"></Property><Property Name="LanguageID"></Property><Property Name="LanguageText"></Property><Property Name="LanguageSystem"></Property><Property Name="LanguageAlternateID"></Property><Property Name="LanguageAlternateText"></Property><Property Name="LanguageAlternateSystem"></Property><Property Name="AlternateCharacterSetSchema"></Property><Property Name="ConformanceStatementID"></Property><Property Name="MessageProfileNamespaceID"></Property><Property Name="MessageProfileUniversalID"></Property><Property Name="MessageProfileUniversalIDType"></Property><Property Name="DecimalSeparator"></Property><Property Name="ElementDelimiter">0x7c</Property><Property Name="ReleaseCharacter">0x5c</Property><Property Name="RepeatingSeparator">0x7e</Property><Property Name="SegmentDelimiter">0xd</Property><Property Name="SubcomponentDelimiter">0x26</Property><Property Name="SubelementDelimiter">0x5e</Property></Data-Structure></Internal-Properties><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>ALERT</HD.1></MSH.3><MSH.4><HD.1>CHVNG</HD.1></MSH.4><MSH.5><HD.1>RADIO</HD.1></MSH.5><MSH.6><HD.1>CHVNG</HD.1></MSH.6><MSH.7><TS.1>20070705161247+0000</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>OMG</MSG.1><MSG.2>O19</MSG.2><MSG.3>OMG_O19</MSG.3></MSH.9><MSH.10>1709</MSH.10><MSH.11><PT.1>P</PT.1></MSH.11><MSH.12><VID.1>2.4</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13></MSH><Extra-
PID><Extra-
PID.1 xsi:nil="true"></Extra-
PID.1><Extra-
PID.2 xsi:nil="true"></Extra-
PID.2><Extra-
PID.3><Extra-
PID.3.1>390971</Extra-
PID.3.1><Extra-
PID.3.2 xsi:nil="true"></Extra-
PID.3.2><Extra-
PID.3.3 xsi:nil="true"></Extra-
PID.3.3><Extra-
PID.3.4>CHVNG</Extra-
PID.3.4><Extra-
PID.3.5>NS</Extra-
PID.3.5></Extra-
PID.3><Extra-
PID.4 xsi:nil="true"></Extra-
PID.4><Extra-
PID.5><Extra-
PID.5.1>Santos</Extra-
PID.5.1><Extra-
PID.5.2>Paula</Extra-
PID.5.2><Extra-
PID.5.3>Cristina Silva Lopes</Extra-
PID.5.3></Extra-
PID.5><Extra-
PID.6 xsi:nil="true"></Extra-
PID.6><Extra-
PID.7>19720117000000+0000</Extra-
PID.7><Extra-
PID.8 xsi:nil="true"></Extra-
PID.8><Extra-
PID.9 xsi:nil="true"></Extra-
PID.9><Extra-
PID.10 xsi:nil="true"></Extra-
PID.10><Extra-
PID.11><Extra-
PID.11.1>R Bernardino Costa 358 Bl D Hab 04</Extra-
PID.11.1><Extra-
PID.11.2 xsi:nil="true"></Extra-
PID.11.2><Extra-
PID.11.3>Valadares</Extra-
PID.11.3><Extra-
PID.11.4 xsi:nil="true"></Extra-
PID.11.4><Extra-
PID.11.5>4405</Extra-
PID.11.5></Extra-
PID.11><Extra-
PID.12 xsi:nil="true"></Extra-
PID.12><Extra-
PID.13 xsi:nil="true"></Extra-
PID.13><Extra-
PID.14 xsi:nil="true"></Extra-
PID.14><Extra-
PID.15 xsi:nil="true"></Extra-
PID.15><Extra-
PID.16 xsi:nil="true"></Extra-
PID.16><Extra-
PID.17 xsi:nil="true"></Extra-
PID.17><Extra-
PID.18>7011588</Extra-
PID.18><Extra-
PID.19 xsi:nil="true"></Extra-
PID.19></Extra-
PID><Extra-
PV1><Extra-
PV1.1 xsi:nil="true"></Extra-
PV1.1><Extra-
PV1.2>URG</Extra-
PV1.2><Extra-
PV1.3><Extra-
PV1.3.1>1</Extra-
PV1.3.1><Extra-
PV1.3.2 xsi:nil="true"></Extra-
PV1.3.2><Extra-
PV1.3.3 xsi:nil="true"></Extra-
PV1.3.3><Extra-
PV1.3.4>CHVNG</Extra-
PV1.3.4></Extra-
PV1.3><Extra-
PV1.4 xsi:nil="true"></Extra-
PV1.4><Extra-
PV1.5 xsi:nil="true"></Extra-
PV1.5><Extra-
PV1.6 xsi:nil="true"></Extra-
PV1.6><Extra-
PV1.7 xsi:nil="true"></Extra-
PV1.7><Extra-
PV1.8 xsi:nil="true"></Extra-
PV1.8><Extra-
PV1.9 xsi:nil="true"></Extra-
PV1.9><Extra-
PV1.10 xsi:nil="true"></Extra-
PV1.10><Extra-
PV1.11 xsi:nil="true"></Extra-
PV1.11><Extra-
PV1.12 xsi:nil="true"></Extra-
PV1.12><Extra-
PV1.13 xsi:nil="true"></Extra-
PV1.13><Extra-
PV1.14 xsi:nil="true"></Extra-
PV1.14><Extra-
PV1.15 xsi:nil="true"></Extra-
PV1.15><Extra-
PV1.16 xsi:nil="true"></Extra-
PV1.16><Extra-
PV1.17 xsi:nil="true"></Extra-
PV1.17><Extra-
PV1.18>URG</Extra-
PV1.18><Extra-
PV1.19><Extra-
PV1.19.1>7088430</Extra-
PV1.19.1><Extra-
PV1.19.2 xsi:nil="true"></Extra-
PV1.19.2><Extra-
PV1.19.3 xsi:nil="true"></Extra-
PV1.19.3><Extra-
PV1.19.4>SONHO</Extra-
PV1.19.4></Extra-
PV1.19><Extra-
PV1.20 xsi:nil="true"></Extra-
PV1.20><Extra-
PV1.21 xsi:nil="true"></Extra-
PV1.21><Extra-
PV1.22 xsi:nil="true"></Extra-
PV1.22><Extra-
PV1.23 xsi:nil="true"></Extra-
PV1.23><Extra-
PV1.24 xsi:nil="true"></Extra-
PV1.24><Extra-
PV1.25 xsi:nil="true"></Extra-
PV1.25><Extra-
PV1.26 xsi:nil="true"></Extra-
PV1.26><Extra-
PV1.27 xsi:nil="true"></Extra-
PV1.27><Extra-
PV1.28 xsi:nil="true"></Extra-
PV1.28><Extra-
PV1.29 xsi:nil="true"></Extra-
PV1.29><Extra-
PV1.30 xsi:nil="true"></Extra-
PV1.30><Extra-
PV1.31 xsi:nil="true"></Extra-
PV1.31><Extra-
PV1.32 xsi:nil="true"></Extra-
PV1.32><Extra-
PV1.33 xsi:nil="true"></Extra-
PV1.33><Extra-
PV1.34 xsi:nil="true"></Extra-
PV1.34><Extra-
PV1.35 xsi:nil="true"></Extra-
PV1.35><Extra-
PV1.36 xsi:nil="true"></Extra-
PV1.36><Extra-
PV1.37 xsi:nil="true"></Extra-
PV1.37><Extra-
PV1.38 xsi:nil="true"></Extra-
PV1.38><Extra-
PV1.39 xsi:nil="true"></Extra-
PV1.39><Extra-
PV1.40 xsi:nil="true"></Extra-
PV1.40><Extra-
PV1.41 xsi:nil="true"></Extra-
PV1.41><Extra-
PV1.42 xsi:nil="true"></Extra-
PV1.42><Extra-
PV1.43 xsi:nil="true"></Extra-
PV1.43><Extra-
PV1.44>20070705154838+0000</Extra-
PV1.44><Extra-
PV1.45 xsi:nil="true"></Extra-
PV1.45><Extra-
PV1.46 xsi:nil="true"></Extra-
PV1.46><Extra-
PV1.47 xsi:nil="true"></Extra-
PV1.47><Extra-
PV1.48 xsi:nil="true"></Extra-
PV1.48><Extra-
PV1.49 xsi:nil="true"></Extra-
PV1.49><Extra-
PV1.50 xsi:nil="true"></Extra-
PV1.50><Extra-
PV1.51>V</Extra-
PV1.51><Extra-
PV1.52 xsi:nil="true"></Extra-
PV1.52></Extra-
PV1><Extra-
ORC><Extra-
ORC.1>NW</Extra-
ORC.1><Extra-
ORC.2><Extra-
ORC.2.1>19013</Extra-
ORC.2.1><Extra-
ORC.2.2>ALERT</Extra-
ORC.2.2></Extra-
ORC.2><Extra-
ORC.3 xsi:nil="true"></Extra-
ORC.3><Extra-
ORC.4 xsi:nil="true"></Extra-
ORC.4><Extra-
ORC.5>NW</Extra-
ORC.5><Extra-
ORC.6 xsi:nil="true"></Extra-
ORC.6><Extra-
ORC.7 xsi:nil="true"></Extra-
ORC.7><Extra-
ORC.8 xsi:nil="true"></Extra-
ORC.8><Extra-
ORC.9 xsi:nil="true"></Extra-
ORC.9><Extra-
ORC.10 xsi:nil="true"></Extra-
ORC.10><Extra-
ORC.11 xsi:nil="true"></Extra-
ORC.11><Extra-
ORC.12><Extra-
ORC.12.1>4292</Extra-
ORC.12.1><Extra-
ORC.12.2>Martinez</Extra-
ORC.12.2><Extra-
ORC.12.3>Cristina</Extra-
ORC.12.3></Extra-
ORC.12><Extra-
ORC.13 xsi:nil="true"></Extra-
ORC.13></Extra-
ORC><Extra-
OBR><Extra-
OBR.1>1</Extra-
OBR.1><Extra-
OBR.2><Extra-
OBR.2.1>19013</Extra-
OBR.2.1><Extra-
OBR.2.2>ALERT</Extra-
OBR.2.2></Extra-
OBR.2><Extra-
OBR.3 xsi:nil="true"></Extra-
OBR.3><Extra-
OBR.4><Extra-
OBR.4.1>10781</Extra-
OBR.4.1><Extra-
OBR.4.2>M<escape V="XE3"/>o direita, duas incid<escape V="XEA"/>ncias</Extra-
OBR.4.2><Extra-
OBR.4.3>CHVNG</Extra-
OBR.4.3></Extra-
OBR.4><Extra-
OBR.5 xsi:nil="true"></Extra-
OBR.5><Extra-
OBR.6 xsi:nil="true"></Extra-
OBR.6><Extra-
OBR.7 xsi:nil="true"></Extra-
OBR.7><Extra-
OBR.8 xsi:nil="true"></Extra-
OBR.8><Extra-
OBR.9 xsi:nil="true"></Extra-
OBR.9><Extra-
OBR.10 xsi:nil="true"></Extra-
OBR.10><Extra-
OBR.11 xsi:nil="true"></Extra-
OBR.11><Extra-
OBR.12 xsi:nil="true"></Extra-
OBR.12><Extra-
OBR.13 xsi:nil="true"></Extra-
OBR.13><Extra-
OBR.14 xsi:nil="true"></Extra-
OBR.14><Extra-
OBR.15 xsi:nil="true"></Extra-
OBR.15><Extra-
OBR.16><Extra-
OBR.16.1>4292</Extra-
OBR.16.1><Extra-
OBR.16.2>Martinez</Extra-
OBR.16.2><Extra-
OBR.16.3>Cristina</Extra-
OBR.16.3></Extra-
OBR.16><Extra-
OBR.17 xsi:nil="true"></Extra-
OBR.17><Extra-
OBR.18 xsi:nil="true"></Extra-
OBR.18><Extra-
OBR.19 xsi:nil="true"></Extra-
OBR.19><Extra-
OBR.20 xsi:nil="true"></Extra-
OBR.20><Extra-
OBR.21 xsi:nil="true"></Extra-
OBR.21><Extra-
OBR.22 xsi:nil="true"></Extra-
OBR.22><Extra-
OBR.23 xsi:nil="true"></Extra-
OBR.23><Extra-
OBR.24 xsi:nil="true"></Extra-
OBR.24><Extra-
OBR.25 xsi:nil="true"></Extra-
OBR.25><Extra-
OBR.26 xsi:nil="true"></Extra-
OBR.26><Extra-
OBR.27><Extra-
OBR.27.1 xsi:nil="true"></Extra-
OBR.27.1><Extra-
OBR.27.2 xsi:nil="true"></Extra-
OBR.27.2><Extra-
OBR.27.3 xsi:nil="true"></Extra-
OBR.27.3><Extra-
OBR.27.4>20070705161237+0000</Extra-
OBR.27.4></Extra-
OBR.27><Extra-
OBR.28 xsi:nil="true"></Extra-
OBR.28></Extra-
OBR><Extra-
NTE><Extra-
NTE.1>1</Extra-
NTE.1><Extra-
NTE.2 xsi:nil="true"></Extra-
NTE.2></Extra-
NTE><Extra-
DG1><Extra-
DG1.1>1</Extra-
DG1.1><Extra-
DG1.2 xsi:nil="true"></Extra-
DG1.2><Extra-
DG1.3><Extra-
DG1.3.1>9233</Extra-
DG1.3.1><Extra-
DG1.3.2>Contusao De Dedo Da Mao</Extra-
DG1.3.2><Extra-
DG1.3.3>ICD9</Extra-
DG1.3.3></Extra-
DG1.3><Extra-
DG1.4 xsi:nil="true"></Extra-
DG1.4><Extra-
DG1.5 xsi:nil="true"></Extra-
DG1.5><Extra-
DG1.6>D</Extra-
DG1.6></Extra-
DG1></OMG_O19>
I think that the problem should be because of the "Extra" (eg. <Extra-
PID.1 xsi:nil="true">) word that B2B puts in every tag.
The strange thing is that, this already worked until two days ago....
What could it be?
Thanks for your help.
Best Regards,
Nuno Fernandes -
DOM Parsing Exception in translator. Dequeuing is failing
Hi,
-> I am working on EDI HIPPA File Protocol.
-> My b2b configuration is working. I am getting the payload xml in IP_IN_QUEUE.
But ESB with AQAdaptor is failing giving the below Exception.
-> ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:202) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: Expected name instead of >. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1151) at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1928) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1276) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:197)
-> I have taken the payload xml from rejectedMessages folder from SOA HOME and written a DOM Parser program
to parse that file.It is throwing org.xml.sax.SAXParseException.
-> I validated this xml with xsd I provide both in Oracle B2b config and in ESB using Altova software, it is throwing errors saying the xml is not valid.
-> So I understood that xml which is gettign generated is not the valid one.
Could you please tell me if I have to make any changes.
Thanks
PraveenaHi Dheeraj,
I did this, I have selected Oracle Integration B2B while generating the xsd, then saved the xsd and then saved ecs.
I gave these ecs and xsd file in my Oracle B2B configruation for Document protocol page.
Then also, I parsed the file which is generated.It is failing in parsing.
I can see that set of empty tags <></> are getting generated before <Segment-SE> tag and after <Loop-2000> as shown below:
</Loop-2100></Loop-2000><></><Segment-SE><Element-96>
(I don't why I am able to see symbols for tags when I am editing this message but once I save the message it is not shown in the forum.actually empty tags are getting geneated.)
I removed these empty tags and parsed it again, then it is parsed successfully.
Could you please tell me what I need to do for not generating these extra empty tags.
my xsd looks as below(pastign for this particular part:
<xsd:element name="Transaction-835">
<xsd:annotation>
<xsd:documentation>Health Care Claim Payment/Advice</xsd:documentation>
<xsd:documentation>This Draft Standard for Trial Use contains the format and establishes the data contents of the Health Care Claim Payment/Advice Transaction Set (835) for use within the context of the Electronic Data Interchange (EDI) environment. This transaction set can be used to make a payment, send an Explanation of Benefits (EOB) remittance advice, or make a payment and send an EOB remittance advice only from a health insurer to a health care provider either directly or via a financial institution.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Internal-Properties" minOccurs="0"/>
<xsd:element ref="Segment-ST"/>
<xsd:element ref="Segment-BPR"/>
<xsd:element ref="Segment-TRN"/>
<xsd:element ref="Segment-REF" minOccurs="0"/>
<xsd:element ref="Segment-DTM" minOccurs="0"/>
<xsd:choice maxOccurs="2" minOccurs="2">
<xsd:element ref="Loop-1000A"/>
<xsd:element ref="Loop-1000B"/>
</xsd:choice>
<xsd:element ref="Loop-2000" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Segment-SE"/>
</xsd:sequence>
<xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
<xsd:attribute name="XDataVersion" fixed="1.0" type="xsd:string"/>
<xsd:attribute name="Standard" fixed="HIPAA" type="xsd:string"/>
<xsd:attribute name="Version" default="V4010X091A1" type="xsd:string"/>
<xsd:attribute name="GUID" default="" type="xsd:string"/>
<xsd:attribute name="CreatedBy" type="xsd:string"/>
<xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
Edited by: Praveena Paruchuru on Mar 10, 2009 6:33 AM
Edited by: Praveena Paruchuru on Mar 10, 2009 6:49 AM -
DOM Parsing Exception in translator
Hi
We are hitting one issue in B2B/SOA 11g.
BPEL instance is not getting created in 11g. Messages are picked from B2B queue and BPEL is failing while dequeing.
It says that
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Please make sure that the xml data is valid.
Is it due to large size of the message. I have seen the message size and it is more than 3 MB.
Pls help
Thanks
SimarjeetHi Anuj
I have analysed the issue in detail. B2B is not generating the payload for one of the message so dequeue is failing and message is rejected.
Say in one EDI file, we have 6 messages then B2B is able to create 6 separate messages while debatching but one of the message payload is empty. Error in log is
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
at oracle.tip.adapter.aq.v2.database.MessageConverter.translateMessageBytes(MessageConverter.java:510)
at oracle.tip.adapter.aq.v2.database.MessageConverter.getSTRUCTPayload(MessageConverter.java:404)
at oracle.tip.adapter.aq.v2.database.MessageConverter.getPayload(MessageConverter.java:139)
at oracle.tip.adapter.aq.v2.database.XMLRecordMessageConverter.getRecord(XMLRecordMessageConverter.java:88)
at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.getInputRecord(AbstractDequeueAgent.java:236)
at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.run(AbstractDequeueAgent.java:101)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: ORABPEL-11211
DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:607)
at oracle.tip.adapter.aq.v2.database.MessageConverter.translateMessageBytes(MessageConverter.java:506)
... 8 more
Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:380)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:321)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:601)
... 9 more
I have also tested the file using various modes unix/pc and ansi/utf-8 encoding. Is this issue related with performance tuning, tablespace etc? -
Hi all
Can anyone plz provide me a good technical documentation(except the Config guide and Installation guide from SAP)on mySAP CRM E-service?
Thanks and regards
DebolinaHello Everybody,
please have a look to the Topic Brainstorming Discussion - Links to CRM Documentation. There you find direct links to the documentation you've requested. Because the information is avaliable there I will close this thread.
Regards
Gregor -
I'm using the following code to retrieve order list is working fine but it give me an error Server was unable to process request ERROR: A server error has occurred when I trying to retrieve order total paid with same code: and the output when retrieve order total paid is [object Object]
var wsUrl = "https://mysite.worldsecuresystems.com/CatalystWebService/CatalystCRMWebservice.asmx?WSDL";
var RetrieveTotalPaidXML =
'<?xml version="1.0" encoding="utf-8"?>\
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">\
<soap12:Body>\
<Order_RetrieveTotalPaid xmlns="http://tempuri.org/CatalystDeveloperService/CatalystCRMWebservice">\
<username>user</username>\
<password>pass</password>\
<siteid>111222</siteid>\
<orderId>112345</orderId>\
</Order_RetrieveTotalPaid>\
</soap12:Body>\
</soap12:Envelope>';
$.ajax({
type: "POST",
url: wsUrl,
Host: "mysite.worldsecuresystems.com",
contentType: "application/soap+xml; charset=utf-8",
data: RetrieveTotalPaidXML,
dataType: "xml",
success: processSuccess,
error: function(){alert("Error: Something went wrong");}
function processSuccess(ResData) {
var RetrieveTotalPaidParse = $.parseXML(ResData);
var $xmlRetrieveTotalPaidParse = $(RetrieveTotalPaidParse);
var $Order_RetrieveTotalPaidResult = $xmlRetrieveTotalPaidParse.find('Order_RetrieveTotalPaidResult');
$Order_RetrieveTotalPaidResult = $(this).find('Order_RetrieveTotalPaidResult').text();
$('#RetrieveTotalPaidResult').text(Order_RetrieveTotalPaidResult);
I think there a bug in BC CRM Web Service when trying to make a request for Order_RetrieveTotalPaid using soap need to be fixPerhaps it would be good to update the sample request as shown on the Developer reference page for this method (and, actually ALL of the SOAP samples)
The sample shows siteid (all lower case) -
While consuming Fusion CRM web service in ADF mobile throwing an error
Hi,
I am developing ADF Mobile using JDeveloper
11.1.2.3 and consuming Fusion CRM ADF Web Services.
While executing CRUD operations with these web services
in ADF mobile app, I am getting SOAP response as *Error in getting response
and got result nothing *.
And also noticed as using JDeveloper ADF mobile App, unable to create URL service
Data Control - REST based for FUsion CRM web services. Where as I am able to
create SOAP based web services data control. It' strange or surprise.
Did anyone face the above problems. Kindly let me know any suggestions or
samples to the below contacts
Regards
Bhaskara Reddy S
00919008466722
bhaskara.sannapureddy at Crmit.comDear Frank,
Based on below links, Fusion CRM also supports REST also apart from regular SOAP Web Services.
http://niallcblogs.blogspot.in/2012/10/204-calling-rest-service-from-fusion-crm.html AND
http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e20388/F412758AN17B21.htm
(For e.g one of linked in profile :http://www.linkedin.com/in/minalkhodani , many teams are developing using SOAP & REST)
Designed and developed integration services using SOAP and REST web services for Oracle Fusion CRM Marketing Modules.)
When creating URL based data control, getting an Error as "Forbidden" , (Does it mean NOT SUPPORTED??) . Kindly advice.
I am calling WEB SERVICE thru SOAP in AMX PAGE code as below after creating Web Services Data Control from ADF Mobile UI thru JDeveloper IDE.
== CODE SNIPPET OF AMX PAGE CALLING SOAP FUSION CRM WEB SERVICE =======
<?xml version="1.0" encoding="UTF-8" ?>
<amx:view xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:amx="http://xmlns.oracle.com/adf/mf/amx"
xmlns:dvtm="http://xmlns.oracle.com/adf/mf/amx/dvt">
<amx:panelPage id="pp1">
<amx:panelFormLayout id="pfl2">
<amx:inputText value="#{bindings.name.inputValue}" label="Person First Name" id="it1"/>
<amx:inputText value="300000001210220" label="Person Object Id" id="it2"/>
</amx:panelFormLayout>
<amx:facet name="header">
<amx:outputText value="Create Person in Fusion CRM" id="ot1"/>
</amx:facet>
<amx:facet name="primary">
<amx:commandButton id="cb1" text="Back" action="__back"/>
</amx:facet>
<amx:facet name="secondary">
<amx:commandButton id="cb2"/>
</amx:facet>
<amx:panelFormLayout id="pfl1">
</amx:panelFormLayout>
<amx:outputText value="#{bindings.message.inputValue}" id="ot2"/>
<amx:outputText value="#{bindings.code.inputValue}" id="ot3"/>
*<amx:commandButton actionListener="#{bindings.createPerson.execute}" text="createPerson"*
*disabled="#{!bindings.createPerson.enabled}" id="cb3"/>*
<amx:iterator var="row" value="#{bindings.personParty1.collectionModel}" id="i1">
<amx:panelLabelAndMessage label=" 300000001210220" id="plam2">
<amx:outputText value="#{row.PartyId}" id="ot5">
<amx:convertNumber groupingUsed="false"/>
</amx:outputText>
</amx:panelLabelAndMessage>
<amx:panelLabelAndMessage label="#{bindings.name.inputValue}" id="plam1">
<amx:outputText value="#{row.PersonFirstName}" id="ot4"/>
</amx:panelLabelAndMessage>
</amx:iterator>
</amx:panelPage>
</amx:view>
Regards
Bhaskara Reddy -
Batch Management in CRM 2007 Service Transactions
Dear SAP colleagues,
I am dealing with a CRM 2007 Service project, and there is a question that has been in my mind for a while.
As far as I know, it is possible to manage product batches in CRM Sales. In fact, the field is standard delivered, and there are a couple of BADIs in SPRO, under Sales Transactions. But when talking about CRM Service, I can`t find any documentation about batch management anywhere, nor the possibility of configuring the functionality.
May anybody give me some light about this issue please?
Thanks in advance.
Pablo RMHi Rupesh,
thank you very much for your answer, but shall I understand that batch must be specified in ECC and cannot be recorded in CRM (in stardad logic)?
Let me explain you a bit more about our needs: we have products with batch numbers that can only be repaired with spare parts with same batch number, since they come from the same manufacturing batch. When defective products arrive to be repaired (we will use In-house repair orders to cope with this) and their batch numbers are identified, there should be an availability check of the spare parts needed considering their batches, just the same way as it is done in CRM Sales for products. As you say, once it has been released, the reservation is made in ECC.
I suposse that there's no solution but a custom development.
Well, thank you again and good bye.
Pablo -
Need to suppress Windows Security dialog when connecting to CRM WCF service from application
I am currently developing a Windows desktop application that uses the CRM WCF service as a data source. The CRM environment uses AD authentication. The problem I have is that our domain enforces a password expiration policy, so every three months each user's
CRM password changes, and the one stored for the user (in encrypted form) in the application becomes invalid.
When that happens, after logging into the application, the user is presented with a Windows Security dialog asking them to enter their network user credentials. If they do so the first time, they're asked up to a dozen more times, to authenticate a bunch
of OrgServiceProxy objects in a pool. This is confusing, frustrating, and dangerous from a security mindset (don't want the user getting too comfortable entering network credentials into every dialog that asks). I want to suppress this popup, and instead have
the CRM authentication immediately throw the SecurityNegotiationException I'm expecting if the credentials passed are wrong. The app will catch that and direct the user to the User Maintenance screen where they can update their credentials.
I know it's possible to put the site in a zone with custom security settings suppressing this prompt, but Group Policy to do that is kind of heavy-handed and could have unintended consequences. I would prefer a programmatic "quick fix" for now,
until we can re-architect the application's security layer to do all authentication against AD.
Thanks.Hi friend,
This forum is to discuss problems of C# development. Your question is not related to the topic of this forum.
You'll need to post it in the dedicated ASP.Net Forum
http://forums.asp.net for more efficient responses, where you
can contact ASP.NET experts. Thanks for understanding.
Have a nice day!
Kristin -
Parse Exception : java.text.ParseException: Unparseable date
I have inherited a UDF in some mapping that on the whole, works okay...
but it throws an error after mapping a few dates:
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
the first few map okay... then i get the exception.
the UDF is as follows:
public String convertDateTimeToUTC(String strDate, Container container) throws StreamTransformationException{
AbstractTrace trace = container.getTrace();
Date date=null;
SimpleDateFormat sdfSource = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZ");
try{
String dt = strDate;
date = sdfSource.parse(dt);
trace.addInfo("Local Date:"+date);
SimpleDateFormat sdfDestination = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss");
strDate = sdfDestination.format(date);
catch(ParseException pe){
trace.addInfo("Parse Exception : " + pe);
return strDate;
can anyone see why this fails after successfully mapping a few fields???the first mapping works correctly...
then we reuse the same fields to map to the additional segments.
the context is correct as it is trying to pull the same fields in... it just throw the error with the same data in the same UDF/Function Library but for different segments! :o(
http://img199.imageshack.us/img199/3104/dateconversion.jpg
as you can see from the screenshot above, the mapping works in the first instance, then fails on subsequent nodes. -
Getting DOM Parsing Exception in translator while Dequeuing the message from JMS topic
Hi All,
Hope you all doing good.
I have an issue.
I am running on 11.1.1.5 SOA suite version on Linux.
In my aplication I have 4 projects which are connected by with topic/queue.
But in one of the communication, the JMS topic throws me the below error in the log, but dequeue happend perfectly fine and the application runs smoothly.
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project1>
JmsConsumer_sendInboundMessage:[des
tination = <TOPIC NAME> subscriber = <Consumer project name>
Error (DOM Parsing Exception in translator.[[
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
) while preparing to send XMLRecord JmsXMLRecord
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project name>
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:603)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:403)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1161)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1048)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
But when I try putting the archived data on this topic, it throws me the same error but even dequeuing doesnt happen.
I have extracted the payload and validated against the xsd, it looks fine and even the validator doesnt throw me any error.
But I guess I am missing something, which I am immediately not getting.
Please let me know, if I am soemthing here which is causing this erro.
Thanks,
ChandruI searched about this error, but no luck.
First time when the message dequeues, the consumer can consume the message but throws the error in the log.
But when I put the message back into queue from archive directory, the consumer doesnt consume message and throws me the same error.
Does anyone faced this sort of issue.
I checked my xsd throughly, and validated it externally. but didnt fine any error.
if anyone knows, suggest me how to resolve this issue.
thanks & regards
Chandru -
'Import file parsing exception' while importing BIAR file
Hi All,
We use Java WebServices SDK for integrating our product with Business Objects. For installing the reports we use the InstallEntSDKWrapper jar to copy the BIAR file containing the reports on to the BO server. Till now we were using BO XI R2 and everything works fine.
But now we have decided to upgrade to BO 3.0 and the reports install no longer works. Here is the error that we get -
[InstallEntSdkWrapper.main] Connecting to CMS rwc-1950-120:6400 as administrator
[InstallEntSdkWrapper.CmsImportFile] Exception: Import file parsing exception
curred : 'Type info incomplete'
[InstallEntSdkWrapper.main] BIAR File could not be imported
Any idea what might be going wrong here? We are trying to import the same BIAR file that were created with the earlier BO version to the 3.0 version server. Couple of questions that I have is -
1. Do we need to repackage the BIAR with 3.0 before attempting to install it? Are there any issues with trying to install a BIAR which is of older BO version?
2. Do we need to add/modify any library (jar) in the runtime to get rid of the exception?
Thanks for all the help.
Regards
Manas
Edited by: Manas Mandlekar on Dec 23, 2009 1:34 AMLucas,
I have not seen this issue before. We'll investigate and contact you directly for more info. I'll post the resolution back to this forum once available.
Doug
Maybe you are looking for
-
Hi, I am holding float value in a variable which i want to convert it into float again. Help Will be rewarded
-
Adobe Reader XI freezes when saving in Windows 8.1
I'm trying to update the editable fields in the US Federal tax forms using Adobe Reader XI on Windows 8.1 (PC - not a tablet). I'm up-to-date on all Windows softward and Adobe Reader software. I could save the original file downloaded from the irs.g
-
T6060 possible problem/error of production...Central speaker is weaker and faded than the others
I just noticed on my recently bought t6060 that the center speaker sounds weaker and faded compared to the other satellites. what might be the problem? i know that the center speaker is intended for voice reproduction in 5.1 streams. On dvd playback
-
I have downloaded a plug-in from a third party for books, but can'rt figure how to get it installed or to use it. Graphicstudio is the download
-
SGA Sizing + OEM Issue+AWR reports
Hi Techies, There is small application(Billing Application) running on Laptop. (Windows Vista 32 bit , RDBMS 10.2.0.3.0.) 1- We have increased the SGA_MAX_SIZE. Thought of Increase 700 M. Once we did the changes it has taken effect as 702 MB Allocate