Wsdl code generating with xsd:choice weblogic 8.1

I am having a problem generating client code from a wsdl using weblogic 8.1.4 iin which the schema contains xsd:choice keyword.
I notice on a couple of forums that this may be a problem.
Is it a problem?
Is there a fix?
Cheers
Charlie

Is JAXB 1.0 used to generate the client code. xsd:choice is supported, but xsd:any is not supported by JAXB 1.0.

Similar Messages

Problem: bpel deployment with xsd choice

hi!
i have the problem that after deploying my bpel process i dont see the choice defined in my xsd. with a very simple example the choice just dont show in the bpel console. (bpel processes => initiate => xml source just shows the xml without the choice)
i use jdeveloper 10.1.3.1.0.3984.
does anyone know a solution for this problem?
thanks
my xsd:
<?xml version="1.0" encoding="ISO-8859-15" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns="http://www.example.org"
            targetNamespace="http://www.example.org"
            elementFormDefault="qualified">
<xsd:element name="exampleElement">
    <xsd:annotation>
      <xsd:documentation>
        A sample element
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="element1" type="xsd:string"/>
        <xsd:choice>
          <xsd:element name="element3" type="xsd:string"/>
          <xsd:element name="element4" type="xsd:string"/>
        </xsd:choice>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
</xsd:schema>the bpel process consists just of an assign-component.

Is JAXB 1.0 used to generate the client code. xsd:choice is supported, but xsd:any is not supported by JAXB 1.0.

The code generated by EJBC in Weblogic 5.1 is wrong!

I have a container managed bean that has a primary key named
productLicenseId as follows:
public class ProductLicenseBean implements EntityBean
public int productLicenseId;
I had this code running in Weblogic 4.5.1 and converted it to EJB 1.1
(now I use java.lang.Integer for the primary key class) and attempted to
build it using WebLogic 5.1. I built your container managed example
(AccountBean), which built fine (it is clear why your example did not
have the problem mine did- the primary key is java.lang.String). After
that, I tried to build my container managed bean, but without success.
Here is a description of my problem:
After trying to compile my simple container-managed program using EJBC
in Weblogic 5.1, I get the following error:
ProductLicenseBeanEOImpl.java:56: Incompatible type for =. Can't convert
int to java.lang.Integer
pk = bean.productLicenseId;
ProductLicenseBeanEOImpl.java is a class that was generated by EJBC. It
is clear that this code is incorrect! The generated code (pk =
bean.productLicenseId) attempts to assign the primary key in the
ProductLicenseBean (an int) to a java.lang.Integer (pk is of type
java.lang.Integer), which is wrong! The source code generated by EJBC is
wrong!
Do you have a bug fix for this, or is there something I'm just not
getting?? !!
I should be able to use a java.lang.Integer as a primary key.
Thanks much for your help.
Tim Kimmet, [email protected]
[timk.vcf]

I had the same problem. I had used the deployer tool and had specified a
primary key class AND a primary key field "ID".
This had put an extra tag in the ejb-jar.xml file <persistence field> which
I hadn't seen before.
Changing the primary key field to "none" fixed caused other problems to show
up in the deployer tool (finders). I had to redo the
deployer project from scratch, this time keeping the primary key field to
"none" and it worked.
Tim Kimmet <[email protected]> wrote in message
news:[email protected]..
I have a container managed bean that has a primary key named
productLicenseId as follows:
public class ProductLicenseBean implements EntityBean
public int productLicenseId;
I had this code running in Weblogic 4.5.1 and converted it to EJB 1.1
(now I use java.lang.Integer for the primary key class) and attempted to
build it using WebLogic 5.1. I built your container managed example
(AccountBean), which built fine (it is clear why your example did not
have the problem mine did- the primary key is java.lang.String). After
that, I tried to build my container managed bean, but without success.
Here is a description of my problem:
After trying to compile my simple container-managed program using EJBC
in Weblogic 5.1, I get the following error:
ProductLicenseBeanEOImpl.java:56: Incompatible type for =. Can't convert
int to java.lang.Integer
pk = bean.productLicenseId;
ProductLicenseBeanEOImpl.java is a class that was generated by EJBC. It
is clear that this code is incorrect! The generated code (pk =
bean.productLicenseId) attempts to assign the primary key in the
ProductLicenseBean (an int) to a java.lang.Integer (pk is of type
java.lang.Integer), which is wrong! The source code generated by EJBC is
wrong!
Do you have a bug fix for this, or is there something I'm just not
getting?? !!
I should be able to use a java.lang.Integer as a primary key.
Thanks much for your help.
Tim Kimmet, [email protected]

Import WSDL file along with XSD

Hi,
I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
Could you please help me out?

