Namespace prefix tags in the generated proxy

Hi,
I am using JDevloper10G to create proxy for a webservice. The generated xml request message seem to contain namespace prefix tags. Is it a bug in 10G and resolved in 11G?
Thanks.

"Is it a bug in 10G and resolved in 11G?"
Easiest way to tell is: download 11g and give it a go. Otherwise log a support request with Oracle Support and ask them.
CM.

Similar Messages

Need help getting rid of those ASX:ABAP tags from the generated XML file!

I was able to transfer xml data from abap internal tables to a string.
Here is the content of the string:
<?xml version="1.0" encoding="iso-8859-1"?>
<asx:abap version="1.0" xmlns:asx="http://www.sap.com/abapxml">
<asx:values>
<DATA>
<item>
<UOM1 />
<UOM2>L</UOM2>
<GL_PR_SEG />
<RECORDMODE>A</RECORDMODE>
</item>
</DATA>
</asx:values>
</asx:abap>
Now my goal is to strip out a couple of tags out of that string directly using xslt.
Do you know of any way i could take out the <asx:abap> and <asx:values> tags using an xslt program. I'd like to be able to strip them out directly from the string itself.

its not function. its within abap.
within your abap program, the xml code is in a string for example xml_string .
use
replace all occurrences of '<ASX:ABAP>' in xml_string with '' .
replace all occurrences of '</ASX:ABAP>' in xml_string with '' .
replace all occurrences of '<ASX:VALUES>' in xml_string with '' .
replace all occurrences of '</ASX:VALUES>' in xml_string with '' .
Hope this solves your issue.
If your question is answered, reward the helpful answers with points and close the thread.
Regards
Raja

JDeveloper 10.1.3 - Disabling ns0: namespace prefix in soap body children ?

I am attempting to use a PeopleSoft web service. However, the PeopleSoft web service does not recognize operations which have a namespace prefix. Using visual studio, namespace prefixes are not used in the child elements of the soap body element. I am able to call the service using visual studio.
JDeveloper 10.1.3 uses a namespace prefix for children of the body element which is recommended by the soap spec. However, I need to disable that behavior so that I can actually get the program working with PeopleSoft.
Can anyone tell me if there is an easy way to disable the ns0: prefix that is used by the generated web service proxy stub? I have traced through the generated proxy code but I do not see any properties that can be modified. The only thing I can think of is to modify the generated code but I do not want to go that route.
Thanks,
Rich

Delete the NS0: related text, in JDev, from your WSDL and it should work. I had the same problem with .NET not liking it also.
Keep in mind you'll have to tweak the WSDL again if you regenerate it.
You sure you're using 10.1.3? I upgraded and it shows the NS0: as a problem in existing projects. I'm working on the latest, production download so maybe it's been corrected.

Disable namespace prefixes in Transformer

hi
I am stuck in a cyclic problem. JAXP XSLT and SchemaValidator do not work together. (Java 1.5 and 1.6)
I have a XSD with a namespace.
When I generate the XML using an XSLT I specify namespace using the namespace attribute of xsl:element
The JAXP transformer always generate the namespace prefix and equate the prefix with the actual URI
Is there a way to disable this behavior, that is, I do want the xmlns URI in the root element but not the prefix?
There are two reasons for wanting an XML without prefixes:
1) The Schema Validator provided with JRE is not able to validate the message with prefix, but it works fine with xmlns URI
<rootelem xmlns="urn:xmlns:xyz.abc.com"> validates fine
but
<ns0:rootelem xmlns:ns0="urn:xmlns:xyz.abc.com"> fails validation with error:
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'ns0:rootelem'.
I am able to generate the first case when I use Saxon based OrangeXSLT plugin for Eclipse but JAXP based transformer always generate the second case.
2) More importantly, I have XML consumers that could use parsing without namespace support and prefixed element will not work there.
I am using StreamResult in the Transformer.transform() call and my guess is that the internal implementation of Transformer might be using a SAX ContentHandler (XML Serializer) to write XML to the outputStream and I guess one way to get around could be that I write a custom ContentHandler and use a SAXResult in the transform call. I am not sure if I am thinking in the right direction.
If I am correct in my guess, could someone please point to some implementation of XMLSerializer that could be overridden just to disable namespace prefixing behavior?
I have removed the namespace from the XSD for things to work. I would appreciate any help with this.

