[runinord]

I need to get rid of the namespace that has been added to OTM 5.5.2
Old transmision looked like
- <Transmission>

but OTM5.5.2 now looks like
- <Transmission xmlns="http://xmlns.oracle.com/apps/otm">

This is measing up all our translations so how do i remove the namespace from the OUT XML output I.e.
remove the xmlns="http://xmlns.oracle.com/apps/otm" from the above

[bmclamb]

We are on 5.0, but we had a similar problem when we upgraded. I believe we had to modify the property setting below in the glog.common.properties file. I'm not sure if it is the same in 5.5

# Added for BPEL integration
glog.integration.printXmlDeclaration=false
glog.integration.xmlNamespace=

Beth

[chrisplough]

Beth,

Thanks for the properties. This may actually help me with a client issue today. Great timing!

Just a note on modifying the OTM property files. All changes should go into the glog.properties file, within the section below. This will automatically override the settings in other lower-level property files (glog.app.properties, glog.web.properties, glog.common.properties, glog.base.properties).

#--------------------------------------------------------------------
# Custom Properties - Beginning
#--------------------------------------------------------------------
# Place all changes, new properties, and custom properties here.
# This section will be used during GC3 Upgrades
#--------------------------------------------------------------------

# Added for BPEL integration
glog.integration.printXmlDeclaration=false
glog.integration.xmlNamespace=

#--------------------------------------------------------------------
# Custom Properties - End
#--------------------------------------------------------------------

Hope this helps!

--Chris

[runinord]

This can be achieved by seting property value
glog.integration.enableXmlNamespace=false
in the glog.properties file.
Runi

[ianlo]

Just a note, one thing I found out was that on a 2-tier environment where the Web and Appare on separate servers, you would need to set the glog.integration.enableXmlNamespace=false on glog.common.properties file on BOTH servers.