first i will tell how my wsdl file is defined
<xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
and in my xsd file for xx:AuthInfo
<xs:complexType name="AuthInfo">
          <xs:sequence>
               <xs:element name="acctName" type="tns:CustName">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                         account name.
                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="password" type="tns:AcctPswd">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                        Specify the password                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
but "AuthInfo" has two inputs.
this is how my Target Message Look like
Tree          Occurences          Type
authInfo     1..1                      xx:AuthInfo
i hope i have cleared u..

Code generated with adobe edge for my website does not work with fireox, but does with IE9 and chrome. Why?

The first time I opened Firefox with the code in my website it worked. Since then it has not worked. I have tried it on another computer and it worked perfectly. That computer runs under Widows XP.

Reload web page(s) and bypass the cache.
*Press and hold Shift and left-click the Reload button.
*Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
*Press "Cmd + Shift + R" (MAC)
Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
*Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
*Tools > Options > Privacy > Cookies: "Show Cookies"
Using "Forget About This Site" will remove everything from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious if you need to keep passwords or other data from that site.<br />
You can't recover from that "forget" unless you have a backup of the affected files.
It doesn't have any lasting effect, so if you revisit such a 'forgotten' website then data from that website will be saved once again.

JAXB generation and XSD choice serious issue

Helo,
Im developing a webservice that uses XSD Choice structure. Unfortunately, this must to done with choice because doesnt make sense using sequences this case.
Ill explain bug using this link:
http://bdoughan.blogspot.com/2011/04/xml-schema-to-java-xsd-choice.html#comment-form
this is exactly same problem as me, JAXB in jdeveloper are generating anotations wrong! I cant map the sequence choice to webservice, that is developed from WSDL...
So, I need some help there, I really need develop this webservice using xsd:choice and cant be done in jdeveloper and dont know why.
I tried put the anotations like this URL but when I call the service, choice element on request was null!
thanks

Hi, i dont know why but when I use JAXB to generate a sample XMl I got this output:
<guiaRequest xmlns="http://www.myservices.gov.br/mensagem/integracaobancaria/guia">
<parametrosConsultaGuia>
<guiaNormalRequest>
<codigoEntidade>B83C15C173633890E0330A67021B3890</codigoEntidade>
<codigoPorte>6</codigoPorte>
<codigoAssunto>148</codigoAssunto>
<numeroTransacaoInternet>267472003</numeroTransacaoInternet>
</guiaNormalRequest>
</parametrosConsultaGuia>
</guiaRequest>
This is correct to my webservice, BUT, when I invoque webservice with xsd:choice I got this request (i see that on enterprise manager) :
<message>
<properties>
<property name="tracking.compositeInstanceId" value="80367" />
<property name="tracking.ecid" value="0000J1pyNtnBDC^5lVg8yZ1DtZWJ002D4z" />
<property name="transport.http.remoteAddress" value="10.106.14.162" />
</properties>
<parts>
<part name="request" >
<ns2:guiaNormalRequest>
<ns2:codigoEntidade>B83C15C173633890E0330A67021B3890</ns2:codigoEntidade>
<ns2:codigoPorte>6</ns2:codigoPorte>
<ns2:codigoAssunto>148</ns2:codigoAssunto>
<ns2:numeroTransacaoInternet>267472003</ns2:numeroTransacaoInternet>
</ns2:guiaNormalRequest>
</part>
</parts>
</message>
This is wrong! see the structure is not correct.

Webservice control generation failled with xsd:all in WSDL, why ?

Hi,
When I try to generate a WS-control out of a WSDL with a
<xsd:all> based type e.g. :
<xsd:complexType name="RemoteComment">
                    <xsd:all>
                         <xsd:element name="id" type="xsd:long"/>
                         <xsd:element name="pageId" type="xsd:long"/>
                         <xsd:element name="created" type="xsd:dateTime"/>
                         <xsd:element name="title" nillable="true" type="xsd:string"/>
                         <xsd:element name="url" nillable="true" type="xsd:string"/>
                         <xsd:element name="creator" nillable="true" type="xsd:string"/>
                         <xsd:element name="content" nillable="true" type="xsd:string"/>
                    </xsd:all>
               </xsd:complexType>
