Generate ws client for horde rpc using netbeans

Hallo developers,
I'd like to access my horde using webservices rcp (http://netvor.sk/horde/rpc.php?wsdl). I am new to ws so i rely on netbeans to generate client for me. Unfortunately it failed :-(
Among other, wsdl describes messages of type xsd:resource and xsd:object (xsd is http://www.w3.org/2001/XMLSchema) like:<message name="mail.getStreamResponse">
<part name="output" type="xsd:resource" />
</message>as a result wscompile dies because resource is not defined in XMLSchema dtd. like: invalid entity name: "resource" (in namespace: "http://www.w3.org/2001/XMLSchema")
I have jdk6 with bundled ws support and nb5.5. with JAX_RCP 1.6 library.
How do I use these message of (custom?) type? Best using some wsimport/wscompe 'options' or maybe fallback to older java version -- I don't have time to 'play' with this (it's not my primary goal) so writing any code is ... aldo i fear that this is some sort of advanced topic and i'll have to study ws more that i'd like to :-)
~~
Adam

If this is not an rpc/encoded WSDL, you should try to use JAX-WS as it supports 100% of schema and is much better than JAX-WS. Check out http://jax-ws.dev.java.net for more information on JAX-WS. Best of all, JAX-WS is part of JDK 6.

Similar Messages

Generate clients for multiple WSLDs using 'clientgen' task.

Issue -
I am trying to generate WS clients for multiple Services(WSDLs). I am using 'clientgen' task. But a 'clientgen'task accepts only one WSDL. If I have more one that one 'clientgen' task, some of the
common classes (generated) are overwritten.
For eg.
WSDL for Contract 1
<s:element name="executeResponse">
<s:complexType>
<s:sequence>
<s:element ref="soa:CancelOrderResponse"/>
</s:sequence>
</s:complexType>
</s:element>
<message name="executeSoapOut">
<part name="parameters" element="s0:executeResponse"/>
</message>
<portType name="CancelOrderSoap">
<operation name="execute">
<input message="s0:executeSoapIn"/>
<output message="s0:executeSoapOut"/>
</operation>
</portType>
<service name="CancelOrder">
<port name="CancelOrderSoap" binding="s0:CancelOrderSoap">
<soap:address location="http://localhost:7001/CoreWSProject/sync/CancelOrder.jws"/>
</port>
</service>
WSDL for Contract 2
<s:element name="executeResponse">
<s:complexType>
<s:sequence>
<s:element ref="soa:CancelOrderResponse"/>
</s:sequence>
</s:complexType>
</s:element>
<message name="executeSoapOut">
<part name="parameters" element="s0:executeResponse"/>
</message>
<portType name="CancelOrderSoap">
<operation name="execute">
<input message="s0:executeSoapIn"/>
<output message="s0:executeSoapOut"/>
</operation>
</portType>
<service name="CancelOrder">
<port name="CancelOrderSoap" binding="s0:CancelOrderSoap">
<soap:address location="http://localhost:7001/CoreWSProject/sync/CancelOrder.jws"/>
</port>
</service>
GENERATED CODE
A class ExecuteResponse will be generated for each service. This class gets overwritten if you use
multiple 'clientgen' tasks.
Question
Is there way to specify multiple WSDLs in 'clientgen' task so that i should be able to package
all the clientcode in one jar without any namespace issues ?
- Sandeep V

If the classes have the same namespace, by default, the same Java package name will be created. There is a packageName attribute on the clientgen Ant task, which provides some control over the Java package name that is used.
There is no way to specify multiple WSDLs to the clientgen Ant task. This makes sense if you subscribe to the notion that a WSDL represents a Web Service. It sounds like you can achieve what you want by:
1. Running clientgen on the first WSDL,
2. Use Ant to extract the contents of the generated JAR into a directory (with a name like clientgen),
3. Running clientgen on the next WSDL,
4. Use Ant to extract the contents of the generated JAR into the same clientgen directory,
5. etc, etc.
Afterwards, you would just need to use Ant to JAR up the clientgen directory. Again, you'll want to specify a different packageName attribute for each WSDL.
HTH,
Mike Wooten

