Rename Element in ALSB

Hi..
I am getting following Response of my Proxy service.
<soapenv:Body>
     <m:getModelPortfolioResponse      xmlns:m="http://modelportfolio">
     <return>
     <java:EQUITY      xmlns:java="java:entities">15.0</java:EQUITY>
     <java:FIXED_INCOME      xmlns:java="java:entities">55.0</java:FIXED_INCOME>
     <java:MUTUAL_FUNDS      xmlns:java="java:entities">30.0</java:MUTUAL_FUNDS>
     <java:PID      xmlns:java="java:entities">100</java:PID>
     <java:REAL_ESTATE      xmlns:java="java:entities">0.0</java:REAL_ESTATE>
     </return>
     </m:getModelPortfolioResponse>
</soapenv:Body>
Now I want to Rename element "getModelPortfolioResponse"
to "displayPortfolioResponse" in AquaLogic Service bus console.
and also want to change namespace "http://modelportfolio" to "http://generatemodel".
Does anyone have an idea how can i do this?
Message was edited by:
mihirkhanwalkar

thnx dear... now I have another little problem...
here is my SOAP message...
     <soapenv:Body>
     <gen:displayModelPortfolioResponse      xmlns:m="http://modelportfolio" xmlns:gen="http://generatemodel">
     <return>
     <java:EQUITY      xmlns:java="java:entities">0.0</java:EQUITY>
     <java:FIXED_INCOME      xmlns:java="java:entities">0.0</java:FIXED_INCOME>
     <java:MUTUAL_FUNDS      xmlns:java="java:entities">0.0</java:MUTUAL_FUNDS>
     <java:PID      xmlns:java="java:entities">100</java:PID>
     <java:REAL_ESTATE      xmlns:java="java:entities">0.0</java:REAL_ESTATE>
     </return>
     </gen:displayModelPortfolioResponse>
     </soapenv:Body>
I want to rename "java:entities" to "java:entity".
Is this possible? If yes HOW?
Thanx in advance dear....!!!!

Similar Messages

Remove SOAP Header Element from ALSB Proxy Service Response

I've got a client of one of my ALSB Proxy services that needs the SOAP header element removed from the response. I'm struggling to find a way to do that with a WSDL-based proxy service. Do I need to change my service to an Any XML Service or is there an easier way?

At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
My client is expecting a soap response and the backend gives back only the XML Response
Thanks in advance!!
~Swagat

Renaming element names in XML

I need to rename some nodes in an XMLType. What will be the appropriate way to do this change? Below is an example input followed by the desired output. Notice that some elements have V2 appended at the end in the output.
(Note: The actual input XML has many more elements that have been omitted in the sample below, only the ones needed to be renamed are shown).
<Request>
     <OrderList>
          <Orders>
               <Order>
                    <OrderCode>A</OrderCode>
                    <OrderItems>
                         <OrderItem/>
                    </OrderItems>
               </Order>
               <Order>
                    <OrderCode>B</OrderCode>
                    <OrderItems>
                         <OrderItem/>
                    </OrderItems>
               </Order>
          </Orders>
     </OrderList>
</Request>
Desired Output:
<Request>
     <OrderList_V2>
          <Orders_V2>
               <Order_V2>
                    <OrderCode>A</OrderCode>
                    <OrderItems>
                         <OrderItem/>
                    </OrderItems>
               </Order_V2>
               <Order_V2>
                    <OrderCode>B</OrderCode>
                    <OrderItems>
                         <OrderItem/>
                    </OrderItems>
               </Order_V2>
          </Orders_V2>
     </OrderList_V2>
</Request>
Thanks

For now, I've used REPLACE to solve the problem. I get String value of the incoming XMLType in a clob, do REPLACE and then change it back to XMLType. The source of the message is an external system. The message comes through a queue. The external system is moving to a new xml message format in an upcoming release. This change is needed only temporarily to handle both new and old messages by the receiving system during the transition period.
Thanks

Rename elements in Layer Pallette

Would be great to have the ability to rename all the elements in the layer pallette, just like in Photoshop. As it stands if I have 100 rectangles on a page, they are all just called "Rectangle" there is no way to differentiate between them.

