WSDL generates incorrect BAPIRET2 code in VS2005

I have tried to import WSDL for two Web Services based on function modules into a Visual Studio C# project.
In both cases, the WSDL generates the web service; however when I build the project, both services have syntax errors in the Reference.cs file for all components of the Bapiret2 class.
Each component generates the following two error messages:
"An object reference is required for the nonstatic field, method or property '<namespace>.System.get"
and
"'string' does not contain a definition for 'Xml'"
In each case, the error messages refer to the line that reads:
"[System.Xml.Serialization.XmlElementAttribute (Form=System.Xml.Schema.XmlSchemaForm.Unqualified)]"
that precedes the "Set" & "Get" methods for each Bapiret2 class component. The errors highlight the "System" and "X,l" components following "Form=" .
Has anyone seen this before?
I'm using SAP 2004s with Support Stack 15, and Visual Studio 2005 SP1 with the Enterprise Services Explorer add-on.
Thanks,
D.

I am working with VB project and encounter this problem.
Now, I found the solution.
It's may be help you. Good lucks.
calling a sap webas 6.20 web service from .net

Similar Messages

Weblogic 6.0 (SP2) generates incorrect java code for JSP with response.sendRedirect()

 Hi,
 Here are the steps to reproduce the problem with the examplesWebApp application
 bundled with wlserver6.0(sp2):
 Product: Weblogic server 6.0 (sp2)
 Browser: IE 5.0
 1. Add index.jsp as the welcome file in WEB-INF/web.xml
 2. Create index.jsp as below:
 <%
 response.sendRedirect("index.html");
 return;
 %>
 <html>
 <head>
 <title>Index JSP file</title>
 </head>
 <body>
 This is index.jsp file 
 </body>
 </html>
 3. Create index.html as below:
 <html>
 <head>
 <title>Index HTML file</title>
 </head>
 <body>
 This is index.html file 
 </body>
 </html>
 4. Run the examples server and make sure examplesWebApp is deployed on the examples
 server using the console
 5. Access the URL http://localhost:7001/examplesWebApp
 The page will display a compilation error as below:
 C:\bea\wlserver6.0\config\examples\applications\examplesWebApp\WEB-INF\_tmp_war_examplesServer_examplesServer_examplesWebApp\jsp_servlet\_index.java:89:
 unreachable statement
 out.print("\r\n<html>\r\n<head>\r\n<title>Simple html</title>\r\n</head>\r\n<body>\r\nThis is index.jsp page\r\n</body>\r\n</html>\r\n");
 ^
 and a look at the generated java code for index.jsp (_index.java) will reveal
 the erroneous code snippet below in the jsp service method:
 try { // error page try block
 //[ /index.jsp; Line: 1]
 response.sendRedirect("index.html"); //[ /index.jsp; Line: 2]
 return; //[ /index.jsp; Line: 3]
 out.print("\r\n<html>\r\n<head>\r\n<title>Simple html</title>\r\n</head>\r\n<body>\r\nThis is index.jsp page\r\n</body>\r\n</html>\r\n");
 } catch (Exception __ee) {
 while (out != null && out != _originalOut) out = pageContext.popBody();
 pageContext.handlePageException(__ee);
 The above web application works fine in Tomcat 3.2.X environment. The Weblogic
 server 6.0 servlet engine should not generate the "out.println()" corresponding
 to the html section of index.jsp. The moment it sees the "return", it should stop
 processing further.
 Can someone from Weblogic support team please verify this and let me know when
 this bug will be fixed?
 One interesting thing I noticed was when we last tried weblogic 6.0 at its beta
 stage, it worked fine after we put in a special patch jar file called "redirectfix.jar"
 we received from weblogic team but somehow it got re-introduced by the time it
 was released!!
 We are planning to migrate our product from tomcat 3.2.x to weblogic 6.0. Our
 product has a lot of pages with such conditional {response.sendRdirect("page.jsp");return;}
 blocks. We would really appreciate a faster response form weblogic team.
 Thanks in advance.
 sam...
 Sam Palanisamy
 Senior Software Engineer
 Manage.com
 2345 N. First Street First Floor
 San Jose CA 95131


Why should it stop when it sees a return? Is that in the spec?
 Peace,
 Cameron Purdy
 Tangosol Inc.
 << Tangosol Server: How Weblogic applications are customized >>
 << Download now from http://www.tangosol.com/download.jsp >>
 "Sam Palanisamy" <[email protected]> wrote in message
 news:[email protected]...
 >
 > Hi,
 >
 > Here are the steps to reproduce the problem with the examplesWebApp
 application
 > bundled with wlserver6.0(sp2):
 >
 > Product: Weblogic server 6.0 (sp2)
 > Browser: IE 5.0
 >
 > 1. Add index.jsp as the welcome file in WEB-INF/web.xml
 >
 > 2. Create index.jsp as below:
 > <%
 > response.sendRedirect("index.html");
 > return;
 > %>
 > <html>
 > <head>
 > <title>Index JSP file</title>
 > </head>
 > <body>
 > This is index.jsp file 
 > </body>
 > </html>
 >
 > 3. Create index.html as below:
 > <html>
 > <head>
 > <title>Index HTML file</title>
 > </head>
 > <body>
 > This is index.html file 
 > </body>
 > </html>
 >
 > 4. Run the examples server and make sure examplesWebApp is deployed on the
 examples
 > server using the console
 >
 > 5. Access the URL http://localhost:7001/examplesWebApp
 >
 > The page will display a compilation error as below:
 >
 C:\bea\wlserver6.0\config\examples\applications\examplesWebApp\WEB-INF\_tmp_
 war_examplesServer_examplesServer_examplesWebApp\jsp_servlet\_index.java:89:
 > unreachable statement
 > out.print("\r\n<html>\r\n<head>\r\n<title>Simple
 html</title>\r\n</head>\r\n<body>\r\n color=\"red\">This is index.jsp page\r\n</body>\r\n</html>\r\n");
 > ^
 >
 > and a look at the generated java code for index.jsp (_index.java) will
 reveal
 > the erroneous code snippet below in the jsp service method:
 >
 > try { // error page try block
 >
 > //[ /index.jsp; Line: 1]
 > response.sendRedirect("index.html"); //[ /index.jsp; Line: 2]
 > return; //[ /index.jsp; Line: 3]
 > out.print("\r\n<html>\r\n<head>\r\n<title>Simple
 html</title>\r\n</head>\r\n<body>\r\n color=\"red\">This is index.jsp page\r\n</body>\r\n</html>\r\n");
 > } catch (Exception __ee) {
 > while (out != null && out != _originalOut) out =
 pageContext.popBody();
 > pageContext.handlePageException(__ee);
 > }
 >
 > The above web application works fine in Tomcat 3.2.X environment. The
 Weblogic
 > server 6.0 servlet engine should not generate the "out.println()"
 corresponding
 > to the html section of index.jsp. The moment it sees the "return", it
 should stop
 > processing further.
 >
 > Can someone from Weblogic support team please verify this and let me know
 when
 > this bug will be fixed?
 >
 > One interesting thing I noticed was when we last tried weblogic 6.0 at its
 beta
 > stage, it worked fine after we put in a special patch jar file called
 "redirectfix.jar"
 > we received from weblogic team but somehow it got re-introduced by the
 time it
 > was released!!
 >
 > We are planning to migrate our product from tomcat 3.2.x to weblogic 6.0.
 Our
 > product has a lot of pages with such conditional
 {response.sendRdirect("page.jsp");return;}
 > blocks. We would really appreciate a faster response form weblogic team.
 >
 > Thanks in advance.
 > sam...
 > Sam Palanisamy
 > Senior Software Engineer
 > Manage.com
 > 2345 N. First Street First Floor
 > San Jose CA 95131
 >
 >

Error while generating java client code from wsdl file

I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
um_workflowSaveCreateProfile.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
 <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
 <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
 <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
 <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
 </port>
 </service>
</definitions>
um_workflowSaveCreateProfile_interface.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
 <types>
 <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
 xmlns="http://www.oblix.com/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
 <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
 <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
 </xsd:schema>
 <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="request">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="params">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref="oblix:ObWorkflowName"/>
 <xsd:element ref="oblix:ObDomainName"/>
 <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
 <xsd:element ref="oblix:noOfFields"/>
 <xsd:element ref="oblix:AttributeParams"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 <xsd:attribute name="version" type="xsd:string" use="optional"/>
 <xsd:attribute name="application" type="xsd:string" use="required" />
 <xsd:attribute name="function" type="xsd:string" use="required" />
 <xsd:attribute name="mode" type="xsd:string" use="optional"/>
 </xsd:complexType>
 </xsd:element>
 </xsd:schema>
 </types>
 <message name="OblixIDXMLInput">
 <part name="authentication" element="oblix:authentication"/>
 <part name="request" element="oblixxmllocalschema:request"/>
 </message>
 <message name="OblixIDXMLOutput">
 <part name="body" element="oblix:Oblix"/>
 </message>
 <portType name="OblixIDXMLPortType">
 <operation name="OblixIDXML_um_workflowSaveCreateProfile">
 <input message="tns:OblixIDXMLInput"/>
 <output message="tns:OblixIDXMLOutput"/>
 </operation>
 </portType>
 <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <operation name="OblixIDXML_um_workflowSaveCreateProfile">
 <soap:operation soapAction="http://www.oblix.com/"/>
 <input>
 <soap:body use="literal"/>
 </input>
 <output>
 <soap:body use="literal"/>
 </output>
 </operation>
 </binding>
</definitions>
I am using WSDL2 Java for generating the client code .
Please suggest where am I wrong .
E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
Using AXIS2_HOME: E:\axis2-1.4
Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
*[ERROR] More than one part for message OblixIDXMLInput*
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:153)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
Input
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:397)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
... 2 more
Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363).
Thanks in advance.
akshay