Create web service client for javafx project in netbeans 6.8

I here have a javafx project and need to create a web service client for it (in netbeans 6.8).
However when I right click this project -> new -> web service client -> input wsdl location\package -> finish, it seems that the client code is never generated. This is quite different from what happens when creating web service client for a java project.
Anyone knows how is this happening?

Thanks for your reply.
I did write my own ws client code but I need to create a web proxy based on an appointed wsdl path. That requires me to create a web service client from netbeans 6.8, like what I described in my first post. Unfortunately, it's not behaving like what I imagined it should do for a java project, even the javafx file itself doesn't have any error. The error occurs in package definition line.
package fx;For the definition above, it cannot access java.lang.builtins.
The question now is about the possibility to include javafx file in an non-javafx, say, java project. Any comments?
---Regards.

Plsql client for twitter api (using oauth)

Hi,
I am probably being a bit optimistic, but does anybody have a plsql client for twitter that will allow me to post status updates from oracle? I found this http://somecodinghero.blogspot.com/2010/09/updating-twitter-from-database-using.html, but it doesn't work, simply giving me 401 Unauthorized whenver I try.
Make my day? Please?
Thanks
Ralph

So.... Are you ready? Let's go.....
Twitter Part:
1. Acess https://dev.twitter.com
2. Login
3. Create New Application
4. Fill out the data requested by twitter(and create application).
5. Click button "Create my acess token".
6. Copy Consumer key     ,Consumer secret     ,Access token     ,Access token secret     to Notepad++(or elsewhere).
7. Click the Tab Settings, and change Application Type to "Read, Write and Access direct messages". click the "Update..."
After installing DB and verified that you have Java 1.5 in your local machine and downloaded twitter4j jar.
1. Open Jdeveloper(i'm working with 11.1.2.1.0)
2. Create a new Application. Create a java Class with:
package client;
import twitter4j.*;
import twitter4j.conf.ConfigurationBuilder;
public class TweetMeMan {
    public static String sendTweet(String msg, String sOAuthConsumerKey, String sOAuthConsumerSecret, String sOAuthAccessToken, String sOAuthAccessTokenSecret ) {
        String result = "Ok";
        try {
            ConfigurationBuilder cb = new ConfigurationBuilder();
            cb.setOAuthConsumerKey(sOAuthConsumerKey);
            cb.setOAuthConsumerSecret(sOAuthConsumerSecret);
            cb.setOAuthAccessToken(sOAuthAccessToken);
            cb.setOAuthAccessTokenSecret(sOAuthAccessTokenSecret);
            TwitterFactory tf = new TwitterFactory(cb.build());
            Twitter twitter = tf.getInstance();
            Status status = twitter.updateStatus(msg);
            System.out.println("Successfully updated the status to [" + status.getText() + "].");
        } catch (Exception e) {
            System.out.println("Error : " + e.getMessage());
            result = e.getMessage();
        return result;
}3. Click Project Settings and in Libraries add twitter4j(version).jar
4. Compile project. No errors? Nice.... Errors? Check the log and fix them ;)
5. Create a New Deployment Profile
5.1. Profle Type : Jar File
5.2 Deployment Profile Name : vrodriguestweet (in my case)
6. Deploy the vrodriguestweet (it will save de jar file in deploy folder)
7. Open command line (cmd.exe)
8. Write
loadjava -r -f -o -user vrodrigues/yourpaswword@YourDB your_location_of_the_jar_created_above\vrodriguestweet.jar9. Open Sqldeveloper(or sqlplus) and check if there is under Java this name exists : client/TweetMeMan
9.1 client is the java package i created the java file.
10. Now let's create the function:
CREATE FUNCTION letsTweetVR (p_message varchar2, p_OAuthConsumerKey varchar2, p_OAuthConsumerSecret varchar2, p_OAuthAccessToken varchar2, p_OAuthAccessTokenSecret varchar2 )
   RETURN VARCHAR2
   AS LANGUAGE JAVA
   NAME 'client/TweetMeMan.sendTweet
     (java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String) return java.lang.String';   10.1. No errors? Amazing....keep going you are almost there...
11. Let's tweet:
BEGIN
DBMS_OUTPUT.PUT_LINE(letsTweetVR('Tweeting from database...Awesome, right?',
                                          'your_OAuthConsumerKey',
                                         ' your_OAuthConsumerSecret',
                                         'your_OAuthAccessToken',
                                        'your_OAuthAccessTokenSecret')
END;Of course you can do this inside a package or passing the values from some interface.... And you can also do other things that twitter4j does... Like Search for Tweets and so on and so on. ;)
Did someone like this? Or i'm an idiot? : D
All credits goes to the developer of twitter4j....
P.S Remember that this is my first usage of java in DB...so if you can do better, please advise ;)
P.S.1. I will blog this with entire full steps.... just trying to get the time for it :/
https://lh6.googleusercontent.com/-ktXgF_N5rQU/Tz0hx8cEbgI/AAAAAAAAA-s/LOoTf_5pnd0/s864/twiiter.png
Edited by: Vitor Rodrigues on 16/Fev/2012 15:46

Weblogic clientgen task generates soap11 client for soap12 wsdl

I am creating a client using the clientgen task on a wsdl that is based on the soap1.2 spec.
When the client invokes the service , the client code throws an exception complaining that the content type is wrong. The client code is using the content type text/xml to communicate with the service however the service is expecting application/soap+xml for communication.
I realise from the specs that text/xml is used by the soap1.1 spec. Is there any additional setting on the client gen task to make it generate a 1.2 client?
The webservice is deployed on weblogic9.2 and the client code is generated using the clientgen task found in 9.2 version of weblogic.

Hi thanks for your reply.
I was using weblogic9.2 when I ran into this issue. Our webapplications run on weblogic9.2.
Subsequently I tried to build the client using the weblogic jar found in the Aqualogic service bus tier which is on weblogic9.2 M2 and the client is able to connect successfully. I guess some fix has been put by weblogic?
When I looked around I could not find any documentation regarding this issue.
Is there a fix for this issue on weblogic9.2 or any relevant documentation highlighting this issue?
Edited by [email protected] at 11/30/2007 5:45 PM

Problem with DII client for Doc/Literal with non built-in type in WL8.1 Sp2

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Need help writing client for WSE 1.0 Web Service

Hello all,
I am attempting to write Java clients against a .Net service that uses WSE 1.0. I can't seem to get any of toolkits I have tried to work with this service. Unfounately, I do not own the service, so I cannot upgrade it to WSE 2.0. The problem seems to be that the WSE 1.0 expects namespaces from the July 2002 version of WS-Security, while all the libraries I have tried (JWSDP, Oracle Web Service Wizard, etc) use the oasis namepsace from January 2004.
Can he one suggest an alternative? Is there a way to set the namespace sent in XWS-Security? I think this might solve the problem...
Thanks,
KS

Hi,
firstly JWSDP 1.5 is pretty old, the latest release of JWSDP is JWSDP 2.0 that happened late last year.
The problem is most likely happening due to a bug in JWSDP 1.5. If you dump the Message that is going over the wire you will probably see
SOAPAction : ""
SOAPAction : "<the correct action value>"
And this is the reason for the failure. I believe you are using SOAP 1.1 messages right ?
What you will need to do is upgrade to
JWSDP 2.0 and more important also upgrade your SAAJ jars in the JWSDP installation to SAAJ 1.3
https://saaj.dev.java.net/files/documents/52/32730/saaj1.3.zip
Alternatively, you can use Sun's Project Tango (Sun's Next Generation WebServices Interoperability Technology Offering) which has been tested to interoperate with Microsoft WCF.
http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/
You can download Project Tango by visiting the following page :
https://wsit.dev.java.net/
Look at the Try It section for instructions on how to use it.
Using the Netbeans Plugin you can develop a java client which can securely communicate with the .Net WebService. All you need to do for that is use Netbeans to create a Java WebService Client by pointing it to the WSDL of the .Net Service.
Let us know if this helped.
Thanks...
Message was edited by:
kumar_at_sun

