OSB namespace replace

Hi all...
I have a webservice defined at OSB that has the following body:
<get:Source xmlns:get="http://www.x1.com/esb/GetManufacturersRequest">string</get:Source>
The namespace is not the actual namespace of the service I am calling, so, I want to use OSB to change it to:
<get:Source xmlns:get="http://soa.x1.com/esb/GetManufacturersRequest">string</get:Source>
I can't seem to figure out the right combination of actions to get this to occurr.
Is there anyway to do this before the web service is actually called? Or, am I just stuck with the namespace the provider has selected?
Thanks for any help!!!

Thanks for the reply!
If I could just beg one more moment of your time....
The proxy is hosted at http://soa.x1.com/esb/GetManufacturersRequest
The actual service called (via the business service) is at http://www.x1.com/esb/GetManufacturersRequest
I want to change the data in the request (using soa.x1.com namespace) to www.x1.com (the actual service namespace) on the fly. This way I can make all namespaces, regardless of where the service may be hosted, relative to the soa.
So, the problem is, I don't really know what to put in the rename function...
The params are:
XPath:
In variable:
Localname:
Namespace:
Maybe I have been a C programmer for too long, but, I don't know whether the XPath should be to the $body or to the actual element/attribute I want to modify. Furthermore I am not sure which of the two parameters LocalName/Namespace is used for the replacement value...
I've looked (not endlessly, but, a lot) through the documentation and google for help/tutorials/api refs, but, I can't find much help on how to use some of the actions or the "bea" extensions to XQuery/XPath expressions...
Thanks again...

Similar Messages

Namespace replace/rename issue in ALSB

Hi,
As part of our project we have been using ALSB3.0. In one of our outbound Proxy flows we have configured transform stage which intern executing XQuery transormation. Post transformation it publish message on BEA JMSTopic in following format.
*<?xml version="1.0" encoding="UTF-8" ?>
<ref:ABCMessage xmlns:ref="http://www.indteur.org/abc/2.1/reference">
<ref:FromEANNumber>NA</ref:FromEANNumber>
<ref:SenderIdentifier>
<ref:SenderIDType></ref:SenderIDType>
<ref:IDValue></ref:IDValue>
</ref:SenderIdentifier>
<ref:SentDate>2009-10-10T18:41:27.870-04:00</ref:SentDate>
<ref:Product>
<ref:RecordReference></ref:RecordReference>
<ref:NotificationType>04</ref:NotificationType>
<ref:RecordSourceName></ref:RecordSourceName>
</ref:Product>
</ref:ABCMessage>*
Please help us in rename/replace namespace prefix from 'ref:' to 'ns1:' at post transformation and before publishing the saem to JMS Topic.
Thanks in advance........

Personally I would mandate that what ever is the consumer of the JMSQ should be compatible with XML name space constructs. If it is not under our control then one solution would be
1) Convert the xml to string
let $strContent := fn-bea:serialize($body)
2) Replace the ref: with ns1:
return fn-bea:inlinedXML(fn:replace( $strContent, "ref:", "ns1:") )
This is a very bad solution but should solve your issue if XML is not huge (huge XML will consume lot of cpu for this transformation ) .Ideally I would recommend changing the behavior of the message consumer.
Also you can try defining name space for http://www.indteur.org/abc/2.1/reference as ns1 in sbconsole proxy name space definitions. I believe even this will work but never tried.Let me know if this works for you.
My two cents
Manoj
Edited by: mneelapu on Oct 13, 2009 9:18 AM

OSB installation - replacing log4j with more newer version

Hi,
Is it safe to replace in production a log4j_1.2.8.jar file that is a part of OSB installation with a newer version - log4j-1.2.16.jar?
We try using JBoss JMS client in the domain where OSB is installed, however it requieres at least 1.2.12 version of log4j.
Thanks,
Yuriy

I wouldn't replace any library bundled with WebLogic. I would rather put new jar into the application and set prefer-web-inf-classes to true.
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/programming/classloading.html#1082452

