JAXB 1.3 can't parse W3 SOAP 2003-05 envelope XML schema

Hello,
I was trying to use JAXB to parse the MMAP schema from the SMS Forum
(http://www.smsforum.net/schemas/mmap/v1.0/mmap.xsd). I finally
tracked it down to XJC choking on the included SOAP envelope schema's
use of the xml:lang attribute for a tag called reasontext. Here's the
pared-down test case:
C:\java\src\baz>%JWSDP_HOME%\jaxb\bin\xjc.bat http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
%JWSDP_HOME%\jaxb\bin\xjc.bat http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'xml:lang' to a(n) attribute declaration component.
  line 97 of soap-envelope.xsd
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'reasontext'.  Element 'attribute' is invalid, misplaced, or occurs too often.
  line 97 of soap-envelope.xsd
Failed to parse a schema.
C:\java\src\baz>I believe that the relevant portions of the schemas and namespaces in
question are:
http://www.w3.org/2003/05/soap-envelope/soap-envelope.xsd
<xs:complexType name="reasontext">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang" use="required" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>http://www.w3.org/2001/XMLSchema.xsd
<xs:complexType name="attribute" mixed="false">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:element name="simpleType" minOccurs="0" type="xs:localSimpleType" />
</xs:sequence>
<xs:attributeGroup ref="xs:defRef" />
<xs:attribute name="type" type="xs:QName" />
<xs:attribute name="use" use="optional" default="optional">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="prohibited" />
<xs:enumeration value="optional" />
<xs:enumeration value="required" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="default" type="xs:string" />
<xs:attribute name="fixed" type="xs:string" />
<xs:attribute name="form" type="xs:formChoice" />
</xs:extension>
</xs:complexContent>
</xs:complexType>http://www.w3.org/2001/XMLSchema.xsd
<xs:attributeGroup name="defRef">
<xs:annotation>
<xs:documentation>for element, group and attributeGroup, which both define and reference</xs:documentation>
</xs:annotation>
<xs:attribute name="name" type="xs:NCName" />
<xs:attribute name="ref" type="xs:QName" />
</xs:attributeGroup>http://www.w3.org/XML/1998/namespace
The namespace whose name is http://www.w3.org/XML/1998/namespace is
bound by definition to the prefix xml: according to Namespaces in XML,
W3C Recommendation 14 Jan 1999. Note that unlike all other XML
namespaces, both the name and the prefix are specified; i.e., if you
want XML 1.0 processors to recognize this namespace, you must use the
reserved prefix xml:.
xml:lang and xml:space
As of the last update of this document, the XML 1.0 Specification
defines two attribute names in this namespace:
xml:lang
Designed for identifying the human language used in the scope of the
element to which it's attached.
.I'm no XML schema expert, but it looks to me like "name" and "ref"
are both valid attributes for an <xs:attribute> tag and that the XML
namespace standard requires XML processors to recognize the xml:lang
attribute. Hence, this appears to me to be a bug in JAXB.
A secondary bug is that the original error message left the name of
the offending included schema blank:
C:\java\src\foo>d:\java\jwsdp\jwsdp-1.3\jaxb\bin\xjc.bat http://www.smsforum.net/schemas/mmap/v1.0/mmap.xsd
parsing a schema...
[ERROR] src-resolve: Cannot resolve the name 'xml:lang' to a(n) attribute declaration component.
  line 97 of
[ERROR] src-ct.0.1: Complex Type Definition Representation Error for type 'reasontext'.  Element 'attribute' is invalid, misplaced, or occurs too often.
  line 97 of
Failed to parse a schema.
C:\java\src\foo>In case it helps with problem diagnosis, I'm running with J2SDK 1.4.2
and have copied the endorsed jar files into the JRE lib as instructured
with JAXB:
C:\java\src\baz>java -version
java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
C:\java\src\baz>dir %JAVA_HOME%\jre\lib\endorsed
dir %JAVA_HOME%\jre\lib\endorsed
Volume in drive D has no label.
Volume Serial Number is 70AE-6E52
Directory of D:\java\j2se\j2sdk1.4.2\jre\lib\endorsed
03/31/2004  09:41 AM    <DIR>          .
03/31/2004  09:41 AM    <DIR>          ..
03/29/2004  01:28 PM            56,619 dom.jar
03/29/2004  01:28 PM            60,963 sax.jar
03/29/2004  01:28 PM         2,823,241 xalan.jar
03/29/2004  01:28 PM         2,667,618 xercesImpl.jar
10/10/2003  06:36 PM         1,379,810 xsltc.jar
               6 File(s)      6,989,573 bytes
               2 Dir(s)   7,889,731,584 bytes free
C:\java\src\baz>I'm quite interested in the resolution of this issue as I'm stopped in
my tracks on progress here. Help with resolution, whether in JAXB or
my usage of it, will be much appreciated. I did a search of existing
issues but didn't notice a duplicate. Thanks in advance.

I have also come across a similar problem with validating an xml file with an xml:lang attribute. It seems to be common across the schema validation and dtd validation. I get the following error with both schema and dtd validation:
Validation Error Msg (0): unexpected attribute "xml:lang"
Validation Error Location (0): FreeFormText
The test file extract looks like this:
<FreeFormText xml:lang="EN">Pelle</FreeFormText>
The schema defines the node as:
<xs:complexType name="FreeFormText">
          <xs:simpleContent>
               <xs:extension base="FreeFormTextType">
                    <xs:attribute name="lang" type="xs:language"/>
               </xs:extension>
          </xs:simpleContent>
</xs:complexType>
and the dtd defines the node as:
<!ELEMENT FreeFormText
     (#PCDATA)>
<!ATTLIST FreeFormText xml:lang CDATA #IMPLIED >
This looks like a bug in JAXB to me aswell. Any help on it would be much appreciated as i am also stuck.

Similar Messages

  • Can castor retrieve the comnstraints provided in an xml schema

    hi,
    plz help me !!!!!!!!!!!
    does castor provide any function to retrieve the constraints
    defined in an xsd
    i know it provides functions for setting the constraints
    can i retrieve the value of constraints fromthe descriptor files returned by cator
    while unmarshalling the xsd file .
    thaks

    Hi 00ps, the way to do this with XSD schemas is to use a "choice" node, where you can select either BusinessEntity or Person.  Each of these nodes can then have different elements (inherited from a common source if you desire).
    Whilst doing all this is entirely possible with the BizTalk schema editor, it is far, far easier to use a specialist tool such as
    XMLSpy, which makes defining complex relationships an easy task.  For example, here is a similar sort of restriction I have in place on a schema:
    The "party" element is used in multiple schemas through the use of an import.  You can either use
    organisation or individual, they both use a common element called
    contact which contains address information etc which would be the same for both, but allow for different structures for party types.
    As you can see from the screen-shot, it's a lot easier to visualise with XML Spy.  The XSD notation is:
    <xs:choice>
    <xs:element name="organisation">
    ...blah...
    </xs:element>
    <xs:element name="individual">
    ...blah...
    </xs:element>
    </xs:choice>
    If this is helpful or
    answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)

  • Is There An XML Schema Parser From Oracle ?

    Is XML parser available from oracle different from Xml Schema parser ? Is schema parser available at all ? Where can I download it ? I tried a brief search and could not find ?
    Help appreciated.
    Thanx
    Soorya

    Thank you. I got it. I am trying to validate against an existing schema. But it always enters the "XMLParseException" handler.
    Could you direct me to the documents which gives some examples ? or a 3 lines to validate would be helpful.
    Thanx again.
    Soorya
    null

  • Can't parse WSDL when useProxy=true

    Hello everyone.
    I'm using Flex since 1.5 and now try to migrate Flex2.0.
    Most of our application need to access data via WebService,
    and we use <mx:WebService> tag to access them.
    In our Flex1.5 environment, we also use Proxy service of Flex
    (with specifying useProxy=true), and it works fine.
    But in Flex2.0, our mxml application can't parse the same
    WSDL when useProxy=true!
    On the other hand, our application can parse correctly when
    not using proxy service. (useProxy=false and set crossdomain.xml on
    the root of datasource Web server.)
    I'was so confusing that I captured HTTP traffic between
    client application and server( both FlexDataService and Data source
    Web Server), with ServiceCapture.
    When useProxy=true, at first, client application sent request
    to Flex Data Service to get not only calling the SOAP operations
    but also calling WSDL itself. After that, Flex Data Service
    returned the response message as WSDL data, and I found the WSDL
    data was broken.
    When useProxy=false, of cource, the WSDL was passed
    datasource Web Server correctly and application could parse it
    without problem.
    These parse error depends on the WebService.
    I wonder this is some bug of Flex Data Service or not.......

    Hello, everyone.
    After that, I tried to change the encoding of WSDL, which was
    broken when useProxy=true, from UTF-16 to UTF-8.
    And I could get correct WSDL data from Flex Data Service's
    proxy.....
    It seems when the encoding of WSDL is UTF-16, the parse is
    failed, but I'm not sure this problem is happened commonly and this
    is some of the bug of Flex Data Services.

  • Parse a soap envelope

    I have a SOAP response envelope that I am trying to parse using extractvalue.
    The response is stored in a xmltype field in a table.
    Table
    create table ws_results
    (x xmltype);SOAP Response
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
         <s:Header>
              <ActivityId CorrelationId="12855f8e-d2be-40c7-81d8-fafa3cf9a779" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">d24174d3-e095-460a-b9f8-2bae66efe813</ActivityId>
         </s:Header>
         <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
              <FetchResponse xmlns="urn: WA.Ecy.ADS.FacilitySite.Services">
                   <FacilitySiteId>99997167</FacilitySiteId>
              </FetchResponse>
         </s:Body>
    </s:Envelope>Here is the SQL that I attempting to use to get the Facility Site ID out
    select extractvalue(x,'/FetchResponse/FacilitySiteId') from ws_results;
    select extractvalue(x,'/FetchResponse/FacilitySiteId','xmlns="http://microsoft.com/wsdl/types/"')
    from ws_resultsThese returns a null.
    Seems like this should be pretty straightforward and I am sure that I am missing something small. Any help would be appreciated.
    Thanks, Tony

    The problem seems to be (at least with me testing) is the xmlns="urn: WA.Ecy.ADS.FacilitySite.Services". Oracle considers it invalid xpath. If it is replaced with "http://www.ms.com/xml", then it seems OK with xpath. You can test this:
    declare
         ---v_xmlText          clob ;      ---varchar2(32765);
         v_xmlText          sys.xmltype;
         v_FacID               varchar2(50) := null;
         v_FacilitySiteId     varchar2(50) := null;
         v_FacilitySiteName     varchar2(50) := null;
    begin
         v_xmlText := sys.xmlType('
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
         <s:Header>
              <ActivityId CorrelationId="48538673-36c0-4f6d-8c05-94b753d0e3ab"
              xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">
              b4af9688-a929-4b9f-a187-fb68f3927240
              </ActivityId>
         </s:Header>
         <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema">
              <FacilitySiteResponse xmlns="http://www.ms.com/xml">
                   <FacilitySiteEntity>
                        <Id>99997167</Id>
                        <FacilitySiteId>99997167</FacilitySiteId>
                        <FacilitySiteName>My New Test Facility</FacilitySiteName>
                        <FacilitySiteKeySearchName>My New Te</FacilitySiteKeySearchName>
                        <VirtualSiteFlag>78</VirtualSiteFlag>
                        <GeographicLocationId>99997167</GeographicLocationId>
                        <CreatedDate>2008-11-07T07:32:21.07</CreatedDate>
                        <ModifiedByName>taus461</ModifiedByName>
                        <ModifiedDate>2008-11-07T07:44:20.723</ModifiedDate>
                        <CreatedByName>taus461</CreatedByName>
                   </FacilitySiteEntity>
                   <GeographicLocationEntity>
                        <Id>99997167</Id>
                        <GeographicLocationId>99997167</GeographicLocationId>
                        <AddressLine1>2020 22nd Ave SE</AddressLine1>
                        <CityName>Olympia</CityName>
                        <CongressionalDistrictNumber xsi:nil="true"/>
                        <COORD_XTNT_CD xsi:nil="true"/>
                        <HorizontalDatumCode>3</HorizontalDatumCode>
                        <HorizontalAccuracyLevelCode>13</HorizontalAccuracyLevelCode>
                        <HorizontalCollectionMethodCode>2</HorizontalCollectionMethodCode>
                        <GeographicPositionCode>8</GeographicPositionCode>
                        <LatitudeDecimalNumber xsi:nil="true"/>
                        <LatitudeDegreeNumber xsi:nil="true"/>
                        <LocationVerifiedFlag xsi:nil="true"/>
                        <LatitudeMinutesNumber xsi:nil="true"/>
                        <LatitudeSecondsNumber xsi:nil="true"/>
                        <LongitudeDecimalNumber xsi:nil="true"/>
                        <LongitudeDegreeNumber xsi:nil="true"/>
                        <LongitudeMinutesNumber xsi:nil="true"/>
                        <LongitudeSecondsNumber xsi:nil="true"/>
                        <BaseReferenceCode>SPCS</BaseReferenceCode>
                        <SOURCE_SCALE_CD>99</SOURCE_SCALE_CD>
                        <VerticalMeasureNumber xsi:nil="true"/>
                        <VerticalMeasureUnitCode>FT</VerticalMeasureUnitCode>
                        <VerticalReferenceCode xsi:nil="true"/>
                        <VerticalCollectionMethodCode xsi:nil="true"/>
                        <VerticalDatumCode xsi:nil="true"/>
                        <VerticalAccuracyLevelCode xsi:nil="true"/>
                        <CountyCodeNumber xsi:nil="true"/>
                        <LocationDescription1>This is my test facility decription</LocationDescription1>
                        <EPARegionName xsi:nil="true"/>
                        <GISVerifiedFlag xsi:nil="true"/>
                        <LegislativeDistrictNumber xsi:nil="true"/>
                        <IndianLandFlag>78</IndianLandFlag>
                        <RangeDirectionCode xsi:nil="true"/>
                        <RangeNumber xsi:nil="true"/>
                        <RegionCode/>
                        <SectionNumber xsi:nil="true"/>
                        <StateCode>WA</StateCode>
                        <SPCSXCoordinateNumber xsi:nil="true"/>
                        <SPCSYCoordinateNumber xsi:nil="true"/>
                        <SPCSZoneCode xsi:nil="true"/>
                        <TownshipDirectionCode xsi:nil="true"/>
                        <TownshipNumber xsi:nil="true"/>
                        <UTMXCoordinateNumber xsi:nil="true"/>
                        <UTMYCoordinateNumber xsi:nil="true"/>
                        <UTMZoneCode xsi:nil="true"/>
                        <WRIAIdNumber xsi:nil="true"/>
                        <ZipCode>98501</ZipCode>
                        <PLAIndicatorCode xsi:nil="true"/>
                        <GISReferenceNumber xsi:nil="true"/>
                        <GISCalculatedLatDecimalNumber xsi:nil="true"/>
                        <GISCalculatedLongDecimalNumber xsi:nil="true"/>
                        <ModifiedByName>taus461</ModifiedByName>
                        <ModifiedDate>2008-11-07T07:44:20.74</ModifiedDate>
                        <CreatedDate xsi:nil="true"/>
                        <CreatedByName>taus461</CreatedByName>
                        <FacilitySite>
                             <Id>99997167</Id>
                             <FacilitySiteId>99997167</FacilitySiteId>
                             <FacilitySiteName>My New Test Facility</FacilitySiteName>
                             <FacilitySiteKeySearchName>My New Te</FacilitySiteKeySearchName>
                             <VirtualSiteFlag>78</VirtualSiteFlag>
                             <GeographicLocationId>99997167</GeographicLocationId>
                             <CreatedDate>2008-11-07T07:32:21.07</CreatedDate>
                             <ModifiedByName>taus461</ModifiedByName>
                             <ModifiedDate>2008-11-07T07:44:20.723</ModifiedDate>
                             <CreatedByName>taus461</CreatedByName>
                        </FacilitySite>
                   </GeographicLocationEntity>
                   <IsOperationSuccess>true</IsOperationSuccess>
              </FacilitySiteResponse>
         </s:Body>
    </s:Envelope>');
         select fac.facID, fac.FacilitySiteId, fac.FacilitySiteName
              into v_FacID, v_FacilitySiteId, v_FacilitySiteName
         from
         xmltable
              xmlnamespaces
                   default 'http://www.ms.com/xml'     
                   ---'http://www.ms.com/xml'
                   ---'http://schemas.xmlsoap.org/ws/2004/08/addressing' as "wsa",
                   ---'http://www.w3.org/2003/05/soap-envelope' as "soap"
              '//FacilitySiteResponse'
              passing v_xmlText
              columns
              FacID               varchar2(50)     path     '//FacilitySiteEntity/Id',
              FacilitySiteId          varchar2(50)     path     '//FacilitySiteEntity/FacilitySiteId',
              FacilitySiteName     varchar2(50)     path     '//FacilitySiteEntity/FacilitySiteName'
         ) fac;
         dbms_output.put_line('FacID = ' || v_FacID);
         dbms_output.put_line('FacSiteID = ' || v_FacilitySiteId);
         dbms_output.put_line('FacSiteName = ' || v_FacilitySiteName);
                    select extractValue(v_xmlText, '//FacilitySiteResponse/FacilitySiteEntity/Id', 'xmlns="http://www.ms.com/xml"')
         into v_FacID from dual;
                   dbms_output.put_line('FacID = ' || v_FacID);
    end;
    /FacID = 99997167
    FacSiteID = 99997167
    FacSiteName = My New Test Facility
    FacID = 99997167
    PL/SQL procedure successfully completed.

  • XI SOAP adapter : Error during parsing the SOAP part

    Hello experts,
    We have several scenarios SOAP to IDocs.
    We are on XI 3.0 SP19, and since 9/6/09 around 4:00 PM GMT, our SOAP channels used to communicate with a specific 3rd party all stoped accepting incoming SOAP requests. All the messages are stucked on third party side, and we get the following error in the defaulttrace and application logs :
    #1.5#001125A5BCD00066000076850013109E00046BF6A963E479#1244607054865#/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.mo.Message.reparseRootDocument()#PIMSOAP#21217##pxaci_PXA_6443451#PIMSOAP#a71ebfa0556d11decc24001125a5bcd0#SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#com.sap.aii.messaging.mo.Message#Plain###Error during parsing the SOAP part --- java.lang.NullPointerException#
    It happened at the same time on all the environments for every interfaces using SOAP message from this sender to XI. That's the reason why we think it is a global issue, but we can not find anything concerning this error. Has anybody encountered this error or would have any clue of where it comes from ?
    Many thanks,
    Best regards,
    Guislain

    Hello Michal,
    Thanks a lot for your help. Actualy we have tested with SOAP UI yesterday and this is what came out of the tests :
    test 1 : we tried to call the XI service with the wsdl and put dummy data inside --> test OK
    test 2 : we loaded in SOAP UI one of the file from our partner and tried to call the service --> test NOT OK
    test 3 : we realized that there were some blank lines at the beginning of the file provided by the partner. we removed these blank lines --> test OK.
    So we first thought that the format of the file sent by the partner was wrong and this is why we were getting the parsing error, because of these blank line. The thing is that these blank lines have always been here ! We have checked with old successful messages and they contain also these lines and if we test them in SOAP UI we get an error also. so it does not seems to come from this.
    Moreover, as I said in my previous message, it happened on all the environments approximatly at the same time, so we are suspecting a global problem, but which one ? That's the million dollar question
    Would you have any other ideas ?
    Thanks a lot,
    Best regards,
    Guislain

  • HTTP response code 500 : Error during parsing of SOAP header

    Hi Experts,
    I have a MAIL to IDOC scenario.  An external third party emails invoices to our inbox - which we pick up and process the attachment.  All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
    When I look at the SOAP header of the failed message I see the values from the dump in this field:
      <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
    Can anyone tell me what SHeaderTHREAD-INDEX does?  Or what my problem is  (Our email is Outlook)
    ERROR MESSAGE.........
    SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage:  ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
    Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

    We work with Microsoft Outlook, but I'm sure this could work with any email system.
    This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company.  This is set up as a regular email account.  On this email put a forward rule to email2 for a particular sender/subject.  email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
    Doing this accomplishes a couple of things:
    1)  We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
    2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
    3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
    Hope this helps your situation.

  • Erro java.lang.IllegalArgumentException: can't parse argument number

    We are trying to making an HTTPS post using the SOAP adapter (sending XML message) and have been receiving an error in the MDT. If we open the message details and click the audit log instead of seeing the steps in the audit log we have an error that says "java.lang.IllegalArgumentException: can't parse argument number".
    The full stack trace: java.lang.IllegalArgumentException: can't parse argument number
         at java.text.MessageFormat.makeFormat(MessageFormat.java:1323)
         at java.text.MessageFormat.applyPattern(MessageFormat.java:447)
         at java.text.MessageFormat.(MessageFormat.java:347)
         at java.text.MessageFormat.format(MessageFormat.java:800)
         at jsp_auditlog1236632324953._jspService(jsp_auditlog1236632324953.java:274)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
         at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Any help would be appreciated.
    Joe

    hi,
    seems you are tryin to conver to integer an string.
    if the data type is OK and the WS is sender, regenerate it and try again
    Thanks
    Rodrigo

  • Could not parse XMBMessage due to Can't parse the document

    *Dear all,*
    *i have a SOAP to RFC Scenario. XML Validation by Adapter is turned on in SenderAgreement.*
    *XSD Files are placed in the correct directory. Incoming requests are validated. However,*
    *it seems that responses produce an error in the soap adapter.*
    *This is the error message i am getting:*
    +SOAP:Fault>+
             +<faultcode>SOAP:Server</faultcode>+
             +<faultstring>Server Error</faultstring>+
             +<detail>+
                +<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">+
                   +<context>XIAdapter</context>+
                   +<code>ADAPTER.JAVA_EXCEPTION</code>+
                   +<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to Can't parse the document+
    +     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1173)+
    +     at sun.reflect.GeneratedMethodAccessor678.invoke(Unknown Source)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:592)....+
    *In SXMB_MONI my response includes the following passages*
    +- <!--  ************************************+
      -->
      +<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RS_OUT</Trace>+
      +<Trace level="3" type="T">Skip Inbound Validation =</Trace>+
      +<Trace level="3" type="T">Skip Outbound Validation =</Trace>+
      +<Trace level="3" type="T">Area = XML_VALIDATION_OUT</Trace>+
      +<Trace level="1" type="T">Reading sender agreement</Trace>+
      +<Trace level="3" type="T">Validation Mode = Validation by Adapter</Trace>+
      +<Trace level="1" type="T">Outbound validation of response takes place</Trace>+
      +<Trace level="3" type="T">Interface Name = SI_xxx_xxx_xxx_Sync_Outbound</Trace>+
      +<Trace level="3" type="T">Interface Namespace = http://xxx.de/xxx</Trace>+
      +<Trace level="3" type="T">Software Component Version = D390B9E10A6B11DF8C15C7540A484C06</Trace>+
      +<Trace level="2" type="T">Java Validation Service Call</Trace>+
      +<Trace level="1" type="T">System error occurred during XML validation</Trace>+
      +<Trace level="1" type="E">CL_XMS_PLSRV_VALIDATION~ENTER_PLSRV</Trace>+
      +</Trace>+
      +<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />+
    +- <!--  ************************************+
      -->
      +<Trace level="3" type="T">Persisting message Status = 023</Trace>+
      +<Trace level="3" type="T">Message version 009</Trace>+
      +<Trace level="3" type="T">Pipeline CENTRAL</Trace>+
      +</SAP:Trace>+
    *I see the following error message:*
      +<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+
    +- <!--  Aufruf eines Adapters+
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="XML_VALIDATION_OUT">CX_XMS_SYSERR_VALIDATION</SAP:Code>
      <SAP:P1>Schema xxx.response.xsd not found in J:\usr\sap\xxx\SYS\global\xi\runtime_server\validation\schema\00000000000000000000000000000000\ u00D3u00B9u00E1 k u00DFŒ u00C7T HL \SI_xxx_xxx_xxx_Sync_Outbound\urnsap-comdocumentsaprfc~functions\xxx.response.xsd (J:\usr\sap\xxx\SYS\global\xi\runtime_server\validation\schema)</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
      <SAP:Stack>System error occurred during XML validation</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    There seems to be an error in the adapter trying to validate the response. Does anyone has a clue as to why ?

    Since i cannot get i running, i helped myself using a java mapping, that i packaged into a jar
    along with the xsd files. See code below:
    import com.sap.aii.*;
    import java.io.File;
    import java.io.FileInputStream;
    import java.io.FileNotFoundException;
    import java.io.FileOutputStream;
    import java.io.IOException;
    import java.io.InputStream;
    import java.io.BufferedReader;
    import java.io.OutputStream;
    import java.io.OutputStreamWriter;
    import java.io.UnsupportedEncodingException;
    import java.io.InputStreamReader;
    import java.io.Reader;
    import javax.xml.transform.sax.SAXResult;
    import javax.xml.transform.sax.SAXSource;
    import javax.xml.transform.stream.StreamSource;
    import javax.xml.validation.Schema;
    import javax.xml.validation.SchemaFactory;
    import javax.xml.validation.Validator;
    import org.xml.sax.InputSource;
    import org.xml.sax.SAXException;
    @SuppressWarnings("unused")
    public class CustomValidator extends AbstractTransformation {
         public void transform(TransformationInput arg0, TransformationOutput arg1)
                   throws StreamTransformationException {
              Validator validator;
              InputStreamReader insr;
              String inputPayloadString;
              try {
                   // Trace
                   getTrace().addInfo("com.xxx.pi.mapping.validation.CustomValidator called");
                   InputStream inputPayloadStream = arg0.getInputPayload()
                             .getInputStream();
                   insr = new InputStreamReader(inputPayloadStream);
                   InputHeader inpHeader = arg0.getInputHeader();          
                   String intfName = inpHeader.getInterface();
                   getTrace().addInfo("Interface Name is :" + intfName);
                   String xsdName = "";
                   if (intfName
                             .equalsIgnoreCase("SI_xxx_Sync_Outbound")) {
                        xsdName = "Z_xxx.xsd";
                   if (intfName.equalsIgnoreCase("SI_xxx")) {
                        xsdName = "Z_xxx.xsd";
                   if (intfName
                             .equalsIgnoreCase("SI_xxx_Sync_Outbound")) {
                        xsdName = "Z_xxx.xsd";
                   if (intfName
                             .equalsIgnoreCase("SI_xxxx_Sync_Outbound")) {
                        xsdName = "Z_xxx.xsd";
                   getTrace().addInfo("Using schema: " + xsdName);
                   if (xsdName.equals(""))
                        throw new StreamTransformationException("Schema für "
                                  + intfName + " nicht gefunden.");
                   BufferedReader reader = new BufferedReader(new InputStreamReader(
                             getClass().getResourceAsStream(
                                       "/com/xxx/pi/mapping/xsd/" + xsdName)));
                   // prepare document validator:
                   String schemaLang = "http://www.w3.org/2001/XMLSchema";
                   SchemaFactory jaxp = SchemaFactory.newInstance(schemaLang);
                   Schema schema = jaxp.newSchema(new StreamSource(reader));
                   validator = schema.newValidator();
              } catch (SAXException saxe) {
                   throw new StreamTransformationException(saxe.getMessage());
              // validate
              try {
                   SAXSource source = new SAXSource(new InputSource(insr));
                   validator.validate(source);
              } catch (Exception e) {
                   getTrace().addInfo(e.getMessage());
                   String trace = e.getMessage();
                   throw new StreamTransformationException(trace, e.getCause());
              // Write the response
              try {
                   inputPayloadString = convertStreamToString(arg0.getInputPayload()
                             .getInputStream());
                   arg1.getOutputPayload().getOutputStream()
                             .write(inputPayloadString.getBytes("UTF-8"));
                   getTrace().addInfo("Schema Validierung erfolgreich !");
              } catch (Exception e) {
                   throw new StreamTransformationException(e.getMessage());
         // helper to convert to String
         private static String convertStreamToString(InputStream in) {
              StringBuffer sb = new StringBuffer();
              try {
                   InputStreamReader isr = new InputStreamReader(in);
                   BufferedReader reader = new BufferedReader(isr);
                   String line;
                   while ((line = reader.readLine()) != null) {
                        sb.append(line);
              catch (Exception exception) {
              return sb.toString();

  • How Can I parse a complex type WSDL using WSDL4J?

    I cannot parse the element Area---helppppppppppp
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://testfinal" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://testfinal" xmlns:intf="http://testfinal" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
    <schema targetNamespace="http://testfinal" xmlns="http://www.w3.org/2001/XMLSchema">
    <element name="x" type="xsd:string"/>
    <complexType name="Area">
    <sequence>
    <element name="f" type="xsd:int"/>
    <element name="fo" type="xsd:int"/>
    </sequence>
    </complexType>
    <element name="f" type="impl:Area"/>
    <element name="getSampleReturn" type="xsd:string"/>
    <element name="sample" type="xsd:string"/>
    </schema>
    </wsdl:types>
    <wsdl:message name="getSampleRequest">
    <wsdl:part element="impl:x" name="x"/>
    <wsdl:part element="impl:f" name="f"/>
    </wsdl:message>

    FYI, many folks on these forums are behind corporate firewalls that won't allow access to that sort of site. Particularly when the amount of code is small, as it is here, you're better off posting it in the forum
    create or replace procedure myProcedure( i int ) is
      TYPE mapx IS TABLE OF NUMBER INDEX BY VARCHAR2(64);
      TYPE mapy IS TABLE OF mapx INDEX BY VARCHAR2(64);
      instanceOfMapx mapx;
      instanceOfMapy mapy;
    begin
        instanceOfMapx('Australia') := 30000000;
        instanceOfMapy('val1'):=instanceOfMapx;
        dbms_output.put_line('hi');
        /* i want here that in my procedure return this instanceOfMapy */
    end myProcedure;If you want to modify that to return an instance of MAPY
    1) You'll need to declare MAPX and MAPY in a package so that they can be referenced in multiple places
    2) You'll need to add an OUT parameter to your procedure
    The smallest change that would work would be
    CREATE OR REPLACE PACKAGE map_pkg
    AS
      TYPE mapx IS TABLE OF NUMBER INDEX BY VARCHAR2(64);
      TYPE mapy IS TABLE OF mapx INDEX BY VARCHAR2(64);
    END map_pkg;
    create or replace procedure myProcedure( i IN integer, instanceOfMapy OUT map_pkg.mapy )
    is
      instanceOfMapx map_pkg.mapx;
    begin
        instanceOfMapx('Australia') := 30000000;
        instanceOfMapy('val1'):=instanceOfMapx;
        dbms_output.put_line('hi');
        /* i want here that in my procedure return this instanceOfMapy */
    end myProcedure;Of course, practically, I'd expect that you'd likely want to move myProcedure into the package you created.
    Justin

  • Mail Receiver Error:  java.lang.IllegalArgumentException: can't parse argum

    Hi everybody,
    I get the error in mail receiver CC:
    java.lang.IllegalArgumentException: can't parse argument number
    My Payload looks like this:
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
      <Subject>The subject</Subject>
      <From>mailadress</From>
      <To>mailadress</To>
      <Content_Type>multipart/mixed; boundary="AaBb--984dfgeSSd3532"</Content_Type>
    - <Content_Description>
      <attachment filename="Filename.txt">content_of_attachment</attachment>
      </Content_Description>
      <Content_Disposition>attachment</Content_Disposition>
      <Content>Constant</Content>
      </ns1:Mail>
    Any ideas?
    Regards
    Mario

    Hi Mario..
    Go thru this thread for it.
    Error Catagory : XI_J2EE_ADAPTER_MAIL
    Regards

  • Mail-Adapter Integration Engine Error during parsing of SOAP header

    Hello,
    we use XI with the mail adapter. Most of the messages are processed correctly. But sometimes I get following errors in the J2EE-logviewer:
    Transmitting the message to endpoint http://<xi-host>:<http-port>/sap/xi/engine
    ?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.a
    pi.RecoverableException: Received HTTP response code 500 : Error during
    parsing of SOAP header.
    Failed to transmit message 4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND)
    due to com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP
    response code 500 : Error during parsing of SOAP header.
    Retries exceded, set message
    4e913640-4cc5-11dc-8560-00e000c55366(OUTBOUND) to status NON_DELIVERED.
    Has somebody else the same problem and solved it or any idea what the matter could be?
    Thanks for your help
    Christian

    Hi Reddy,
    We´ve got the following scenario:
    Exchange-Server (is always up)
    XI Mail-ReceiverAdapter
    I use IMAP4 to access the Outlook-Email-Box
    Everything works fine. But some Emails aren´t processed.
    I think it´s a problem between adapterframework and the integration engine?
    There is no difference between the emails?
    If you´ll need further informations ask me?
    Thanks

  • Error during parsing of SOAP header

    Hi all,
    I have configured the j-meter to send an http request to inegration engine of PI.
    The request xml that I am sending is as follows:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Header>
    <SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
    versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
    </SOAP:Main>
    </SOAP:Header>
    <SOAP:Body>
    <ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
    <Record>
    <FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
    <BaseUOM>KG</BaseUOM>
    <AlternateUOM>GEB</AlternateUOM>
    <UnitsInAlternateUOM>100</UnitsInAlternateUOM>
    <UnitsInBaseUOM>2268</UnitsInBaseUOM>
    <Active_Deleted></Active_Deleted>
    </Record>
    </ns1:UnitOfMeasure>
    </SOAP:Body>
    </SOAP:Envelope>
    I am getting the following response from the XI:
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Header>
    </SOAP:Header>
    <SOAP:Body>
    <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
    </SAP:Stack></SAP:Error></detail></SOAP:Fault>
    </SOAP:Body>
    </SOAP:Envelope>
    Any idea as to why PI is not able to parse the request header?
    Thanks,
    Amit

    Hi,
    Better to take WSDL from PI(ID window) and try.

  • Can't parse configuration  jsf-ri-runtime.xml

    When I try to do the Example about JSF in (How To Use JSF with JDeveloper 10g) and run it I found this problem
    SEVERE: Can't parse configuration file:classloader:/com/sun/faces/jsf-ri-runtime.xml
    and I have jDeveloper ver 9.0.5.2
    and java ver 1.4.2.04
    Plz Help
    Alaa

    I installed the 9.052 build of JDeveloper and it solved the problem. Per forum thread: Re: JSF Configuration error in JDeveloper10g

  • Can't parse configuration file

    hi i'm trying to deploy an application on oc4j 10.1.3.1.0. i use Eclipse IDE and ant for deploy.
    i have this:
    [java] java.rmi.RemoteException: bindWebApp() failed!; nested exception is:
    [java] oracle.oc4j.admin.internal.DeployerException: Can't parse configuration file:code-source:/C:/JDeveloper/j2ee/home/applib/adf-faces-impl.jar!/META-INF/faces-config.xml
    [java] at com.evermind.server.administration.DefaultApplicationServerAdministrator.bindWebApp(DefaultApplicationServerAdministrator.java:420)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:585)
    [java] at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
    [java] at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    [java] at java.lang.Thread.run(Thread.java:595)
    [java] Caused by: oracle.oc4j.admin.internal.DeployerException: Can't parse configuration file:code-source:/C:/JDeveloper/j2ee/home/applib/adf-faces-impl.jar!/META-INF/faces-config.xml
    [java] at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1224)
    [java] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:321)
    [java] at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1130)
    [java] at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:738)
    [java] at com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
    [java] at com.evermind.server.Application.getHttpApplication(Application.java:545)
    [java] at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
    [java] at com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.<init>(HttpSite.java:1909)
    [java] at com.evermind.server.http.HttpSite.addHttpApplication(HttpSite.java:1606)
    [java] at oracle.oc4j.admin.internal.WebApplicationBinder.bindWebApp(WebApplicationBinder.java:238)
    [java] at com.evermind.server.administration.DefaultApplicationServerAdministrator.bindWebApp(DefaultApplicationServerAdministrator.java:418)
    [java] ... 7 more
    [java] Error: bindWebApp() failed!; nested exception is:
    [java] oracle.oc4j.admin.internal.DeployerException: Can't parse configuration file:code-source:/C:/JDeveloper/j2ee/home/applib/adf-faces-impl.jar!/META-INF/faces-config.xml

    I had similar problems with jsf-impl.jar.
    Sun do provide the xsd schemas locally inside the jar files so internet connection
    should not be required if parser is configured right.
    In my case I removed commons-digester-1.6.jar from my application and replaced it
    with commons-digester.jar supplied by JDeveloper builtin library named Commons Digester 1.5.
    Digester was configuring the (oracle) xerces parser.

Maybe you are looking for

  • How do i put 'photo library' and photo folders onto my pc?

    A while ago I had over 6000 photos in camera, mostly screen shots. So i imported them and sorted them out into photos taken by the camera and screen shots, put them into different folders then put them onto my phone. So i have Camera Roll & Photo Str

  • FCP6 Media Manager crashing

    Hi I have a client on FCP6 (latest version of it, I believe) on a 27" iMac with 10.6. She has a project with ~1.5TB media spread across a couple of locations, and wants to move everything to a new drive so she can send it down to her editor. However,

  • Real Time Communication

    HI Gurus, Can any one tell me what is  REAL TIME COMMUNICATION. Also I request information / details on RTCIS. Regards Ajoy

  • Multiple formats and frame rates in one sequence

    i have material shot on many different cameras. it includes PAL and NTSC, HD and SD, 24, 25, 30, and 60 fps, ProRes, DCVProHD, DVCam, etc etc. the final product is going to HD in both NTSC 24fps and Pal 25fps, for NatGeo domestic and international. t

  • Setting Timeline Markers Script in After Effects CS6

    So I'm without my desktop computer for the time being and am using a laptop in its place-which means I do not have access to a numpad. Going out to buy one is my last resort, as I don't have enough leisure time to visit a trusty electronics store. So