Moving to latest Xalan and Xerces solved the problem.
But a new one surfaced.
Xalan's latest transformer does not handle StreamSource correctly and throws some exception internally (IOException related to end of stream), with the message:
SystemId Unknown; Line #-1; Column #-1; Premature end of file.
It work correctly if a DOMSource is provided as the input. This does not make sense, since the InputStream my code is using for StreamSource is ByteArrayInputStream for an in-memory XML and such error would happen if this stream is read more than once without calling a reset in between.
Please let me know if this seems like a valid bug or if I am doing something wrong.

Better rss feeds without jf namespace prefix

Hi Discussions,
It would be nice if the RSS feeds provided did not use these 'jf' namespace prefixed tags, but rather plain old RSS tags that most RSS readers, inclusive of Safari & Mail currently understand. The feeds contain tags like:
<jf:creationDate>Mon, 31 Mar 2008 14:02:16 -0500</jf:creationDate>
<jf:modificationDate>Mon, 31 Mar 2008 14:02:16 -0500</jf:modificationDate>
<jf:author>J.K. ROFLing</jf:author>
<jf:replyCount>0</jf:replyCount>
it would be better if they were something like:
<pubDate>Mon, 31 Mar 2008 14:02:16 -0500</pubDate>
<author>J.K. ROFLing</author>
or
<dc:creator>J.K. ROFLing</dc:creator>
or if they included such standard tags in addition to the jf: tags. As it is now, an rss reader doesn't know what these tags are and gives each entry the pubDate of the entire feed, and includes no author or subject info.
The feeds could also include the discussion group name as a "category" tag for each entry. that would perhaps be even better when a couple of feeds are grouped together.
As it is today the RSS feeds aren't nearly as compatible with Safari and Mail or other RSS readers as one might reasonably hope/expect. With all the work already sunk into providing the feeds at all, it would be nice to go the last couple of inches and make them (more) useable.
Cheers,
Chris

Hi Nick,
I added the namespace to the file (as per the below) but it gives compilation errors (C:\JDeveloper\mywork\FeedReader\RSSViewController\public_html\rssFeedReader.jsff - Error(4,11): This attribute is not recognized)
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
xlmns: h="http://java.sun.com/jsf/html">
<af:panelGroupLayout layout="vertical" id="qjgpgl1">
<af:outputText value="#{bindings.titleHead.inputValue}"
inlineStyle="color:Black; font-weight:bold;" id="qjgot1"/>
<af:outputText value="#{bindings.titleDesc.inputValue}"
inlineStyle="color:Gray;" id="qjgot2"/>
<af:spacer width="10" height="10" id="qjgs1"/>
<af:forEach var="row" items="#{bindings.Feed.rangeSet}">
<h:panelGrid columns="1" id="qjgpg1">
<af:goLink text="#{row.title}"
destination="#{row.link}"
inlineStyle="width:100%; font-weight:bold; color:ActiveCaption;"
id="qjggl1"/>
<af:outputText value="#{row.description}"
inlineStyle="color:Black;" id="qjgot3"/>
<af:spacer width="10" height="5" id="qjgs2"/>
</h:panelGrid>
</af:forEach>
</af:panelGroupLayout>
</jsp:root>

How to remove namespace prefix

hi,
i have a problem in receiver SOAP adapter because of namespace prefix.
so i have to remove the namespace prefix from the paylaod. but namespace should be there...
what are the possibilities to remove the namespace prefix alone from the payload?
Thanks & Regards,
Krish

hi,
you have to simply add one module in your communication channel
that is XMLAnonymizerBean
you can refer below for help:
Remove namespace prefix or change XML encoding with the XMLAnonymizerBean
http://help.sap.com/saphelp_nw04/helpdata/en/2e/bf37423cf7ab04e10000000a1550b0/frameset.htm
hope it helps.
regards,
ujjwal kumar

Compilation Error for import classes not found in generated Proxy Class

Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]