OSB, action Replace

Hello!
I need for add '1' to value of "Value" in xml (800 -> 8001). Part of xml which i want edit is:
<multiRef id="id388">
    <key>NM_SCHEMA</key>
    <value>SCHEMA_NAME</value>
</multiRef>
<multiRef id="id389">
    <key>KD_REG</key>
    <value>800</value>
</multiRef>
When i try to replace then first i set XPath:
.//multiRef[key='KD_REG']/value
The question is: how i can use XQuery to replace node content with right value?

For Each [ multiRef ] in [ .//multiRef[key='KD_REG']] of [ body ]
Indexed by [ undefined Variable ] with total count in [ undefined Variable ]
Do (
Replace [ node contents ] of [ ./value ]
in [ multiRef ] with [fn:concat($multiRef/value/text(),'1')]
Work fine in my case.
fn:concat documentation - http://www.xqueryfunctions.com/xq/fn_concat.html

OSB namespace definition problem

Hi,
How can I use "op:subtract-dates($arg1 as xs:date, $arg2 as xs:date) as xs:dayTimeDuration?" xquery function ? I added prefix="op" with the URI="http://www.w3.org/2002/08/xquery-operators". But I got the "unknown function" error.
Thanks.

Hi,
As per the spec :
http://www.w3.org/TR/xquery-operators/
(1.2 Namespaces and Prefixes - section)
Functions defined with the op prefix are described here to underpin the definitions of the operators in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0]. These functions are not available directly to users, and there is no requirement that implementations should actually provide these functions. For this reason, no namespace is associated with the op prefix. For example, multiplication is generally associated with the * operator, but it is described as a function in this document:
op:numeric-multiply($arg1 as numeric, $arg2 as numeric) as numeric
so probably this isn't available for use. however you can rely on similar xpath functions from the engine.
hope this helps.
regards,
Jitendra
Edited by: user10071542 on Feb 23, 2010 10:10 PM

OSB & fn:replace

Hi all,
I've a proxy of type Any XML Service that publishes the contents to another system.
The xml contents is:
<msg_asset>
<name_list>
<name lang="automatic">
<normal>My Holding 
AG CHF (1111111)</normal>
<short>My Hldg N</short>
<long>My Holding AG CHF</long>
</name>
</name_list>
</msg_asset>
and I need to remove  or to replace  with a space because the target system is not able to process a multiline 'name'.
I tried with
fn:replace($message, '', '')
but it is not working ...
Do you have any suggestion ?
kind regards
ferp

Hi Patrick,
you're right :-) my sequence of characters to be removed/replaced has been interpreted by the forum !!!!
The xml contents received as input is:
<msg_asset>
<name_list>
<name lang="automatic">
<normal>My Holding & #10;& #13;AG CHF (111111)</normal>
<short>My Hldg N</short>
<long>My Holding AG CHF</long>
</name>
</name_list>
</msg_asset>
The sequence of characters to be removed or replaced with a blank is:
& #13
without any space between & and #
I add the space so you can see what is sequence of characters to be removed/replaced and so it is not interpreted by the forum.
As I said I tried with
fn:replace($message, '& #13', '')
but it is not working.
(Again the extra space between & and # has been added only to make sure you can see in the correct way my post).
Thanks
ferp

Changing the namespace prefix in OSB body content

I would like to change the namespace prefix of the namespace in the content of the Body in OSB (Replacing g: with dg:)
For example:
<g:Information>
<g:firtName>John<g:firstName>
<nc:date>1970-01-01<nc:date>
</g:Information>
should become
<dg:Information>
<dg:firtName>John<dg:firstName>
<nc:date>1970-01-01<nc:date>
</dg:Information>
Any idea how can I do this?

Re: Namespace replace/rename issue in ALSB
Regards,
Anuj

Controlling Namespace Prefix in OSB10gR3

Hi,
I am doing a xquery transformation in my application, where I have defined a few namespaces with prefixes, but the prefixes get changed in my output. Is there anyway I can control the namespace prefixes.
Thanks,
Balaji.

Hi Balaji,
Have you defined those namespaces in OSB configuration with same prefix? If no, please do so, it should work.
Few alternate approaches are mentioned here -
Re: Namespace replace/rename issue in ALSB
Regards,
Anuj

Remove prefix xml in OSB

hi,
i have this xml
<operacionDummy xmlns="http://sample.services.dummy/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<arg0 xmlns="">
<fechaOperacion>2010-04-29T16:17:34.687000-04:00</fechaOperacion>
<valorAuditoriaNuevo>2</valorAuditoriaNuevo>
</arg0>
<arg1 xmlns="">
<capitalSubscrito>100000.0</capitalSubscrito>
<razonSocial>Razon Social3</razonSocial>
</arg1>
<ns1:ubicacionWebDTO xmlns:ns1="//sample.services.dummy/">
<ns1:direccion>[email protected]</ns1:direccion>
<ns1:idTipo>E</ns1:idTipo>
<ns1:idUbicacionWeb>1</ns1:idUbicacionWeb>
</ns1:ubicacionWebDTO>
<ns1:telefonoDTO xmlns:ns1="//sample.services.dummy/" xsi:type="ns1:telefonoDTO">
<ns1:codigoAcceso>0212</ns1:codigoAcceso>
<ns1:idPais>1</ns1:idPais>
<ns1:nombrePais>Venezuela</ns1:nombrePais>
<ns1:numeroTelefonico>2222222</ns1:numeroTelefonico>
<ns1:tipoUbicacion>O</ns1:tipoUbicacion>
</ns1:telefonoDTO>
</operacionDummy>
i want this
<operacionDummy xmlns="http://sample.services.dummy/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<arg0 xmlns="">
<fechaOperacion>2010-04-29T16:17:34.687000-04:00</fechaOperacion>
<valorAuditoriaNuevo>2</valorAuditoriaNuevo>
</arg0>
<arg1 xmlns="">
<capitalSubscrito>100000.0</capitalSubscrito>
<razonSocial>Razon Social3</razonSocial>
</arg1>
<arg2 xmlns:ns1="//sample.services.dummy/">
<direccion>[email protected]</direccion>
<idTipo>E</idTipo>
<idUbicacionWeb>1</idUbicacionWeb>
</arg2>
<arg3 xmlns:ns1="//sample.services.dummy/" xsi:type="ns1:telefonoDTO">
<codigoAcceso>0212</codigoAcceso>
<idPais>1</idPais>
<nombrePais>Venezuela</nombrePais>
<numeroTelefonico>2222222</numeroTelefonico>
<tipoUbicacion>O</tipoUbicacion>
</arg3>
</operacionDummy>
Basically i want to remove the prefixes and make a rename...
I want to acomplish this by actions in the osb or by XQuery transformations..
Thanks in advance
Edited by: gfandino on 29-abr-2010 16:38
Edited by: gfandino on 29-abr-2010 16:38

Xquery function of string replacement should be easiest. (definitely not suited for some use cases)
Refer--
Re: Namespace replace/rename issue in ALSB
Re: OSB 10gR3, XSD's, namespaces, etc
Manoj

OSB how to avoid insertion of xmlns:xsi="xsi" in balise

Hi,
We have web services with saml tag.
When proxy service process the datas, the SAML assertion have been modified with en added namespace : xmlns:xsi="xsi" or xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Does it possible to avoid that OSB add this namespace when it process data?
thanks in advance,

1) Convert the xml to string
let $strContent := fn-bea:serialize($body)
2) Replace the ref: with ns1:
return fn-bea:inlinedXML(fn:replace( $strContent, "ref:", "ns1:") )
This is a temporary solution but should solve your issue if XML is not huge (huge XML will consume lot of cpu for this transformation ) .Ideally I would recommend changing the behavior of the message consumer.
Re: Namespace replace/rename issue in ALSB
http://forums.oracle.com/forums/thread.jspa?messageID=4018989�
Namespace declarations
Manoj
Edited by: Manoj Neelapu on Apr 13, 2010 2:52 PM