Java client for WCF STS service without netbeans etc.?

I want to communicate with a WCF service that uses an STS. I want to know what I am doing, so I don't want to use netbeans. If I have to use netbeans to figure it out for myself, can you help me interpret this part of the documentation for metro:
https://metro.java.net/guide/ch12.html#gghnt
How do I retrieve the certificate from the .NET service to use if I follow the instructions?
Or, other suggestions would be helpful.
Thanks

I'm a bit confused why you're using an Applet to do this as it will require you to serve the Applet from the same server as where the .Net web service lives.
If I was doing it I'd take advantage of the web service capabilities built into Java 6 (the only supported version from Sun). The wsimport tool would be able to reverse engineer the WSDL from the .net web service and generate client side classes for you.

JAX-RPC Client for VB-SoapToolkit3.0 WebService

I need to develop a JAX-RPC client for a VB6.0 WebService (the WebService being generated through MS SoapToolkit3.0).
I'm using JWSDP 1.0_01. The WSDL that the JWSDP is using to generate the stubs is the one generated by the MS SoapToolkit. My WebService
has only one method (Public Test(xpto As String)As String) that receives and returns a string.
So what's the problem:
- JAX-RPC client sends a SOAP packet different than what the WebService expects, especially in the namespaces. JAX-RPC generates some strange namespaces, like xmlns:ns0="xpto" (xpto is the name of the argument of the WebService) or xmlns:ns1="Result xpto"
- Looking at the JAX-RPC generated WebService interface, I see that instead of String, the method test receives a StringHolder (???). What's a string holder, and why isn't a String?
The resumed message returned by the WebService:
<mserror:description>WSDLReader:None of the matching operations for soapAction http://tempuri.org/Test/action/WS.Test could successfully load the incoming request. Potential typemapper problem HRESULT=0x80070057: The parameter is incorrect.
- Server:One of the parameters supplied is invalid. HRESULT=0x80070057: The parameter is incorrect.
</mserror:description>
Any help would be apreciated.
Thanks