Hi,
I resolved the other errors by changing all references from com.bea.jcom.Variant
etc to com.linar.jintegra.class name..all were present under the com.linar.jintegra
package.
Thank you all anyways,
Regards,
rahul
"Rahul Srivastava" <[email protected]> wrote:
>
Hi,
We are generating java classes for the COM dll using JCOM com2java compiler.
We are getting a compilation error for import class not found when compiling
the
generated Proxy java source code. It can't find the com.bea.jcom.Dispatch
class that
the generated Proxy java source code extends. It also can't find com.bea.jcom.Variant
or com.bea.jcom.Param. These are interfaces or data types or classes used
by COM
library.
I added weblogic.jar to my class path and the only Dispatch class i found
inside
the weblogic.jar is com.linar.jintegra.Dispatch;
We have com objects for which we want to develop an EJB client to interface
with
the COM object using JCOM with Native Mode disabled.
Any help on the compilation error..I tried changing the extends for Dispatch
to com.linar.jintegra.Dispatch
but the other errors are still there.
To begin with, I think the generated code should not refer to any of the
COM data
types.
Any help please.
Thank you in advance,
Regards,
Rahul Srivastava
[email protected]

PI Generates Proxy - CX_INVALID_TRANSFORMATION

HI PI Experts...
This error relates to PI7.1
We have generated a new proxy to invoke a Service Interface on PI7.1. So we have an ECC6 system calling PI7.1 via proxy.
Our scenario is working...but we sporadically get a short dump with an execption: CX_INVALID_TRANSFORMATION
Pls note that the Simple Transformation XSLT is being executed in the 'background' within the generated proxy code and has been generated via the sproxy transaction. It was not custom developed.
And as I have previously stated, it does work and this error seems to occur on a random basis. For for example, i would inokve the proxy and everyhting works and then 10mins later, executing the proxy with the same data results in a short dump.
I have checked out the following OSS notes:
701467
773330
But these seem 'out-dated' and I dont believe they are applicable to PI7.1.
Has anyone experienced this issue before?
Any help would be greatly appreciated.
In the meantime, I will be looging an OSS issue as well...and will keep you guys informed.
Cheers
Yackeen

Hi All,
I believe this is an OSS issue to be resolved. What I have found thus far is as follows:
The exact error is:
<SAP:Stack>
      Error during proxy processing An exception with the type CX_AI_SYSTEM_FAULT occurred, but
       was neither handled locally, nor declared in a RAISING clause PARSE_APPLICATION_DATA
       Error during XML => ABAP conversion (Response Message; error ID:
           CX_INVALID_TRANSFORMATION;
            ( Error Text: The transformation /1SAI/TXSA452BFBF0DF199E50745 could not be executed))
             Error during XML => ABAP conversion (Response Message; error ID:
              CX_INVALID_TRANSFORMATION;
            ( Error Text: The transformation /1SAI/TXSA452BFBF0DF199E50745 could not be executed))
             The transformation /1SAI/TXSA452BFBF0DF199E50745 could not be executed
</SAP:Stack>
I then checked out & reactivated the specific generated XSLT program (_/1SAI/TXSA452BFBF0DF199E50745_) transaction xslt_tool. This still had no affect.
I then deleted the generated xsl program. Reran my interface and it worked!!!
But then we I ran the interface again, it then failed again. So I am in the process of raising an OSS issue.
Cheers
Yackeen

Geetting unbound namespace prefix error when merging

Client gave me 3 lists to merge. Two worked. The third is giving me unbound namespace prefix error. The first time I tried to open this particular file I got a warning that it wasn't mac compatible and will open as read-only. I got it open, copied and pasted into a new doc. But whenever I try to merge I get the namespace error. I did a google search and it said there can't be any colons or parenthesis in the data field. Far as I could determine doing a search there aren't any. Any help appreciated. Thx.

First thing I do--because I inherently do not trust clients--is to open merge lists in Excel or LibreOffice, then export them out as tab-delimeted files. As long as Excel opens them and the data is where it ought to be, this usually fixes encoding errors that can come in depending upon what last had them open and were saved from.
Mike

Namespace prefix for Security elements being removed from SOAP Header

Hello, I'm seeing a strange problem when accessing a web service using two different Netbeans projects.
If I use a Netbeans Java Application, add the Web Client Reference , add the web client code, all works fine and the wsse:Security element looks like this:
<S:Header>
<ns4:Security xmlns:ns2="IAMP" xmlns:ns3="urn:realops.com:amp:workflow" xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<ns4:UsernameToken>
<ns4:Username>admin</ns4:Username>
<ns4:Password>admin123</ns4:Password>
</ns4:UsernameToken>
</ns4:Security>
However if I do a similar sort of thing but access the web service via a Web Application, the namespace prefix is removed from all child elements wsse:Security like so:
<S:Header>
<ns4:Security xmlns:ns2="IAMP" xmlns:ns3="urn:realops.com:amp:workflow" xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<UsernameToken>
<Username>admin</Username>
<Password>admin123</Password>
</UsernameToken>
</ns4:Security>
Which causes an authentication exception.
The question is, why, when the wsdl are exactly the same for both projects , is the namespace prefix removed from the web app?
Thanks in advance,
jsz.