Stripping CDATA in OSB

Hi there,
I have an incoming message which has CDATA tag in it...
Is there an easy way to stip the CDATA and just return the raw xml?
I tried some osb/xquery replace... but it does not seem to work...
[OSB Tracing] Entering stage stage1 with message context:
[MessageContextImpl body="<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><![CDATA[<PURCHASE_ORDER_150 partner="XXX" transaction="PURCHASEORDER" version="1.50" timestamp="2011-04-19T10:36:55" ...................
......_QTY_ORDERED></CONTROL></PURCHASE_ORDER_150>]]></soapenv:Body>"
Thanks
Ganesh

(:: pragma bea:global-element-parameter parameter="$pURCHASE_ORDER_1501" element="ns0:PURCHASE_ORDER_150" location="GG_ORDER.xsd" ::)
(:: pragma bea:global-element-return element="ns1:GGGetOrderResponse" location="GGGetOrder.xsd" ::)
declare namespace ns1 = "http://www.sample.com/GetHttpOrder/GGGetOrder";
declare namespace ns0 = "http://sample";
declare namespace xf = "http://tempuri.org/GG_Order/asdasd/";
declare function xf:asdasd($pURCHASE_ORDER_1501 as element(ns0:PURCHASE_ORDER_150))
as element(ns1:GGGetOrderResponse) {
<ns1:GGGetOrderResponse>
<ns0:PURCHASE_ORDER_150>{ $pURCHASE_ORDER_1501/@* , $pURCHASE_ORDER_1501/node() }</ns0:PURCHASE_ORDER_150>
</ns1:GGGetOrderResponse>
declare variable $pURCHASE_ORDER_1501 as element(ns0:PURCHASE_ORDER_150) external;
xf:asdasd($pURCHASE_ORDER_1501)
Edited by: Ganesh on Apr 27, 2011 9:41 PM

OSB or Oracle ESB????

Hi all..
We know that oracle has two service bus's OSB and Oracle ESB....i heard in future releases of SOA Suite OSB gonna replace Oracle ESB..and
Oracle ESB will behave something as mediator...Can someone explan wats the oracle statergy regarding these two products in future...also
wch is best OSB or Oracle ESB...can someone throw light on this.

Oracle ESB’s primary mission was
to provide service mediation and application integration capabilities to SOA
composite application developers. This use-case can be described as “in-line
mediation” since it is used for transformation, routing and event delivery inside of
what is logically a composite application.
Oracle Service Bus on the other
hand focused on solving the operations and scalability problems in a standalone
service bus. Here the use-cases that it focused on were those of service
virtualization, on-ramping and aggregation of external services and gateway
functionality.
By combining the respective strengths of Oracle ESB and AquaLogic Service Bus(Now OSB)
in the Oracle SOA Suite platform, Oracle will enable all the common ESB usecases
and provide unmatched flexibility and functional capabilities.
The Mediator(OESB/ESB) is an intra-composite mediation component that is
deployed within an application. It is responsible for brokering
communications between components that make up a composite, enabling
transformation, routing, event delivery and payload validation inside the
composite. The main users of the Mediator are application developers
assembling multiple components into a composite application which can
be deployed, versioned and managed as a single deployment unit (all based
on the SCA, or Service Component Architecture, standard). This is the
component that all the Oracle Fusion Applications are leveraging, as well
as AIA – the Oracle Application Integration Architecture. Oracle ESB
seamlessly evolves into the Mediator in the 11gR1 release.
The Oracle Service Bus provides standalone service bus capabilities,
enabling separation of concerns between application developers and target
systems or services. The main users of the Oracle Service Bus are
integration developers and operations personnel. Their mission is to shield
application developers from changes in the endpoint services or systems
and to prevent those systems from being overloaded with requests from
upstream applications. In the 10g and 11g releases, the Oracle Service Bus
will also be augmented with key features from the current Oracle ESB,
such as domain-value-map, cross-references, JCA adapters and a
JDeveloper-based design-time. The Oracle Service Bus is based on
Aqualogic Service Bus, with the incorporation of some of the advanced
features from the Oracle SOA platform.

Integration Builder - Repository - Users - Roles

Is it possible to come up with ABAP role with the help of which he can login to Integration Repository but can not change any of the objects but for the one in a specific component.
I could make it work where the user is given SAP_XI_DEVELOPER role and I can restrict him to access some objects using another Role that I built in IR. I know about excluding him full edit access etc. This is like giving him full access with modify permissions with SAP_XI_Developer and excluding him permission on some of the objects.
I tried to give a test user SAP_XI_DIPLAY_USER and then giving him include-fulledit on a specific Software component. But this did not work.
If anybody worked on this please let me know.
Regards
Mike

Hi Michael,
Yes it is possible, this is what i found on help.sap.com,
To make changes to authorizations on the ABAP side, proceed as follows for each dialog user role:
       1.      Call transaction PFCG.
       2.      Copy the single role SAP_XI_<role>_ABAP into the customer namespace (replace the prefix SAP).
       3.      Create a new composite role in the customer namespace (for example, *_XI_<role>).
       4.      Assign the new single role (suffix _ABAP) to the new composite role.
       5.      Assign the new SAP single role (suffix _J2EE) to the new composite role.
       6.      Make changes to the new single role (suffix _ABAP).
       7.      Generate an authorization profile for the new single role (suffix _ABAP).
Basically what is important is that the single roles with a J2EE suffix are still assigned to the current composite role. These J2EE single roles are known to the J2EE applications and are required for automatic authorization assignments during deployment.
I hope it helps,
Thanks,
Varun

Modify the contents of xquery resource using customization file

I have a xquery resource that stores constants that are environment specific.
Is there a way to use the 'customization file' feature in OSB to replace the contents of the file instead of having separate xquery resources for each environment ?

You cannot do this using the customization feature..

Facing challenges in CCSID

My OSB proxy service is reading UTF-8 encoding XML messages from an IBM WebSphere MQ and the XML has the following elements with special chars:
<value>10% ֠15%</value>
<value>This corrected report is issued to correct the Interpretation from Ӳ5 Ԡto Ԡ250 Ԯ There are no other changes to the original report.</value>
When I opened my XML with N++ edition with UTF-8 encoding format it’s showing the following special chars: x96, x93, x94.
Now the problem is OSB is replacing all these special chars with question mark symbol (?) while reading from IBM WebSphere MQ queue. How to avoid this behavior? Please advise.
Thanks in advance

Thanks.
I assigned CCSID value to 1208 in MQ Connection resource still I am getting the following exception:
Caused By: com.bea.wli.sb.sources.TransformException: Failed to parse XML text
     at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:206)
     at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
     at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
     at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
     at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
     at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
     at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
     at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
     at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
     at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
     at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
     at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
     at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: org.apache.xmlbeans.XmlException: error: Illegal XML character: 0x1a
org.apache.xmlbeans.impl.piccolo.io.IllegalCharException: Illegal XML character: 0x1a
     at org.apache.xmlbeans.impl.piccolo.xml.XMLReaderReader.read(XMLReaderReader.java:169)
     at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yy_refill(PiccoloLexer.java:3477)
     at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:3962)
     at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
     at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
     at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
     at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3456)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1331)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1305)
     at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:360)
     at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:765)
     at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:197)
     at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
     at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
     at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
     at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
     at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
     at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
     at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
     at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
     at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
     at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
     at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
     at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
     at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3488)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1331)
     at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1305)
     at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:360)
     at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:765)
     at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:197)
     at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
     at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
     at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
     at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
     at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
     at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
     at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
     at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
     at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
     at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
     at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
     at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
     at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
     at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
     at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
     at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

OSB namespace replace

Similar Messages

Maybe you are looking for