Hello,
Were you able to resolve this issue ?
I am seeing the same issue and at my wits end.
regards
Amit

How to generate the java code of a table's data model by parsing it's FXML?

I have know how to create FXML file that describes a table. Meanwhile, according to [Oracle Tutorial|http://docs.oracle.com/javafx/2/fxml_get_started/fxml_tutorial_intermediate.htm#CACFEHBI], it is a best practice to implement a class that defines the data model and provides methods and fields to further work with the table.
However, It's rather cumbersome and time consuming to typing the code. So, is there any tools that can generate the java code of a table's data model by parsing it's FXML describe file?
Regards, Qinn
Edited by: 854675 on Oct 7, 2012 11:02 PM

I have know how to create FXML file that describes a table. Meanwhile, according to [Oracle Tutorial|http://docs.oracle.com/javafx/2/fxml_get_started/fxml_tutorial_intermediate.htm#CACFEHBI], it is a best practice to implement a class that defines the data model and provides methods and fields to further work with the table.
However, It's rather cumbersome and time consuming to typing the code. So, is there any tools that can generate the java code of a table's data model by parsing it's FXML describe file?
Regards, Qinn
Edited by: 854675 on Oct 7, 2012 11:02 PM

How to set a field that automatically generates a unique 'code'/'ID' for fillable PDF form?

Hi,
I'm trying to create a PDF fillable form with Acrobat X Pro.
Can Acrobat allow a function, so that it can automatically generate a 'number'/'code' which I could use as an 'identifier'?
eg. A hidden field named: 'DOC ID' and provide 100001 when added to response file as it's submitted and '100002' to another file when it another is submitted/added onto the response file etc...
I am aware that Response files, if submitted correctly, could automatically generate numbers like 001, 002 etc...
But I'd like to see if I could create a field, that 'numbers' the document for me automatically and uniquely.
Any help and/or suggestions would be appreciated.
Winnie

Hi,
to do this you need kind of interactivity in your form.
You can achieve this either by:
1) using JavaScript onchange-events on forename and surname items, or
2) use the AJAX Computations option of ApexLib, see: http://www.oracle-and-apex.com/ajax-computations-rich-client-feeling/
brgds,
Peter
Blog: http://www.oracle-and-apex.com