Hello, I'm seeing a strange problem when accessing a web service using two different Netbeans projects.
If I use a Netbeans Java Application, add the Web Client Reference , add the web client code, all works fine and the wsse:Security element looks like this:
<S:Header>
<ns4:Security xmlns:ns2="IAMP" xmlns:ns3="urn:realops.com:amp:workflow" xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<ns4:UsernameToken>
<ns4:Username>admin</ns4:Username>
<ns4:Password>admin123</ns4:Password>
</ns4:UsernameToken>
</ns4:Security>
However if I do a similar sort of thing but access the web service via a Web Application, the namespace prefix is removed from all child elements wsse:Security like so:
<S:Header>
<ns4:Security xmlns:ns2="IAMP" xmlns:ns3="urn:realops.com:amp:workflow" xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<UsernameToken>
<Username>admin</Username>
<Password>admin123</Password>
</UsernameToken>
</ns4:Security>
Which causes an authentication exception.
The question is, why, when the wsdl are exactly the same for both projects , is the namespace prefix removed from the web app?
Thanks in advance,
jsz.

Transform generated proxy tables into 'z' tables

Hello to everyone,
My doubt is really persistent and it's an important one...
Imagine we have an wsdl and we create a enterprise service proxy client. The R3 will generate 'Z' tables for the structure which the webservice needs for the request and the response.
How can I transform those generated proxy tables into normal 'Z' tables from the R3 Dictionary database?
Is it possible? Or do I have to create similar tables to the proxy tables?
The problem is that the response structure is really huge, and the work needed to create all the tables necessary to acomodate and all the mapping between the generated proxy tables and the ones that I'll have to create is HUGE!!!... Can I transform in any way those proxy tables?
Any help will be appreciated....

Hello Gonçalo
The generated proxy tables are indeed structures (and table types). In your case you have plenty of these structures that have to be "converted" into normal Z-tables.
One approach would be to use an
eCATT for this task. The steps could be as following:(1) Create a new z-table
(2) Include the corresponding proxy structure
(2.a) Transfer fields from include and remove .INCLUDE reference
(3) Remove obsolete fields
(4) Add additional fields
(5) Generate the z-table
Regards
Uwe

Missing namespace prefix in the soap body

Hello
The soap body that is produced along with soap header for my webservice. I
am the client talking to a server. The first piece in RED color is what
weblogic generates to send to the client but does NOT work. The one below
though works fine which is what I manipulated by hand to send to the
server. I have no idea why weblogic drops the namespace prefix in the
BODY.
-Narahari
The message is as shown below
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</Fulfill>
</env:Body>
</env:Envelope>
When you see the data carefully, the env:Body has the Fulfill element. But
it does have a namespace prefix on it. This causes the call to fail. If I
change the above segment manally to look like
POST /FS HTTP/1.1
Host: asgappsrv10:6211
Content-Type: text/xml; charset=utf-8
Connection: close
SOAPAction: "ListDomains"
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
<n1:Credentials xmlns:n1="urn:criticalpath:fs:api:1.0"
xsi:type="n1:Credentials">
<Username xsi:type="xsd:string">admin@default</Username>
<Password xsi:type="xsd:string">password</Password>
<SessionId xsi:nil="true"/>
</n1:Credentials>
</env:Header>
<env:Body
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<n2:Fulfill xmlns:n2="urn:criticalpath:fs:api:1.0"
xsi:type="n2:Fulfill">
<Request xsi:type="xsd:string">ListDomains</Request>
<RequestAttributes soapenc:arrayType="n2:Attribute[0]"/>
<Async xsi:type="xsd:boolean">false</Async>
</n2:Fulfill>
</env:Body>
</env:Envelope>

Hi All,
we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

Printing with Apex generates error (namespace prefix ref....)