Can you send the WSDL that you used to generate the JAXRPC client?
Thanks

Using JarSettings to generate EJB client jar, but supported classes missed

Appreciated for any comments in advance.
I am using @jarSetting to generate EJB client jar file from workshop 9.2. The remote method of EJB has one input parameter that is defined as an interface. The interface is included in client jar, but the implementation of this interface is not.
Please advise how I can add the implementation of this interface to client jar?
Best Regards,
James

Hi James,
I believe the algorithm for creating the client jar is to simply inspect the EJB interfaces using reflection and to include all user defined classes and exceptions that are referenced by the interfaces. In your case, it sounds like a class is not being included because it is not directly referenced by one of the EJB interfaces.
I think the client jar creation algorithm can be described as "best effort" and unfortunately, it does not always end up including all classes needed by the client. I would recommend you add the additional classes manually using the jar tool.
- Matt

How to change the web service address of NetBeans generated WS client

I am currently experimenting with web services using netbeans and Sun Application Server.
Basically I am creating simple web services using net beans and then deploy them on the app server and then create another pfoject with web service reference to that web service to invoke the service.
My problem is when a project is deliverd to the production site the the client applications web service reference will need to be configured to refer to the production web service address. But when I looked at the generated web service client code the address is hard coded.
How can I change the address to the web service of a web service reference created in net beans either using some configuration file (without having to recompile the client) or at runtime.
Thanks in advance

