Call a method with complex data type from a DLL file

Hi,
I have a win32 API with a dll file, and I am trying to call some methods from it in the labview. To do this, I used the import library wizard, and everything is working as expected. The only problem which I have is with a method with complex data type as return type (a vector). According to this link, import library wizard can not import methods with complex data type.
The name of this method is this: const std::vector< BlackfinInterfaces::Count > Counts ()
where Count is a structure defined as below:
struct Count
Count() : countTime(0) {}
std::vector<unsigned long> countLines;
time_t countTime;
It seems that I should manually use the Call Library Function Node. How can I configure parameters for the above method?

You cannot configure Call Library Function Node to call this function. LabVIEW has no way to pass a C++ class such as vector to a DLL.

Similar Messages

Creating Web service for PL/SQL Procedure with Complex Data Types

I need to created web service for PL/SQL Procedure with Complex Data types like table of records as parameters, how do we map the pl/sql table type parameters with web service, how to go about these?

Hello,
When you are creating a service from a Stored Procedure, the OracleAS WS tools will create necessary Java and PL wrapper code to handle the complex types (table of record) properly and make them compatible with XML format for SOAP messages.
So what you should do is to use JDeveloper or WSA command line, to create a service from your store procedure and you will see that most of the work will be done for you.
You can find more information in the:
- Developing Web Services that Expose Database Resources
chapter of the Web Service Developer's guide.
Regards
Tugdual Grall

How to access complex data type from a soap web services?

hello
can u please tell me how can i access complex data type from a soap web service from jdeveloper 10g
Jdeveloper generates 3 classes
serviceStub
getproperties
response
i have to retreview the data which is a complex data type it gives some
unknown type. and the return value is a key-value pair data type .
regards
vs

After you create the partner link and the invoke (to create the variables), change the element type of the response message to the complex type definition of your collection that appears in the XSD. You can do the same thing if you want to change the element type of the payload of the request message as well.

Working with complex data types in web services ...

Hi All,
I have created a webservice and created an interface for that in ADF. Now as my web service returns a complex data type, i followed the steps given in this article "http://www.oracle.com/technology/products/jdev/howtos/1013/wsadf/adfcomplexwstypes.html" and it works fine, my results also get displayed. But only issue is i get a warning "JBO-25009: Cannot create an object of type:java.util.calendar with value:2008-09-23T23:51:30.000+05:30" and if i replace all the java.util.Date with oracle.jbo.domain.Date then i get a warning "JBO-25009: Cannot create an object of type:oracle.jbo.domain.Date with value:2008-09-23T23:51:30.000+05:30". Now i am unable to understand this although i believe it is a data type mapping issue, but not sure how to rectify it.
Anybody knows the wayout?
Regards
Lokesh

Andre,
Thanks for youe response. I also tried makeing data type as string in place of date in data control.xml and it worked fine. So it confirms that i am facing with exactly similar issue as yours.
I tried solution 2 mentioned in Frank's mail but its not helping[in fact i am already using web proxy as i am delaing with complex data types]. I created a web proxy and in java bean i placed break points to check the control flow[in order to check the root cause] but control never reaches the java bean!! I am not sure about the cause for it...control should pass through java bean isn't it??
I am quite new to SOA...so can somebody just elaborate on how to rectify this using web proxy. I have been using this rl "http://www.oracle.com/technology/products/jdev/howtos/1013/wsadf/adfcomplexwstypes.html" to work with web proxies" to work with proxies.
Regards
Lokesh

Consuming an ASP web service which responds with complex data types...

