XML Provider Exception

Hi,
I�m trying to develop a new XMLProvider a after compiling it and conf. the provider and channel in the portal, it shows ERROR: Content is not available.
I�m working with portal 6.2 and AppServ 7.
The debug is the following:
02/05/2004 04:08:43:623 PM ART: Thread[Thread-307,5,main]
ERROR: ProviderCaller.run(): exception thrown from MGCustomXML
java.util.MissingResourceException: Can't find bundle for base name CustomXMLProvider, locale en_US
     at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804)
     at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:694)
     at java.util.ResourceBundle.getBundle(ResourceBundle.java:661)
     at com.sun.portal.providers.ProviderAdapter.getResourceBundle(ProviderAdapter.java:734)
     at com.sun.portal.providers.xml.XMLProvider.getContent(Unknown Source)
     at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusableProviderCaller.java:158)
I�ll thank any advice, Pablo

Refer http://forum.java.sun.com/thread.jspa?tstart=30&forumID=34&threadID=542044&trange=15

Similar Messages

  • 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

  • Custom security provider exception

    Good day, colleagues. I want to raise an old topic.
    I use custom security provider exceptions:
    -AccountExpiredException
    -AccountLockedException
    However, the login() method only captures FailedLoginException
    try
      CallbackHandler pwcall = new weblogic.security.URLCallbackHandler(user, pass.getBytes("UTF-8"));
      subject = weblogic.security.services.Authentication.login(pwcall);
      weblogic.servlet.security.ServletAuthentication.runAs(subject, request);
    catch (javax.security.auth.login.LoginException e) {
      e.printStackTrace();
    javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User ...
      at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:240)
      at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
      at java.security.AccessController.doPrivileged(Native Method)
    I found similar questions IdentityAssertion custom exception, FailedLoginException asked many years ago for WLS 9.2
    Their solution (wlp.propogate.login.exception.cause=true) does not work for WLS 10.3.
    How to propagate original LoginException?
    Or exception message only.

    I did it! look closely to source code:
    javax.security.auth.login.LoginContext:875
    if (moduleStack[i].entry.getControlFlag() == AppConfigurationEntry.LoginModuleControlFlag.REQUISITE) {
      // if REQUISITE, then immediately throw an exception
      if (methodName.equals(ABORT_METHOD) || methodName.equals(LOGOUT_METHOD)) {
           if (firstRequiredError == null)
                firstRequiredError = le;
      } else {
           throwException(firstRequiredError, le);
    } else if (moduleStack[i].entry.getControlFlag() == AppConfigurationEntry.LoginModuleControlFlag.REQUIRED) {
      // mark down that a REQUIRED module failed
      if (firstRequiredError == null)
           firstRequiredError = le;
    } else {
      // mark down that an OPTIONAL module failed
      if (firstError == null)
           firstError = le;
    javax.security.auth.login.LoginContext:922
    // we went thru all the LoginModules.
    if (firstRequiredError != null) {
      // a REQUIRED module failed -- return the error
      throwException(firstRequiredError, null);
    } else if (success == false && firstError != null) {
      // no module succeeded -- return the first error
      throwException(firstError, null);
    } else...
    I set Control flag: OPTION to DefaultAuth (was REQUIRED)
    and order it after my LoginModule. (restart required!)
    Now I catch my exceptions %)

  • Java Mail/EJB/WebLogic/weblogicSP6 "No Such Provider Exception"

    Hi,
    My application that is coded to send e-mail is not performing at all.
    Application architecture is as follows:
    1)JSP-EJB on Web Logic App server and
    2)SMTP Host is IIS server and its SMTP service.
    3)Using Java Mail API and installed Service Pack 6 of WebLogic that supports Java Mail API
    4)EJB Programs coded as per the Sun JavaMail API documentation.
    5)Send Mail occuring in the EJB.
    Runtime Error: "No such provider exception"
    Could u help me by instructing me about:
    1)weblogic service pack installation.
    2)sample ejb
    PS:Same code on a simple java class fired on command line is executing without any exception. Wheras in an EJB on Weblogic is throwing the exception.

    That error you are seeing typically comes from JavaMail being unable to
    contact the SMTP host. Are you sure that you are a valid user/permitted to
    access the mailer?
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc
    "Omm" <[email protected]> wrote in message
    news:3a3cd390$[email protected]..
    >
    Hi,
    My application that is coded to send e-mail is not performing at all.
    Application architecture is as follows:
    1)JSP-EJB on Web Logic App server and
    2)SMTP Host is IIS server and its SMTP service.
    3)Using Java Mail API and installed Service Pack 6 of WebLogic thatsupports Java Mail API
    4)EJB Programs coded as per the Sun JavaMail API documentation.
    5)Send Mail occuring in the EJB.
    Runtime Error: "No such provider exception"
    Could u help me by instructing me about:
    1)weblogic service pack installation.
    2)sample ejb
    PS:Same code on a simple java class fired on command line is executingwithout any exception. Wheras in an EJB on Weblogic is throwing the
    exception.
    >
    >

  • No Such Provider Exception SunJSSE

    Hello,
    We are facing problem using SunJSSE with WebSphere4.0. We placed jsse jars in the jre/lib/ext directory and in our code we are trying to create SSLcontext as below
    context = SSLContext.getInstance("SSL","SunJSSE");
    tmFact=TrustManagerFactory.getInstance("SunX509","SunJSSE");
    kmfact = KeyManagerFactory.getInstance("SunX509","SunJSSE");
    And then intializing the context with trustmanager[], keymanager[] and secure random parameters.
    In our code we are dynamicaly setting the provider as
    java.security.Security.insertProviderAt(new com.sun.net.ssl.internal.ssl.Provider(),2);
    We also made the entry in the java.security file statically.
    However we are occasionally getting No such Provider Exception SunJSSE.
    Please note all this is running under websphere 4.0 and IBM has IbmjSSE jars in the jre/lib/ext as well.
    Any Ideas? thoughts? comments? help?
    Thanks

    Hi,
    I'm having a similar problem to this, what was wrong with this ? as it appears the provider should be available.
    Thanks

  • MDM Meta Data Provider Exception

    Hi,
    I am getting this exception while making the Metadata Provider
    Stack Trace of Exception
    oracle.express.olapi.data.full.ExpressDataProvider@71b246
    29-Apr-2003 10:19 FATAL - Olap helper class : MDM Meta Data Provider Exception
    com.sun.corba.ee.internal.corba.AnyImpl@3744bc
         at oracle.express.idl.util.OlapiExceptionHelper.SQL2Java(OlapiExceptionHelper.java:15)
         at oracle.express.idl.ExpressConnectionModule.ServerInterfaceStub.getVersionInfo(ServerInterfaceStub.java:137)
         at oracle.express.olapi.data.full.ExpressDataProvider._checkVersion(ExpressDataProvider.java:263)
         at oracle.express.olapi.data.full.ExpressDataProvider.connect(ExpressDataProvider.java:194)
         at oracle.express.olapi.data.full.ExpressDataProvider.initialize(ExpressDataProvider.java:179)
         at com.pg.emfg.eops.helperclasses.Olap.startUp(D:/Source Code/src/com/pg/emfg/eops/helperclasses/Olap.java:83)
    .pg.emfg.eops.component.dynamicviewreport.eventaction.DynamicViewReportEventAction.perform
    Code Segment Used
    // Makes the connection
    objConnection = (oracle.jdbc.OracleConnection) DBManager.getOlapConnection();
    objTranProvider = new ExpressTransactionProvider();
    objDataProvider = new ExpressDataProvider(objConnection, objTranProvider); // Create the ExpressData Provider
    objDataProvider.initialize();
    mdp = (MdmMetadataProvider) objDataProvider.getDefaultMetadataProvider();
    This exception occurs randomly most of the times the code works fine, but then sometimes it throws this.
    I am unable to determine the root cause of the exception.
    Please help me with the actual cause for this exception and the likely solution.
    Thanks

    Anthony
    This problem is coming on HP and windows both
    with the 9.2.0.2 olap api jar files.
    I had raised a tar regarding this and was told to post the problem on OTN on this thread.
    Current status still using ORACLE connection pooling.
    Got exceptions with OCI Connection Pool
    Olap API excepiotn are encountered during Cursor,(Cursor Manager) Creation.
    There are three different exception encountered.
    1>>
    oracle.express.ExpressServerExceptionError class: OLAPI
    Server error descriptions:
    DPR: Unable to execute the query, Generic at
    TxsOqCursorManager::fetchInitialBlocks
    OES: ORA-040, Generic at TxsRdbSelectStatement:execute()
    at
    oracle.express.olapi.data.full.FullCursorBlockFetcher.fetchAnyCursorBlock(FullCu
    rsorBlockFetcher.java:111)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.prepareForOpenCurso
    r(ExpressSpecifiedCursorManager.java:350)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.createCursor(Expres
    sSpecifiedCursorManager.java:191)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.createCursor(Expres
    sSpecifiedCursorManager.java:150)
    at com.pg.emfg.eops.helperclasses.Olap.obtainCursor(D:/Source
    2>>
    oracle.express.idl.util.OlapiException
    at
    oracle.express.idl.ExpressOlapiDataCursorModule.CursorManagerInterfaceStub.fetch
    InitialBlocks(CursorManagerInterfaceStub.java:204)
    at
    oracle.express.olapi.data.full.FullCursorBlockFetcher.fetchAnyCursorBlock(FullCu
    rsorBlockFetcher.java:102)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.prepareForOpenCurso
    r(ExpressSpecifiedCursorManager.java:350)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.createCursor(Expres
    sSpecifiedCursorManager.java:191)
    at
    oracle.express.olapi.data.full.ExpressSpecifiedCursorManager.createCursor(Expres
    sSpecifiedCursorManager.java:150)
    at com.pg.emfg.eops.helperclasses.Olap.obtainCursor(Olap.java:1171)
    3>>
    oracle.express.idl.util.OlapiException
    at
    oracle.express.idl.ExpressOlapiDataSourceModule.DefinitionManagerInterfaceStub.c
    reateCursorManager(DefinitionManagerInterfaceStub.java:103)
    at
    oracle.express.olapi.data.full.DefinitionManager.createCursorManager(DefinitionM
    anager.java:339)
    at
    oracle.express.olapi.data.full.ExpressDataProvider.createCursorManager(ExpressDa
    taProvider.java:426)
    at
    oracle.olapi.data.source.DataProvider.createCursorManager(DataProvider.java:151)
    at com.pg.emfg.eops.helperclasses.Olap.obtainCursor(Olap.java:1220)
    After these exceptions that user session can no longer use the application, thesame exception will prop up for all cursors creation attempts.
    Also sometimes the only way to make the application work is to restart the
    Application Server (JRUN).
    The compound Cursor is then traversed to obtain the data fetch shown in the
    report.
    Now the user can select say 10 measures, Based on that 10 cursorManagers and
    subesequent cursors are created.
    Also this was one request, the user can make subsequent requests, during which
    new cursors will be made.
    No where in the Code am I actually closing cursorManager or the cursor
    Could you provide a specific root cause, which i can target.

  • XML Provider deployment

    hi, I�m trying to add a new XML Provider with the next command:
    bash-2.05# dpadmin a -u amadmin -w password -d porlet /app1/opt/SUNps/CustomXMLProvider.xml
    bash: dpadmin: command not found
    bash-2.05#
    I�m following the developer�s manual and I can�t make it work. I�m sure the current directory is OK. Any ideas? Thank you, Pablo

    Thank you for your fast answer. In fact, the directory is not the default but, as I said, that was not the problem. The script dpadmin has to be run like this:
    ./dpadmin add .......
    If you don�t do that the shell says "command not found" or something like that. Thank you anyway

  • ORDSYS.ORDDOC generating "No XML provider found"

    Hi all, in my DB table there is a column of type ORDSYS.ORDDOC. I tried to drag&drop the correspondent ViewObject inside a UIX page, but suddently the graphical display of the page is replaced by the following error:
    Error 500 occurred:
    java.lang.NullPointerException: No XML Provider found
    at oracle.cabo.servlet.xml.PageDescriptionUtils.createPageDescription(Unknown Source)
    at oracle.cabo.servlet.xml.DefaultPageDescriptionCache.createPageDescription(Unknown Source)
    The problem is that the error propagates to all uix pages of the project! I tried deleting both the table and the related bindings, but the error still persists. If I compile the project i get
    Error: No XMLProvider found
    for each uix page.
    Only when i delete the entire project and open previous copy the problem disappears.
    Anybody knows what happens inside JDev? A similar problem at design time amazes me!!!!!!

    Hello I figured out the problem. The web.xml file has both DefaultFileUpload and OrdFileUpload settings. After i removed one of them, It works fine.

  • XML Transformation exception ??

    I customized a XMLProvider to get feed from a content provider on the fly. During transformation I get this exception:
    04/15/2003 03:18:15:896 PM EDT: Thread[Thread-25,5,main]
    ERROR: XMLProvider.doTransform():Error in transforming xml.
    ; Line#: 2; Column#: -1
    javax.xml.transform.TransformerException: Next character must be ";" terminating
    reference to entity "ID".
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
    l.java:660)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImp
    l.java:1118)
    at com.sun.portal.providers.xml.XMLProvider.doTransform(XMLProvider.java
    :216)
    at com.sun.portal.providers.xml.XMLProvider.getContent(XMLProvider.java:
    280)
    at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusablePro
    viderCaller.java:145)
    04/15/2003 03:18:15:902 PM EDT: Thread[Thread-25,5,main]
    ERROR: XMLProvider.getContent():Error in XML transformation.
    XML piece looks like this:
    <Story>
    <headline>Scientists finish the DNA book of life</headline>
    <url>http://apidemo.yellowbrix.com/pages/apidemo/Story.nsp?story_id=38091348& amp;ID=apidemo</url>
    <pubsource>Evening Times; Glasgow (UK)</pubsource>
    <pubdate>2003-04-14</pubdate>
    <arrival_time>Apr 15, 01:11 AM </arrival_time>
    <category>Biotechnology</category>
    </Story>
    url element has '&' before ID has been properly taken care of with escape codes '& amp;' from the content provider.
    The issue is that the xml document goes through fine when I copy this feed in a file and run the portal.
    Anyone any ideas please.
    Thanks.

    Thanks for the reply. I tried using 'value-of' and 'copy-of' and it didn't work. While using 'value-of' portal hangs and timesout.
    XSL looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="html" indent="yes"/>
    <xsl:template match="/">
    <html>
         <body style="font-family:Arial,helvetica,sans-serif;font-size:12pt; background-color:#EEEEEE">
              <xsl:for-each select="WebApi/Story">
                   <div>
                        <span style="font-weight:bold;color:white">
                        <a> <xsl:attribute name="href">
    <xsl:copy-of select="url"/> </xsl:attribute><xsl:value-of select="headline"/></a>
                        </span>
                   </div>
              </xsl:for-each>
         </body>
    </html>
    </xsl:template>
    </xsl:stylesheet>
    Sample piece of XML
    <WebApi>
    <Story>
    <headline>Gene Work May Help Treat Aging</headline>
    <url>http://apidemo.yellowbrix.com/pages/apidemo/Story.nsp?story_id=38158601&ID=apidemo</url>
    <pubsource>The Boston Globe</pubsource>
    <pubdate>2003-04-17</pubdate>
    <arrival_time>Apr 17, 10:10 AM </arrival_time>
    <category>Biotechnology</category>
    </Story>
    </WebApi>

  • XML Sax Exception with 9.2.0.5 express*.jar files for Olap API

    I was using the olap_api_92.jar that
    came with jdeveloper for the olap api and having a coding problem.. In trying to see
    if I could resolve the previous problem, I set my classpath to use the jar files provided with the 9.2.0.5
    install for AiX.. all beginning with express*.jar
    I now get an XML parsing error that I can't fix..
    which jar is good, the olap_api_92.jar seems to work..
    Help!
    thanks,
    Lisa Cox
    OCLC Inc.
    java.lang.RuntimeException: org.xml.sax.SAXParseException: <Line 179, Column 18>: XML-0124: (Fatal Error) An attribute cannot appear more than once in the same start tag.
    at oracle.olapi.metadata.MetadataFetcher.processXML(MetadataFetcher.java:237)
    at oracle.olapi.metadata.MetadataFetcher.fetchBaseMetadataObjects(MetadataFetcher.java:180)
    at oracle.olapi.metadata.BaseMetadataProvider.fetchMetadataObject(BaseMetadataProvider.java:150)
    at oracle.olapi.metadata.BaseMetadataProvider.fetchMetadataObject(BaseMetadataProvider.java:107)
    at oracle.olapi.metadata.mdm.MdmMetadataProvider.getMetadataObject(MdmMetadataProvider.java:147)
    at oracle.olapi.metadata.mdm.MdmMetadataProvider.getRootSchema(MdmMetadataProvider.java:174)
    at oracle.express.mdm.MdmMetadataProvider.getRootSchema(MdmMetadataProvider.java:144)
    at org.oclc.xwc.olap.OlapClient.main(OlapClient.java:494)

    The OLAP component versions are empty.
    <Check key="OLAP Catalog version" value=""/>
    <Check key="OLAP AW Engine version" value=""/>
    <Check key="OLAP API Server version" value=""/>
    Please doublecheck that the catpatch.sql script ran without any errors.
    Aneel Shenker
    Senior Product Manager
    Oracle Corp.

  • XML Loader Exception

    I get the following exception whenever I run the XMLLoader class.
    Error loading stylesheet file:/C:/Documents and Settings/mfortner/jbproject/MedlineXMLLoader/medline.xslt
    oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'INSERT'.
    at oracle.xml.parser.v2.XSLStylesheet.error(XSLStylesheet.java:1403)
    at oracle.xml.parser.v2.XSLStylesheet.processResult(XSLStylesheet.java:615)
    at oracle.xml.parser.v2.XSLStylesheet.initStylesheet(XSLStylesheet.java:421)
    at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:217)
    at XMLLoader.main(XMLLoader.java:21)
    00001: Inserted.
    Processed 1Documents
    I've tried moving the xsl:version attribute, putting it in it's own <?xsl-stylesheet ?> tag didn't work either. I've tried removing it, same problem. I've tried switching xmlparserv2.jar files (there are two files with different file sizes that come in the xdk) -- that didn't work either.
    I'm running the XMLLoader with the following parameters:
    -file sampmed2.xml -connName medline -transform medline.xslt -docTag MedlineCitationSet
    Any suggestions????
    The XSLT I'm using looks like this.
    <?xml version="1.0"?>
    <INSERT xsl:version="1.0" xmlns:xsl="http://www.w3.org/XSL/Transform">
    <!-- Process Medline Records -->
    <ROWSET table="medline_records">
    <xsl:for-each select="MedlineCitation">
    <ROW>
    <MedlineID><xsl:value-of select="MedlineID"/></MedlineID>
    <PMID><xsl:value-of select="PMID"/></PMID>
    <DateCreated><xsl:apply-templates select="DateCreated" mode="processDateCreated"/></DateCreated>
    <DateCompleted><xsl:apply-templates select="DateCompleted" mode="processDateCompleted"/></DateCompleted>
    <DateRevised><xsl:apply-templates select="DateRevised" mode="processDateRevised"/></DateRevised>
    <Journal><xsl:apply-templates select="Journal" mode="processJournal"/></Journal>
    <ArticleTitle><xsl:value-of select="ArticleTitle"/></ArticleTitle>
    <AuthorList><xsl:value-of select="AuthorList"/></AuthorList>
    <Country><xsl:value-of select="MedlineJournalInfo"/></Country>
    <MedlineTA><xsl:value-of select="MedlineJournalInfo/MedlineTA"/></MedlineTA>
    <MedlineCode><xsl:value-of select="MedlineJournalInfo/MedlineCode"/></MedlineCode>
    <NlmUniqueID><xsl:value-of select="MedlineJournalInfo/NlmUniqueID"/></NlmUniqueID>
    <CitationSubset><xsl:value-of select="CitationSubset"/></CitationSubset>
    </ROW>
    </xsl:for-each>
    </ROWSET>
    <!-- Process Date Elements (DateCreated, DateCompleted, and DateRevised -->
    <xsl:template select="DateCreated" mode="processDateCreated">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <xsl:template select="DateCompleted" mode="processDateCompleted">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <xsl:template select="DateRevised" mode="processDateRevised">
    <xsl:value-of select="YEAR"/>-<xsl:value-of select="MONTH"/>-<xsl:value-of select="DAY"/>
    </xsl:template>
    <!-- Process Journal Elements -->
    <xsl:template select="JOURNAL" mode="processJournal">
    ISSN<xsl:value-of select="ISSN"/> VOLUME<xsl:value-of select="Volume"/> PAGES<xsl:value-of select=""/>
    </xsl:template>
    <!-- Process Medline Abstract Records -->
    <ROWSET table="medline_abstracts">
    <xsl:for-each select="MedlineCitation">
    <MedlineID><xsl:value-of select="MedlineID"/></MedlineID>
    <Abstract><xsl:value-of select="AbstractText"/></Abstract>
    </xsl:for-each>
    </ROWSET>
    </INSERT>
    And the XML I'm loading looks like this:
    <MedlineCitationSet>
    <MedlineCitation>
    <MedlineID>96264942</MedlineID>
    <PMID>8655018</PMID>
    <DateCreated>
    <Year>1996</Year>
    <Month>07</Month>
    <Day>30</Day>
    </DateCreated>
    <DateCompleted>
    <Year>1996</Year>
    <Month>07</Month>
    <Day>30</Day>
    </DateCompleted>
    <DateRevised>
    <Year>2000</Year>
    <Month>12</Month>
    <Day>18</Day>
    </DateRevised>
    <Article>
    <Journal>
    <ISSN>0017-0011</ISSN>
    <JournalIssue>
    <Volume>67</Volume>
    <Issue>1</Issue>
    <PubDate>
    <Year>1996</Year>
    <Month>Jan</Month>
    </PubDate>
    </JournalIssue>
    </Journal>
    <ArticleTitle>[Effect of fetal and neonatal growth on the occurrence of some diseases in adults]</ArticleTitle>
    <Pagination>
    <MedlinePgn>34-6</MedlinePgn>
    </Pagination>
    <Abstract>
    <AbstractText>The findings of many authors show that reduced fetal growth is followed by increased mortality from cardiovascular disease in adult life. They are further evidence that cardiovascular disease originates, among other risk factors, through programming of the bodies structure and metabolism during fetal and early post-natal life. Wrong maternal nutrition may have an important influence on programming.</AbstractText>
    </Abstract>
    <Affiliation>Katedry i ZakEadu Chemii i Analizy LekC3w, AM w Katowicach.</Affiliation>
    <AuthorList>
    <Author>
    <LastName>Jendryczko</LastName>
    <FirstName>A</FirstName>
    <Initials>A</Initials>
    </Author>
    <Author>
    <LastName>Poreba</LastName>
    <FirstName>R</FirstName>
    <Initials>R</Initials>
    </Author>
    </AuthorList>
    <Language>pol</Language>
    <PublicationTypeList>
    <PublicationType>Journal Article</PublicationType>
    <PublicationType>Retracted Publication</PublicationType>
    <PublicationType>Review</PublicationType>
    <PublicationType>Review, Tutorial</PublicationType>
    </PublicationTypeList>
    <VernacularTitle>WpEyw przebiegu rozwoju pEodu i noworodka na ujawnienie sie niektC3rych chorC3b okresu dorosEego.</VernacularTitle>
    </Article>
    <MedlineJournalInfo>
    <Country>POLAND</Country>
    <MedlineTA>Ginekol Pol</MedlineTA>
    <MedlineCode>FR3</MedlineCode>
    <NlmUniqueID>0374641</NlmUniqueID>
    </MedlineJournalInfo>
    <CitationSubset>IM</CitationSubset>
    <CommentsCorrections>
    <CommentIn>
    <RefSource>Ginekol Pol. 1998 Jul;69(7):561</RefSource>
    </CommentIn>
    <RetractionIn>
    <RefSource>Ginekol Pol 1998 Jul;69(7):559-60</RefSource>
    </RetractionIn>
    </CommentsCorrections>
    <MeshHeadingList>
    <MeshHeading>
    <Descriptor>Adult</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Cardiovascular Diseases</Descriptor>
    <SubHeading>etiology</SubHeading>
    <SubHeading MajorTopicYN="Y">mortality</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Child Development</Descriptor>
    <SubHeading MajorTopicYN="Y">physiology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>English Abstract</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Fetal Development</Descriptor>
    <SubHeading MajorTopicYN="Y">physiology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Fetal Growth Retardation</Descriptor>
    <SubHeading>complications</SubHeading>
    <SubHeading MajorTopicYN="Y">physiopathology</SubHeading>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Human</Descri ptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Infant, Newborn</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Nutrition</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Risk Factors</Descriptor>
    </MeshHeading>
    <MeshHeading>
    <Descriptor>Survival Rate</Descriptor>
    </MeshHeading>
    </MeshHeadingList>
    <NumberOfReferences>11</NumberOfReferences>
    </MedlineCitation>
    <MedlineCitation>...</MedlineCitation>
    </MedlineCitationSet>

    You have a typo in your namespace declaration:
    xmlns:xsl="http://www.w3.org/XSL/Transform"
    should be
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

  • XSLT Transform in XML Signature: Exception

    Hello,
    I have following problem with an XSLT tranform in my XML signature. Here is the code I use to add XSLT to signature:
    main() {
    DOMStructure stylesheet = new DOMStructure( getStylesheet() );
    XSLTTransformParameterSpec spec = new XSLTTransformParameterSpec( stylesheet );
    transforms.add( fac.newTransform( Transform.XSLT, spec ) );
    private Element getStylesheet() throws Exception {
         String stylesheet = //"<?xml version=\"1.0\"?>" +
                        "<xslt:stylesheet version=\"1.0\" xmlns:xslt=\"http://www.w3.org/1999/XSL/Transform\">\n" +
                        " <xsl:include href=\"http://extern XSLT\" />\n" +
                        " <xslt:template match=\"/\">" +
                        " <xsl:apply-imports />" +
                        " </xslt:template>" +
                        "</xslt:stylesheet>\n";
         DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
         //dbf.setValidating( true );
         return dbf.newDocumentBuilder().parse( new ByteArrayInputStream( stylesheet.getBytes() ) ).getDocumentElement();
    I get following exception:
    javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.dsig.TransformException: com.sun.org.apache.xml.internal.security.transforms.TransformationException: Cannot find xslt:stylesheet in Transform
    Original Exception was com.sun.org.apache.xml.internal.security.transforms.TransformationException: Cannot find xslt:stylesheet in Transform
         at org.jcp.xml.dsig.internal.dom.DOMReference.transform(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMReference.digest(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.digestReference(Unknown Source)
         at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.sign(Unknown Source)
    In google I cannot find any details what can be wrong.
    Any suggestions?
    Thanks in advance,
    errno

    Thanks for your response. Sorry - I tried both versions with xslt and xsl - doesn't worked -> the error in my post is actually caused through the multiple changes of this part of code. Here once again:
    private Element getStylesheet() throws Exception {
              String stylesheet = //"<?xml version=\"1.0\"?>" +
                                       "<xslt:stylesheet version=\"1.0\" xmlns:xslt=\"http://www.w3.org/1999/XSL/Transform\">\n" +
                                       " <xslt:include href=\"external XSLTl\" />\n" +
                                       " <xslt:template match=\"/\">" +
                                       " <xslt:apply-imports />" +
                                       " </xslt:template>" +
                                       "</xslt:stylesheet>\n";
              DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
              //dbf.setValidating( true );
              return dbf.newDocumentBuilder().parse( new ByteArrayInputStream( stylesheet.getBytes() ) ).getDocumentElement();
    Thanks,
    errno

  • Remove  Namespace from XML File except Attribute

    Hi  XI  Experts ,
    1.I have referred to the code of xslt Generic XSLT Code to Remove ALL Namespaces from XML:
    http://forums.sdn.sap.com/thread.jspa?threadID=1920630
    But this removes the Attribute : id  from the records .
    My expected output is supposed to be :
    <?xml version="1.0" encoding="GBK"?>
    <body>
      <head>
        <nsrsbh>112001069711</nsrsbh>
        <nsrmc>诺维信(中国)生物技术有限公司出口发票</nsrmc>
        <dcrq>20120209</dcrq>
        <sssq_q>20111201</sssq_q>
        <sssq_z>20120207</sssq_z>
        <records>4</records>
      </head>
      <data>
        <record id="1">
           <fpdm></fpdm>
        </record>
    </data>
    </body
    But after using this XSLT code it removes :id from <record_1 id=> and generated the below code :
    The xml file now doesn't contain teh attribute :id
    <?xml version="1.0" encoding="GBK"?>
    <body>
      <head>
        <nsrsbh>112001069711</nsrsbh>
        <nsrmc>诺维信(中国)生物技术有限公司出口发票</nsrmc>
        <dcrq>20120209</dcrq>
        <sssq_q>20111201</sssq_q>
        <sssq_z>20120207</sssq_z>
        <records>4</records>
      </head>
      <data>
        <record>
          1
          <fpdm></fpdm>          
           </record>
    </data>
    </body>
    Could  you please provide your input
    Plaese note : Here  XI versin iS x1 3.0 SP7 . I have tried suing the Analyzer bean for the Encoing  of Chinese : GBK Intsead of UTF-8 in the Namespace  . But AF_Modules/XMLAnonymizerBean is not comptacible with XI 3.0 SP7
    Hence i have used the following code to remove namespcae and add  Encoding :GBK instead of UTF-8:
    <?xml version="1.0" ?>
    <xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output encoding="GBK"/>
    <xsl:template match="node()|@*">
      <xsl:copy>
       <xsl:apply-templates select="node()|@*"/>
      </xsl:copy>
    </xsl:template>
    </xsl:stylesheet>

    You could use exclude-result-prefixes.
    For example:
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:wt="http://www.example.com" exclude-result-prefixes="wt">
    </xsl:stylesheet>

  • Mapping Error - XML Parser Exception

    We have a scenario where an ABAP Client Proxy sends a message to PI. This message is transformed into the mail package format and an email sent via the mail adapter.
    The Interface Mapping has 2 steps. The 1st step uses an XSL transformation to format the <Content> as html. This step also sets the <Subject>, <To> and <Content_Type> fields. The 2nd step uses a graphical message mapping to dynamically set the <From> field based on the sender system.
    We are experiencing the following intermittent error with this scenario:
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_EUK_MM_MailFrom_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
    This relates to the 2nd mapping step (graphical message mapping) described above.
    The message trace provides the following detail
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Entity 'lt' undefined(:main:, row:3, col:227) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    This suggests that the XML produced by the XSL transformation is invalid.
    The strange thing is that it is very difficult to replicate the error as it doesn't always occur even with the same payload! If the message is restarted it processes successfully. Testing the interface mapping in the IR, with the same payload, works successfully.
    I would welcome any ideas you may have on this.
    Thanks
    Mark

    Hi Mark,
    thing i know now why it works at "restart".
    When the message comes first you get the character '&lt;' in your xml for example: '&<(0'
    and you get the ParserException.
    Now the message is stored for queueing in the db. I assume the characters are now stored in the 'right way': '&amp;amp;&amp;lt;(0'
    When the message now will be restarted everything works fine.
    Regards,
    Olaf

  • XML Parser Exception on Punch Out Setup Request

    I am on the supplier side of the procurement process. Recently I was tasked with bringing on a new buying group, but we have encountered a strange issue. The buyer set up my company in their ERP system, however they are getting an error when trying to punch out to my website...which is listed below.
    Error Code: 400 Invalid XML Format In Login Response Document Unable to parse the Login Response XML.
    XMLParserException
    oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'meta'.
    at oracle.xml.parser.v2.XMLError.flushErrors1
    After some investigation, I am confident the problem resides in the buyers BrowserFormPost URL. The problem seems to be that instead of using "&amp;" for ampersand between the URL variables, it is passing in the & symbol (& is a protected character in XML), which is causing the Oracle XML parser to throw this exception. As a result, the set up request is never getting to me.
    The buyer has opened a couple of tickets now with Oracle support, but both times the ticket has been closed and the buyer has been instructed to contact the supplier (me). I don't know enough about the buyer side Oracle system to instruct them on how to fix this issue. Any help would be greatly appreciated.

    Hi Rakesh,
    You need to have an S-User ID to access SAP Notes. For your convenience, I am pasting the content of SAP Note 954035.
    Process, block and CO could not be created in GP
    Symptom
    After upgrade of SAP-EU component to version 7.0 SP8 in Guided Procedures process, block and callable object could not be created. On design time screen   appears error message:
    com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
    During attempt to start process through the Runtime screen you will get an error message:
    Cannot load callable object container:
    Failed to get Related Model Object for the object
    com.sap.caf.eu.gp.ui.actions.decpage.
    CDecisionPageInterfaceViewdecisionPageUsage1,relation View
    In SP9, the following message could be found:
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
    Proceed as stated for SP8.
    Other terms
    This is WebDynpro problem caused by an inconsistency of versions.
    Solution
          1. Redeploy the SCA SAP-EU (if redeployment does not help undeploy and deploy again) components:
              o caf/eu/gp/ui/dt/comp/cons,
              o caf/eu/gp/ui/dt/comp and
              o caf/eu/gp/ui/actions  from software component SAP-EU
    or
          2. Apply the SP8 patch 1 if you upgrade to SP8. Both components mentioned below will be updated:
              o caf/eu/gp/ui/dt/comp/cons
              o caf/eu/gp/ui/dt/comp
    See if it solves your problem.
    Bye
    Ankur

Maybe you are looking for