bump...

JAX-WS -- Force a wsimport generated ws client to use http POST method

I've used wsimport to generate a JAX-WS client for a wsdl and xsd bindings that were provided to me.
The basic implementation goes something like this.
URL serviceUrl = ...url to the live web service's wsdl (this will change often and needs to be data driven)
QName qname = new QName("thenamespace", "MyService")
MyService myService = new MyService(serviceUrl, qname);
At this point a http GET request is sent to the server which promptly spits back a "405: method not allowed" because it is only configured to accept the http POST method.
Unfortunately i cannot change this behavior and need a way to get the web service client to generate http POST requests.
Setting the following seemed to have no effect.
System.setProperty("javax.xml.ws.http.request.method", "POST");
Thanks!

so, keep the wsdl as a local resource and use a url for the local resource. then the service will not request the remote wsdl.

Generate standalone java client for weblogic (11g) webservice

Hi All,
I am a newbie to web logic family. I am using web logic 11g server and deployed JAX-WS web service on it using the documentation given for the same. I have created one complex object to return some data from the server as web service. I am able to build, deploy and run the web service using ant task on same machine.
But I need to deploy client classes on another machine and call web service from machine other than I am using for creating and deploying web service. Can you please tell me how can I achieve this ? Which jar files are needed to run a web service client generated through ant task and how can I create web service client differently using Eclipse IDE?
I have generated Client classes as jar using eclipse OEPE but I dont have any idea how can I use it because it changes the package name and class names also :(
Please help me out any hint would be greatly appreciated. :)

Hi All,
I have found all the answers regarding my query from the link below :
[Overview of Web Services Invocation|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv/client.html#wp229351]
May be this would be helpful to the newbie who is just like me :) yippy :)

Generate dbsequnce for a table using a bean

Is it possible to generate the next dbsequence for a table using bean?
Thanks