Here's my problem - I'm trying to consume a web service from a provider that uses complex data types.
The starting part of the WSDL looks like this (I've not included the whole thing) - named have been changed to protect the innocent:
<wsdl:definitions targetNamespace="http://domain_name">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://domain_name">
<s:element name="Authentication">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Username" type="s:string"/>
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string"/>
<s:element minOccurs="0" maxOccurs="1" name="Token"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AuthenticateResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="AuthOK" type="s:int"/>
<s:element minOccurs="0" maxOccurs="1" name="Token"/>
</s:sequence>
</s:complexType>
</s:element>
Since it's a complexType return, with a sequence, I'd expect an array or structure returned, but instead I just get the "AuthOK" value, and no way to get anything else.
Here are the ways I've tried calling it:
<cfscript>
    WS = createObject("webservice", "https://WSDL_URL");
    WS_ret = WS.Authentication(Username = "username", Password = "password", Token = "");
</cfscript>
<cfdump var="#WS_ret#" />
<cfinvoke webservice="WSDL_URL" method="Authentication" returnVariable="WS_ret">
    <cfinvokeargument name="userID" value="7253320" />
    <cfinvokeargument name="password" value="ctpjxs3" />
    <cfinvokeargument name="SecurityToken" value="" />
</cfinvoke>
<cfdump var="#WS_ret#" />
Any ideas how I can get the other variables in the sequence? I have other calls after this that have a much larger amount of variables, and as such I can't use it without being about to get more of the

Thanks for the reply.
If I CFDUMP the variable it returns just "1", no XML tags, nothing at all around the data - according to the web service providers they say that they are supplying the Token part as long as the first variable is "1" (a logical true if the authentication passed). If it is "0" then no Token is returned, that is why it's optional.
As for the CFdocs issue, look here:
http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=webservices_25.html
The paragraph before it (about 2/3 down the page) states:
In this example, the operation updateEmployeeInfo takes a complex type as input and returns a complex type as output. To handle the input parameter, you create a structure. To handle the returned value, you write it to a ColdFusion variable, as the following example shows:
It even states that you call "updateEmployeeInfo", and nowhere mentions "echoStruct" as a method - it's seemingly been put in as a random method name, or a function call for something else. The WSDL above the example only mentions "updateEmployeeInfo" and "updateEmployeeInfoSoapOut", again not mentioning "echoStruct".
I see this as an error in the docs as it's calling a non-existant entity in the WSDL, which should cause a run-time error.

++Custom Serialization with Complex Data type (Nested Classes)

Hi,
We have a scenario wherein we need to write CUSTOM SERIALIZERS for complex datatypes like INVOICE & ORDER (INVOICE inturn has ADDRESS type among others, ORDER has ADDRESS type, a COLLECTION of type ORDERITEM each of which are Java Classes in themselves)
The example of Custom Serializer given in the SOA AS Dev Guide http://download.oracle.com/docs/cd/B31017_01/web.1013/b28975/custserial.htm#CFHHIBCA)
shows only a simple java type used for serialization and deserialization.
Can anyone please help us out by sharing any example depicting the CUSTOM SERIALIZERs for COMPLEX DATA TYPES?
Thanks in advance,
Pavan.

Hello,
Could you please post the code of your classes in the forum (at least the interfaces) ?
Regards
Tugdual Grall

Web Services with Complex Data Types in ADF 11g

Shay Shmeltzer's following blogpost can answer my questions but all the links there
http://blogs.oracle.com/shay/2009/09/web_services_with_complex_data.html
Can you please point us to the correct links for the following documents?
http://www.oracle.com/technology/tech/fmw4apps/agile/pdf/adf11g-agile.pdf
http://www.oracle.com/technology/products/jdev/tips/fnimphius/wsdccomplexinputtype/index.html

Thanks. We are using a Java Proxy to consume the web service as we need to use JAX-WS handlers. We created data control from the service stub that was created by the proxy. Our issue is with the response XML which comes as a complex type. Also, the data control is understanding the complex type and is creating the structure right. The problem is when we drag that control on a JSF page. No data is displayed. We think that we are not traversing the complex object properly which is creating the issue.
I understand that you answer related to the input is applicable to output as well. We can change the structure by flattening it but we thought that in 11G there is some new features where we can use the complex types out of the box without any change. Is that true? Also, any luck in finding the documents (broken links) on your blog page?

Call Oracle procedure with custom data type within Java and Hibernate

I have a custom date TYPE in Oracle
like
CREATE TYPE DATEARRAY AS TABLE OF DATE;
and I have a Oracle function also
like
CREATE OR REPLACE FUNCTION doesContain (list DATEARRAY, val VARCHAR2) RETURN NUMBER
IS
END doesContain;
In my Java class,
I have a collection which contain a list of java.util.Date objects
When I call Oracle function "doesContain", how to pass my java collection to this Oracle function ...
anyone can provide solutions?
Please !!!
Thanks,
Pulikkottil

Vu,
First of all you need to define your types as database types, for example:
create or replace type T_ID as table of number(5)Then you need to use the "oracle.sql.ARRAY" class. You can search this forum's archives for the term "ARRAY" in order to find more details and you can also find some samples via the JDBC Web page at the OTN Web site.
Good Luck,
Avi.

Error while calling XQuery Function with xs:date type as Argument

Hi,
I have follwing function in my DataService .
declare function tns:getXXXDetail($effectiveDate as xs:date,
$cancelDate as xs:date) as element(ns26:XXXAccount)* {
          implCode
declare function tns:testGetXXXDetail($searchCriteria as element(ns15:locateMemberXXXDetail))
               as element(ns26:XXXAccount)* {
for $Account in tns:getXXXDetail($searchCriteria/ns16:accountTypeDates/ns18:effectiveDate,
     $searchCriteria/ns16:accountTypeDates/ns18:cancelDate)
return $Account
I am trying to test the getXXXDetail() function from testGetXXXDetail .
The searchCriteria is a complex type with date elements effectiveDate and cancelDate, both are optional
When i test with effectiveDate,cancelDate elements present in $searchCriteria its working fine.
When i remove these dates element i am getting follwing error
"expected exactly one item, got 0 items" error
Any Clue ?

When i remove these dates element i am getting follwing error"expected exactly one item, got 0 items" error
Sounds like your schema for these items indicates minOccurs="1" (or relies on that as the default).
Edit the schema and change the definitions to be...
<xs:element name="effectiveDate" minOccurs="0" ... />

Manual WSDL creation with Complex data types

I'm trying to manually generate a WSDL, for a bpel workflow, so the wsdl constructs do not come from a Java class file, or any of the other normal ways you might generate a WSDL.
I have successfully created a Definition object from the WSDLFactory, with the code shown below, that appears to be correct, based on reverse engineering of a WS compliant WSDL. The reversed engineered WSDL was created by IONA Artix.
When I use file WSDLFactoryImpl.WSDLWriterImpl.writeWSDL() to write the WSDL file I get the wsdl:types and wsdl:service definition objectsin the file, but not the wsdl:message, wsdl:portType or wsdl:binding objects.
The reverse engineered WSDL file has been imported into objects via WSDLReaderImpl, and the resulting Definition object appears correct (based on all system.outs). This definition can be successfully written to file via the same WSDLFactoryImpl.WSDLWriterImpl.writeWSDL(). which results in a correct WSDL file.
I'm hoping someone can spot my problem.
Chris Yoerg
WSDLFactory.java************************************************************************************************
package com.dralasoft.bpel.util;
import java.util.*;
import java.io.*;
import javax.xml.namespace.QName;
import javax.xml.parsers.*;
import javax.wsdl.WSDLException;
import javax.wsdl.extensions.UnknownExtensibilityElement;
import org.w3c.dom.*;
import com.ibm.wsdl.*;
import com.ibm.wsdl.factory.WSDLFactoryImpl;
import com.ibm.wsdl.extensions.soap.*;
/** This class generates a wsdl from scratch
* the way the namespaces have been left seem to be correct in that the individual
* porttype, binding and service objects pick up the message parts as seen in the
* individual system.outs and in the system.out of the definition
* if you use the tns prefix iteration as seen in the comment out "trial" code
* you get an error that the tns namespace does not exist in the definition
* even though it is definitely there
* the non namespace "trial" code also behaves the same way as this iteration,
* aka the stuff shows in the definition outputs, but never ends up outputed to
* file */
//import com.dralasoft.bpel.BPELWorkflow;
public class WSDLFactory {
public WSDLFactory() {
public void makeWorkflowWSDL(){
WSDLFactoryImpl factory = null;
Constants constants = new Constants();
SOAPConstants soapconstants = new SOAPConstants();
try {
factory = (WSDLFactoryImpl) WSDLFactoryImpl.newInstance();
catch (WSDLException we) {
System.out.println("wsdl excepiotn " + we.getMessage());
// get a new definition from the factory
DefinitionImpl definition = (DefinitionImpl) factory.newDefinition();
// add target namespace and additional namespaces that might be there
definition.setTargetNamespace("http://www.yoerg.net");
definition.addNamespace("tns", "http://www.yoerg.net");
definition.addNamespace("soap", "http://schemas.xmlsoap.org/wsdl/soap/");
definition.addNamespace("xsd", "http://www.w3.org/2001/XMLSchema");
definition.addNamespace("wsdl", "http://schemas.xmlsoap.org/wsdl/");
// added for generic purposes
definition.addNamespace("xsi", "http://www.w3.org/2001/XMLSchema-instance");
// specify the service name
QName qname = new QName("http://www.yoerg.net",
"PurchaseOrderProcess");
definition.setQName(qname);
// create types **********************************************************
TypesImpl types = (TypesImpl) definition.createTypes();
// generate a schema in DOM to set into the types object
javax.xml.parsers.DocumentBuilderFactory domfactory =
javax.xml.parsers.DocumentBuilderFactory.newInstance();
javax.xml.parsers.DocumentBuilder builder = null;
try {
builder = domfactory.newDocumentBuilder();
catch (javax.xml.parsers.ParserConfigurationException pce) {
System.out.println("parser config exception " + pce.getMessage());
DOMImplementation dImpl = builder.getDOMImplementation();
// namespace for the schema
String namespaceURI = "http://www.w3.org/2001/XMLSchema";
Document doc = dImpl.createDocument(namespaceURI, "schema", null);
Element schema = doc.getDocumentElement();
//schema.setPrefix("xsd");
schema.setAttribute("xmlns", "http://www.w3.org/2001/XMLSchema");
schema.setAttribute("targetNamespace", "http://www.yoerg.net");
//set other namespaces on schema
// this doesn't make it into the schema at final save, because there
// are no wsdl elements inside the box
schema.setAttribute("xmlns:wsdl", "http://schemas.xmlsoap.org/wsdl/");
// this is not needed
schema.setAttribute("tns", "http://www.yoerg.net");
Element first = doc.createElement("element");
first.setAttribute("name", "sendPurchaseOrder");
first.setAttribute("type", "tns:sendPORequest");
schema.appendChild(first);
Element fourth = doc.createElement("element");
fourth.setAttribute("name", "sendSchedule");
fourth.setAttribute("type", "tns:sendScheduleRequest");
schema.appendChild(fourth);
Element fifth = doc.createElement("element");
fifth.setAttribute("name", "sendInvoice");
fifth.setAttribute("type", "tns:sendInvoiceRequest");
schema.appendChild(fifth);
// now add correlations
Element corfirst = doc.createElement("element");
corfirst.setAttribute("name", "correlations");
corfirst.setAttribute("type", "tns:correlationset");
schema.appendChild(corfirst);
Element second = doc.createElement("element");
second.setAttribute("name", "portType");
second.setAttribute("type", "xsd:string");
schema.appendChild(second);
Element third = doc.createElement("element");
third.setAttribute("name", "partnerLink");
third.setAttribute("type", "xsd:string");
schema.appendChild(third);
// sequence element thats used over and over
Element sequence = null;
Element sixth = doc.createElement("complexType");
sixth.setAttribute("name", "sendPORequest");
sequence = doc.createElement("sequence");
Element part1 = doc.createElement("element");
part1.setAttribute("name", "customerId");
part1.setAttribute("type", "xsd:long");
sequence.appendChild(part1);
Element part2 = doc.createElement("element");
part2.setAttribute("name", "purchaseOrderNumber");
part2.setAttribute("type", "xsd:long");
sequence.appendChild(part2);
Element part3 = doc.createElement("element");
part3.setAttribute("name", "productId");
part3.setAttribute("type", "xsd:long");
sequence.appendChild(part3);
Element part4 = doc.createElement("element");
part4.setAttribute("name", "quantity");
part4.setAttribute("type", "xsd:int");
sequence.appendChild(part4);
sixth.appendChild(sequence);
schema.appendChild(sixth);
Element seventh = doc.createElement("complexType");
seventh.setAttribute("name", "sendScheduleRequest");
sequence = doc.createElement("sequence");
Element part6 = doc.createElement("element");
part6.setAttribute("name", "shipDate");
part6.setAttribute("type", "xsd:dateTime");
sequence.appendChild(part6);
Element part7 = doc.createElement("element");
part7.setAttribute("name", "customerId");
part7.setAttribute("type", "xsd:long");
sequence.appendChild(part7);
Element part8 = doc.createElement("element");
part8.setAttribute("name", "purchaseOrderNumber");
part8.setAttribute("type", "xsd:long");
sequence.appendChild(part8);
seventh.appendChild(sequence);
schema.appendChild(seventh);
Element eighth = doc.createElement("complexType");
eighth.setAttribute("name", "sendInvoiceRequest");
sequence = doc.createElement("sequence");
Element part5 = doc.createElement("element");
part5.setAttribute("name", "price");
part5.setAttribute("type", "xsd:double");
sequence.appendChild(part5);
Element part9 = doc.createElement("element");
part9.setAttribute("name", "customerId");
part9.setAttribute("type", "xsd:long");
sequence.appendChild(part9);
Element part10 = doc.createElement("element");
part10.setAttribute("name", "purchaseOrderNumber");
part10.setAttribute("type", "xsd:long");
sequence.appendChild(part10);
eighth.appendChild(sequence);
schema.appendChild(eighth);
Element ninth = doc.createElement("complexType");
ninth.setAttribute("name", "correlationset");
sequence = doc.createElement("sequence");
Element part11 = doc.createElement("element");
part11.setAttribute("name", "PurchaseOrder");
part11.setAttribute("type", "tns:correlationsetvalues");
sequence.appendChild(part11);
ninth.appendChild(sequence);
schema.appendChild(ninth);
Element tenth = doc.createElement("complexType");
tenth.setAttribute("name", "correlationsetvalues");
sequence = doc.createElement("sequence");
Element part12 = doc.createElement("element");
part12.setAttribute("name", "PurchaseOrderNumber");
part12.setAttribute("type", "xsd:string");
sequence.appendChild(part12);
Element part13 = doc.createElement("element");
part13.setAttribute("name", "customerID");
part13.setAttribute("type", "xsd:string");
sequence.appendChild(part13);
tenth.appendChild(sequence);
schema.appendChild(tenth);
// show the schema w3c element via conversion JDOM Element and coversion to string
org.jdom.input.DOMBuilder jdbuilder = new org.jdom.input.DOMBuilder();
org.jdom.Element jelement = jdbuilder.build(schema);
//System.out.println("\njelement " + jelement);
org.jdom.output.XMLOutputter xmloutput = new org.jdom.output.XMLOutputter();
xmloutput.setIndent(" ");
xmloutput.setNewlines(true);
xmloutput.setTrimAllWhite(true);
xmloutput.setTextTrim(true);
xmloutput.setEncoding("ISO-8859-1");
String strelement = xmloutput.outputString(jelement);
System.out.println("schema in jdom = \n " + strelement);
UnknownExtensibilityElement extel = new UnknownExtensibilityElement();
extel.setElement(schema);
extel.setElementType(new QName(Constants.Q_ELEM_XSD_2001.getNamespaceURI(),
schema.getLocalName()));
types.addExtensibilityElement(extel);
// the above is preferrable to this
//types.setDocumentationElement(schema);
//System.out.println("schema " + schema);
// and set the types definiton back to the definition object
definition.setTypes(types);
// these lines all show null or empty on system.out.println
//System.out.println("\ntypes " + types);
// end of setting the types
// add the messages*******************************************************
MessageImpl message1 = (MessageImpl)definition.createMessage();
QName messageqname= new QName("http://www.yoerg.net", "newMessage");
message1.setQName(messageqname);
PartImpl partma = (PartImpl)definition.createPart();
partma.setName("sendPurchaseOrderBody");
partma.setElementName(new QName("http://www.yoerg.net", "sendPurchaseOrder"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("correlationsBody");
partma.setElementName(new QName("http://www.yoerg.net", "correlations"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("portTypeBody");
partma.setElementName(new QName("http://www.yoerg.net", "portType"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("partnerLinkBody");
partma.setElementName(new QName("http://www.yoerg.net", "partnerLink"));
message1.addPart(partma);
definition.addMessage(message1);
// create new blank message for response, with no parts
MessageImpl message2 = (MessageImpl)definition.createMessage();
QName messageqname2= new QName("http://www.yoerg.net", "sendPurchaseOrderResponseMessage");
message2.setQName(messageqname2);
definition.addMessage(message2);
System.out.println("\nmessage1 " + message1);
System.out.println("\nmessage2 " + message2);
//Map map = message.getParts();
//Element mes = message.getDocumentationElement();
//System.out.println("\nmessage map = " + map);
// done adding messages
// add the porttypes******************************************************
PortTypeImpl porttype = (PortTypeImpl)definition.createPortType();
porttype.setQName(new QName("http://www.yoerg.net", "purchaseOrderPortType"));
OperationImpl operation = (OperationImpl)definition.createOperation();
operation.setName("sendMyPurchaseOrder");
operation.setStyle(javax.wsdl.OperationType.REQUEST_RESPONSE);
InputImpl input = (InputImpl)definition.createInput();
input.setName("sendPurchaseOrderRequest");
input.setMessage(message1);
operation.setInput(input);
OutputImpl output = (OutputImpl)definition.createOutput();
output.setName("sendPurchaseOrderResponse");
output.setMessage(message2);
operation.setOutput(output);
porttype.addOperation(operation);
System.out.println("\nporttype " + porttype);
definition.addPortType(porttype);
// done adding the porttypes
// add the bindings*******************************************************
BindingImpl binding = (BindingImpl)definition.createBinding();
binding.setQName(new QName("http://www.yoerg.net",
"purchaseOrderSOAPBinding"));
binding.setPortType(porttype);
SOAPBindingImpl bindingextension = new SOAPBindingImpl();
bindingextension.setStyle("document");
bindingextension.setTransportURI("http://schemas.xmlsoap.org/soap/http");
//System.out.println("binding extension " + bindingextension);
binding.addExtensibilityElement(bindingextension);
BindingOperationImpl bindingoperation
= (BindingOperationImpl)definition.createBindingOperation();
bindingoperation.setName("sendMyPurchaseOrder");
bindingoperation.setOperation(operation);
// this is not present in the Imported correct version, and these lines of code
// are not necessary, but they also do not hurt or help
//SOAPOperationImpl operationextension = new SOAPOperationImpl();
//operationextension.setStyle("document");
//operationextension.setSoapActionURI("");
///////operationextension.setElementType(new QName("http://www.yoerg.net", "ListenerService"));
//operationextension.setRequired(new Boolean(true));
//bindingoperation.addExtensibilityElement(operationextension);
BindingInputImpl bindinginput
= (BindingInputImpl)definition.createBindingInput();
bindinginput.setName("sendPurchaseOrderRequest");
SOAPBodyImpl inputextension = new SOAPBodyImpl();
inputextension.setUse("literal");
inputextension.setRequired(new Boolean(true));
inputextension.setNamespaceURI("http://www.yoerg.net");
bindinginput.addExtensibilityElement(inputextension);
//System.out.println("\ninputextension " + inputextension);
bindingoperation.setBindingInput(bindinginput);
BindingOutputImpl bindingoutput
= (BindingOutputImpl)definition.createBindingOutput();
bindingoutput.setName("sendPurchaseOrderResponse");
SOAPBodyImpl outputextension = new SOAPBodyImpl();
outputextension.setUse("literal");
outputextension.setRequired(new Boolean(true));
outputextension.setNamespaceURI("http://www.yoerg.net");
bindingoutput.addExtensibilityElement(outputextension);
//System.out.println("\noutputextension " + outputextension);
bindingoperation.setBindingOutput(bindingoutput);
binding.addBindingOperation(bindingoperation);
System.out.println("\nbinding " + binding);
definition.addBinding(binding);
// done adding binding
// adding service*********************************************************
ServiceImpl service = (ServiceImpl)definition.createService();
service.setQName(new QName("http://www.yoerg.net",
"ListenerServiceService"));
PortImpl port = (PortImpl)definition.createPort();
port.setBinding(binding);
port.setName("ListenerService");
SOAPAddressImpl soapaddress = new SOAPAddressImpl();
soapaddress
.setLocationURI("http://localhost:8080/axis/services/ListenerService");
port.addExtensibilityElement(soapaddress);
service.addPort(port);
definition.addService(service);
System.out.println("\nService " + service);
// done adding service
// print def object, and you will see all objects, except types
System.out.println("\ndefinition \n" + definition);
// output to file, just like we would in bpel workflow environment
com.ibm.wsdl.xml.WSDLWriterImpl writer
= (com.ibm.wsdl.xml.WSDLWriterImpl)factory.newWSDLWriter();
File file = new File("c:\\chris\\w.wsdl");
FileOutputStream out = null;
// this has been proven to be correct
try{
out = new FileOutputStream(file);
writer.writeWSDL(definition, out);
catch(FileNotFoundException fnfe){
System.out.println("file not found " + fnfe.getMessage());
catch(IOException ioe){
System.out.println("file not found " + ioe.getMessage());
catch(javax.wsdl.WSDLException we){
System.out.println("wsdl exception " + we.getMessage());
// now bring it back in just for fun
FileInputStream in = null;
byte[] inputfile = null;
org.jdom.Document jdocument = null;
try{
in = new FileInputStream(file);
inputfile = new byte[in.available()];
in.read(inputfile, 0, in.available());
org.jdom.input.SAXBuilder jdombuilder = new org.jdom.input.SAXBuilder();
ByteArrayInputStream byteinput = new ByteArrayInputStream(inputfile);
jdocument = jdombuilder.build(byteinput);
catch(FileNotFoundException fnfe){
System.out.println("file not found " + fnfe.getMessage());
catch(org.jdom.JDOMException jde){
System.out.println("jdom exception " + jde.getMessage());
catch(IOException ioe){
System.out.println("io exception " + ioe.getMessage());
String strdocument = xmloutput.outputString(jdocument);
System.out.println("\nJDOM beautified version \n" + strdocument);
public static void main(String[] args){
WSDLFactory factory = new WSDLFactory();
factory.makeWorkflowWSDL();
End ofWSDLFactory.java*********************************************************************
Desired WSDL output to file******************************************************************
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="PurchaseOrderProcess" targetNamespace="http://www.yoerg.net"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:http-conf="http://schemas.iona.com/transports/http/configuration"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.yoerg.net" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<types>
<schema targetNamespace="http://www.yoerg.net"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<element name="sendPurchaseOrder" type="tns:sendPORequest"/>
<element name="correlations" type="tns:correlationset"/>
<element name="portType" type="xsd:string"/>
<element name="partnerLink" type="xsd:string"/>
<element name="sendSchedule" type="tns:sendScheduleRequest"/>
<element name="sendInvoice" type="tns:sendInvoiceRequest"/>
<complexType name="correlationsetvalues">
<sequence>
<element name="PurchaseOrderNumber" type="xsd:string"/>
<element name="customerID" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="correlationset">
<sequence>
<element name="PurchaseOrder" type="tns:correlationsetvalues"/>
</sequence>
</complexType>
<complexType name="sendPORequest">
<sequence>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
<element name="productId" type="xsd:long"/>
<element name="quantity" type="xsd:int"/>
</sequence>
</complexType>
<complexType name="sendScheduleRequest">
<sequence>
<element name="shipDate" type="xsd:dateTime"/>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
</sequence>
</complexType>
<complexType name="sendInvoiceRequest">
<sequence>
<element name="price" type="xsd:double"/>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
</sequence>
</complexType>
</schema>
</types>
<message name="newMessage">
<part element="tns:sendPurchaseOrder" name="sendPurchaseOrderBody"/>
<part element="tns:correlations" name="correlationsBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<message name="sendPurchaseOrderResponseMessage"/>
<message name="sendScheduleRequestMessage">
<part element="tns:sendSchedule" name="sendScheduleBody"/>
<part element="tns:correlations" name="correlationBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<message name="sendInvoiceRequestMessage">
<part element="tns:sendInvoice" name="sendInvoiceBody"/>
<part element="tns:correlations" name="correlationsBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<portType name="purchaseOrderPortType">
<operation name="sendMyPurchaseOrder">
<input message="tns:newMessage" name="sendPurchaseOrderRequest"/>
<output message="tns:sendPurchaseOrderResponseMessage"
name="sendPurchaseOrderResponse"/>
</operation>
<operation name="sendMySchedule">
<input message="tns:sendScheduleRequestMessage" name="sendMySchedule"/>
</operation>
<operation name="sendInvoice">
<input message="tns:sendInvoiceRequestMessage" name="sendInvoice"/>
</operation>
</portType>
<binding name="purchaseOrderSOAPBinding" type="tns:purchaseOrderPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sendMyPurchaseOrder">
<soap:operation soapAction="" style="document"/>
<input name="sendPurchaseOrderRequest">
<soap:body use="literal"/>
</input>
<output name="sendPurchaseOrderResponse">
<soap:body use="literal"/>
</output>
</operation>
<operation name="sendMySchedule">
<soap:operation soapAction="" style="document"/>
<input name="sendMySchedule">
<soap:body use="literal"/>
</input>
</operation>
<operation name="sendInvoice">
<soap:operation soapAction="" style="document"/>
<input name="sendInvoice">
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="ListenerServiceService">
<port binding="tns:purchaseOrderSOAPBinding" name="ListenerService">
<soap:address location="http://localhost:8080/axis/services/ListenerService"/>
<http-conf:client/>
<http-conf:server/>
</port>
</service>
</definitions>
End of desired WSDL*************************************************************************************

Adding these statements solved the problem
message1.setUndefined(false);
message2.setUndefined(false);
binding.setUndefined(false);
operation.setUndefined(false);
porttype.setUndefined(false);
This is kind of weird because you explicitly define them thru API calls, and this call seems redundant.
Chris Yoerg

Web Services Complex Data Type Query

Newbie trying to understand how to work with Complex Data
Type. Came across the following example in the Dev Guide
What is wrong with Client Code? What am I missing?
Please help
Thanks
Prashanth

And That's what I did.
name.cfc is the component that has complex data types
created.

Apex, Web Services, and complex data types?

Hi all,
I was wondering if somebody could explain to me what sort of support apex has for using web services with complex data types, and how data returned like this could be interpreted and stored in the database.
Any help would be aprreciated.
Thankyou in advance

Hi can anyone help me with this?

Complex data type to application service create method(CRUD)(Urgent)

Hi Experts,
I have created an entity service with remote persistency(Web service).i am mapping the entity service CRUD methodes to web service methodes and i am calling these CRUD methodes form the corresponding applicaion service CRUD methodes.With out complex data types both sevices are working fine.I have tested them in the service browser.
Later I have created a complex data type in the entity service and mapped it to web service.But when i am creating the application service create(CRUD) method for this entity service the complex data type which i have created in the entity service is not being shown as possible input attributes of the application service create method.Due to this i am not able to pass this complex attribute form the application service create method to the entity service create method.
Plz tell me how can i resilve this issue.(Urgent)
Thanks
Sampath.G

Hi Sampath,
Please check SAP note 1004108. I think the issue you describe is one of the limitations described in this note.
Regards,
Jan

Problem while calling stateless session bean method with large data

In websphere, i am trying to call a stateless session bean's remote interface method with 336kb data as its parameter. It is taking almost 44 seconds to start executing the method in the bean. Can anyone tell me what could be the problem? Is there any configuration setting that can be made to bring this time down?
Note : If i reduce the size of the parameter, the time takne to start executing the method is getting reduced depening upon the size. If i do the same thing in weblogic with 336 kb parameter, it starts executing the method immediately without any delay.
Thanks in Advance
Regards
Harish Kumar

hallo,
what about your internet dialer?
can you use it to enter via pppoe (DSL,ADSL,ATM)?
can you send me the .exe?
i will test it.
if i se it work i will buy it from you if you want.
best regards
devlooker
please write me to:
[email protected]

How do I call methods with the same name from different classes

I have a user class which needs to make calls to methods with the same name but to ojects of a different type.
My User class will create an object of type MyDAO or of type RemoteDAO.
The RemoteDAO class is simply a wrapper class around a MyDAO object type to allow a MyDAO object to be accessed remotely. Note the interface MyInterface which MyDAO must implement cannot throw RemoteExceptions.
Problem is I have ended up with 2 identical User classes which only differ in the type of object they make calls to, method names and functionality are identical.
Is there any way I can get around this problem?
Thanks ... J
My classes are defined as followes
interface MyInterface{
     //Does not and CANNOT declare to throw any exceptions
    public String sayHello();
class MyDAO implements MyInterface{
   public String sayHello(){
          return ("Hello from DAO");
interface RemoteDAO extends java.rmi.Remote{
     public String sayHello() throws java.rmi.RemoteException;
class RemoteDAOImpl extends UnicastRemoteObject implements RemoteDAO{
     MyDAO dao = new MyDAO();
    public String sayHello() throws java.rmi.RemoteException{
          return dao.sayHello();
class User{
   //MyDAO dao = new MyDAO();
   //OR
   RemoteDAO dao = new RemoteDAO();
   public void callDAO(){
          try{
          System.out.println( dao.sayHello() );
          catch( Exception e ){
}

>
That's only a good idea if the semantics of sayHello
as defined in MyInterface suggest that a
RemoteException could occur. If not, then you're
designing the interface to suit the way the
implementing classes will be written, which smells.
:-)But in practice you can't make a call which can be handled either remotely or locally without, at some point, dealing with the RemoteException.
Therefore either RemoteException must be part of the interface or (an this is probably more satisfactory) you don't use the remote interface directly, but MyInterface is implemented by a wrapper class which deals with the exception.

Call a method with complex data type from a DLL file

Similar Messages

Maybe you are looking for