(for example Atlassion Conluence's SOAP interface uses this)
I get a ERROR: sites/javapolis/xmlrpc/confluenceservicev1.wsdl Line 3, Col 0: Error in WSDL: Cannot extend a type with 'all' content model
Any ideas anyone ?

dieterd,
Try with xsd:sequence intead of xsd:all ?

PI does not combine .wsdl file with .xsd files.

Hi,
I imported .wsdl file with necessary .xsd files in PI system (7.1).
PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
Is there anyone to help me to solve problem with test it in PI system.
I send .wsdl file and necessary .xsd files as attachment his mail address.
Thanks.

Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
Do you want me to send .wsdl and .xsd files zipped into your mail box
instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
Regards,
Abhishek.

Problem with WSDL generated with wscompile JAX-RPC

Ok well I have successfully built a Web Service (From an existing wsdl) and Static Stub Client they work perfectly. I then I tried to connect to it using a Delphi Web Service Client. The client cant change, the problem I am getting is it is requesting using the variable name I am using and the WSDL has String_1.
Ie. it gives me:
unexpected element name: expected=String_1, actual= {targetNameSpace} [Variable Name]
I suspect this is a problem with how the WSDL is generated any suggestions?

THanks for the response, I originally used axis WSDL2Java. And only used the interface class. I think this is where my whole thing fell down. Although this worked with a static stub client that I used.
I have now generated the server side java files using wscompile and am l looking how to implement the server. It doesn't look like it has a implementation class there. And there isn't much information on how to do it.

What is wrong with the idl code generated by packager.exe?

Hello everybody,
I am trying to figure out what is wrong with the idl code generated by packager.exe. In the evaluation for the bug posted at http://developer.java.sun.com/developer/bugParade/bugs/4964563.html it says that the IDispatch interface is not exposed correctly and thus early binding of java objects is not possible using the current activex bridge implementation.
As I am no idl expert I have no idea what that means. However, I managed to dig out the idl code generated by packager.exe for the following example bean:
package test;
public class MyBean
     protected int value;
     public MyBean()
     public void setMyValue(int _value)
          value = _value;
     public int getMyValue()
          return value;
     public MyBean getSelfReference()
          return this;
}The corresponding idl code generated by packager.exe is
uuid(81B0BF63-2A55-11D8-A73E-000475EBF021),
version(1.0)
library MyBean
importlib("Stdole2.tlb");
dispinterface MyBeanSource;
dispinterface MyBeanDispatch;
uuid(81B0BF64-2A55-11D8-A73E-000475EBF021),
version(1.0)
dispinterface MyBeanSource {
properties:
methods:
uuid(81B0BF65-2A55-11D8-A73E-000475EBF021),
version(1.0)
dispinterface MyBeanDispatch {
properties:
[id(4097)]
int myValue;
methods:
[id(32768)]
VARIANT_BOOL equals(IDispatch* arg0);
[id(32769)]
IDispatch* getClass();
[id(32770)]
int getMyValue();
[id(32771)]
IDispatch* getSelfReference();
[id(32772)]
int hashCode();
[id(32773)]
void notify();
[id(32774)]
void notifyAll();
[id(32775)]
void setMyValue(int arg0);
[id(32776)]
BSTR toString();
[id(32779)]
VARIANT wait([optional] VARIANT var0, [optional] VARIANT var1);
uuid(81B0BF62-2A55-11D8-A73E-000475EBF021),
version(1.0)
coclass MyBean {
[default, source] dispinterface MyBeanSource;
[default] dispinterface MyBeanDispatch;
};Does anyone know what is wrong with this code and maybe how to fix the idl code? Generating the dll should then be easy (I already tried several variations of the idl code but as my idl knowledge is limited it didn't really do what I wanted).

Then the question is why it does work with visual controls (even if you set them to non-visible)?

Import WSDL with xsd:long incorrectly results in INT4

When importing a WSDL, all fields marked as xsd:long result in INT4 in the proxy class. But long is [supposed to be|http://www.w3schools.com/schema/schema_dtypes_numeric.asp] 8-byte (64 bit). We thus get the following error:
SOAP:1.001 CX_SY_CONVERSION_OVERFLOW:XSLT exception.
An error occurred when deserializing in the simple transformation program
/1SAI/TXS291D096A2B8E35E8375E.
Overflow converting from '2147483648'
<xsd:element minOccurs="0" name="Available" type="xsd:long"/>

Hello Marc
The only way is to manually edit the WSDL file and replace xsd:long
with xsd:string with pattern="\d+" and length="<n>"or
xsd:decimal with fractionDigits="0" totalDigigs="<n>"
Afterwarts regenerate proxy and you'll see that the
technical ABAP-Type is changed to STRG/DEC.
addtional info:
We recomment to use
xsd:decimal with totalDigits="19"
fractionDigits="0"
This is the shortest DEC that is big enought to accept the largest
xsd:long.
Future sight:
In release SAP_BASIS 702 this workaround is already fixed,
here you can change the technical type for xsd:long in proxy
editor directly to STRG or DEC(0,19) without modify the WSDL.
Thanks
Kenny

Problem with .c code generated from proc compiler.

I am having a problem compiling the c code generated from the proc pre-compiler.
First some info on my system.
[root@dell-xps-420-22 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Client release 5.4 (Tikanga)
[root@dell-xps-420-22 ~]# cat /proc/version
Linux version 2.6.18-164.11.1.el5 ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Wed Jan 6 13:26:04 EST 2010
[root@dell-xps-420-22 ~]# uname -a
Linux dell-xps-420-22.drew.com 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
I have written a simple PRO*C program to test the compile.
[oracle@dell-xps-420-22 etl]$ cat Test.pc
#include <stdio.h>
main(int argc,char **argv)
printf("Testing ........\n");
[oracle@dell-xps-420-22 admin]$ cat pcscfg.cfg
sys_include=(/usr/include,/usr/include/linux,/build/s630/precomp/public,/usr/lib/gcc/x86_64-redhat-linux/4.1.1/include)
include=$(ORACLE_HOME)/precomp/public
include=$(ORACLE_HOME)/precomp/hdrs
include=$(ORACLE_HOME)/precomp/include
CODE=cpp
TYPE_CODE=ORACLE
DEF_SQLCODE=YES
VARCHAR=YES
LTYPE=short
define=__x86_64__
When compiling the Test.pc program with the pcscfg.cfg file above.
[oracle@dell-xps-420-22 etl]$ proc Test.pc
Pro*C/C++: Release 10.2.0.1.0 - Production on Sun Feb 21 19:51:15 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
System default option values taken from: /u01/app/oracle/product/10.2.0/db_1/precomp/admin/pcscfg.cfg
[oracle@dell-xps-420-22 etl]$ gcc -c ./Test.c -I . -I$ORACLE_HOME/precomp/public
./Test.c:117: error: expected identifier or '(' before string constant
./Test.c:131: error: expected identifier or '(' before string constant
The code generated by the proc compiler that has problems is below.
//File Test.c
// Prototypes
Line 117: extern "C" {
void sqlcxt (void **, unsigned int *,
struct sqlexd *, const struct sqlcxp *);
void sqlcx2t(void **, unsigned int *,
struct sqlexd *, const struct sqlcxp *);
void sqlbuft(void **, char *);
void sqlgs2t(void **, char *);
void sqlorat(void **, unsigned int *, void *);
// Forms Interface
Line 131: extern "C" { void sqliem(char *, int *); }
It seems like the compiler is generating c++ code but the gcc compiler is only compiling in cc mode. I've tried a number of options in the pcscfg.cfg file to no avail. I have tried the different options for the CODE=cpp in the pcscfg.cfg file but still get the same error and/or multiple errors. I have also tried to compile the oracle demo programs using the demo_proc.mk file and also get the same error.
The install of Oracle is fine. I can start the database and have created a needed user and tables but cannot successfully compile the pro*C code.

My proc is also compiling for cpp code but in the pcscfg.cfg file there is no "CODE=cpp"

NWDS Webdynpro Code Generator overwrites custom source with old fragements

Hello,
I am developing Web Dynpro Components in Java with NWDS 7.1. and I am experiencing a strange behavoiur of the code generator. After I save the changes I made to a View in the "View Editor" the View is rebuild and the corresponding Java Source Code gets overwritten with an older version of it.
The same thing happens after editing the model or context bindings of the view controller, except that in this case all Java Sources are rebuild and overwritten. Its not that all method implementations are deleted, itu2019s the matter that they are replaced by older versions.
As a developer I think thatu2019s very dangerous, because sometimes I don't recognize which code areas are rewritten by designtime - I get Null Pointer Exu2019s by runtime.
Does anyone of you have an advice for me how to avoid these problems? Does anyone of you experienced the same behaviour before?
Thanks in advance!
Kind regards
Andreas Horn

Your question is not NWDI related. Post it in the [Web Dynpro for Java|Web Dynpro Java; forum or the [Java EE 5 @ SAP forum|Java Development;.

Problem Import WSDL with XSD import Schema

Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
   <wsdl:types>
      <xsd:schema targetNamespace="http://tempuri.org/Imports">
         <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
         <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
         <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
      </xsd:schema>
   </wsdl:types>
   <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
      <wsdl:part name="parameters" element="tns:AddItemHO" />
   </wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.

Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards

Cannot generate WSDL files With B1WS Wsdl Services Generator

Hello
I am trying to use the WSDL service generate for SAP web services and its causing me a bit of grief.
Whenever I run it crashes and dies I assume it is because I putting the wrong information in the fields. I have performed all the actions in the help file but I don't seem to be able to find anything anywhere that gives me the exact details of what should go in the text boxes in the generator :
Server -- I assume itu2019s the windows computer name (i.e. TEST)
DbSever type -- No worries itu2019s a drop down even I can figure that out
License Sever -- I assume itu2019s the License server as shown settings :3000 (i.e. TEST:30000)
User Name -- I assume itu2019s the SQL username
Password -- I assume itu2019s the SQL password
Hopefully I have something really simple really wrong.
Thanks in advance for any help.
Darren

This forum is for Crystal Reports. Post your question to the B1 forum.

Wsdl code generating with xsd:choice weblogic 8.1

Similar Messages

Maybe you are looking for