If you are only interested in the number in the bean, you should implement a service method in out application module, expose it to the client interface and call this via the binding layer.
public oracle.jbo.domain.Number getSequenceNumber()   {
        try    {
            String seq = "YOUR_DB_SEQUENCE_SEQ";
            oracle.jbo.server.SequenceImpl empSeq =
                new oracle.jbo.server.SequenceImpl(seq, getDBTransaction());
            oracle.jbo.domain.Number zSerienNrSeq = empSeq.getSequenceNumber();
            return zSerienNrSeq ;
        catch (Exception e)        {
            e.printStackTrace();
        return null;
}Timo

How to generate client for GetFile service of Webcenter Content Management.

How to generate client for GetFile service of Webcenter Content Management.
Downloaded file : GetFile.wsdl
<?xml version="1.0" encoding="utf-8" ?>
- <definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.stellent.com/GetFile/" targetNamespace="http://www.stellent.com/GetFile/" xmlns="http://schemas.xmlsoap.org/wsdl/">
- <types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.stellent.com/GetFile/">
- <s:element name="GetFileByID">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="dID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="rendition" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="extraProps" type="s0:IdcPropertyList" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="GetFileByIDResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetFileByIDResult" type="s0:GetFileByIDResult" />
</s:sequence>
</s:complexType>
</s:element>
- <s:complexType name="GetFileByIDResult">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="FileInfo" type="s0:FileInfo" />
<s:element minOccurs="0" maxOccurs="1" name="downloadFile" type="s0:IdcFile" />
<s:element minOccurs="0" maxOccurs="1" name="StatusInfo" type="s0:StatusInfo" />
</s:sequence>
</s:complexType>
- <s:element name="GetFileByName">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="dDocName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="revisionSelectionMethod" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="rendition" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="extraProps" type="s0:IdcPropertyList" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="GetFileByNameResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetFileByNameResult" type="s0:GetFileByNameResult" />
</s:sequence>
</s:complexType>
</s:element>
- <s:complexType name="GetFileByNameResult">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="FileInfo" type="s0:FileInfo" />
<s:element minOccurs="0" maxOccurs="1" name="downloadFile" type="s0:IdcFile" />
<s:element minOccurs="0" maxOccurs="1" name="StatusInfo" type="s0:StatusInfo" />
</s:sequence>
</s:complexType>
- <s:complexType name="FileInfo">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="dDocName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dDocTitle" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dDocType" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dDocAuthor" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dSecurityGroup" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dDocAccount" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="dRevClassID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="dRevisionID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="dRevLabel" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dIsCheckedOut" type="s:boolean" />
<s:element minOccurs="0" maxOccurs="1" name="dCheckoutUser" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dCreateDate" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dInDate" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dOutDate" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dStatus" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dReleaseState" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dFlag1" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dWebExtension" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dProcessingState" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dMessage" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dReleaseDate" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dRendition1" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dRendition2" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dIndexerState" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dPublishType" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dPublishState" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dDocID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="dIsPrimary" type="s:boolean" />
<s:element minOccurs="0" maxOccurs="1" name="dIsWebFormat" type="s:boolean" />
<s:element minOccurs="0" maxOccurs="1" name="dLocation" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dOriginalName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dFormat" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dExtension" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dFileSize" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="CustomDocMetaData" type="s0:IdcPropertyList" />
</s:sequence>
</s:complexType>
- <s:complexType name="StatusInfo">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="statusCode" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="statusMessage" type="s:string" />
</s:sequence>
</s:complexType>
- <s:complexType name="IdcPropertyList">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="property" type="s0:IdcProperty" />
</s:sequence>
</s:complexType>
- <s:complexType name="IdcProperty">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="name" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="value" type="s:string" />
</s:sequence>
</s:complexType>
- <s:complexType name="IdcFile">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="fileName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="fileContent" type="s:base64Binary" />
</s:sequence>
</s:complexType>
</s:schema>
</types>
- <message name="GetFileByIDSoapIn">
<part name="parameters" element="s0:GetFileByID" />
</message>
- <message name="GetFileByIDSoapOut">
<part name="parameters" element="s0:GetFileByIDResponse" />
</message>
- <message name="GetFileByNameSoapIn">
<part name="parameters" element="s0:GetFileByName" />
</message>
- <message name="GetFileByNameSoapOut">
<part name="parameters" element="s0:GetFileByNameResponse" />
</message>
- <portType name="GetFileSoap">
- <operation name="GetFileByID">
<input message="s0:GetFileByIDSoapIn" />
<output message="s0:GetFileByIDSoapOut" />
</operation>
- <operation name="GetFileByName">
<input message="s0:GetFileByNameSoapIn" />
<output message="s0:GetFileByNameSoapOut" />
</operation>
</portType>
- <binding name="GetFileSoap" type="s0:GetFileSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <operation name="GetFileByID">
<soap:operation soapAction="http://www.stellent.com/GetFile/" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
- <operation name="GetFileByName">
<soap:operation soapAction="http://www.stellent.com/GetFile/" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="GetFile">
- <port name="GetFileSoap" binding="s0:GetFileSoap">
<soap:address location="http://localhost:7101/_dav/cs/idcplg" />
</port>
</service>
</definitions>

Hi,
I would suggest you to check the time recording functionality, see
details in:
http://help.sap.com/saphelp_sm70ehp1_sp26/helpdata/en/d5/299631364d4e959
c6609ca3bc24740/content.htm
Another possibility is configuring the Service Level Agreement, see
details in SDN blog:
Service Desk: SLA configuration hints
https://weblogs.sdn.sap.com/pub/wlg/24813
or
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24813
Thanks
Regards,
Vikram

Generate ws client for horde rpc using netbeans

Similar Messages

Maybe you are looking for