WS-I compliance of wsdl generated by BPEL

Hi All,
I generated a very simple synchronous BPEL process with defaults, and assigned the input to the ouput. The wsdl generated is not WS-I compliant. It gives an error:-
Assertion: BP2703
Result
failed
Failure Detail Message
Schema validation failed
Failure Detail Message
Schema validation failed: The element 'http://schemas.xmlsoap.org/wsdl/:definitions' has invalid content. An error occurred at , (1, 1179).
The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:partnerLinkType' element is not declared. An error occurred at , (1, 1179).
The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:role' element is not declared. An error occurred at , (1, 1211).
The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:portType' element is not declared. An error occurred at , (1, 1240).
It seems to be giving an error for the partner link element!!!! I am testing this because in my project I am getting the same error. How can I make the wsdl WS-I compliant..

Expose the WSDL from Sender Agreement or Inbound Processing in the ICO and test accordingly with SOAPUI.
In case still you are getting the error in the sense you can prefer XMLAnonymizer bean or play with the namespaces you may have to go with the JAVA or XSLT mapping.
XI: XML node into a string with graphical mapping?

Urgent How to generate a random code such as registration code?

I would like to ask that how to generate a random code?
For example, when you register a E-mail account, you need to enter the code for activation. I would like to create a java Bean to do this job. Would you help me?