Put this suggestion under "Ideas for Muse"

How to rename element (node) names in an XMLType column?

I have a source table with a xml data stored in an XMLType column.
The xml contains elements/nodes identified by numbers. I need to replace the numbers with the appropriate names.
The plsql below does this, but has two issues:
i. It selects the data into a clob and does a text replace on the elements in a loop. This works, but is super slow for 3500+ xml rows (about 500 node pairs per row).
ii. Once the data has had the element numbers replaced with the names, it inserts the new xml (clob wrapped in xmltype function) into the table with the XMLType attribute.
The problem with the latter action is that it is failing due to nls client vs server settings, or so it appears from what I could dig up. The actual error message:
ORA-19202: Error occurred in XML processing
LPX-00242: invalid use of ampersand ('&') character (use &)
Error at line 3
There are come entities in the original xml like "" (the degree symbol).
My question is two-fold:
a). Can I replace the element names without straying from the xmltype datatype? If so, how?
b). If I cannot do "a.)", then what must I do ensure that the clob gets converted correctly to xmltype and inserted into the table?
SQL> select <some rows> from nls_database_parameters ;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET WE8ISO8859P1
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
SQL> SELECT * FROM NLS_SESSION_PARAMETERS;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
----code below-----
(note, this is a stripped down version of the original, so there may be typos)
declare
l_xmlclob CLOB;
l_newxml XMLType;
v_record_uid NUMBER(20);
CURSOR my_cur IS
select a.elementname,b.tagname
from t_elements a, t_tags b
where (a.element_uid = b.element_uid)
begin
select br.xml_data.getClobVal() xml_data into l_xmlclob from t_elements;
FOR my_rec IN my_cur LOOP
l_xmlclob := replace(l_xmlclob,my_cur.elementname,my_cur.maptag_name);
END LOOP;
l_newxml := XMLType(l_xmlclob);
insert into test_translated_xml (xml_data) values (l_newxml);
end;
(hopefully I haven't missed anything)
Any tips or hints would be much appreciated.
Thanks!

Hello again,
Take a look at html entity codes: http://www.w3schools.com/tags/ref_entities.asp.
You can use this:
insert into t values (xmltype('<test>'||dbms_xmlgen.convert('this is a test &')||'deg;</test>'));
or
insert into t values (xmltype('<test>'||dbms_xmlgen.convert('this is a test &')||'#176;</test>'));
see this: ° (& deg;) or this: ° (& #176;)
SQL*Plus will not display degree character. But this is valid enitity code, and when you generate HTML out of this, it should be displayed properly in web browser.
HTML is in fact XML, that is validated by specific DTD (Document Type Definition).
Paweł

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

Difficulties to rename elements in Finder

Hello,
I've a problem with the 4.8 update: Everytime I simple-click an element to change its name, its title, which should become blue, becomes instead transparent, which forces me to calculate how many letters I've to bring my cursor back to make the change. I've sometimes had that problem in former updates, but with X.4.8 it's happening all the time.
Has anybody else experienced the same issue?
Thank you
Regards

Hello,
I haven't installed any third party program since i upgraded. Perhaps aMule or Quicktime are causing me some troubles, they seem unstable (with the spining ball quite often).
Thanks
Regards
PS: I've been using AppZapper (which increases unistalling process) since a few months. But I don't think that it changes the Finders way of working. What do you think?
Perhaps a clean reinstallation of Tiger would do it. But it's time consumer...

Rename namespaces in Aqualogic service bus

When I try to rename namespaces in ALSB the new namespaces is created and validated against the schema, but the old one is still exist. How I can delete the old namespace.
Example
<cus:soapHeader xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest">
     <com:version>1</com:version>
     <com:callingAppID>MaxP</com:callingAppID>
</cus:soapHeader>
After rename
<cus1:soapHeader xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest"
xmlns:cus1="http://www.crm.bellalaint/es/CustomerProfileService"
xmlns:com1="http://www.bellalaint /enterprise/CommonRequest" >
<com1:version>1</com:version>          <com1:callingAppID>MaxP</com:callingAppID>
</cus:soapHeader>
I want to remove xmlns:cus="http://www.crm.bell/es/CustomerProfileService"xmlns:com="http://www.bell/enterprise/CommonRequest" from response

Could you send me the WSDLS?
My email address [email protected]

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

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

Namespaces in conversion table

We're encountering an issue with the use of namespaces with elements in a conversion table. The Adobe documentation seems to suggest that namespaces are supported in Frame, and, in documents that are already structured, we encounter no problems.
However, when we attempt to convert an unstructured doc using namespaced elements in the second column of the conversion table, the process won't work. We get errors for every element that includes a namespace prefix.
We've tried to get around the issue by assigning qualifiers in the third column and then using those in the first column, but with no luck.
Any thoughts or suggestions would be much appreciated.

Quoted from the Structure Developer Reference:
The following characters are not allowed in an element tag, but
can appear in a format or qualifier tag if you precede them with a backslash (\) in the table:
( ) & | , * + ? % [ ] : \
end quote.
The structure conversion tables have been around far longer than namespaces in XML, so we just have to hope that they get updated soon.
You will also find that some of FrameMaker's building blocks and EDD context rules have trouble with the colon character where it has long been used by FrameMaker for other purposes.
I tend to rename elements that have an XML namespace using XSLT, eg:
xml:lang in XML is transformed into xml.lang in FrameMaker which makes it possible to write EDD rules that refer to the value of the xml.lang attribute.
Ian

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

Creating Acrobat 3D files from Microstation - problems

I am using Microstation as my CAD platform. There are a number of ways I can create 3D files from within Microstation, but only one method seems to allow the transfer of the levels used in Microstation. I do this by opening Acrobat 3D, then importing the microstation 3D file. Doing this brings across all the Microstation level info into the model tree. That is perfect, BUT, the model is not rendering properly/fully in Acrobat.
The Microstation file is about 3MB in size and the created pdf file is 7MB in size.
Another method I've used is to export from with Microstation to a "u3d" file format, then import that file into Acrobat 3D. This method and a few others I have tried will import the 3D model, fully rendered without problem, but none of the levels are imported from Microstation. These files are about 1.5MB or less.
The problem is that it is important for my clients to be able to use the model tree to toggle various levels on and off. It is not practical for me to use the 3D Toolkit to group and rename elements to match the Microstation levels.
Can anyone help me here? I'm thinking there must just be a setting I need to toggle on and off somewhere to fix the problem.
I am using Microstation V8, Acrobat 3D Version 8, My workstation is dual processor @ 3 GHz and 2GB RAM.

Yes, all versions of Acrobat can do that.
On Tue, Mar 31, 2015 at 11:54 PM, mariab59929580 <[email protected]>

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

How can a structured frame be used for translating books to foreign languages?

I keep reading about how a structured approach can improve the translation process (from english to foreign languages), however, i can't seem to find specifics about a particular method or tutorials about how to go about it (specifically). My question is, how (specifically) can structured framemaker be used for translation from english to foreign languages? Links to tutorials on this issue would be greatly appreciated. Thank you.

@Ian Proudfood
A well organized XML based project will definitely save translation costs. There are many advantages to the XML approach to translation management including:
Almost zero DTP rework costs - make the EDD/Template do all of the work!
Translation is application version independent - no need to wait for the Translation Memory/CMS system vendor to support the latest version of FrameMaker.
»... a well organized XML based project will definitively save translation costs.« – I have read sentences like this from a lot of consultants. And I have consulted/supported a lot of customers after those consultants left the stage. I always hear more or less the same from all of those clients. No question, I hear a lot of arguments for working with XML in tech doc, most of the arguments you mention included. Most of the tech writers are happy with the new structured FrameMaker and enjoy writing. And, cross your heart: Finally there's no alternative to XML in the long term if you take your tech writer job seriously. No question – working with pure XML in a professional information architecture in a structured, guiding editing environment like FrameMaker is cool, fun, faster and produces more open, more accessible, more reusable, more reliable, more consistent, in a nutshell: more valuable data.
But what I have never ever heard, and I'm talking about several hundred companies, is: We save more money on translation now. You might imagine that this is surprising me since many years. This is why I always ask: Did you save any costs in your translation projects? Surprisingly the answer is always: No. Actually some – no, wait: many – tell me, that their translation agency even charges more now, because they have a lot of new costs:
Costs, to customize their translation memory system to the clients custom xml,
costs to follow badly or not documented changes in the client's xml structure (DTD/Schema changes) in the TMS,
costs because of more engineering work like
valididating xml in advance,
fixing invalid xml exports,
fixing invalid translations due to – sometimes massively – increased amount of tag errors because of tagging differences of "old" (legacy mif) and "new" (xml) tags,
dealing with just too big XML files that need to be carefully split, so that the TMS has a chance to read it, or alternatively:
"glue" the ten-thousand xml "snippets" to more handy chunks,
project managers and translators that need to do additional checks, validations, verifyings - and often not knowing what to do with those cryptic error messages, meaning additional support costs
Of course, many if no all of these and many other problems I did not mention here can be solved. And many are not exactly system immanent problems but communication problems (like introducing or renaming elements/attributes but not documenting this and not communicating this to the translation service provider) or would apply to any system change (e.g. also when switching from Word to Frame). However, I do not know of any single translation company on this planet (and I know virtually thousands of them from countries all over the world) that reduced the price per word for just a single pence, just because the client switched over from Word/Quark/FrameMaker/InDesign/Whatever to XML.
Just ask your translation service provider: Will you charge me less per word if I send you XML instead of MIF? I would really be surprised to hear a "yes". And frankly, if you have ever compared a professional FrameMaker document with the same document in xml format in a professional system like Trados: There is actually no difference that would justify any price difference. The text is the same, the amount of words identical, the number of tags is identical, it even looks identical in the translation system (I can post screenshots if you like). From the translation perspective there is no single reason why a translator should charge a single pence less.
So, it's a modern myth, that switching to xml reduces translation costs. That might be true, if you come from a really medieval documentation szenario with MS Word or the like, with manual formatting without any styles and so on (I see tech docs every day where even the TOC is typed in manually!!!) and swith from there to a modern structured xml authoring in combination with other supporting tools like authoring memory / authoring assistance, controlled language, translation memory and terminology managent and control, snippet based content management and so on. That will increase the consistency and quality of your data, which will reduce translation costs in the long term. But the truth is: This has nothing to do with XML per se, but with professional writing and professional management.
So, what's left in the money saving story? No more DTP in the target languages? I always hear, that with XML and FrameMaker you do not have to "format" the translated document. The truth is: If you have a professionally formatted (unstructured) document, you don't have to take care of it, too. Modern tools like Trados keep 100% of the formatting 100% correct in the translated document. If the underlying template is intelligent enough to take account of text amount changes due to longer translations, and if you don't have too many local formatting overrides, the DTP is actually zero and can be reduced to a few mintes/hours for "flying" of the document to check out for unexpeted problems wich can occure in both structured and unstructured documents.
Just to give some numbers on this: We are processing every day technical documentations for a quite big company. A typical documentation from them is about 250 pages in unstructured FrameMaker 9 (source language is English). Until now they were resistent to all my XML pushing. The Documentation is based on a straight, simple template (with our help "reduced to the max") and there are no formatting overrides (a script automatically checks this). The post translation Quality Assurance effort is - depending on the target language - usually something between 1 to 4 hours – that's a few seconds per page for the languages where already a lot of past Quality Assurance Steps went back into the Translation Memories and up to a minute per page for more "problematic" languages).
So, again: XML will not save you a single pence on translations. But it might help you to produce more open, more accessible, more reusable, more reliable, more consistent, in a nutshell: more valuable data. But if you already have properly set up (ustructured) FrameMaker Documents and already work with a professional translation memory system, you will be quite disappointed to learn, that the impressive money saving promises you recently saw on that great PowerPoint slides melt down to a few bucks over a couple of years.
Kind regards,
Stefan Gentz

Rename Element in ALSB

Similar Messages

Maybe you are looking for