Unsupported wsdl to as generation

I read somewhere that simpleType containing a restriction is unsupported in Flex. I'm using Flex 4 beta and anywhere I do this I get no code generated for "someString". Is there a fix for this or a work around other than removing the restriction?
 <xsd:element name="someString">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>

Hi Jason,
It seems you've hot one of our known issues. From what I see
in the wsdl code pasted above you are using a document-literal
unwrapped. As per bug [
http://bugs.adobe.com/jira/browse/FB-11388
the code generator does not properly determine what type of
doc-literal wsdl you have, and sets the isWrapped and wrappedQName
on a operation's request and response messages incorrectly.
To fix this, simply go into the BaseEchoService.as class and
comment out these two lines:
requestMessage.isWrapped = true;
responseMessage.isWrapped = true;
Then everything should work all right.
Hope this helps,
Cristian

Similar Messages

WSDL error during generation of ABAP proxy for web service

Hi friends,
I am getting error during the generation of ABAP proxy object for web service developed in .NET .
Error : Proxy generation terminated: WSDL error (<extension> not supported).
How to make this WSDL file compatible for ABAP proxy.
I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
If any one worked on this. Please help me its urgent.
Thanks and regards,
Shivanand.

HI ,
I am having the same issue!!!
Does ABAP Proxy Generation support <extension> ?
Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
Thanks

WSDL/client-stub generation without EJBs ?

My WL7 application invokes methods on external subscriber
web-apps. I need to provide WSDLs for these external apps, since
they'll be implemented by our customers.
Currently, I create 'dummy' EJBs, then create .ears out of it,
run 'servicegen' to create a dummy webservice, then run
'clientgen' to create the WSDLs and the client stub classes
that I'll finally use. I'd like to avoid some of the above
steps. Ideally, I'd just create the appropriate Java interface
classes, then use some tool to create the WSDL and the
client-stub classes. Is this possible ?
-john

Hi John,
Have you considered using a WSDL generation GUI, such as
http://www.omniopera.com/omniopera.html
Bruce
BTW, you do realize that when a webservice is deployed on WLS v7, the
WSDL is available to anyone using
http://<host>:<port>/<context_url>/<webservice>?WSDL
john wrote:
Bruce, I'm not sure how I would use those other tasks to obtain
what I want. AFAIK, the only way to generate a WSDL for a service
is to use the 'clientgen' task. And the clientgen task requires
the actual webservice implementation in the form of a .ear
file.
In my case, I need to create WSDLs which I then pass on to
my customers, for them to implement and host. Currently, to do
this I have to myself implement the desired dummy webservice
and then use clientgen to obtain the WSDL (along with the
stubs etc ..)
thanx
-john
Bruce Stephens <[email protected]> wrote:
Hi John,
In addition to the servicegen and clientgen ant tasks there are now
several other narrowly focused ant tasks such as autotype, and
source2wsdd. Check out the documentation:
http://edocs.bea.com/wls/docs70/webserv/assemble.html#1011066
Hope this helps,
Bruce
john wrote:
My WL7 application invokes methods on external subscriber
web-apps. I need to provide WSDLs for these external apps, since
they'll be implemented by our customers.
Currently, I create 'dummy' EJBs, then create .ears out of it,
run 'servicegen' to create a dummy webservice, then run
'clientgen' to create the WSDLs and the client stub classes
that I'll finally use. I'd like to avoid some of the above
steps. Ideally, I'd just create the appropriate Java interface
classes, then use some tool to create the WSDL and the
client-stub classes. Is this possible ?
-john

Generating Ruby Web Service Access Classes from a WSDL

If you have tried to consume a web service from Ruby you surely have noticed how annoying is to write manually all the Ruby code just to invoke a service with complext input parameters' structure:
- You have to know what do the input parameters, their structure and type look like;
- You have to write Ruby classes for them to encapsulate the structures;
- You have to instantiate these classes and pass the objects to the web service proxy class;
- You have to interprete the output parameters.
All this is not impossible of course, but if you are just consumer of the web service and not the developer, if you don't have the exact documentation, you have to read the WSDL description of the service and create the Ruby classes (structures) for the parameters.
Fortunately there is a small, though handy tool, called wsdl2ruby.rb. It accomplishes all these boring tasks for you.
In the following example I will try to show you how wsdl2ruby can be used to generate Ruby classes for accessing a SAP NetWeaver web service, called CreditChecker1 (a web service for checking if a person is reliable credit consumer).
To generate the necessary classes we will create a ruby script. Let us name it ws2rgen.rb. Here is what this file looks like:
# Import the wsdl2ruby library.
require 'wsdl/soap/wsdl2ruby'
require 'logger'
# Callback function for the WSDL 2 Ruby generation options.
def getWsdlOpt(s)
 optcmd= {}
 s << "Service"
 optcmd['classdef'] = s
 #should work but doesn't, driver name is derived from classname
 #if you specify both it breaks, same thing for client_skelton
 #optcmd['driver'] = s
 optcmd['driver'] = nil
 #optcmd['client_skelton'] = nil
 optcmd['force'] = true
 return optcmd
end
# Create logger.
logger = Logger.new(STDERR)
# Create WSDL2Ruby object and generate.
worker = WSDL::SOAP::WSDL2Ruby.new
worker.logger = logger
# WSDL file location.
worker.location = "http://mysapserver:53000/CreditChecker1/Config1?wsdl"
# Where to generate.
worker.basedir = "temp"
# Set options.
worker.opt.update(getWsdlOpt("Service"))
# Heat.
worker.run
The procedure is straightforward. First we create the WSDL2Ruby object, set its properties location and basedir and then set all other options via the callback function getWsdlOpt(). For further information about these parameters one could consult the source code of wsdl2ruby or contact the developers. Nevertheless the default options are pretty satisfactory. With the last line we start the generation. Two Ruby files will be generated in the temp folder, which is a subfolder of the script's current folder. Please, create the folder "temp" before executing the script.
This generates two files. The first one is CreditChecker1Wsd.rb, containing the necessary data structures:
require 'xsd/qname'
# {urn:CreditChecker1Vi}areReliable
class AreReliable
@@schema_type = "areReliable"
@@schema_ns = "urn:CreditChecker1Vi"
@@schema_qualified = "true"
@@schema_element = [["persons", "ArrayOfPerson"]]
attr_accessor :persons
def initialize(persons = nil)
 @persons = persons
end
end
# {urn:CreditChecker1Vi}areReliableResponse
class AreReliableResponse
@@schema_type = "areReliableResponse"
@@schema_ns = "urn:CreditChecker1Vi"
@@schema_qualified = "true"
@@schema_element = [["response", ["ArrayOfboolean", XSD::QName.new("urn:CreditChecker1Vi", "Response")]]]
def Response
 @response
end
def Response=(value)
 @response = value
end
def initialize(response = nil)
 @response = response
end
end
# {urn:CreditChecker1Vi}isReliable
class IsReliable
@@schema_type = "isReliable"
@@schema_ns = "urn:CreditChecker1Vi"
@@schema_qualified = "true"
@@schema_element = [["person", "Person"]]
attr_accessor :person
def initialize(person = nil)
 @person = person
end
end
# {urn:CreditChecker1Vi}isReliableResponse
class IsReliableResponse
@@schema_type = "isReliableResponse"
@@schema_ns = "urn:CreditChecker1Vi"
@@schema_qualified = "true"
@@schema_element = [["response", ["SOAP::SOAPBoolean", XSD::QName.new("urn:CreditChecker1Vi", "Response")]]]
def Response
 @response
end
def Response=(value)
 @response = value
end
def initialize(response = nil)
 @response = response
end
end
# {urn:java/lang}ArrayOfboolean
class ArrayOfboolean < ::Array
@@schema_type = "boolean"
@@schema_ns = "http://www.w3.org/2001/XMLSchema"
@@schema_element = [["boolean", ["SOAP::SOAPBoolean[]", XSD::QName.new("urn:java/lang", "boolean")]]]
end
# {urn:com.sap.scripting.test.services.creditchecker.classes}Person
class Person
@@schema_type = "Person"
@@schema_ns = "urn:com.sap.scripting.test.services.creditchecker.classes"
@@schema_element = [["age", "SOAP::SOAPInt"], ["name", "SOAP::SOAPString"], ["purse", "Purse"]]
attr_accessor :age
attr_accessor :name
attr_accessor :purse
def initialize(age = nil, name = nil, purse = nil)
 @age = age
 @name = name
 @purse = purse
end
end
# {urn:com.sap.scripting.test.services.creditchecker.classes}Purse
class Purse
@@schema_type = "Purse"
@@schema_ns = "urn:com.sap.scripting.test.services.creditchecker.classes"
@@schema_element = [["color", "SOAP::SOAPString"], ["money", "Money"]]
attr_accessor :color
attr_accessor :money
def initialize(color = nil, money = nil)
 @color = color
 @money = money
end
end
# {urn:com.sap.scripting.test.services.creditchecker.classes}Money
class Money
@@schema_type = "Money"
@@schema_ns = "urn:com.sap.scripting.test.services.creditchecker.classes"
@@schema_element = [["amount", "SOAP::SOAPDouble"], ["currency", "SOAP::SOAPString"]]
attr_accessor :amount
attr_accessor :currency
def initialize(amount = nil, currency = nil)
 @amount = amount
 @currency = currency
end
end
# {urn:com.sap.scripting.test.services.creditchecker.classes}ArrayOfPerson
class ArrayOfPerson < ::Array
@@schema_type = "Person"
@@schema_ns = "urn:com.sap.scripting.test.services.creditchecker.classes"
@@schema_element = [["Person", ["Person[]", XSD::QName.new("urn:com.sap.scripting.test.services.creditchecker.classes", "Person")]]]
end
The second file is CreditChecker1WsdDriver.rb. In it you can find a generated child class of SOAP::RPC::Driver, containing all methods of this web service, so you don't need to add every method and its parameters to call the web service.
require 'CreditChecker1Wsd.rb'
require 'soap/rpc/driver'
class CreditChecker1Vi_Document < ::SOAP::RPC::Driver
DefaultEndpointUrl = "http://mysapserver:53000/CreditChecker1/Config1?style=document"
MappingRegistry = ::SOAP::Mapping::Registry.new
Methods = [
def initialize(endpoint_url = nil)
 endpoint_url ||= DefaultEndpointUrl
 super(endpoint_url, nil)
 self.mapping_registry = MappingRegistry
 init_methods
end
private
def init_methods
 Methods.each do |definitions|
 opt = definitions.last
 if opt[:request_style] == :document
 add_document_operation(*definitions)
 else
 add_rpc_operation(*definitions)
 qname = definitions[0]
 name = definitions[2]
 if qname.name != name and qname.name.capitalize == name.capitalize
 ::SOAP::Mapping.define_singleton_method(self, qname.name) do |*arg|
 __send__(name, *arg)
 end
 end
 end
 end
end
end
There is a problem with this script, since the Methods array is empty. I suppose it is due to the imports in the SAP NetWeaver WSDL, maybe wsdl2ruby is not mighty enough to handle these WSDL imports. When I succeed in overcoming this, I will post again in this thread to let everybody know.
Message was edited by: Vasil Bachvarov

Hi,
I find Ruby to be really tough to consume SAP WebServices. For simple scenarios like currency conversion may it is good. But for complex scenarios such as Purchase Order entry etc..I found it very annoying to use wsdl2ruby and see that it didnt generate correct proxies.
Until wsdl2ruby is stable enough to support complex datatypes, authentication etc. my recommendation is to use JRuby and use Java Proxies generated by NW Developer studio until pure Ruby's web service support improves.
Following link might be of interest w.r.t wsdl2ruby
http://derklammeraffe.blogspot.com/2006/08/working-with-wsdl2r-soap4r-and-complex.html
Regards
Kiran

WSDL of XI Webservice receiver

Hi!
I currently try to figure out how the SOAP Adapter of XI works. In our situation we would like to send data to the XI system to be able to process the data in SAP or transfer it to other systems.
I figured out that I need to install the adapter engine, set up a communication channel, define a Sender Agreement, Receiver Determination and Interface Determination (with Mapping).
Currently I am a little bit confused, about how the SOAP message must be structured. In the Intergration Builder (Directory) I am able to create the WSDL for proxy generation, but where is the content of the WSDL defined? Does it come from the mapping?
At the moment I have no system where I can test all the things, so I just read thousands of help documents and forum posts.
Thanks & Regards
Benjamin

Hi!
I currently try to figure out how the SOAP Adapter of XI works. In our situation we would like to send data to the XI system to be able to process the data in SAP or transfer it to other systems.
I figured out that I need to install the adapter engine, set up a communication channel, define a Sender Agreement, Receiver Determination and Interface Determination (with Mapping).
Currently I am a little bit confused, about how the SOAP message must be structured. In the Intergration Builder (Directory) I am able to create the WSDL for proxy generation, but where is the content of the WSDL defined? Does it come from the mapping?
At the moment I have no system where I can test all the things, so I just read thousands of help documents and forum posts.
Thanks & Regards
Benjamin

Error on Client WebService generation

Dear all,
I am trying to generate a client webservice for Microsoft Exchange Server from the exchange.wsdl.
While generation I get the following error.
+Incorrect value: XSD-Namensraum http://schemas.microsoft.com/exchange/services/2006/types nicht verfügbar
Exception of class CX_SIDL+
Does anybody knows what this means and how I can fix this to generate the client proxy from the WSDL.
Best regards
Roman

Hi,
Thanks for sharing the doc.
I had followed the steps as mentioned in the doc.
After specifying default mappings(Package name and Root Package Type) , I continued with the creation of Proxy.
When I click on the Finish button I am getting the mentioned error.
I can create proxy if I don't mention the default mappings.
Thakns

Error generating Client Proxy - object missing in WSDL

Hello,
I have error while generating Client Proxy.
I have WSDL and XSD in files. I get error message:
object <message name="requestUPOMessage"> missing in WSDL
Diagnosis
In the WSDL document, the object
 "<portType name="GateServicePortType"> <operatio..."
from the namespace
"https://bramka.edeklaracje. mf.gov.pl/"
links to the object
 "<message name="requestUPOMessage">"
from the namespace
 "https://bramka.e-deklaracje.mf.gov.pl/"
However, this last object does not exist in the WSDL document.
WSDL FILE and XSD FILE: http://www.sendspace.com/filegroup/N8kSxPp5bhY2nVfcNBbAXg
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns="https://bramka.edeklaracje.
mf.gov.pl/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:gate="https://bramka.e-deklaracje.mf.gov.pl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="https://bramka.edeklaracje.
mf.gov.pl/">
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:include schemaLocation="GateService.xsd"/>
</xs:schema>
</wsdl:types>
<wsdl:message name="sendDocumentWithAttachmentResponseMessage">
<wsdl:part name="part1" element="ns:sendDocumentWithAttachmentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendUnsignDocumentResponseMessage">
<wsdl:part name="part1" element="ns:sendUnsignDocumentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="requestUPOResponseMessage">
<wsdl:part name="part1" element="ns:requestUPOResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentResponseMessage">
<wsdl:part name="part1" element="ns:sendDocumentResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendUnsignDocumentMessage">
<wsdl:part name="part1" element="ns:sendUnsignDocument">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentMessage">
<wsdl:part name="part1" element="ns:sendDocument">
</wsdl:part>
</wsdl:message>
<wsdl:message name="requestUPOMessage">
<wsdl:part name="part1" element="ns:requestUPO">
</wsdl:part>
</wsdl:message>
<wsdl:message name="sendDocumentWithAttachmentMessage">
<wsdl:part name="part1" element="ns:sendDocumentWithAttachment">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="GateServicePortType">
<wsdl:operation name="sendDocument">
<wsdl:input message="gate:sendDocumentMessage">
</wsdl:input>
<wsdl:output message="gate:sendDocumentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<wsdl:input message="gate:sendUnsignDocumentMessage">
</wsdl:input>
<wsdl:output message="gate:sendUnsignDocumentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<wsdl:input message="gate:sendDocumentWithAttachmentMessage">
</wsdl:input>
<wsdl:output message="gate:sendDocumentWithAttachmentResponseMessage">
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<wsdl:input message="gate:requestUPOMessage">
</wsdl:input>
<wsdl:output message="gate:requestUPOResponseMessage">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="GateServiceSOAP12Binding" type="gate:GateServicePortType">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendDocument">
<soap12:operation soapAction="urn:sendDocument" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<soap12:operation soapAction="urn:sendUnsignDocument" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<soap12:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<soap12:operation soapAction="urn:requestUPO" style="document"/>
<wsdl:input>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="GateServiceSOAP11Binding" type="gate:GateServicePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendDocument">
<soap:operation soapAction="urn:sendDocument" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendUnsignDocument">
<soap:operation soapAction="urn:sendUnsignDocument" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sendDocumentWithAttachment">
<soap:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="requestUPO">
<soap:operation soapAction="urn:requestUPO" style="document"/>
<wsdl:input>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="GateService">
<wsdl:port name="GateServiceSOAP12port" binding="gate:GateServiceSOAP12Binding">
<soap12:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
</wsdl:port>
<wsdl:port name="GateServiceSOAP11port" binding="gate:GateServiceSOAP11Binding">
<soap:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="https://bramka.edeklaracje.
mf.gov.pl/xsd" targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:element name="sendDocument">
<xs:complexType>
<xs:sequence>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendUnsignDocument">
<xs:complexType>
<xs:sequence>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendUnsignDocumentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentWithAttachment">
<xs:complexType>
<xs:sequence>
<xs:element name="attachment" type="xs:base64Binary" minOccurs="0"/>
<xs:element name="document" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sendDocumentWithAttachmentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="requestUPO">
<xs:complexType>
<xs:sequence>
<xs:element name="refId" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="requestUPOResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="upo" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="xs:int"/>
<xs:element name="statusOpis" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Maybe someone know what is wrong in wsdl file and how to correct this?

Hi Marcus,
Did you fix the problem?
I'm asking because I'm dealing with the same problem! I tried to generate a Proxy object from a WSDL document and I can't... I always receive the error "Cannot generate proxy (object missing in WSDL, see long text)". I have checked on the service.sap.com and I found a xls document with all unsupported WSDL elements and one of them is the "part name=" and I have it in my WSDL! I don't know how to workaround this issue, can you help me please?
Thanks in advance,
Ricardo.

Stub(Proxy) generation for external Web Service in SAP NW WebAS 6.40

Hi,
Can anyone tell me what tool is used to generate the proxy files for accessing any external web services in SAP NetWeaver WebAS 6.40 for JAVA (SAP DevStudio 2.0.5).
Do i have to install any components or configuration for using external web services?
Thanks,
Mital.

Hi Peter,
Thanks for the reply.
I have already gone through the Email Web Service tutorial. And implemented the tutorila.But no where they have mentioned about the toolkit they are using to generate stub files and SOAP request.(for eg Axis tool for WSDL to java generation).
Also I am facing problems while I am trying to use an external webservice. I have posted the problem at Re: WebDynpro External Web Service Model.
It would be nice if uyou can go through the problem and help me in solving the problem.
Also can you please tell me the link for the mentioned documents on importing web service model.
Thanks,
Mital.

How to use the same element in different Web-Services?

I have defined a web-services in two WSDL files.
I want to use the same type in this two services. Because if one service call the other one, it could pass the class it just got. Otherwise, the classes can't be casted.
Web-Service1:
public com.package1.State inputValue (com.package1.State state) {
return state;
Web-Service2:
public com.package2.State inputValue (com.package2.State state) {
return state;
}And now, If I call from the Service2, the Service1 and put
Service1.inputValue(com.package2.State state) ;
I can't do this, can't cast and so on. But I want my tool WSDL2Java, will create the same State.class for two Web-Services, like:
Web-Service1:
public com.package3.State inputValue (com.package3.State state) {
return state;
Web-Service2:
public com.package3.State inputValue (com.package3.State state) {
return state;
}Is it possible? How to define it in wsdl?
Thanks in advance.

You can certainly do this in WSDL, simply put your
common element in a schema file and "include" it into
each of your WSDL files. Obviously your element will
have to use the same namespace in all places.
I'm not sure whether wsdl2java can cope with
"include" statements in WSDL. I know plenty of other
similar tools, e.g. Axis and .Net tools, didn't
support this however they may have moved on since I
used them.
To get around this you have to "manually" include the
schema in each wsdl for code generation purposes.Thanks for the answer. I did as you said and it works fine.

Calling Web Service from CRM using proxy

Hi all,
I'm facing a problem trying to call a web service from CRM (WAS 620) via XI 3.0. The response that XI recieves from the web service contains SOAP Envelope, and the mapping fails because of it. I built the proxy manually, because if I load WSDL the proxy generation in CRM generates error that sais that external definition coudn't be used.
Is there any way to remove SOAP envelope from the response while mapping?
Is it possible to call web service from WAS 620?
Thanks!!!!
Anya.

Hi Manish,
SOAP adapter does pass the message to XI (this message contains SOAP envelope although XI expects to get message without it), and during the mapping step i get "Runtime Exception in Message-Mapping transformatio~".
I suppose it's because i created proxy manually. I did so because when i imported WSDL, and tried to generate proxy in CRM, i got an error message that said that proxy couldn't be generated because external definitions are only allowed in XI 3. But my XI version is 3.0! And when I generate the same proxy in my R/3 system that is installed on WAS 640, it works.
What can I do?
Cheers,
Anya.

Proxy object to consume web service

Hi,
I want to consume a web service in ABAP (on a WAS 7 box) and have read many blogs/posts about using a proxy object.
I've gone to SE80 and selected create a service consumer, enter the URL for the WSDL.
The generation of the proxy fails with the following messages;
Proxy-Generierung: Fehler aufgetreten
Exception occured in the library handler
not implemented
There is no other help or information in these errors.
Does anyone have any ideas on what is causing this and what I can do to successfully generate a proxy to consume the web service ?
Cheers
James

Hello Torsten,
It seems that the Web Service You are going to consume is a SOAP 1.2 one.
It is apparently making use of the so-called "SOAP Web Method Feature" which is part of the SOAP 1.2 specification (see [Web Method Feature (W3C)|http://www.w3.org/TR/soap12-part2/#WebMethodFeature]).
Unfortunately, SOAP 1.2 is, to the best of my knowledge, not supported as yet by the SOAP Adapter in SAP NW 7.0 / 7.1. That leaves You, in theory, with one of the following options:
- It might be possible to consume that service with the help of Axis framework (see [Using the Axis Framework in the SOAP Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm]). SAP Help states that with the help of the Axis framework SOAP 1.2 can be used. However, there are no further details on that subject, especially whether Web Method feature can be utilised (btw - has anyone tried this?).
- Ask service provider for a SOAP 1.1-compatible WSDL.
- Attempt to reverse engineer the SAP SOAP proxy so that it is capable of consuming a SOAP 1.2 Web Method-based web service (has anyone done this before?).
Would You be so kind to post whether, and how, You were able to consume this web service?
Kind regards
Wiktor Nyckowski

Calling ABAP Web Service at https destination

Hi!
I have created an ABAP Proxy that calls an external web service at an http destination. When trying the same for a service at an https destination I get the error message 
HTTP error (return code 110, message "" when specifying the URL for the WSDL file. I tried one of Thomas Jungs blogs on HTTPS services (/people/thomas.jung3/blog/2005/05/13/calling-webservices-from-abap-via-https), but here he says that "When we begin to get differences (From http setup) is in the setup of the Logical Port". Am I missing something? Some configuration to be done?
Thanks for your input!
-Ole
Message was edited by:
Ole Mugaas

Hi!
Do you mean trying to access the WSDL through an already defined HTTP connection? My problem arises when trying to enter the URL to the WSDL during proxy generation...

Tips to install 8.20 version

Are there any tips for installing 8.20? I need to update to check out the script updater. Do I need to uninstall the old version or reinstall?
Are there any issues I should be aware of?
Is there a release document that shows the fixes or enhancements this version contains?
Thank you

tlandis,
I guess you have allready upgraded, but here are some additional info regarding your post... :-D
When you de-install your current version, it will just unregister the dlls and stuff that the installer have registered on your PC. all files will remain on your system...and as mentioned in the first reply to your question, you can simply re-install on top of your old installation. I do however recommend that you backup your scripts/workspaces just to be on the safe side. ;-)
Here is a overview of some of the enhancements:
eTester
Script Updater ? e-Tester now includes a batch Script Updater utility that enables users to update multiple scripts at once. Common updates such as base url, script settings, test settings, object paths and more can be specified and applied to any number of scripts at once through this new utility which is accessible from the main e-TEST suite folder.
Results Report Enhancements ? The e-Tester Results Report has been enhanced to include more detailed content and an improved layout. This HTML report is also now generated from a customizable XSL file which can be modified by users if needed.
Web Services Enhancements ? e-Tester 8.20 includes multiple enhancements to the Web Services testing module such as:
Ability to define which WSDL parser to use for WSDL-based script generation or to specify the location of a custom parser.
Ability to generate Web Services requests with attachments that utilize DIME, MTOM and SwA standards
Ability to generate secure Web Services requests based on username token security
General bug fixes, program improvements and maintenance updates.
eLoad
Reporting Enhancements ? e-Load 8.2 includes multiple enhancements for both real-time and post-run reports including:
Default Graphs definitions are now available for post-run reporting against stored e-Load Sessions. This enables users to select from a pre-defined set of default graphs rather than having to select individual data series to create a graph. New default graph options are also now available in both real-time and post-run reporting interfaces.
Users can now enable a secondary y-axis for viewing multiple data series that are of varying scales. Users can specify whether to plot each data series against the primary or secondary y-axis.
A threshold line can now be added to an e-Load graph to allow users to graph their data series relative to a predefined threshold value
The Saved Queries feature has been enhanced to allow users to map counters from a saved graph query against differently named counters from the e-Load Session the query is being applied against.
Graph legends can now be edited through the e-Load graph options
e-Load 8.20 includes a new report generator for creating load test reports from pre-defined templates. Templates can be created in RTF format and include both user defined content as well as tags that extract graphs or test data from e-Load Session results. These templates can then be uploaded to e-Load and used for generating reports against any Session file from the Create Reports?Reports tab.
ServerStats System Editor ? e-Load 8.20 includes a new system editor function for more granularly defining monitored systems. Users can now automatically discover or manually define the specific components of a monitored system (including CPUs, disks, databases, etc.) so that ServerStats Profiles and Metrics can be applied against these specific components rather than just to the system as a whole.
Unix Agent Support ? e-Load 8.20 now supports Virtual User Agent Systems running on Unix/Linux operating systems through the e-Load Java Agent.
General bug fixes, program improvements and maintenance updates.
eME
New Web Reporting Interface ? e-Manager Enterprise 8.20 includes a new Web Reports interface that provides new and improved capability for viewing, editing and creating e-ME Reports via e-ME?s Web UI. This major enhancement allows users to:
Access all of e-ME?s default reports from e-ME?s new Reports tab in the Web user interface.
Clone and edit e-ME?s default reports, including editing report content and filters
Create new custom reports, including both text and graphical reports, from within e-ME Web UI
Filter reports using saved filter definitions
Export reports and data tables in multiple standard formats and email reports to other users from e-ME
Save new reports as "Public" and viewable by all users or in a personal "My Reports" folder
Create and view multi-report dashboards from e-ME's new Dashboard tab in the Web UI
Specify permissions for report viewing and editing
Enhanced Search Capability ? An enhanced search interface in e-ME?s Web UI enables users to:
Perform multi-field conditional searches (using AND, OR and nested AND/OR queries)
Save search query filters by name and recall them for future searches
Reuse saved search filters for reports filtering or for filtering the e-ME tree view
Display and edit search results in the e-ME tree view even if they are filtered out of the user?s current view
Improved Usability ? e-ME 8.20 also includes multiple usability enhancements such as:
Ability to save multiple tree view display groupings for Requirements, Tests and Issues and access saved groups from a dropdown in the main Web UI
Ability to save multiple tree view or grid view filters for Requirements, Tests and Issues and access saved filters from a dropdown in the main Web UI.
"Goto" feature for quick access to any Requirement, Test or Issue by number from the Web UI toolbar
General bug fixes, program improvements and maintenance updates.

Error during generation of the WSDL: BUILD FAILED java.lang.NoClassDefFoundError: com/sun/javadoc/Type

When I create an EJB Transport Business Service, after selecting the jar that has the EJB 2.1 artefacts (Remote, Home, etc) the oepe plugin fails and can't continue.
As I understand it seems that there is a problem with the classpath of ant build.xml that oepe creates inside folder /tmp/alsbejbtransport/ to compile the bs and generate the wsdl. I checked if tools.jar is in the classpath (in eclipse) and is included, so I can't figure out wich is the problem.
I found this in Oracle, but not helps solve the problem:
BEA-398120
Error: The WSDL for the typed transport endpoint could not be accessed.
Description
There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration
Action
Contact technical support
This is the the full stacktrace that shows eclipse.
Generate : Error during generation of the WSDL:
BUILD FAILED
java.lang.NoClassDefFoundError: com/sun/javadoc/Type
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createSourceBuilder(JamServiceFactoryImpl.java:205)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createBuilder(JamServiceFactoryImpl.java:158)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createClassLoader(JamServiceFactoryImpl.java:137)
 at com.bea.util.jam.provider.JamServiceFactoryImpl.createService(JamServiceFactoryImpl.java:78)
 at weblogic.wsee.util.JamUtil.parseSource(JamUtil.java:152)
 at weblogic.wsee.tools.anttasks.JwsLoader.loadJClasses(JwsLoader.java:186)
 at weblogic.wsee.tools.anttasks.JwsLoader.load(JwsLoader.java:75)
 at weblogic.wsee.tools.anttasks.JwsModule.loadWebServices(JwsModule.java:569)
 at weblogic.wsee.tools.anttasks.JwsModule.generate(JwsModule.java:369)
 at weblogic.wsee.tools.anttasks.JwsModule.build(JwsModule.java:256)
 at weblogic.wsee.tools.anttasks.JwscTask.execute(JwscTask.java:184)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.Task.perform(Task.java:348)
 at org.apache.tools.ant.Target.execute(Target.java:357)
 at org.apache.tools.ant.Target.performTasks(Target.java:385)
 at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
 at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
 at org.apache.tools.ant.Main.runBuild(Main.java:758)
 at org.apache.tools.ant.Main.startAnt(Main.java:217)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.lang.ClassNotFoundException: com.sun.javadoc.Type
 at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1400)
 at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1341)
 at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1088)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
 ... 27 more
Total time: 0 seconds
Eclipse Installation details:
*** System properties:
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=M20110909-1335
eclipse.commands=-os
linux
-ws
gtk
-arch
x86_64
-showsplash
-launcher
{home}/Development/oepe-indigo/eclipse
-name
Eclipse
--launcher.library
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so
-startup
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata
1e418010
-vm
/usr/bin/java
eclipse.home.location=file:{home}/Development/oepe-indigo/
eclipse.launcher={home}/Development/oepe-indigo/eclipse
eclipse.launcher.name=Eclipse
[email protected]/../p2/
eclipse.p2.profile=PlatformProfile
eclipse.product=org.eclipse.platform.ide
eclipse.startTime=1374623921455
eclipse.vm=/usr/bin/java
eclipse.vmargs=-Xms256m
-Xmx768m
-XX:MaxPermSize=512m
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3
-Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
-Dosb.home={home}/Oracle/Middleware/Oracle_OSB1
-Dosgi.bundlefile.limit=750
-Dosgi.nl=en_US
-Dmiddleware.home={home}/Oracle/Middleware
-jar
{home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
equinox.use.ds=true
file.encoding=UTF-8
file.encoding.pkg=sun.io
file.separator=/
guice.disable.misplaced.annotation.check=true
harvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester
http.nonProxyHosts=localhost
java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
java.awt.printerjob=sun.print.PSPrinterJob
java.class.path={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
java.class.version=50.0
java.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/endorsed
java.ext.dirs=/usr/lib/jvm/jdk1.6.0_45/jre/lib/ext:/usr/java/packages/lib/ext
java.home=/usr/lib/jvm/jdk1.6.0_45/jre
java.io.tmpdir=/tmp
java.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_45/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.protocol.handler.pkgs=null|com.bea.wli.sb.resources.url|com.bea.wli.sb.resources.jca.upgrade.url|weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net|weblogic.net
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_45-b06
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_45
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=20.45-b01
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
jna.platform.library.path=/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator=
middleware.home={home}/Oracle/Middleware
oracle.eclipse.tools.weblogic.ui.isWebLogicServer=true
org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog
org.eclipse.equinox.launcher.splash.location={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
org.eclipse.equinox.simpleconfigurator.configUrl=file:org.eclipse.equinox.simpleconfigurator/bundles.info
org.eclipse.m2e.log.dir={home}/workspace/pragma/.metadata/.plugins/org.eclipse.m2e.logback.configuration
org.eclipse.update.reconcile=false
org.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,OSGi/Minimum-1.2,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6
org.osgi.framework.language=en
org.osgi.framework.os.name=Linux
org.osgi.framework.os.version=3.8.0
org.osgi.framework.processor=x86-64
org.osgi.framework.system.capabilities=osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0, 1.1, 1.2",osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6"
org.osgi.framework.system.packages=javax.accessibility,javax.activation,javax.activity,javax.annotation,javax.annotation.processing,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.jws,javax.jws.soap,javax.lang.model,javax.lang.model.element,javax.lang.model.type,javax.lang.model.util,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.script,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.tools,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters,javax.xml.bind.attachment,javax.xml.bind.helpers,javax.xml.bind.util,javax.xml.crypto,javax.xml.crypto.dom,javax.xml.crypto.dsig,javax.xml.crypto.dsig.dom,javax.xml.crypto.dsig.keyinfo,javax.xml.crypto.dsig.spec,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.soap,javax.xml.stream,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stax,javax.xml.transform.stream,javax.xml.validation,javax.xml.ws,javax.xml.ws.handler,javax.xml.ws.handler.soap,javax.xml.ws.http,javax.xml.ws.soap,javax.xml.ws.spi,javax.xml.ws.wsaddressing,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.css,org.w3c.dom.events,org.w3c.dom.html,org.w3c.dom.ls,org.w3c.dom.ranges,org.w3c.dom.stylesheets,org.w3c.dom.traversal,org.w3c.dom.views,org.w3c.dom.xpath,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers
org.osgi.framework.uuid=901615cd-f3f3-0012-11b6-a3bca4d97ac1
org.osgi.framework.vendor=Eclipse
org.osgi.framework.version=1.6.0
org.osgi.supports.framework.extension=true
org.osgi.supports.framework.fragment=true
org.osgi.supports.framework.requirebundle=true
os.arch=amd64
os.name=Linux
os.version=3.8.0-26-generic
osb.home={home}/Oracle/Middleware/Oracle_OSB1
osgi.arch=x86_64
osgi.bundlefile.limit=750
osgi.bundles=reference:file:javax.transaction_1.1.1.v201105210645.jar,reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110502-1955.jar@1:start
osgi.bundles.defaultStartLevel=4
osgi.bundlestore={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/bundles
osgi.configuration.area=file:{home}/Development/oepe-indigo/configuration/
osgi.framework=file:{home}/Development/oepe-indigo/plugins/org.eclipse.osgi_3.7.1.R37x_v20110808-1106.jar
osgi.framework.extensions=reference:file:javax.transaction_1.1.1.v201105210645.jar
osgi.framework.shape=jar
osgi.framework.version=3.7.1.R37x_v20110808-1106
osgi.frameworkClassPath=., file:{home}/Development/oepe-indigo/plugins/javax.transaction_1.1.1.v201105210645.jar
osgi.install.area=file:{home}/Development/oepe-indigo/
osgi.instance.area=file:{home}/workspace/pragma/
osgi.instance.area.default=file:{home}/workspace/
osgi.logfile={home}/workspace/pragma/.metadata/.log
osgi.manifest.cache={home}/Development/oepe-indigo/configuration/org.eclipse.osgi/manifests
osgi.nl=en_US
osgi.nl.user=en_US
osgi.os=linux
osgi.splashLocation={home}/Development/oepe-indigo/plugins/org.eclipse.platform_3.7.1.v201109091335/splash.bmp
osgi.splashPath=platform:/base/plugins/org.eclipse.platform
osgi.syspath={home}/Development/oepe-indigo/plugins
osgi.tracefile={home}/workspace/pragma/.metadata/trace.log
osgi.ws=gtk
path.separator=:
securerandom.source=file:/dev/./urandom
socksNonProxyHost=localhost
sun.arch.data.model=64
sun.boot.class.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/resources.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/rt.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/sunrsasign.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jsse.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/jce.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/charsets.jar:/usr/lib/jvm/jdk1.6.0_45/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/jdk1.6.0_45/jre/classes
sun.boot.library.path=/usr/lib/jvm/jdk1.6.0_45/jre/lib/amd64
sun.cpu.endian=little
sun.cpu.isalist=
sun.desktop=gnome
sun.io.unicode.encoding=UnicodeLittle
sun.java.command={home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher {home}/Development/oepe-indigo/eclipse -name Eclipse --launcher.library {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505/eclipse_1407.so -startup {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.overrideVmargs -exitdata 1e418010 -vm /usr/bin/java -vmargs -Xms256m -Xmx768m -XX:MaxPermSize=512m -Dsun.lang.ClassLoader.allowArraySyntax=true -Dweblogic.home={home}/Oracle/Middleware/wlserver_10.3 -Dharvester.home={home}/Oracle/Middleware/Oracle_OSB1/harvester -Dosb.home={home}/Oracle/Middleware/Oracle_OSB1 -Dosgi.bundlefile.limit=750 -Dosgi.nl=en_US -Dmiddleware.home={home}/Oracle/Middleware -jar {home}/Development/oepe-indigo//plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
sun.java.launcher=SUN_STANDARD
sun.jnu.encoding=UTF-8
sun.lang.ClassLoader.allowArraySyntax=true
sun.management.compiler=HotSpot 64-Bit Tiered Compilers
sun.os.patch.level=unknown
svnkit.http.methods=Basic
svnkit.library.gnome-keyring.enabled=false
user.country=AR
user.dir={home}/Development/oepe-indigo
user.home={home}
user.language=es
user.name={username}
user.timezone=America/Argentina/Buenos_Aires
weblogic.home={home}/Oracle/Middleware/wlserver_10.3
Thanks!!

run this one in command prompt and then convert the applet using converter tool
JC_HOME = C:\java_card_kit-2_2_2\bin\
set CLASSES=%JCHOME%\lib\apduio.jar;%JC_HOME%\lib\apdutool.jar;%JC_HOME%\lib\jcwde.jar;%JC_HOME%\lib\converter.jar;%JC_HOME%\lib\scriptgen.jar;%JC_HOME%\lib\offcardverifier.jar;%JC_HOME%\lib\api.jar;%JC_HOME%\lib\installer.jar;%JC_HOME%\lib\capdump.jar;
D:\NareshPalle\jcardRE\Smart\src>java -classpath %_CLASSES% com.sun.javacard.con
verter.Converter -out EXP JCA CAP -exportpath .\exp -applet 0x0a:0x00:0x00:0x00:0x0e:0x01:0x02:
0x03:0x04:0x05:0x06 PackageName appletName 0x01:0x02:0x03:0x04:0x05:0x0
6:0x07:0x08 1.0
or
go to following directory and run the converter tool in command prompt
step 1: cd C:\java_card_kit-2_2_2\bin\
then run this command under the above directory
step 2:converter -classdir E:\Pathof Your applet class file -out EXP JCA CAP -exportpath E:\path of exp files folder -applet AID PackageName AppletName PackAID major.minor no
For more doubts mail me....
*[removed by moderator]*
Thanks and Regards
NareshPalle
Edited by: EJP on 31/03/2012 20:09: removed your email address. Unless you like spam and unless you think these forums are provided for your personal benefit only, posting an email address here serves no useful purpose whatsoever.

ABAP Proxy generation terminated (WSDl choice element not supported)

Hello
Im trying to generate ABAP proxy from WSDL file (A valid XSD file has imported as External definitions in to XI Integration Repository and created Out bound Interface which gives WSDL file for Proxy generation in SPROXY).
Unfortunately one of the WSDL file element "<choice>" not supported by ABAP Proxy Generation. it gives the following error.
Proxy generation terminated: WSDL error (<choice> not supported)
Message no. SPRX038
Syntax of <choice> element code in WSDL file:
<xsd:choice minOccurs='1' maxOccurs='1'>
<xsd:element name='Employees' minOccurs='1' maxOccurs='1'>
</xsd:element>
</xsd:choice>
Can some one please help if already come across this kind of problem.
Please suggest me if there any alternate element for WSDL <choice>.
Regards
Rajesh

Hi Aamir
Thanks for your help...
I have gone through attached thread.
Does It means should i change <choice> element with any alternate element. If it is the case can u suggest me any alternate to <choice> element.
Can u pls tell what are all changes i need to do in WSDL file to support ABAP proxy generation.
Regards
Rajesh

Unsupported wsdl to as generation

Similar Messages

Maybe you are looking for