In fact, I would like to set a 10 digi codes randomly (such as FH654CS081, MKO624VG9f) for user input when they register the forum account. This random code will be sent to the user's email. User have to input this code to a JSP web site. Also, the code which is inputed by user will be matched with the database. If user input success, the forum account will be activated.
By generating this 10 digi codes, I want to handle this generation by using java bean.
1) Any thing else i need to import ? (such as <% page import="java.......?")
2) Any functions can handle this task?
3) Any example can be my reference?
Thank you very much

WSDL generated from service that references XMLBean is invalid

Env: Weblogic Workshop 9.2.0
Build id: 783464
When I validate a WSDL generated from a service that imports XMLBean classes (auto-generated by the XMLBeans Builder) it shows numerous errors including src-resolve.4.2. and ?The part ?parameters? has an invalid value ?hello? ??. All my schemas validate without error in both Workshop and XMLSpy. This happens for both the WSDL generated from the right click menu and from the auto generated WSDL located in the build sub-directory.
Related to this problem, when I deploy the web service (for some reason I can deploy it if I don?t deploy the WSDL) sometimes I either can reach the web service and sometimes I receive a failure related to the parse of the WSDL stating java.util.NoSuchElementException as the reason.
Has anyone else seen these kinds of problems?

I'm going to open a support case but here are the XSDs
There are four in total ... I have marked the top and bottom of each so you can clearly identify them.
---AddressData.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:addr="http://www.test.org/address" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/address" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:complexType name="AddressType">
 <xs:sequence>
 <xs:element name="LineOne" type="addr:LineOneType"/>
 <xs:element name="LineTwo" type="addr:StreetAddressType" minOccurs="0"/>
 <xs:element name="City" type="addr:CityType"/>
 <xs:element name="State" type="addr:StateType"/>
 <xs:element name="Zip" type="addr:ZipType"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="LineOneType">
 <xs:choice>
 <xs:element name="StreetAddress" type="addr:StreetAddressType"/>
 <xs:element name="POBoxAddress" type="addr:POBoxAddressType"/>
 </xs:choice>
 </xs:complexType>
 <xs:complexType name="StreetAddressType">
 <xs:sequence>
 <xs:element name="StreetAddress" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="POBoxAddressType">
 <xs:sequence>
 <xs:element name="POBoxAddress" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="CityType">
 <xs:sequence>
 <xs:element name="City" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="StateType">
 <xs:sequence>
 <xs:element name="State" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ZipType">
 <xs:sequence>
 <xs:element name="Zip" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