Hello forum helpers,
i have installed bi publisher standalone and bi publisher desktop with MS Word 2003.
I have generated a rtf document as a template.
I loaded this rtf template into the apex database and started the TEST REPORT BUTTON in apex report queries.
But i have seen no report.
So, I have placed a xdodebug.cfg file into the folder java/jre/lib and so i have several logfiles created after processing printing.
This logfiles shows this lines, which i do not understand:
[030211_051252364][oracle.apps.xdo.template.FOProcessor][STATEMENT] Log file 'xdo_030211_051252364_fo_data_14.xsl' is created.
[030211_051252364][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setData(InputStream) is called.
[030211_051252364][oracle.apps.xdo.template.FOProcessor][STATEMENT] Log file 'xdo_030211_051252364_fo_data_15.xml' is created.
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] Log file 'xdo_030211_051252364_fo_out6.out' is created.
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setOutput(OutputStream)is called.
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setOutputFormat(byte)is called with ID=3.
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] Start Memory: max=247MB, total=62MB, free=23MB
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.generate() called.
[030211_051252379][oracle.apps.xdo.template.FOProcessor][STATEMENT] createFO(Object, Object) is called.
[030211_051252395][oracle.apps.xdo.common.xml.XSLT10gR1][STATEMENT] Oracle XML Developers Kit 10.1.0.5.0 - Production
[030211_051252395][oracle.apps.xdo.common.xml.XSLT10gR1][STATEMENT] Scalable Feature Disabled
[030211_051252410][oracle.apps.xdo.common.xml.XSLTWrapper][ERROR] XSL error:
XML-22008: (Error) Namespace prefix 'ref' used but not declared.
[030211_051252410][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) is called.
[030211_051252426][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) done. All inputs are cleared.
[030211_051252426][oracle.apps.xdo.template.FOProcessor][ERROR] End Memory: max=247MB, total=62MB, free=20MB
[030211_051252426][][EXCEPTION] java.lang.reflect.InvocationTargetException
You see, that an xml-22008 Error appears.
In google i only found, that the declaration of this reference must be before using it. Seems to be logical.
But the template is generated by BI Publisher himself, so now i do not understand.
I have no choice to declare references, the xml file is made by bi publisher.
Has anyone a solution for this ?
Thank you for help.
Frank

Issue was solved, found it in the bi publisher options in word 2003

How to add namespace prefix to root tag in XSL version 1.1 SOA 11g

Hi Experts,
   Can any one post solution for adding namespace prefix to root tag using XSL version 1.1 in SOA 11g?
I have tried the below options and none is working.
1. Removing prefix add in exclude-prefixes in XSL.But still seeing no prefix for root tag.
2. Added the <xsl-element>   tag with namespace.But it is not working
3. Added the below XSL code and it is not working.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
   xmlns:ns0="https://api.ladbrokes.com/v1/sportsbook-couchbase/Temp.xsd">
<xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
<xsl:template match="@* | node()">
   <xsl:copy>
   <xsl:apply-templates select="@* | node()"/>
   </xsl:copy>
</xsl:template>
<xsl:template match="/*">
   <xsl:element name="ns0:{local-name()}">
   <xsl:copy-of select="namespace::*" />
   <xsl:apply-templates select="@* | node()" />
   </xsl:element>
</xsl:template>
</xsl:stylesheet>

Try this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="@*|text()|comment()|processing-instruction()">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>
    <xsl:template match="/">
        <RootTag xmlns:ns0="https://api.ladbrokes.com/v1/sportsbook-couchbase/Temp.xsd">
            <xsl:apply-templates select="@*|node()"/>
        </RootTag >
    </xsl:template>
    <xsl:template match="*">
        <xsl:element name="{local-name()}">
            <xsl:apply-templates select="@*|node()"/>
        </xsl:element>
    </xsl:template>
</xsl:stylesheet>

Error in generating the Java Proxy

Hi all,
While generating a Java Proxy, I am getting an error :
Unable to generate proxies
Construct not supported
Can anybody please suggest the possible reason and solution for the same.
Thanks and best regards,
Kulwant

In the Integration Repository documentation for External Definitions you find a hint where you can find a document describing restrictions on the handling of XSD.
In that document you can see, that references to global elements are not supported by the java proxy generation.
Therefore, you have to edit your document accordingly.
regards
chandra

Namespace prefix tags in the generated proxy

Similar Messages

Maybe you are looking for