Proxy class sometimes generate bean class by webmethod name

Hi,
I have designed a wrapper for my proxy classes for our project Web logic integration into Siebel
I found that during generation of proxy classes, the generated proxy class contain a bean class which is named same as the exposed web service method name, which I use to get the parameter name of method thru reflection from this generated bean class. But sometimes it doesn't generate this bean class at all, i don't know the reason why it does so.
Can any one let me know why this happens so,or is there any way that i can get this bean class in the name of exposed web service method name get generated always.
Also I want to know how to keep generated the webparam annotation for the for the exposed webemethods> Is that controlled by the web service provider?
Thanks
Krishnakumar (Siebel Core - Web logic integration)
[email protected]

It depends on the service style used by the WSDL, the class wrapping the webservice operation is generated only for document literal wrapper style.

Similar Messages

Best Practice for WSDL Generate Proxy Class for Web Service with Two Versions

Dear All
Thank you in advance for you help.
I would like to generate proxy classes for same function but with two versions.
Old version web service (v23.2) is used for stable modules in a project which is not going to modify.
However, enhancement is added in new version web service (v24) and is going to use in any future modules.
For example,
wsdl.exe -o="TestProxy.cs" -l:CS -n:Test -sharetypes https://community.workday.com/custom/developer/API/Notification/v23.2/Notification.wsdl https://community.workday.com/custom/developer/API/Notification/v24.0/Notification.wsdl
It generates similar classes with an '1' added at the end of the class name.
ublic partial class Event_TargetObjectType {
private Event_TargetObjectIDType[] idField;
public partial class Event_TargetObjectType1 {
private Event_TargetObjectIDType1[] idField; ...}
Since the function inside some class is the same, is it possible for WSDL.exe to generate proxy classes automatically that if the class is the same, then generate one class only (sameFunction()) but if it detects the class is different, then add '1'
to the end of class name (differentFunction() and differentFunction1())
i.e.
public class sameFunction()
public class differentFunction()
private int a;}
public class differentFunction1()
{ private int b;
Best Regards
mintssoul

Hi mintssoul,
As per this case, I have shared corresponding details below :
1.As far as I know, WCF doesn’t support method overloading directly
2.Because WSDL doesn’t support method overloading (not OOPs).
3.WCF generates WSDL which specifies the location of the service and the operation or methods the service exposes.
4.WCF use Document/Literal WSDL Style : Microsoft proposed this standard where the soap body element will contain the web method name.
5.By default all the WCF services conform to the document literal standard where the soap body should include the method name.
6.but you can differ the method in the same manually by using Name attribute like below
For example:
    [OperationContract(Name="Integers")]
    int Display(int a,int b)
    [OperationContract(Name="Doubles")]
double Display(double a,double b)
7. Or I suggest you that can use svcutil to map multiple namespaces for generating wcf service proxies .
    for more information about this, refer here :
http://stackoverflow.com/questions/1103686/use-svcutil-to-map-multiple-namespaces-for-generating-wcf-service-proxies

Proxy Classes generated by NWDS 7.1 CE

Dear Experts,
When i try to generate a proxy classes (using NWDS 7.1 CE) for the WSDL file given by PI team,
my generated classes have service.getHTTP_PORT() instead of service.getMyOperationPort().
by this, please let me know, if my proxy classes are generated correctly, if not what should i do to generate them correctly.
Thanks in Advance
Hari Krishna. D

HI,
You are not able to see all those options becuase the NWDs might be not installed completely.
Open NWDS & Goto Help --> software updates, it will update the NWDS from SAP market place and then you may be able to see all those options.
Thanks
Swarup

Can't create client proxy classes from WebLogic-generated WSDL file

We have a web service that we used to generated a WSDL file. We then used clientgen
to try and create the client proxy classes from the WSDL. This failed. Doesn't
it seem reasonable that if WebLogic creates a WSDL that WebLogic should also be
able to consume that WSDL?

Can you please post the wsdl?
Regards,
-manoj
http://manojc.com
"Robert" <[email protected]> wrote in message
news:40db0bc0@mktnews1...
>
We have a web service that we used to generated a WSDL file. We then usedclientgen
to try and create the client proxy classes from the WSDL. This failed.Doesn't
it seem reasonable that if WebLogic creates a WSDL that WebLogic shouldalso be
able to consume that WSDL?

Problem generating proxy class

hi,
i am using Axis to generate java proxy classes from wsdl as follow
D:\Axis>java -cp .;d:\axis\lib\wsdl4j-1.5.1.jar;d:\axis\lib\saaj.jar;d:\axis\lib
\jaxrpc.jar;d:\axis\lib\axis-ant.jar;d:\axis\lib\log4j-1.2.8.jar;d:\axis\lib\com
mons-discovery-0.2.jar;d:\axis\lib\commons-logging-1.0.4.jar;d:\axis\lib\axis.ja
r;d:\axis\lib\activation.jar;d:\axis\lib\mailapi.jar org.apache.axis.wsdl.WSDL2J
ava -N"urn:crmondemand/ws/ecbs/opportunity/10/2004"="crmondemand.ws.ecbs.opportu
nity.10.2004"
- Unable to find required classes (javax.activation.DataHandler and javax.mail.i
nternet.MimeMultipart). Attachment support is disabled.
Exception in thread "main" java.lang.NoClassDefFoundError: org/xml/sax/helpers/D
efaultHandler
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
no. of other such error
at org.apache.axis.wsdl.toJava.Emitter.<init>(Emitter.java:144)
at org.apache.axis.wsdl.WSDL2Java.createParser(WSDL2Java.java:209)
at org.apache.axis.wsdl.gen.WSDL2.<init>(WSDL2.java:96)
at org.apache.axis.wsdl.WSDL2Java.<init>(WSDL2Java.java:194)
at org.apache.axis.wsdl.WSDL2Java.main(WSDL2Java.java:371)
D:\Axis>-N"urn:/crmondemand/xml/Opportunity/Data"="crmondemand.xml.opportunity.D
ata"
The filename, directory name, or volume label syntax is incorrect.
D:\Axis>-N"urn:/crmondemand/xml/Opportunity/Query"=crmondemand.xml.opportunity.Q
uery Opportunity.wsdl
The filename, directory name, or volume label syntax is incorrect.
i have all the classes but still getting error...please help ....searching over net i found wsdl2java require url of web service... i downloaded wsdl file from CRM OD admin....

Hi, you need to add activation.jar and mail.jar to your project, classpath settings.
Regards
SL

Unable to Generating a proxy class for the Enterprise Service

Hi ,
I am trying to consuming an SAP XI Web
Service in Visual Studio 2005. I followd this document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3057b5a7-99d0-2910-8f8f-f357dc4b70b5">Consume ES Workplace Enterprise Services with Microsoft .Net 2.0 and Visual Studio .Net 2005:</a>.
While try to create a Proxy Class for the WSDL file(XI) using wsdl.exe tool it shows the error like this "There is an error in XML document -Value cannot be null Parameter name:name".
If there any way to pass the parameter through wsdl.exe tool .
Regards,
Malini.V

Check for unnecessary spaces in the WSDL file. Especially in xsd:union tags.
I had the following problem:
<xsd:union memberTypes=" xsd:time genericTime" ...
Correct:
<xsd:union memberTypes="xsd:time genericTime" ...
and WSDL.exe was able to generate the proxy class code.
Kind regards
Holger

IIOP Java mode - proxy classes generation

Hello,
I have been able to use Jave-mode for call-in from a Java client to a
Forte Server. Among the generated Java files, I observe that for each
service object, there is also an IIOP proxy class - Java file with the
_pxy name appended to the front.
for example: ServerClass is a Tool Class, and there is a service object
based on it. The "Make Distribution" process has generated the
corresponding pxyServerClass.java also. It may be that the proxy
files are generated for all Forte classes. I am not sure.
The whole scheme of things has worked perfectly well for a simple test
project that I wrote.
But, there is another Plan, our Project's main Plan, that has some
Supplier Plans, which in turn have a few other Supplier Plans, etc, the
generated Java files does not have a single proxy class! I am unable to
figure out why. Are there places that I should look for?
In all, there are 2 DB Resouce Service Objects, 5 TOOL SOs in our
application configuration. I tried switching the Distributed property
from Allowed to IsDefault, but that didn't alter anything.
Any help will be greatly appreciated.
On a related note:
When using IDL mode...
Operator overriding is not allowed when using IDL2Java compiler of
VisiBroker. You have class B that extends A. A method is redefined may
be, with say different parameters. The .idl file won't compile, aborts
with an error "attempt to redefine operator/varialbe". I heard from a
colleague of mine (in fact I saw it compiling on his machine) that
OrbixWeb allows this. This seemed like a basic requirement, it was hard
to imagine that IDL syntax would not support that. Now, I realise that
it is a problem with Visigenic product. Have other developers come
across this problem? Is there a workaround?
Thanks,
Kishore Puvvada
International Business Corporation
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi Mark!!
I would suggest you to check the components created for the Interface. The main components of an Enterprise beans are like this:
<Interface>_PortTypeImplRemote
<Interface>_PortTypeImplRemoteHome
<Interface>_PortTypeImplLocal
<Interface>_PortTypeImplLocalHome
<Interface>_PortTypeBean
You can decompile if you have the Class file. It may be possible that the file got corrupted while creation.
Decompile the file if you have only the class file(Use DJ Compiler or JAD.exe). This will tell you whether the error is with the bytecode of the bean class.
Cheers!!
AnuraG

How to create proxy class for a Siebel WS which has many Workflows in it?

Hi,
I am facing a strange problem. I have a Web Service for which there are many workflows associated with this. When I generate WSDL for this Web Service and later on generate proxy class in .NET, it creates mutilple classes for each workflow. From UI, I can invoke a perticular method for the class for which I am interested in. But when I am building the same in JDeveloper, using Web Service proxy, I get only one class and I am not interested in invoking method in this class but interested in some other class for which the proxy was not generated. Is there some way to generate multiple classes in JDeveloper proxy?
Thanks,
Sudha.

I have figured this out. Actually Generate proxy creates package and it includes all the class in it. Now i am able to invoke web service method call.

Getting Bad Type Error when calling a method in the proxy class

Hi,
I have generated the proxy classes from wsdl.
When I am calling the methods in the proxy class from one of external class, I am getting following error.
Can anyone please help me in resolving this issue.
javax.xml.ws.soap.SOAPFaultException: org.xml.sax.SAXException: Bad types (interface javax.xml.soap.SOAPElement -> class com.intraware.snetmgr.webservice.data.SubscribeNetObjectReference) Message being parsed:
     at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
     at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy176.find(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy173.find(Unknown Source)
     at com.xxx.fs.FNServices.findAccountWs(FNServices.java:132)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
     at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
     at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
     at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:268)
     at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:403)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:532)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:253)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
     at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:171)
     at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
     at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
     at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:336)
     at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:95)
     at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Thanks