</xs:schema>
---AddressData.xsd Stop---
---CustomerData.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:cust="http://www.test.org/customerdata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:addr="http://www.test.org/address" xmlns:pri="http://www.test.org/priority" xmlns:ndata="http://www.test.org/ndata" targetNamespace="http://www.test.org/customerdata" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:import namespace="http://www.test.org/priority" schemaLocation="CustomerPriority.xsd"/>
 <xs:import namespace="http://www.test.org/address" schemaLocation="AddressData.xsd"/>
 <xs:import namespace="http://www.test.org/ndata"
 schemaLocation="DataType.xsd" />
 <xs:element name="CustomerData">
 <xs:annotation>
 <xs:documentation>
 Comment describing your root element
 </xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Customer" type="cust:CustomerType" />
 <xs:element name="otherData1" type="ndata:newDataType" />
 <xs:element name="secondaryAddress"
 type="addr:AddressType" />
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:complexType name="CustomerType">
 <xs:sequence>
 <xs:element name="name" type="cust:CustomerNameType"/>
 <xs:element name="address" type="addr:AddressType"/>
 <xs:element name="priority" type="pri:PriorityLevelType"/>
 <xs:element name="data" type="cust:moreData"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="CustomerNameType">
 <xs:sequence>
 <xs:element name="lastname" type="xs:string"/>
 <xs:element name="firstname" type="xs:string"/>
 <xs:element name="title" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:element name="anotherBitOfData" type="xs:gMonthDay"/>
 <xs:complexType name="moreData">
 <xs:sequence>
 <xs:element name="data1" type="xs:string"/>
 <xs:element name="data2" type="xs:long"/>
 </xs:sequence>
 </xs:complexType>
</xs:schema>
---CustomerData.xsd Stop---
---CustomerPriority.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:pri="http://www.test.org/priority" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/priority" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:element name="CustomerPriority">
 <xs:annotation>
 <xs:documentation>Comment describing your root element</xs:documentation>
 </xs:annotation>
 <xs:complexType>
 <xs:sequence>
 <xs:element name="priority" type="pri:PriorityLevelType"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:complexType name="PriorityLevelType">
 <xs:choice>
 <xs:element name="Level1Value" type="xs:string"/>
 <xs:element name="Level2Value" type="xs:string"/>
 <xs:element name="Level3Value" type="xs:string"/>
 </xs:choice>
 </xs:complexType>
</xs:schema>
---CustomerPriority.xsd Stop---
---DataType.xsd Start---
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ndata="http://www.test.org/ndata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pri="http://www.test.org/priority" targetNamespace="http://www.test.org/ndata" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:import namespace="http://www.test.org/priority"
 schemaLocation="CustomerPriority.xsd" />
 <xs:complexType name="newDataType">
 <xs:sequence>
 <xs:element name="pri" type="xs:string" />
 </xs:sequence>
 </xs:complexType>
</xs:schema>
---DataType.xsd Stop---

WSDL generated by web service map

Hi,
I am totally new to ODSI. I noticed that the WSDL generated by the Web Service Map for a Data Service always contains two schemas in the types section, with an import directive in the first schema which refers to the second. The structure of the types section is something like this:
<types>
<xs:schema>
<xs:import namespace="N1">
</xs:schema>
<xs:schema targetNameSpace="N1">...</xs:schema>
</types>
The question is : is it possible to have a single schema instead of two in a logical data service? In other words, to what extent can the WSDL be customized?
I apologize in advance if the question is dumb, but as I have said, I am totally new to this product.
Thank you very much for your help
Alberto

The request and response elements will always be generated in the form below. It cannot be customized.
<xs:schema targetNamespace="ld:hello_ws" elementFormDefault="qualified" xmlns:stns="ld:hello_ws" ... >
<s:element name="HelloWorld">
<s:element name="HelloWorldResponse">
</>
Unless the targetnamespace for your logical data service matches, there will always need to be a second schema element.
Your logical dataservice can have whatever schema you want.

Incorrect SIA code in DME file for Foreign payments in Italy

Hello All
I am trying to create a DME file payments in Italy.
The DME FIle is being created by program RFFOIT_FOR.
I am Getting an incorrect SIA code.
Can anyone tell me from wehere can I update this code
Thanks a LOt!!!

Hi
Thx for your prompt reply
I have already applied the note.
Now I want to populate the table
I need the list which contains countries and their UIC codes

How do I Add Authentication to the WSDL generated?

Hi Experts,
I am creating web service in CAF to get All task assigned to a user using BPM API.
The WSDL generated while testing from wsnavigator is picking up as a guest user even if I am entering the user details in invocation parameters.
Can some one tell me how do I add authentication to the WSDL I have generated in CAF?
Thanks in Advance
Kumar.

Hi Kumar,
You Can find the above Section in : Go to http://hostname:port/nwa and open Configuration--->Connectivity --> Single Service Administration and open Service Definitions tab and select the application service for which you want to create the Authentication.
Cheers
Piyas

Generating of QR code in offline mode

