XSLT Mapper doesn't support xsi:type

I'm starting to think that XSLT Mapper supports only the basic features of XML Schema ...
It (XSLT Mapper in JDeveloper) does not seem to support mapping to generate this kind of element (cannot do it in Design view, when added to the Source view, cannot go back to Design view):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>
If we leave this in Source view and run the xsl, the resulting XML has a validation error, the last element (FromAChildEntity is not known). The XML is valid in XML Spy.
This problem combines with not being able to map two source elements to one target element, makes XSLT Mapper not able to deal with XML Schema inheritance at all.... ?

I just want to reformat the XML from the original message (didn't realize I had to escape some of the characters). This is the XML that cannot be validated by JDeveloper):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
&lt;A&gt;ABC&lt;/A&gt;
&lt;B&gt;1&lt;/B&gt;
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>

Similar Messages

  • SAML Credential Mapper does not support credential type

    Has anybody any idea on what could be causing the message below, which is being logged several times?
    <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <1309285937475> <BEA-000000> <SAMLCredentialMapperV2: getCredentials(Subject): getCredentialInternal() called>
    <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <1309285937475> <BEA-000000> <SAMLCredentialMapperV2: getCredentialInternal(): **SAML Credential Mapper does not support credential type: weblogic.UserPassword, returns null**>
    Best regards
    Update: Forgot to mention this is SOA Suite 11G environment
    Edited by: user9501748 on Jun 28, 2011 11:53 AM

    I've got the same issue too.
    My setup is to have one domain acting as both Source and Destination.
    For every 10 seconds, I'm seeing 4 of these logs, and the CPU consumption is 100% consistently.
    ####<2-Jun-2009 11:00:27 o'clock AM EDT> <Debug> <SecuritySAMLCredMap> <MYHOST> <AdminServer> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1243954827839> <BEA-000000> <SAMLCredentialMapperV2: getCredentials: Subject initiator>
    ####<2-Jun-2009 11:00:27 o'clock AM EDT> <Debug> <SecuritySAMLCredMap> <MYHOST> <AdminServer> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1243954827839> <BEA-000000> <SAMLCredentialMapperV2: getCredentials(Subject): getCredentialInternal() called>
    ####<2-Jun-2009 11:00:27 o'clock AM EDT> <Debug> <SecuritySAMLCredMap> <MYHOST> <AdminServer> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1243954827839> <BEA-000000> <SAMLCredentialMapperV2: getCredentialInternal(): SAML Credential Mapper does not support credential type: weblogic.UserPassword, returns null>
    Does anyone know what's happening? I've got one of the Security Provider = Active Directory, and thus there's no password returning. Could it be the root cause of the problem?

  • Message tracking fails with 'The server software doesn't support the type of search requested' for only a SINGLE user in org

    Ok this is a weird one.  Message tracking works fine for all my users except for one where I get the above message.  I've tried stopping/restarting the transport services and renaming the tracking log but no luck.  Any ideas?

    Updated and resolved for my situation:
    I called MS Premier and this is now resolved for my issue with a workaround. The technician is going to submit a bug fix but basically he found another bug ticket from summer 2009 that stated "if the mailbox has more than 49 proxy addresses entered within
    the Email addresses tab the search command will fail".
    We re-tested a few failed search mailboxes by removing unnecessary proxy addresses from that tab the searches worked fine.
    Hope this helps others.
    Mike
    This resolved the issue I was having as well - the recipient I was trying to track for had a ton of extra smtp addresses that were not needed.  Removing them fixed the issue.

  • Adobe doesn't support this type of Mac?

    Old pdf files won't open since Mac OS X (10..4) installed on my old MacBook & a MacMini. Suggestions?

    How do they not open?
    What are you opening them with? Apple Preview or Adobe Acrobat/Reader? Is the result the same in both apps?
    It's a very strange problem because PDF is built into Mac OS X! You should not need any Adobe software to read them.
    (Missing fonts should not matter, they should open anyway. Especially if the PDF maker embedded the fonts, which many do.)

  • Support for file tag in XSLT to create dynamic pages  - Gallery type 'Flash'

    Based on my understanding, when you export, LR Web engine looks for transformer.xslt by default if the gallery type is HTML. It allows to use <file name="outputfilename.html"> tag in this transformer.xslt to create new files.<br /><br />But to my knowledge I don't see the above defaults working if the gallerytype is Flash. Why? I don't understand why LR is restricting the Flash based galleries from creating dynamic output files via XSLT.<br /><br />I tried setting xmlTransformer file name to transformer.xslt in galleryInfo.lrweb and leaving xmlPath to blank but this doesn't seem to work. If I give some dummy XML name, it creates the xml in that name, but ignores creating new files I mentioned in the <file> tag in xslt.<br /><br />Can someone please explain if there are any alternates or if possibly fixed in the next release ?

    Are you the one who commented out the code you're looking for ?//String desc = StringFactory.getString(attributes.getValue("desc"));You just have to modify you AttributeObject class to hold a new field : String description. And then, it's up to you to create a new constructor or a new setter method.
    Btw, this is not a Swing related question.

  • Xsi:type information is missing after Marshalling in JAXB

    Hi,
    I'm trying to mock the webservice, i have created classes for schema using JAXB (without any customization) and it's working. But when i try to marhsall my objects , it doesn't generate the xsi:type information of any element and attribute. I want this information since my webservice client needs this information.
    I have tried to use mapSimpleTypeDef ="true" generateElementProperty="false" but it doesn�t help.
    Following is output of marshal process
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <MessageRetrieveResponseReturn xmlns:java="java:types.api.brokerapi.soap.mms"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <return>
         <APIVersion>1.0</APIVersion>
         <ErrorCode>1000</ErrorCode>
         <ErrorInfo> Success</ErrorInfo>
         <BillingInfo xsi:type="java:BillingInfoObject" xsi:nil="true"/>
              <HeaderInfo xsi:type="java:HeaderInfoType" xsi:nil="true"/>
              <Content xsi:type="java:MessageContentType" xsi:nil="true"/>
              </return>
    </MessageRetrieveResponseReturn>
    I want output to be look like following
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <MessageRetrieveResponseReturn xmlns:java="java:types.api.brokerapi.soap.mms" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <return xsi:type="java:MessageRetrieveResponse" >
         <APIVersion xsi:type="java:apiVersionType">1.0</APIVersion>
         <ErrorCode xsi:type="xsd:string">1000</ErrorCode>
         <ErrorInfo xsi:type="xsd:string">Success</ErrorInfo>
         <BillingInfo xsi:type="java:BillingInfoObject" xsi:nil="true"/>
              <HeaderInfo xsi:type="java:HeaderInfoType" xsi:nil="true"/>
              <Content xsi:type="java:MessageContentType" xsi:nil="true"/>
              </return>
    </MessageRetrieveResponseReturn>
    I'm new to JAXB. Please let me know what I�m missing here
    Regards

    Not got a single answer , surprise whether the question is too dumb to ask or JAXB doesn't support feature or my requirement is weird :-) ... in any case let me know please
    regards

  • Generating CDATA containing XML-like text using XSLT Mapper in OFM 11g

    Hi,
    One of our partners requires XML to be sent as XML string inside a CDATA section. The use of "real" XML is not an option at the moment. We try to generate something like the following using XSLT/XSLT Mapper in SOA Suite 11g:
    <element>
    <![CDATA[
    <supplierElement1>
    <supplierElement2>
    etcetera
    <supplierElement2>
    </supplierElement1>
    ]]>
    </element>
    We've tried the following two approaches, so far unsuccessful:
    <xsl:template match="/">
    <inp1:singleString>
    <inp1:input>
    <xsl:text disable-output-escaping="yes">&lt;![CDATA[test]]&gt;</xsl:text>
    </inp1:input
    </inp1:singleString>
    </xsl:template>
    resulting in:
    <inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString">
    <inp1:input>&lt;![CDATA[test]]></inp1:input>
    </inp1:singleString>
    and:
    <xsl:output method="xml" indent="yes" cdata-section-elements="input"/>
    <xsl:template match="/">
    <inp1:singleString>
    <input>test</input>
    </inp1:singleString>
    </xsl:template>
    resulting in:
    <inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <input>test</input>
    </inp1:singleString>
    Does anyone know how to generate the CDATA section declaratively (within XSLT/XSLT Mapper), without resorting to custom code and parsing as we have to do now?
    Thanks!
    Ronald

    The exact error message I'm getting is :
    ABAP XML formatting error in XML node of type "element", name: "abap"

  • Missing xsi:type, invalid xml generated, jaxb 1.6

    Hi,
    i've this XML Schema defined for my doc/lit web service:
    <complexType name="CasDataType">
      <sequence>
        <element name="key"  type="long"  nillable="false  minOccurs="1" maxOccurs="1"/>
      </sequence>
    </complexType>
    <complexType name="AddressDataType">
      <complexContent>
        <extension base="tns:CasDataType">
          <sequence>
            <element name="FirstName"  nillable="true" minOccurs="0" type="string"/>
            <element name="LastName"  nillable="true" minOccurs="0" type="string"/>
          </sequence>
        </extension>
      </complexContent>
    </complexType>If i create a AddressDataType and return it with my web service, the jaxb-marshaller generates this xml code:
    <casDataTypes>
          <key>123</key>
          <FirstName>Ingo</FirstName>
          <LastName>Siebert</LastName>
    </casDataTypes>But correct would be this:
    <casDataTypes xsi:type="AddressDataType" >
          <key>123</key>
          <FirstName>Ingo</FirstName>
          <LastName>Siebert</LastName>
    </casDataTypes>Is this error already known?
    Is it fixed with jaxb 2.0?
    I doesn't like annotations, is it possible with jaxb 2.0 (XJC task) to geneate files without annotations?
    Cheers,
    Ingo

    Not got a single answer , surprise whether the question is too dumb to ask or JAXB doesn't support feature or my requirement is weird :-) ... in any case let me know please
    regards

  • Ehlpdhtm.js script error - Object doesn't support property or method 'Activate'

    RH 9.0.2.271
    Windows 7 64-bit
    This "Object doesn't support property or method 'Activate' ehlpdhtm.js error all of a sudden started popping up when I view any of the chms I build from my file system.
    I initially through it was a 64-bit problem because if I view the chm from my file system I get the script error. But if I copy it to a 32-bit PC or run it from within RH (after it's compiled for example) or a 32-bit version of our software, it runs fine. (However, one of my co-workers tried it on her 64-bit machine and didn't receive any error.) In any case, it seems to be happening on my machine only.
    Anyway, it's not on every topic, but on every one that calls the ehlpdhtm.js script with this line of code, it appears to be happening:
    <script src="ehlpdhtm.js" type="text/javascript" language="JavaScript1.2"></script>
    I don't think hhactivex.dll plays with this js at all, but just in case, I unregistred and re-registered that dll to no effect. I also tried explicitly adding in ehlpdhtm.js as a baggage file. Again, to no effect.
    What could have changed on my system to make this start happening? And any ideas on how to fix it?

    Well here's some more info I found out. If I unregister the 64-bit hhactivex.dll the script error  goes away. Of course my Glossary tab is grayed out as shown below, so that's not really an option:
    Reregistering the 64-bit hhactivex.dll again shows the script errors. Plus, if I then go to my glossary it's completely empty as shown here:
    If I copy this help down into a 32-bit machine everything works: the glossary has glossary terms, there's no script errors.
    In short, I don't know what's going on, but the script error I'm getting is somehow related to having the 64-bit dll registered.

  • How to use xslt mapper with sequence occurences

    I'm using Bpel process manager.
    I'm trying to use multiple partname fields in my xsd. I'have defined a sequence occurence in my xsd.
    In the xslt mapper I see just one partname. How can I map initials, nickname, fullname etc to the 'different' partnames while I just see one.
    I'hope somebody can help me?
    Jasper Goede

    I use the following xsd (just part of the whole xsd):
    <xsd:complexType name="nameType">
    <xsd:sequence>
         <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
         </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="partnameType">
         <xsd:sequence>
         <xsd:element name="typename" type="typenamenameType"/>
         <xsd:element name="text" type="nametextType"/>
         </xsd:sequence>
         </xsd:complexType>
    In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

  • Disabling validation in xslt mapper

    My xslt source code is valid as per xslt 1.0 and runs correctly when deployed. But the design view of the xslt mapper throws errors. How can I disable the error-checking of the xslt mapper?
    Thanks,
    Bipin Raj
    PS:
    Below is the xslt code that I added to my map, followed by the errors I am getting.
    <ns0:NOTES>
    <xsl:attribute name="index">
    <xsl:value-of select='string("1")'/>
    </xsl:attribute>
    <xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-N9">
    <xsl:value-of select="ns1:Element-369"/>
    <xsl:text>|</xsl:text>
    </xsl:for-each>
    <xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-MSG">
    <xsl:value-of select="ns1:Element-933"/>
    <xsl:if test="position() != last()">
    <xsl:text>|</xsl:text>
    </xsl:if>
    </xsl:for-each>
    </ns0:NOTES>
    Errors:
    Error: Invalid Usage of <for-each> Element
    Error: xsl:for-each does not Support Mixed Content
    Error: xsl:for-each does not Support Mixed Content
    Error: Invalid Usage of <for-each> Element
    Error: Invalid Usage of <if> Element
    Error: xsl:for-each does not Support Mixed Content
    Error: xsl:for-each does not Support Mixed Content
    Error: This Node is Already Mapped : "/ns0:PROCESS_PO_007/ns0:DATAAREA/ns0:PROCESS_PO/for-each"
    Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-933)
    Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-369)

    Can you explain a bit more what you want to do. It's very vague right now. Probably will be able to help you out.
    Thanks

  • How to use xslt mapper

    I'have created a xsd with sequence occurences. In the xslt mapper I try to connect nickname, initials and full name to the same field, because I just see one field.
    Can somebody help me?
    Thanks
    Jasper

    I use the following xsd (just part of the whole xsd):
    <xsd:complexType name="nameType">
    <xsd:sequence>
         <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
         </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="partnameType">
         <xsd:sequence>
         <xsd:element name="typename" type="typenamenameType"/>
         <xsd:element name="text" type="nametextType"/>
         </xsd:sequence>
         </xsd:complexType>
    In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

  • Where is XSLT mapper?

    I was advised by PeopleSoft Tech Support (who now work for Oracle!) that JDeveloper contained a utility for creating XSLT. There directions were to right-click the project, expand General, select XML, then select XSLT mapper in the Items list. Problem: XSLT mapper is NOT in that list, and I did not leave anything out when installing (Studio 10.1.3.0.3.3412)
    Essentially I have an XML interface file that I generate out of PeopleSoft Financials - and I have an XML file that my non-PS client wants to receive. There is a gap between - ok, a chasm - and apparently this XSLT mapper enables you to drag a field from one file into the other & it will generate the XSLT code for you.
    Can anyone shed some light on where this tool is? Thanks!

    Paul, this is not in the EA1 realese of JDeveloper 10.1.3.
    Something like this is suppose to be part of the BPEL extension to JDeveloper 10.1.3 production.
    There are other "more manual" XSLT capabilities in JDeveloper right now.
    See here:
    http://www.oracle.com/technology/products/jdev/101/viewlets/101/xsltdebug_viewlet_swf.html

  • Weblogic Pool Driver doesn't support XA driver

              I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle
              XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server
              starts it gives me the following exception: Weblogic Pool Driver doesn't support
              XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe full error
              trace is shown below:
              <Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer "jmsTestJmsServer1"
              store failed to open java.io.IOException: JMS JDBC store, connection pool = <jmsTestJdbcConnectionPool>,
              prefix = <JMS1>: cannot determine DBMS type
              <java.sql.SQLException: Pool connect failed : java.lang.Exception: Weblogic Pool
              Driver doesn't support XA driver, Please change your config to use a Non-XA driver
              <     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
              <     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
              <     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
              <     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
              <     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
              <     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
              <     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
              <     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
              <     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
              <     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
              <     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
              <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
              <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
              <     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
              <     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
              <     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              <     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              <     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              <     at java.lang.reflect.Method.invoke(Method.java:324)
              <     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
              <     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
              <     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
              <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              <     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
              <     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
              <     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
              <     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
              <     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
              <     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
              <     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
              <     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              <     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
              <     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
              <     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
              <     at weblogic.Server.main(Server.java:32)
              

              It appears that WebLogic 8.1 does not have the "user transactions enabled" flag
              for a connection factory. I see references to this flag in earlier versions of
              WebLogic. The closest thing in WL 8.1 seems to be the "XA Connection Factory Enabled"
              flag.
              Tom Barnes <[email protected]> wrote:
              >Actually, all you normally need to check is "user transactions enabled".
              >The XA versions of the javax.jms interfaces (which are generated
              >via XA connection factories) are not required - except
              >that I think that MDBs make a check for this.
              >
              >Naresh Bhatia wrote:
              >> So I assume that the XA capability is enabled by checking the "XA Connection
              >Factory
              >> Enabled" checkbox for the JMS connection factory.
              >>
              >> Thanks.
              >> Naresh
              >>
              >> Tom Barnes <[email protected]> wrote:
              >>
              >>>Just use a non-XA driver and non-XA pool for JMS JDBC stores.
              >>>WL JMS' XA capability does not come from its JDBC driver.
              >>>
              >>>Naresh Bhatia wrote:
              >>>
              >>>
              >>>>I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store
              >>>
              >>>uses the Oracle
              >>>
              >>>>XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen
              >>>
              >>>the JMS server
              >>>
              >>>>starts it gives me the following exception: Weblogic Pool Driver doesn't
              >>>
              >>>support
              >>>
              >>>>XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2.
              >THe
              >>>
              >>>full error
              >>>
              >>>>trace is shown below:
              >>>>
              >>>><Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer
              >>>
              >>>"jmsTestJmsServer1"
              >>>
              >>>>store failed to open java.io.IOException: JMS JDBC store, connection
              >>>
              >>>pool = <jmsTestJdbcConnectionPool>,
              >>>
              >>>>prefix = <JMS1>: cannot determine DBMS type
              >>>><java.sql.SQLException: Pool connect failed : java.lang.Exception:
              >>>
              >>>Weblogic Pool
              >>>
              >>>>Driver doesn't support XA driver, Please change your config to use
              >>>
              >>>a Non-XA driver
              >>>
              >>>><     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
              >>>><     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
              >>>><     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
              >>>><     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
              >>>><     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
              >>>><     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
              >>>><     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
              >>>><     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
              >>>><     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
              >>>><     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
              >>>><     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
              >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
              >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
              >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
              >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
              >>>><     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              >>>><     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              >>>><     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              >>>><     at java.lang.reflect.Method.invoke(Method.java:324)
              >>>><     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
              >>>><     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
              >>>><     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
              >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
              >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
              >>>><     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
              >>>><     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
              >>>><     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
              >>>><     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
              >>>><     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
              >>>><     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
              >>>><     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
              >>>><     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
              >>>><     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
              >>>><     at weblogic.Server.main(Server.java:32)
              >>>>
              >>>
              >>
              >
              

  • SendXSIType not displaying xsi:type information in soap

    We're attempting to communicate with a webservice that requires type information be passed with the SOAP request. I've seen many notes that suggest setting the sendXSIType = true in the partnerLinkBinding will accomplish this. I have set this value and verified it is in the deployed bpel.xml, but the process is still not generating the SOAP request with xsi:type information.
    Has anyone encountered this issue and overcome it? Any advice is much appreciated.
    Thanks,
    Mike

    In case anyone is curious...
    sendXSIType appears to ONLY work with rpc/endcoded style .wsdl files. There is currently a bug logged with Oracle support to determine a fix for document style webservices.
    As a workaround, I used <bpelx:rename> to recast the datatype to itself. Which basically forces the datatype to be used in the SOAP output. More info can be found here:
    http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/manipdoc.htm

Maybe you are looking for