Anoop

Hi Vlad,
The service has not been changed since i have generated the proxy.
I tried calling the service from soapUI and I am getting the following error now.
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:uri="uri:webservice.subscribenet.intraware.com" xmlns:uri1="uri:subscribenet.intraware.com">
<soapenv:Header>
<uri:SessionHeader>
<uri:SessionID>hjkashd9sd90809dskjkds090dsj</uri:SessionID>
</uri:SessionHeader>
</soapenv:Header>
<soapenv:Body>
<uri:Find>
<uri:SubscribeNetObjectReference>
<uri1:ID></uri1:ID>
<uri1:IntrawareID></uri1:IntrawareID>
<uri1:SharePartnerID></uri1:SharePartnerID>
</uri:SubscribeNetObjectReference>
</uri:Find>
</soapenv:Body>
</soapenv:Envelope>
Response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>org.xml.sax.SAXException: WSWS3279E: Error: Unable to create JavaBean of type com.intraware.snetmgr.webservice.data.SubscribeNetObjectReference. Missing default constructor? Error was: java.lang.InstantiationException: com.intraware.snetmgr.webservice.data.SubscribeNetObjectReference. Message being parsed:</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Thanks
Anoop

RMI exception calling web service from proxy class

I am getting the following error attempting to call a web service from a proxy. It appears to relate to the type of objects I am trying to send vs the type that is expected. Following the exception I am adding a copy of the control where calling the web service is sucessful, a copy of the proxy class that I am using to make this unsucessful call, and the controller.jpf that has the formBean where I am creating my objects
Caught Exception Calling the Web Service from the Proxy. The Exception is the f
ollowing: java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SO
APException: failed to serialize class org.openuri.www.CreateAccountCheckingReq
uestweblogic.xml.schema.binding.SerializationException: type mapping lookup fail
ure on class=class controls.CheckingService$anyType TypeMapping=TYPEMAPPING SIZE
=5
ENTRY 1:
class: org.openuri.www.CreateAccountCheckingResponse
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingResponse
ser: org.openuri.www.CreateAccountCheckingResponseCodec@c0f4da
deser: org.openuri.www.CreateAccountCheckingResponseCodec@b1dd4
ENTRY 2:
class: org.openuri.www.FundingInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:FundingInfoAnonType
ser: org.openuri.www.FundingInfoAnonTypeCodec@1d36711
deser: org.openuri.www.FundingInfoAnonTypeCodec@13a59e
ENTRY 3:
class: org.openuri.www.AccountInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:AccountInfoAnonType
ser: org.openuri.www.AccountInfoAnonTypeCodec@1de5959
deser: org.openuri.www.AccountInfoAnonTypeCodec@bbf788
ENTRY 4:
class: org.openuri.www.CustomerInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:CustomerInfoAnonType
ser: org.openuri.www.CustomerInfoAnonTypeCodec@7824f9
deser: org.openuri.www.CustomerInfoAnonTypeCodec@1c35fe1
ENTRY 5:
class: org.openuri.www.CreateAccountCheckingRequest
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingRequest
ser: org.openuri.www.CreateAccountCheckingRequestCodec@1cbcd7b
deser: org.openuri.www.CreateAccountCheckingRequestCodec@11f60ce
; nested exception is:
javax.xml.soap.SOAPException: failed to serialize class org.openuri.www
.CreateAccountCheckingRequestweblogic.xml.schema.binding.SerializationException:
type mapping lookup failure on class=class controls.CheckingService$anyType Typ
eMapping=TYPEMAPPING SIZE=5
ENTRY 1:
class: org.openuri.www.CreateAccountCheckingResponse
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingResponse
ser: org.openuri.www.CreateAccountCheckingResponseCodec@c0f4da
deser: org.openuri.www.CreateAccountCheckingResponseCodec@b1dd4
ENTRY 2:
class: org.openuri.www.FundingInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:FundingInfoAnonType
ser: org.openuri.www.FundingInfoAnonTypeCodec@1d36711
deser: org.openuri.www.FundingInfoAnonTypeCodec@13a59e
ENTRY 3:
class: org.openuri.www.AccountInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:AccountInfoAnonType
ser: org.openuri.www.AccountInfoAnonTypeCodec@1de5959
deser: org.openuri.www.AccountInfoAnonTypeCodec@bbf788
ENTRY 4:
class: org.openuri.www.CustomerInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:CustomerInfoAnonType
ser: org.openuri.www.CustomerInfoAnonTypeCodec@7824f9
deser: org.openuri.www.CustomerInfoAnonTypeCodec@1c35fe1
ENTRY 5:
class: org.openuri.www.CreateAccountCheckingRequest
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingRequest
ser: org.openuri.www.CreateAccountCheckingRequestCodec@1cbcd7b
deser: org.openuri.www.CreateAccountCheckingRequestCodec@11f60ce
Java Control for the web service:
package controls;
import weblogic.webservice.context.WebServiceContext;
* @jc:location http-url="http://localhost:7001/Checking.jws"
* @jc:wsdl file="#CheckingWsdl"
* @jc:handler callback="MessageHandler" operation="MessageHandler"
public interface CheckingService extends com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class CustomerInfo
implements java.io.Serializable
public java.lang.String FirstName;
public java.lang.String LastName;
public java.lang.String MiddleName;
public int SSN;
public int CustomerNumber;
public java.util.Calendar CreationDate;
public java.util.Calendar LastModifiedDate;
public static class FundingInfo
implements java.io.Serializable
public float Amount;
public java.util.Calendar CurrentDate;
public int AccountNumber;
public static class anyType
implements java.io.Serializable
public com.bea.xml.XmlObject[] t;
public static class AccountInfo
implements java.io.Serializable
public int AccountNumber;
public float Balance;
public int CustomerNumber;
public java.util.Calendar LastModifiedDate;
public WebServiceContext context = CheckingService.context;
* @jc:protocol form-post="false" form-get="false"
public AccountInfo CreateAccountChecking (CustomerInfo CustomerInfo, FundingInfo FundingInfo, anyType CommonHeader);
static final long serialVersionUID = 1L;
/** @common:define name="CheckingWsdl" value::
<?xml version="1.0" encoding="utf-8"?>

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.openuri.org/">
<types>
<s:schema targetNamespace="http://www.openuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema">
<s:element name="CreateAccountCheckingRequest">
<s:complexType>
<s:sequence>
<s:element name="CustomerInfo">
<s:complexType>
<s:sequence>
<s:element name="FirstName" type="s:string" nillable="false"/>
<s:element name="LastName" type="s:string" nillable="false"/>
<s:element name="MiddleName" type="s:string" nillable="true"/>
<s:element name="SSN" type="s:int"/>
<s:element name="CustomerNumber" type="s:int"/>
<s:element name="CreationDate" type="s:dateTime"/>
<s:element name="LastModifiedDate" type="s:dateTime"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FundingInfo">
<s:complexType>
<s:sequence>
<s:element name="Amount" type="s:float"/>
<s:element name="CurrentDate" type="s:dateTime"/>
<s:element name="AccountNumber" type="s:int"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="CommonHeader" type="s:anyType"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="CreateAccountCheckingResponse">
<s:complexType>
<s:sequence>
<s:element name="AccountInfo">
<s:complexType>
<s:sequence>
<s:element name="AccountNumber" type="s:int"/>
     <s:element name="Balance" type="s:float"/>
     <s:element name="CustomerNumber" type="s:int"/>
     <s:element name="LastModifiedDate" type="s:dateTime"/>
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string"/>
</s:schema>
</types>
<message name="CreateAccountCheckingSoapIn">
<part name="parameters" element="s0:CreateAccountCheckingRequest"/>
</message>
<message name="CreateAccountCheckingSoapOut">
<part name="parameters" element="s0:CreateAccountCheckingResponse"/>
</message>
<portType name="CheckingSoap">
<operation name="CreateAccountChecking">
<input message="s0:CreateAccountCheckingSoapIn"/>
<output message="s0:CreateAccountCheckingSoapOut"/>
</operation>
</portType>
<binding name="CheckingSoap" type="s0:CheckingSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="CreateAccountChecking">
<soap:operation soapAction="http://www.openuri.org/CreateAccountChecking" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="Checking">
<port name="CheckingSoap" binding="s0:CheckingSoap">
<soap:address location="http://localhost:7001/Checking.jws"/>
</port>
</service>
</definitions>
FOLLOWING IS THE PROXY CLASS THAT IS UNSUCCESSFUL
import controls.CheckingService.anyType;
import java.util.ArrayList;
import java.util.List;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import org.openuri.CreateAccountCheckingResponseDocument.CreateAccountCheckingResponse;
import org.openuri.www.CustomerInfoAnonType;
import org.openuri.www.FundingInfoAnonType;
import weblogic.jws.proxies.*;
import weblogic.webservice.context.WebServiceContext;
import weblogic.webservice.context.WebServiceSession;
import weblogic.webservice.core.handler.WSSEClientHandler;
import weblogic.webservice.tools.pagegen.result;
import weblogic.xml.security.UserInfo;
import weblogic.xml.security.wsse.Security;
import weblogic.xml.security.wsse.SecurityElementFactory;
//import weblogic.jws.proxies.WebServiceB;
//import weblogic.jws.proxies.WebServiceB_Impl;
//import weblogic.jws.proxies.WebServiceBSoap;
public class CheckingWSProxy
public static void CallWS(Controller.CreateAccountCheckingForm form)
String user;
String pass;
try{
* Instantiate the main proxy class. The proxy class has the same name as the
* web service, with "_Impl" appended.
Checking myservice = new Checking_Impl("http://localhost:7001/ConsumerAccountApp/schemas/CheckingService.wsdl");
WebServiceContext context = myservice.context();
WebServiceSession session = context.getSession();
* Registers a handler for the SOAP message traffic.
HandlerRegistry registry = myservice.getHandlerRegistry();
List list = new ArrayList();
list.add(new HandlerInfo(WSSEClientHandler.class, null, null));
registry.setHandlerChain(new QName("Checking"), list);
* Set the username and password token for SOAP message sent from the client, through
* the proxy, to the web service.
user = form.getUsername();
pass = form.getPassword();
UserInfo ui = new UserInfo(user, pass);
session.setAttribute(WSSEClientHandler.REQUEST_USERINFO, ui);
* Adds the username / password token to the SOAP header.
SecurityElementFactory factory = SecurityElementFactory.getDefaultFactory();
Security security = factory.createSecurity(null);
security.addToken(ui);
session.setAttribute(WSSEClientHandler.REQUEST_SECURITY, security);
* Get the protocol-specific proxy class.
CheckingSoap msg=myservice.getCheckingSoap();
* Invoke the web service method
msg.createAccountChecking((CustomerInfoAnonType)form.getProxyCustomerInfo(), (FundingInfoAnonType)form.getProxyFundingInfo(), (Object)form.get_CommonHeader());
catch (Exception ex)
System.out.println("Caught Exception Calling the Web Service from the Proxy. The Exception is the following: " + ex.toString());
FOLLOWING IS THE FORMBEAN IN THE CONTROLLER.JPF FILE
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class CreateAccountCheckingForm extends FormData
private anyType _CommonHeader;
private controls.CheckingService.FundingInfo _FundingInfo;
private controls.CheckingService.CustomerInfo _CustomerInfo;
private java.util.Date dOut;
private java.util.Calendar cOut;
private CustomerInfo proxyCustomerInfo;
private FundingInfo proxyFundingInfo;
private String stringDate;
private String currentDate;
private String lastModifiedDate;
private String creationDate;
private String systemMessage;
private String username;
private String password;
private String accountType;
private String trashTransferAccount;
private String trashAccountNumber;
private boolean secureFlag;
public void set_CustomerInfo(controls.CheckingService.CustomerInfo _CustomerInfo)
_CustomerInfo.CreationDate = parseDate(getCreationDate());
_CustomerInfo.LastModifiedDate = parseDate(getLastModifiedDate());
this._CustomerInfo = _CustomerInfo;
public controls.CheckingService.CustomerInfo get_CustomerInfo()
if(this._CustomerInfo == null)
this._CustomerInfo = new controls.CheckingService.CustomerInfo();
_CustomerInfo.CreationDate = dateNow();
_CustomerInfo.LastModifiedDate = dateNow();
return this._CustomerInfo;
public CustomerInfo getProxyCustomerInfo()
this.proxyCustomerInfo = (CustomerInfo)this._CustomerInfo;
return this.proxyCustomerInfo;
public void set_FundingInfo(controls.CheckingService.FundingInfo _FundingInfo)
_FundingInfo.CurrentDate = parseDate(getCurrentDate());
this._FundingInfo = _FundingInfo;
public controls.CheckingService.FundingInfo get_FundingInfo()
if(this._FundingInfo == null)
this._FundingInfo = new controls.CheckingService.FundingInfo();
_FundingInfo.CurrentDate = dateNow();
return this._FundingInfo;
public FundingInfo getProxyFundingInfo()
this.proxyFundingInfo = (FundingInfo)this._FundingInfo;
return this.proxyFundingInfo;
public void set_CommonHeader(anyType _CommonHeader)
this._CommonHeader = _CommonHeader;
public anyType get_CommonHeader()
if(this._CommonHeader == null)
this._CommonHeader = new anyType();
return this._CommonHeader;
public java.util.Calendar dateNow()
this.dOut = new Date();
Calendar cOut = this.cOut.getInstance();
cOut.setTime(this.dOut);
this.cOut = cOut;
return this.cOut;
public java.util.Calendar parseDate( String strDate )
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
Calendar cOut = this.cOut;
df4.setLenient( false );
try
this.dOut = df4.parse( strDate );
} catch ( ParseException e )
cOut.getInstance();
cOut.setTime(dOut);
this.cOut = cOut;
return this.cOut;
public void setStringDate( String stringDate )
this.stringDate = stringDate;
public String getStringDate()
return this.stringDate;
public void setCurrentDate( String currentDate )
this.currentDate = currentDate;
public String getCurrentDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.currentDate = df4.format(_FundingInfo.CurrentDate.getTime());
return this.currentDate;
public void setLastModifiedDate( String lastModifiedDate )
this.lastModifiedDate = lastModifiedDate;
public String getLastModifiedDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.lastModifiedDate = df4.format(_CustomerInfo.LastModifiedDate.getTime());
return this.lastModifiedDate;
public void setCreationDate( String creationDate )
this.creationDate = creationDate;
public String getCreationDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.creationDate = df4.format(_CustomerInfo.CreationDate.getTime());
return this.creationDate;
public void setUsername( String username )
this.username = username;
public String getUsername()
return this.username;
public void setPassword( String password )
this.password = password;
public String getPassword()
return this.password;
public void setAccountType( String accountType )
this.accountType = accountType;
public String getAccountType()
return this.accountType;
public void setTrashTransferAccount( String trashTransferAccount )
this.trashTransferAccount = trashTransferAccount;
public String getTrashTransferAccount()
return this.trashTransferAccount;
public void setTrashAccountNumber( String trashAccountNumber )
this.trashAccountNumber = trashAccountNumber;
public String getTrashAccountNumber()
return this.trashAccountNumber;
public void setSystemMessage( String systemMessage )
this.systemMessage = systemMessage;
public String getSystemMessage()
return this.systemMessage;
public void setSecureFlag( boolean secureFlag )
this.secureFlag = secureFlag;
public boolean getSecureFlag()
return this.secureFlag;
}

This exception means that xml namespaces are different.
Etc. soap has xml element which doesn't belong to namespace of parent xml element and namespace is set without prefix.
I had such problem.
Try to set namespace prefix for this element.
Example:
<el1>
<el2 xmlns="http://..."/>
</el1>
Should be
<el1>
<q:el2 xmlns:q="http://..."/>
</el1>

Error occures while Sap R/3 sytem triggers XI message (using proxy class)

<b>Error occures while Sap R/3 sytem triggers XI message (using proxy class)</b>
1- I prepared message in XI side
2- I used sproxy transaction in R/3 side and generate proxy class
3- I used necessary methods in Abap program in R/3 side
4- Somethimes, message does not work and generate error like below
What must I do to solve this problem. Thanks
<u><b>Error message (Reported in SXMB_MONI in Sap R/3 side)</b></u><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="112" p2="HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten." p3="" p4="">HTTP.HTTP_CLIENT_SEND_FAILED</SAP:Code>
<SAP:Text language="TR">Error during http send: Error code: 112 Error text: HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten.</SAP:Text>
</SAP:ErrorHeader>

Hi,
Check thiss
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Error no 2
Regards
Aashish Sinha
PS : Reward points if helpful

How to use CL_PROXY_BASIS instead of CL_PROXY_CLIENT your ABAP Proxy class?

Hello experts,
I have a scenario where a new basis release was done in my development and testing SAP boxes (Basis Release 710 I believe) which means from then on when generating an ABAP Proxy class the inheriting class will be used is CL_PROXY_CLIENT as opposed to the previous CL_PROXY_BASIS.
This causes a problem though because the target date for the project, which uses this ABAP proxy, is supposed to be in the production system before the date when the basis release will be done in the production system. Obviously this will cause delays in my project since if I were to move my objects to production before the basis release a dump/syntax error will occur in production because the class CL_PROXY_CLIENT is not expected be production yet.
The next plan is to try to use CL_PROXY_BASIS instead of CL_PROXY_CLIENT, by editing my ABAP Proxy Class be force. My question is, what steps do I need to take so that I can change these classes so CL_PROXY_BASIS will be referenced/used instead of CL_PROXY_CLIENT ?
I hope to hear from all of you soon.
Regards

>
Rich Heilman wrote:
> Bad idea. Your dev and prod boxes should be at the same basis level at all times.
>
Which release and SP level are you still on?

C# Proxy Classes from SAP WSDL files

We are trying to generate proxy classes for SAP eSOA web services using C# and Visual Studio 2005.
When we try to run Microsoft's proxy class generation utility, WSDL.exe, errors are generated that attribute incorrect syntax to the SAP WSDL file:
> Microsoft (R) Web Services Description Language Utility [Microsoft (R)
> .NET Framework, Version 2.0.50727.42] Copyright (C) Microsoft
> Corporation. All rights reserved.
> Warning: This web reference does not conform to WS-I Basic Profile v1.1.
> R2028, R2029: A DESCRIPTION using the WSDL namespace and the WSDL SOAP
> binding n amespace MUST be valid according to the XML Schemas found at
> http://schemas.xmls oap.org/wsdl/2003-02-11.xsd and http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.
> xsd.
> - Warning: The element 'definitions' in namespace
> 'http://schemas.xmlsoap.org /wsdl/' has invalid child element 'properties' in namespace 'urn:com-sap:ifr:v2:
> wsdl'. List of possible elements expected: 'import, types, message,
> portType, bi nding, service' in namespace
> 'http://schemas.xmlsoap.org/wsdl/'. Line 1748, posi tion 4.
>
> SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of
> implementat ion guidelines that recommend how a set of core Web
> services specifications shou ld be used together to develop
> interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
>
> For more details on the WS-I Basic Profile v1.1, see the specification
> at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
The WSDL file is obtained from the SAP ES Workplace, from the following URL:
http://erp.esworkplace.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?&id=4FFC1A97663611DA36BB000F20DAC9EF&fragID=&packageid=DBBB6D8AA3B382F191E0000F20F64781&iv=
We have already tried both SAP files available from this location; neither works.
Any insight you can offer to help us generate these proxy classes is welcome. Note that the SAP PDF file, "ESOA-Roadmap-Workshop.PDF" talks about one syntactic incompatibility with Microsoft WSDL (on page 70), but this solution does not work, and indeed the token 'parameters' does not appear anywhere in either SAP WSDL file for Create Maintenance Request eSOA.
Thanks for any help you can offer!
-- Julian Mensch

I have the same problem after renaming "parameters" to "parameter" and I'm using the same example ES that's in the document:
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_EMPLOYEEBASICDBYEMPLOYEEQR/version3?sap-client=800&wsdl=1.1
wsdl.exe from .NET Framework 2.0.50727.42 gives me
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementat
ion guidelines that recommend how a set of core Web services specifications shou
ld be used together to develop interoperable Web services. For the 1.1 Profile,
those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification
at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I'm sure it's something really stupid since this example worked at some point for whoever wrote the doc...
It's sad that there is basically no .NET support from the SAP side and apart from a few documents there is basically no developer documentation or samples...

ABAP proxy class - data structure

I generated a ABAP Proxy Class and the data structure I want to use is put automatically under item structure which has 0...unbounded type.
1. How can I get rid of this item structure as it will create another unnecessary level for my mapping
2. If my source structure has only 3 level, and the target structure has more than 3 (including item), how to map it?
e.g.
Source structure: Level 1(occurrence 1) > Level 2(1)> Level 3(0..1)
Target structure: Level 1(1])--> Level 2(0...1) --> item (0..unbounded) ---> Level 4(0..1)
I need to map level 3 from my source to level 4 in target, but it didn't seem to work.
Thanks.

--->1. How can I get rid of this item structure as it will create another unnecessary level for my mapping
You can delete the proxy at Application Server.....make necessary changes at XI Message Interface and again generate the proxy...
-->Source structure: Level 1(occurrence 1) > Level 2(1)> Level 3(0..1)
Target structure: Level 1(1])--> Level 2(0...1) --> item (0..unbounded) ---> Level 4(0..1)
For this you need to make use of context change features of XI Mapping.
Regards,

Error: "cannot be resolved or is not a type" of webservice proxy class

Hello I'm novice in Web Dyn Pro, could you please assist me.
I have project that was developed before by others, now I encountered with errors during compilation of web service project based on ejb. If more concretely, problems occured in one auto-generated proxy class that refer to another proxy class that I don't know why was absent.
Problems occures in lines like this
com.accenture.mdp.company.model.companybasic.proxies.DefaultServiceImpl service = com.accenture.mdp.company.model.companybasic.CompanyBasic. getServiceImpl ();
Error com.accenture.mdp.company.model.companybasic.proxies.DefaultServiceImpl cannot be resolved or is not a type Request_CompanyServiceViDocument_addCompany.java
I suppose that exists the way to generate absented proxies automaticaly, may be by using wizards, but I don't know how.
Could anybody help me ?

Hi Sergy,
Welcome to SDN!
Did you try Repair, Reload and Rebuild options?
(Right click on the project, you will get the options)
If still the problem exists, Close and Open the project.
Check the versions of your NWDS and the project developed NWDS are same?
Regards,
Siva

Proxy class sometimes generate bean class by webmethod name

Similar Messages

Maybe you are looking for