Hello everyone. I want help to generate QR code in the offline mode. I did
try to generate QR code using labview but when am online. i am able to generate
the qr code. I will attach my VI below for the online.
Can some1 help me please.
Solved!
Go to Solution.
Attachments:
name.vi ‏19 KB
1q.JPG ‏67 KB
1q2.JPG ‏31 KB

Zahkay wrote:
Hello again sir
Yeah i am new in labview and with the specific term you used make me like i have to check it out.
i will try my best to understand.
Thank you very much
In case you find easier and more direct Vi, i will grateful to hear from you
Regards
This is one of those times that you just say thank you and keep learning.
There is nothing "Basic" in that code. not the code and not the math. And the correct honorific in this case would be "Doctor" As in "more degrees than most thermometers" (Not that he doesn't play with large numbers of negative degrees that don't appear on most thermometers)
The strange thing is he probably coded that up "just for fun" Some days his examples just make me want to go play with a frisbee.
Jeff

Dynamically generate JSF Source code in a JSP

Hi,
I have a JSP and instead of writing the JSF source Code like:
<h:inputText
styleClass="entryInput"
id="textNumberOfServerMachinesInput"
value="#{DataAccess.value}"
valueChangeListener="#{InputValueChanged.processValueChange}">
</h:inputText>
manually in the jsp I want the JSF source code to be added dynamically to the jsp.
So what I want is including a tag in the jsp and this tag generates JSF source code like seen above.
This source code should then be treated just the way it would be if I had written it manually in the JSP. This means that the dynamically generated JSF code must be interpreted and all Listeners and Beans work just fine.
How can I make this???

Hi,
I have a smiliar problem:
JSP:
<h:panelGrid binding="#{fileUploadGrid.panelGrid}">
 <%-- emty in jsp --%>
</h:panelGrid>The panel should be populated with items the backing bean creates in source code:
FileUploadGrid.java
public void setUploadFieldNumber(int uploadFieldNumber) {
 this.uploadFieldNumber = uploadFieldNumber;
 this.refresh();
private void refresh() {
 if (this.panelGrid == null)
 this.createPanelGrid();
 List children = this.panelGrid.getChildren();
 children.clear();
 for (int i = 0; i < this.uploadFieldNumber; i++) {
 HtmlOutputText out = new HtmlOutputText();
 out.setTitle("Image " + i);
 out.setRendered(true);
 HtmlInputText in = new HtmlInputText();
 children.add(out);
 children.add(in);
private void createPanelGrid() {
 this.panelGrid = new HtmlPanelGrid();
 this.panelGrid.setColumns(2);
 this.panelGrid.setCellpadding("1");
 this.panelGrid.setBorder(1);
 this.panelGrid.setWidth("50%");
 this.panelGrid.setRendered(this.isRendered());
public void setPanelGrid(HtmlPanelGrid panelGrid) {
 this.panelGrid = panelGrid;
public HtmlPanelGrid getPanelGrid() {
 return this.panelGrid;
}The backing bean is initialized in faces-config.xml:
<managed-bean>
<managed-bean-name>fileUploadGrid</managed-bean-name>
<managed-bean-class>org.smi.pte.isf.FileUploadGrid</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
 <property-name>rendered</property-name>
 <value>true</value>
</managed-property>
<managed-property>
 <property-name>uploadFieldNumber</property-name>
 <value>6</value>
</managed-property>
</managed-bean>The problem is: although the debug output of the faces framework (I use it along with Tomcat) shows that the in- and output fields are added correctly to the panel, the page remains empty at display.
Thanks in advance for any help.
F. Eckhardt

SUN AS generates wrong WS code very often !

Hi
I am using NB 4.1 and SUN AS 8.1 to create some WEB services. I am using JSR 109 compatible WS stub generation. Application server generates them when a WS is being deployed.
There are several cases when it generates wrong java code that cannot be compiled.
I have created a very simple WS that returns an array of custom class objects (DTOs).
package lv.test;
import lv.test.dto.OneDTO;
public class BugTestWebServiceImpl implements BugTestWebServiceSEI
    public OneDTO[] test()
        return new OneDTO[] {};
}And here is my DTO class.
package lv.test.dto;
import java.io.Serializable;
public class OneDTO implements Serializable
    private String tx3dstatus;
    public OneDTO()
    public String getTx3dstatus()
        return tx3dstatus;
    public void setTx3dstatus(String tx3dstatus)
        this.tx3dstatus = tx3dstatus;
}Quite simple, isn't it ? Now you can get very stupid code out from SUN AS just by changing some simple WS settings.
Let's disable documentliteral and enable rpcliteral. After all it should be RPC style WebService, not Document-style. And behold , you will get some stupid java code that doesn't even compile !
[#|2005-06-01T18:33:29.390+0300|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=21;|DPL5035:Error while running ejbc
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- jaxrpc compilation exception
C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-modules\RPCBug\lv\test\BugTestWebServiceSEI_Tie.java:56: incompatible types
found : lv.test.dto.OneDTO[]
required: lv.test.OneDTO[]
((lv.test.BugTestWebServiceSEI) getTarget()).test();
^
Why it assumes that DTO should be in the same package where WS implementation is ?
Another interesting thing happens if you disable both documentliteral and rpcliteral:
[#|2005-06-01T18:59:44.578+0300|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=13;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- jaxrpc compilation exception
C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-modules\RPCBug\lv\test\dto\OneDTO_SOAPSerializer.java:51: cannot resolve symbol
symbol : method setTx3Dstatus (java.lang.String)
location: class lv.test.dto.OneDTO
instance.setTx3Dstatus((java.lang.String)member);
^
|#]
[#|2005-06-01T18:59:44.312+0300|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=13;|C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-modules\RPCBug\lv\test\dto\OneDTO_SOAPSerializer.java:69: cannot resolve symbol
symbol : method getTx3Dstatus ()
location: class lv.test.dto.OneDTO
ns3_myns3_string__java_lang_String_String_Serializer.serialize(instance.getTx3Dstatus(), ns1_tx3dstatus_QNAME, null, writer, context);
^
|#]
[#|2005-06-01T18:59:44.312+0300|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=13;|C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-modules\RPCBug\lv\test\dto\OneDTO_SOAPBuilder.java:39: cannot resolve symbol
symbol : method setTx3Dstatus (java.lang.String)
location: class lv.test.dto.OneDTO
_instance.setTx3Dstatus((java.lang.String)memberValue);
^
|#]
Now it has generated code that tries to use non-existing method !
Why it's so buggy ?
If you don't believe me you can get whole NB 4.1project from http://maris.site.lv/RPCBug.zip and try it yourself.

I think there are some known restrictions and bugs - check with JAXRPC folks : http://forums.java.net/jive/forum.jspa?forumID=46;

SQL LDR LKM generating incorrect CTL file

Hi,
The LKM for SQL LDR is generating incorrect CTL file for a fixed length data file. Due to this the ODI is erring out.
Here are the contents of the CTL file:
SnpsOutFile "-File=//Myserver/myfile.ctl"
OPTIONS (
     SKIP=0,
     ERRORS=0,
     DIRECT=TRUE
LOAD DATA
INFILE "//Myserver/myfile.RDY"
BADFILE "//Myserver/myfile.bad"
DISCARDFILE "//Myserver/myfile.dsc"
DISCARDMAX 1
INTO TABLE ORA_SCHEMA.C$_0RAW_TABLE
     C1_CHAR9     POSITION(:),
     C2_CHAR2     POSITION(:),
     C3_CHAR6     POSITION(:),
     C4_CODE          POSITION(:),
     C5_RAWG_CODE     POSITION(:),
     C6_E_NUMBER     POSITION(:),
     C7_T_NUMBER     POSITION(:),
     C8_C_COLOR     POSITION(:),
     C9_D_COLOR     POSITION(:),
     C10_R_CODE     POSITION(:)
Why is "POSITION(:)" not getting the numbers before and after ":" ?
I reverse engineered this file and have the correct values for "Physical Length" and "Logical Length"
TIA,
Ankit

Hi Ankit,
I think the column transformation mappings are set on the Source (radio button) in the Integration Interface Mapping window.
Change the column transformation mappings to be executed on STAGE .
It should resolve this issue.
Thanks,
Sutirtha

WSDL generates incorrect BAPIRET2 code in VS2005

Similar Messages

Maybe you are looking for