An RPC-style message

please see this ...
An RPC-style message has the XML payload wrapped inside an operation element in a SOAP body
what does payload means here ?
In English payload means
+(1) the passengers and goods on a ship or an aircraft for which payment is received+
+(2)the goods that a vehicle, for example a lorry/truck, is carrying; the amount it is carrying+
+(3)the explosive power of a bomb or a missile+
+(4)the equipment carried by a spacecraft or satellite+
but none seems a good fit in this context. what does XML payload means ? also why such naming ?

The payload is the part of the load carrying capacity which can be hired out and paid for, i.e. which is the purpose of the transport. As opposed to the truck itself, the message headers, the casing, the aircraft itself, whose only purpose is to carry the payload. In this case 'payload' refers to the message body, the application message itself.
You can build a plane but if it won't carry a payload it serves no useful purpose. Cf. Howard Hughes and the Spruce Goose.

Similar Messages

How to handle rpc/encoded style messages using BizTalk?

I am integrating with a lot of services and one of our customers has a service with rpc/encoded style
I could consume and generate schema from their wsdl file via BizTalk consume WCF wizard.
Once I am trying to call the service with request message that generated from the schema, it is giving an error that can not desterilize the first element of the message.
No Deserializer found to deserialize a 'FieldName' using encoding style 'null'
I compared the stub xml request message from SaopUI and I noticed that the xml expecting the data type with the element like this .
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<sozlesmeNo xsi:type="xsd:string">?</sozlesmeNo>
<bankaKodu xsi:type="xsd:string">?</bankaKodu>
<anahtar xsi:type="xsd:string">?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
On the other hand, I got the request of the message from Fiddler using the BizTalk , and the generate xml of the BizTalk schema without the data type.
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama>
<sozlesmeNo>?</sozlesmeNo>
<bankaKodu>?</bankaKodu>
<anahtar>?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
In SoapUi, if I remove a datatype from the message, I will get same error from the BizTalk request.
I read some articles that rpc/encoded style are not supported but I am not sure and these articles are not clear.
I also read that it was supported with Soap adapter but now it is deprecated.
So, Is there any one has an experience in rpc/encoded style messages and how to handle these message in BizTalk or is there any work around to handle these messages?
Your inputs really appreciate it.
Thanks in advance,
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

Hi,
Please refer to the document which might help you:
#RPC/Encoded Style
http://www.c-sharpcorner.com/UploadFile/martinkropp/DesigningInteroperableWebService11232005044847AM/DesigningInteroperableWebService.aspx

Java.lang.NoSuchMethodException in RPC style WS in WL6.1

Hi,
I am facing some veered exception in the RPC style WS. The SS-EJB that I used as the web service is working fine when I directly try to access the EJB.
When I wrote a client I get the following exception on the server side.
<Jan 30, 2002 11:41:54 AM IST> <Error> <HTTP> <[WebAppServletContext(2318716,w
-services,/web-services)] Root cause of ServletException
<Jan 30, 2002 11:41:54 AM IST> <Error> <HTTP> <[WebAppServletContext(2318716,w
-services,/web-services)] Root cause of ServletException
java.lang.NoSuchMethodException
at java.lang.Class.getMethod0(Native Method)
at java.lang.Class.getMethod(Class.java:888)
at weblogic.soap.server.servlet.StatelessBeanAdapter.init(StatelessBeadapter.java:78)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubpl.java:700)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStImpl.java:643)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStumpl.java:588)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpjava:368)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.java:242)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebApprvletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Following is the code that's written on the client side.
ProjectBrokerWSClient client = new ProjectBrokerWSClient();
// Obtaining the initial context.
Context context = new InitialContext();
// Making a lookup for the required servlet.
WebServiceProxy proxy = (WebServiceProxy)context.lookup(http://localhost:7001/PB/PBBeanSL.PBHomeSL/PBBeanSL.PBHomeSL.wsdl" );
SoapMethod method = proxy.getMethod("selfTest");
Object result = method.invoke(new Object[]{"# Test message #"});
The function in the bean is as follows.
public String selfTest(String ostrMessage){
log("inside selfTest()" + ostrMessage);
return "# M e s s a g e r e c e i v e d #";
Please let me know if some thing is wrong out here or I have missed out any conf.
cheers.
n a v i n.
[att1.html]

yes i have done the ContextFactory settings.
cheers,
navin.
"Per Mengshoel" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
Have you tried setting the ContextFactory before
creating it :
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.soap.http.SoapInitialContextFactory");
//you might want to add this too
h.put("weblogic.soap.verbose", "true" );
Context context = new InitialContext(h);
-Per
"Navin Sidhaye" <[email protected]> wrote:
Hi,
I am facing some veered exception in the RPC style WS. The SS-EJB that
I =
used as the web service is working fine when I directly try to access
=
the EJB.
When I wrote a client I get the following exception on the server side.
<Jan 30, 2002 11:41:54 AM IST> <Error> <HTTP> =
<[WebAppServletContext(2318716,w
-services,/web-services)] Root cause of ServletException
<Jan 30, 2002 11:41:54 AM IST> <Error> <HTTP> =
<[WebAppServletContext(2318716,w
-services,/web-services)] Root cause of ServletException
java.lang.NoSuchMethodException
at java.lang.Class.getMethod0(Native Method)
at java.lang.Class.getMethod(Class.java:888)
at =weblogic.soap.server.servlet.StatelessBeanAdapter.init(StatelessBeadapter=
..java:78)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at =weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubpl.jav=
a:700)
at =weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStImpl.j=
ava:643)
at =weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStumpl.ja=
va:588)
at =weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpjava:3=
68)
at =weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.jav=
a:242)
at =weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.jav=
a:200)
at =weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebApprvletC=
ontext.java:2456)
at =weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestpl.jav=
a:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Following is the code that's written on the client side.
ProjectBrokerWSClient client =3D new ProjectBrokerWSClient();
// Obtaining the initial context.
Context context =3D new InitialContext();
// Making a lookup for the required servlet.
WebServiceProxy proxy =3D =
(WebServiceProxy)context.lookup(http://localhost:7001/PB/PBBeanSL.PBHomeS=
L/PBBeanSL.PBHomeSL.wsdl" );
SoapMethod method =3D proxy.getMethod("selfTest");
Object result =3D method.invoke(new Object[]{"# Test message =
The function in the bean is as follows.
public String selfTest(String ostrMessage){
log("inside selfTest()" + ostrMessage);
return "# M e s s a g e r e c e i v e d #";
Please let me know if some thing is wrong out here or I have missed out
=
any conf.
cheers.
n a v i n.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DTahoma size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>I am facing some veered exception
=
in the RPC=20
style WS. The SS-EJB that I used as the web service is working fine when
=
I=20
directly try to access the EJB.</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>When I wrote a client I get the =
following=20
exception on the server side.</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D1><Jan 30, 2002 11:41:54 AM IST>
=
<Error>=20
<HTTP> =
<[WebAppServletContext(2318716,w<BR>-services,/web-services)]=20
Root cause of ServletException<BR><Jan 30, 2002 11:41:54 AM IST>=20
<Error> <HTTP>=20
<[WebAppServletContext(2318716,w<BR>-services,/web-services)] Root
=
cause of=20
ServletException<BR></FONT><FONT face=3DArial size=3D2><FONT=20
size=3D1>java.lang.NoSuchMethodException<BR> =
; =20
at java.lang.Class.getMethod0(Native=20
Method)<BR> at=20
java.lang.Class.getMethod(Class.java:888)<BR> &nbs=
p; =20
at=20weblogic.soap.server.servlet.StatelessBeanAdapter.init(StatelessBeadapter=
..java:78)<BR> =20
at=20
javax.servlet.GenericServlet.init(GenericServlet.java:258)<BR> =
; =20
at=20weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubpl.jav=
a:700)<BR> =20
at=20weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStImpl.j=
ava:643)<BR> =20
at=20weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStumpl.ja=
va:588)<BR> =20
at=20weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpjava:3=
68)<BR> =20
at=20weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.jav=
a:242)<BR> =20
at=20weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubpl.jav=
a:200)<BR> =20
at=20weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebApprvletC=
ontext.java:2456)<BR> =20
at=20weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestpl.jav=
a:2039)<BR> =20
at=20
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)<BR> &n=
bsp; =20
at=20weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)<BR></FONT></FON=
T></DIV>
<DIV><FONT size=3D2><FONT size=3D1><FONT face=3DTahoma =
size=3D2>Following is the code=20
that's written on the client side.</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D1> =20
ProjectBrokerWSClient client =3D new =
ProjectBrokerWSClient();</FONT></DIV>
<DIV><FONT face=3DArial size=3D1></FONT> </DIV>
<DIV><FONT face=3DArial size=3D1>
=
// Obtaining=20
the initial context.<BR> Context
=
context =3D=20
new InitialContext();<BR></FONT><FONT face=3DArial =
size=3D1></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D1> =
//=20
Making a lookup for the required=20
servlet.<BR> WebServiceProxy proxy
=
=3D=20
(WebServiceProxy)context.lookup(</FONT><A =
href=3D"http://localhost:7001/PB/"><FONT=20
size=3D1><A=20
href=3D"http://localhost:7001/PB/PBBeanSL.PBHomeSL/PBBeanSL.PBHomeSL.wsdl=
">http://localhost:7001/PB/</FONT></A><FONT=20
size=3D1>PBBeanSL.PBHomeSL/PBBeanSL.PBHomeSL.wsdl</A>" =
);</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D1> =
SoapMethod=20
method =3D proxy.getMethod("selfTest");<BR></FONT><FONT face=3DArial
=
size=3D2><FONT=20
size=3D1> Object result =3D =
method.invoke(new=20
Object[]{"# Test message #"});</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT =
size=3D1></FONT></FONT> </DIV>
<DIV><FONT size=3D2><FONT size=3D1><FONT face=3DTahoma size=3D2>The =
function in the bean=20
is as follows.</FONT></FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D1>
=
public String=20
selfTest(String ostrMessage){</FONT></DIV>
<DIV><FONT face=3DArial size=3D1></FONT> </DIV>
<DIV><FONT face=3DArial size=3D1> =20
log("inside selfTest()" +=20
ostrMessage);<BR> &n=
bsp; return=20
"# M e s s a g e r e c e i v e d=20
#";<BR> }<BR></FONT></DIV>=
<DIV><FONT size=3D1><FONT face=3DTahoma size=3D2>Please let me know if
=
some thing is=20
wrong out here or I have missed out any conf.</FONT></FONT></DIV>
<DIV><FONT size=3D1><FONT face=3DTahoma =
size=3D2></FONT></FONT> </DIV>
<DIV><FONT size=3D1><FONT face=3DTahoma =
size=3D2>cheers.</FONT></FONT></DIV>
<DIV><FONT size=3D1><FONT face=3DTahoma size=3D2><STRONG>n a v i=20
n.</STRONG></FONT></DIV></FONT>
<DIV><FONT face=3DArial size=3D1> </DIV></FONT>
<DIV><FONT face=3DArial size=3D2><FONT size=3D1><FONT =
size=3D2></FONT> </DIV>
<DIV><BR></DIV></FONT></FONT></BODY></HTML>

RPC Style Web Service and SSL

Hi,
Has anyone tried (and maybe succeeded) in accessing an
RPC-style Web Service deployed on WebLogic Server 6.1 using
SSL? I have a Web Service deployed and am able to access it using JNDI and the
weblogic.soap.http.SoapInitialContextFactory
INITIAL_CONTEXT_FACTORY. However, when I try to set the
Context.SECURITY_PROTOCOL to "ssl" and access the secure port,
I get a "java.net.SocketException: Unexpected end of file from
the server" error message.
Does the weblogic.soap.http.SoapInitialContextFactory not
support SSL? Do I need to do the SOAP/XML messaging myself,
without being able to make use of the WebLogic convenience
classes? Thanks! Rob

Alright!
Glad you got it working ;-)
Actually, the problem with the protocol being hardcoded to http in the wsdl.jsp,
is a bit strange. It's unusual that the BEA engineers that coded the wsgen component
and support classes, didn't use something like the following:
<soap:address location="<%= request.getScheme() + "://" + request.getServerName()
+ ":" + request.getServerPort() %>/security/examples/webservices/security/PhoneBookService"/>
I don't use wsgen too much, because I need to have more control over the J2EE
packaging. It (wsgen) is great for spitting out stuff, but not really setup for
doing Web service packaging that use classes (i.e. helper files, frameworks, etc.)
that it doesn't generate. I think they (BEA) might be looking into integrating
the Web Services assembly process with other tools like WebGain, Forte, etc. to
alleviate these types of issues.
Anyway, glad you got it working, so now you can help somebody else (time permitting,
of course) with this topic in the future!
Regards,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
>
Mike,
Thank you very much for your response! The next to
last sentence did it for me (when you mentioned checking
that the location attribute of the soap:address element
was set properly)! I noticed that when I viewed the WSDL
file via the browser (by clicking on the link in the
index.html page), I saw http://host:<unsecure_port> when
I requested it over the unsecure port, but I saw
http://host:<secure_port> when I requested the WSDL over
the secure port. Notice it did not say https!
So, I unjarred the EAR file that was generated by my
wsgen task, and then unjarred the generated WAR file
contained therein. When I looked at wsdl.jsp, I noticed
that "http" was hard-coded in the location attribute, but
that the host name and port number were dynamically
generated. So I added a scriplet to dynamically place an
"s" after "http" (if request.isSecure()) and rejarred up
the WAR and EAR files.
Now when I deployed the EAR file, I see "https" when
I request the WSDL over the secure port, and my client
(actually your client;) works! Awesome! I really appreciate
your help! Now my only issue is why did the wsdl.jsp have
"http" hard-coded, not accounting for secure requests.
These files were generated by the WSGEN task in ANT.
I figure it's either: I have a configuration problem,
I have a problem with my ANT build script, my version of
WebLogic Server (6.1 w/SP1 built 9/18/2001) has a bug, or
maybe you just have to manually go in and modify the wsdl.jsp
file if you want to use https :(. Please let me know if
you have any insight on this, and I will also follow up
with WebLogic support. Thanks again! Rob
"Michael Wooten" <[email protected]> wrote:
Hi Rob,
I am absolutely sure the code I posted works, so we need to approach
this from
a different angle ;-)
First, I know why the Context.SECURITY_PROTOCOL approach doesn't works.
It's because
the namespace in the Web Services code examples is not the same oneas
the one
used for RMI objects, EJBs, JDBC Data Sources, etc. For those objects,
the Context.PROVIDER_URL
is something like "t3://localhost:7001", and the INITIAL_CONTEXT_FACTORY
is "weblogic.jndi.WLInitialContextFactory".
The one being used with WebLogic Web Services, is mainly just functioning
as a
mechanism for manufacturing WebServiceProxy objects, because it is a
non-instanciable!
It does this by using a subclass of javax.naming.Context called SOAPContext,
which
is completely hidden from you, but also doesn't do much except implement
the lookup()
method. The implementation of this method ignores the Context.SECURITY_URL
property,
but it does pay attention to the "java.naming.security.principal" and
"java.naming.security.credentials"
properties. You don't need these properties for SSL, just Basic Authentication.
Enough about that, though. The service end-point is a servlet right?
So this means
it has a URL that begins with http or https, which in turn means the
WebLogic
servlet engine gets the SOAP request and sends it to the StatelessSessionAdapter
servlet. To WLS, this is just like any other HTTP/HTTPS request sent
to it ;-)
There is no special "SOAP-related" HTTP/HTTPS handler in WLS, but the
SSL challenge
dance still happens. So my first question is, are you sure you havethe
HTTPS
attributes set properly in the WebLogic console. SSL/HTTPS should be
enabled and
the "Hostname Verification Ignored" checkbox should be checked. Next,
are you
sure the URL assigned to the location attribute of the <service> element
in the
WSDL is correct (i.e. https://localhost:7002)? Are you using the "dynamic
client"
approach?
Regards,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
Mike,
Thanks for your response. I downloaded the code example that
you
posted
last week, as well as the code example that you posted in October for
a similar
request (BEA Support pointed me towards that). Unfortunately, I still
can't get
the Web Service to respond to the client request when the client uses
the HTTPS
port for the WebLogic Server.
I tried two different client approaches. The first uses the client
code
that you posted in October, the WebServiceProxy approach. The second
approach
is based on the example in the WebLogic documentation, which uses the
weblogic.soap.SoapInitialContextFactory
class with the javax.naming.Context object to perform a lookup on the
service
(which closely resembles rmi without the narrowing).
Both client classes fail to invoke the the service itself viaHTTPS
(although
they both work when making HTTP requests to the unsecure port). However,
when
I run the client based on the client class that you posted in October
and make
an HTTPS request, I can see in the output where it is able to download
the WSDL
file and use it (via the WebServiceProxy) to describe the availablemethods
for
the associated Web Service. It is only when the actual invoke() method
is called
on the SoapMethod object (which in turn sends the XML request to the
Web Service
Servlet), that the server doesn't respond, and the client fails with
an UnexpectedEndOfFileException
(i.e. no response).
So, do you know why the servlet that the RPC-style Web Serviceuses
to handle
requests would not respond to HTTPS requests, when it processes HTTP
requests
without a problem (using the same client code that fails with the HTTPS
request)?
I am using WebLogic Server 6.1 w/SP1 on a Solaris 8 platform. Thanks
for any
advice you can give me! Rob
"Michael Wooten" <[email protected]> wrote:
Hi Rob,
Check out the attached zip for "insights" into how to do this. It
contains
the
code for two Web service "consumers" (that the new fangled word fora
"client")
and the web.xml and weblogic.xml for the RPC-style Web Service, that
they consume.
Hope this helps,
Mike Wooten
"Rob Nelson" <[email protected]> wrote:
Hi,
Has anyone tried (and maybe succeeded) in accessing an
RPC-style Web Service deployed on WebLogic Server 6.1 using
SSL? I have a Web Service deployed and am able to access it using
JNDI
and the
weblogic.soap.http.SoapInitialContextFactory
INITIAL_CONTEXT_FACTORY. However, when I try to set the
Context.SECURITY_PROTOCOL to "ssl" and access the secure port,
I get a "java.net.SocketException: Unexpected end of file from
the server" error message.
Does the weblogic.soap.http.SoapInitialContextFactory not
support SSL? Do I need to do the SOAP/XML messaging myself,
without being able to make use of the WebLogic convenience
classes? Thanks! Rob

Retrieving client ip from RPC-style web service

Hi,
I've got an rpc-style web service and I would like to log the incoming client
ip address (i.e. I need to get at the HTTPRequest object). Can this be done by
passing some kind of SOAP context parameter in the argument list of my exposed
methods? If this is not doable, is implementing SOAP message handlers the way
to to go? I would rather not do the latter, as the web service is working well
and don't want to play with my code too much.
Thanks

I tried this, following the example in http://e-docs.bea.com/wls/docs70/webapp/filters.html,
but I still can't get it to work. The init() method gets called, but doFilter(ServletRequest
req, ServletResponse resp, FilterChain fc) does not. The "filter" part of my
web.xml looks like:
<filter>
<filter-name>serviceFilter</filter-name>
<filter-class>webservices.ServiceFilterImpl</filter-class>
</filter>
<filter-mapping>
<filter-name>serviceFilter</filter-name>
<url-pattern>/myPattern/myWebService</url-pattern>
</filter-mapping>
The only thing I could thing of is that maybe my url-pattern is wrong, although
this seems unlikely as my web service is able to process requests sent using
http://myWLSMachine:7001/myPattern/myWebService.
In fact, in the the WLS access.log file, I have:
[07/Oct/2002:11:51:01 -0400] "POST /myPattern/myWebService HTTP/1.0" 200 3011.
Do you know if there's something in the JAX-RPC API that I could use to get at
the client ip address? I dug through the documentation and came across something
called "ServletEndpointContext", but I'm not sure if this will do the trick.
Thanks for your time,
Danielle
"manoj cheenath" <[email protected]> wrote:
One way to do this may be to write a servlet filter
and map the filter to the URL of your service.
regards,
-manoj
"Danielle Vella" <[email protected]> wrote in message
news:[email protected]..
Hi,
I've got an rpc-style web service and I would like to log the incomingclient
ip address (i.e. I need to get at the HTTPRequest object). Can thisbe
done by
passing some kind of SOAP context parameter in the argument list ofmy
exposed
methods? If this is not doable, is implementing SOAP message handlersthe
way
to to go? I would rather not do the latter, as the web service isworking
well
and don't want to play with my code too much.
Thanks

Rpc style wsdl

Dear Experts,
           We have a wsdl with soapenc type and soapenc array type. The webservice is RPC style.
does PI 7.0 support rpc style call. I read we could do it by creating soap request and using do not use soap
envelope. Still do we need to encode the values before sending it out of PI?   where does the encoding take place ?
   I am using the soap lookup for the webservice call. So can i use the soap request structure directly inside the udf ? Please help...
Thanks,
Aju

Hi Shabarish,
               Thanks for the reply.
1. So our option is to ask the webservice provider to change it to doc type , right?
2.And what to do with soapen data type . do we need to do the encoding before we send.. what i mean to ask is how does PI handle the datatype differences.. for example if we send a string type data to a soap enc type data type ... should we do the encoding. and where does the encoding happen ?
3. when we use the do not use soap envelope , we need to create the soap request in the message mapping ,
including the header and send to adapter, and adapter makes the call with it wihout making any changes. is that right ?
Thanks,
Aju

Weblogic RPC-Style webservice parameter problem

I am getting a strange error when using RPC-style web services. When I
try and pass and object which contains an array of objects I get an
error. When returning this same object from a function I have no errors.
I have noticed that if I change the arrayType from anyType in the
incoming soap message to one of the xml schema primitives there is no
problem -- such as int, long, and string. I am using Weblogic 8.1 sp3. I
have used a java client, .net client, and the JWS web page to recreate
this problem. Here is the error I am receiving back from the service:
Invalid Request for setTestObject
com.bea.wlw.runtime.core.request.RequestValidationException: Error
deserializing arguments.
Encountered an xml tag without a recognized type: the type must be
declared with an xsi:type attribute.
Caused by: com.bea.xml.marshal.XmlEncodingException: Encountered an xml
tag without a recognized type: the type must be declared with an
xsi:type attribute.
and here is my wsdl generated from the JWS:
<?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 elementFormDefault="qualified"
targetNamespace="http://www.openuri.org/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:ope="http://www.openuri.org/">
<s:element name="TestObject" nillable="true" type="ope:TestObject"/>
<s:complexType name="TestObject">
<s:sequence>
<s:element name="_prop" type="s:string" minOccurs="0"/>
<s:element name="_set" type="ope:ArrayOfanyType" minOccurs="0"/>
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfanyType">
<s:sequence>
<s:element name="anyType" type="s:anyType" nillable="true"
minOccurs="0" maxOccurs="unbounded"/>
</s:sequence>
</s:complexType>
</s:schema>
<s:schema elementFormDefault="qualified"
targetNamespace="http://www.openuri.org/encodedTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:enc2
="http://www.openuri.org/encodedTypes"
xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<s:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<s:complexType name="TestObject">
<s:sequence>
<s:element name="_prop" type="s:string" minOccurs="0"/>
<s:element name="_set" type="enc2:ArrayOfanyType" minOccurs="0"/>
</s:sequence>
</s:complexType>
<s:complexType name="ArrayOfanyType">
<s:complexContent>
<s:restriction base="enc:Array">
<s:sequence>
<s:element name="anyType" type="s:anyType" minOccurs="0"
maxOccurs="unbounded"/>
</s:sequence>
<s:attribute ref="enc:arrayType" wsdl:arrayType="s:anyType[]"/>
</s:restriction>
</s:complexContent>
</s:complexType>
<s:complexType name="ObjectArrayItem">
<s:sequence>
<s:element name="_prop" type="s:string" minOccurs="0"/>
</s:sequence>
</s:complexType>
</s:schema>
</types>
<message name="getTestObjectSoapIn"/>
<message name="getTestObjectSoapOut">
<part name="getTestObjectResult" type="s1:TestObject" xmlns:s1
="http://www.openuri.org/encodedTypes"/>
</message>
<message name="setTestObjectSoapIn">
<part name="inTestObject" type="s1:TestObject" xmlns:s1
="http://www.openuri.org/encodedTypes"/>
</message>
<message name="setTestObjectSoapOut"/>
<message name="getTestObjectHttpGetIn"/>
<message name="getTestObjectHttpGetOut">
<part name="Body" element="s0:TestObject"/>
</message>
<message name="getTestObjectHttpPostIn"/>
<message name="getTestObjectHttpPostOut">
<part name="Body" element="s0:TestObject"/>
</message>
<portType name="ObjectArrayTestSoap">
<operation name="getTestObject">
<input message="s0:getTestObjectSoapIn"/>
<output message="s0:getTestObjectSoapOut"/>
</operation>
<operation name="setTestObject">
<input message="s0:setTestObjectSoapIn"/>
<output message="s0:setTestObjectSoapOut"/>
</operation>
</portType>
<portType name="ObjectArrayTestHttpGet">
<operation name="getTestObject">
<input message="s0:getTestObjectHttpGetIn"/>
<output message="s0:getTestObjectHttpGetOut"/>
</operation>
</portType>
<portType name="ObjectArrayTestHttpPost">
<operation name="getTestObject">
<input message="s0:getTestObjectHttpPostIn"/>
<output message="s0:getTestObjectHttpPostOut"/>
</operation>
</portType>
<binding name="ObjectArrayTestSoap" type="s0:ObjectArrayTestSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
<operation name="getTestObject">
<soap:operation soapAction="http://www.openuri.org/getTestObject"
style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
<operation name="setTestObject">
<soap:operation soapAction="http://www.openuri.org/setTestObject"
style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://www.openuri.org/"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<binding name="ObjectArrayTestHttpGet" type="s0:ObjectArrayTestHttpGet">
<http:binding verb="GET"/>
<operation name="getTestObject">
<http:operation location="/getTestObject"/>
<input>
<http:urlEncoded/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<binding name="ObjectArrayTestHttpPost"
type="s0:ObjectArrayTestHttpPost">
<http:binding verb="POST"/>
<operation name="getTestObject">
<http:operation location="/getTestObject"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<service name="ObjectArrayTest">
<port name="ObjectArrayTestSoap" binding="s0:ObjectArrayTestSoap">
<soap:address
location="http://localhost:7001/RPCObjectArrayFailureWeb/com/test/Object
ArrayTest.jws"/>
</port>
<port name="ObjectArrayTestHttpGet" binding="s0:ObjectArrayTestHttpGet">
<http:address
location="http://localhost:7001/RPCObjectArrayFailureWeb/com/test/Object
ArrayTest.jws"/>
</port>
<port name="ObjectArrayTestHttpPost"
binding="s0:ObjectArrayTestHttpPost">
<http:address
location="http://localhost:7001/RPCObjectArrayFailureWeb/com/test/Object
ArrayTest.jws"/>
</port>
</service>
</definitions>
Thanks for the help.
Steve

Hello Omar,
I have the same problem with BEA WLP 8.1 SP4.
Did you find any issue in order to solve it ?
Thanks for any help.
Sincerely,
GÃ©rard

Bad Request OSB Local Proxy to Business RPC Style

Hello,
I have a problem calling a web service rpc style base from a local proxy.
Here is the situation.
I have 1 Bussiness Service RPC style base (wsdl base).
I have 1 Proxy Service (Local Transport) Lets call this one LPS1.
I have 1 Proxy Service (Local Transport) Lets call it LPS2.
When I call BS from osb console, the response is OK.
When I call from osbconsole LPS1 to BS through a rountin node the response is OK. (I also tried Service Callout).
BUT, When I call from osbconsole LPS2 to LPS1 to BS, I got BAD REQUEST...
I have already tried everythin, but I could not I get the solution.
Thus,
call BS = OK
call LPS1 -> BS = OK.
call LPS2 -> LPS1 -> BS = BAD REQUEST.
I have compared both outbound variables and there are the same.
Thanks in advance.
Gustavo.

Swapnil,
Publish call will be blocking if QoS is set as Exactly-Once.
If QoS is Best-Effort and target endpoint is a one-way proxy service then it is a blocking call (source proxy waits for target proxy message flow completion) and if QoS is Best-Effort and target endpoint is a request-response proxy service then control returns back to source proxy as soon as Request pipeline of target proxy message flow completes.
Regards,
Anuj

Generate Client Proxy from a RPC-Style encoded WSDL

Hi Experts,
I was just trying to consume a RPC-Style encoded WSDL,
but the creation of the client proxy failed with the following error message:
Exception occurred in library handler
Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/
Does anyone know, if it's possible to consume a RPC-Style encoded Web Service?
Thanks in advance!

Hi Sandeep,
Could you try invoking clientgen [1] directly to see if this properly
consumes your WSDL?
Thanks,
Bruce
[1]
http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
Sandeep wrote:
>
Hi,
I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
as parameter and returns another XMLBean object. The web service works fine when
tested using the workshop's test browser but when i am trying to generate a client
proxy trough the workshop's test browser, it displays this warning:
Failed to generate client proxy from WSDL definition for this service
and does not generate the proxy.
I'll appreciate any thoughts on this.
Thanks
Sandeep

Import RPC-style WSDL

Hello!
I currently implement a RFC -> RFC adapter -> XI -> SOAP adapter -> Web Service scenario. I have imported the WSDL of the Web Service as External Definition into the Integration Repository to use it for the RFC <-> Web Service mapping within the graphical mapping tool.
Until now I only have imported document-style WSDL and there never have been any problems. Now the WSDL is RPC-style which means that the messages described by the <wsdl:types>...</wsdl:types> part should be enclosed by an additonal structure describing the Web Service operation to be executed.
However, in the graphical mapping tool the structure for the Web Service operation is missing and thus the Web Service call cannot be executed. How can I solve this problem without changing the WSDL or creating an additional XLST or Java mapping?
It seems that there is no problem with the WSDL. When I loaded it with the Web Service Navigator test tool of the SAP Web Application Server the structure describing the Web Service operation has been generated in the request message.
Regards, Tanja Schättler

Hi Tanja
Check this note 856597, it even has some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
A snippet from the note,
"Q: Can I convert an RPC styled WSDL to a document styled WSDL?
            A: It is difficult to answer yes or no because the answer depends on the WSDL instance and the implementation of the code that binds the XML instance to some native object. The problem comes from the fact that these two styles describe web services in different layers. The document style WSDL describes how one can bind an XML document to the SOAP message format. In contrast, the RPC style WSDL describes how one can bind an object to the SOAP message format. One can imagine that this works in two steps: first representing the object as an XML document and then binding this XML document to the SOAP message format. How this first step works is controlled by the SOAP encoding name. For the standard encoding specified in the SOAP specification, most objects can be easily described in an equivalent XML schema. Some special objects such as references and arrays must be represented by some special rules and some additional meta information in XML. This implies that these additional attributes and elements must also be described in the XML schema and the document style based proxy must set these values in the instance appropriately.
            One must however note that even if one has an equivalent document style WSDL, this does not automatically guarantees the interoperability. Some RPC styled service implementations have significant interoperability problems such as requiring the xsi:type attribute for every element or the SOAP encoding attribute at some particular element. If one has to call such non conformant SOAP service, one must adjust the message accordingly.
           Attachment wsdl_style_samples. zip contains some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
            Related Questions "Does the RPC or Document style in WSDL play a role in the SOAP adapter?"
cheers
Sameer

Quick Web Services Using Document Style Messaging

Hello all,
I am using Apache Axis and am trying to set up a document style (message based) webservice that will receive a DOM object, modify that DOM object, and return it as a new DOM object. I have not problems with standard RPC style webservices, but am unsure as to where to go with the more complex. I have included everything that may be helpful to give me an answer.....
I have set up my webservice (a very simple one to get this going):
package testing.webservices;
import org.w3c.dom.Document;
import org.apache.axis.MessageContext;
public class DocTest{
public Document doSubmission(MessageContext msgContext, Document inDoc)throws Exception{
return inDoc;
I set this class up in Axis with my deploy.wsdd file:
<deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
<service name="DocService" style="java:MSG">
<parameter name="className" value="testing.webservices.DocTest" />
<parameter name="allowedMethods" value="doSubmission" />
</service>
</deployment>
When I look at Axis it lists this DocService as an active service. Can anyone tell me what the client code would look like to send a Document object to my simple webservice and receive a document object back? Any help would be greatly appreciated.
J-Rod
NOTE: This is what I have so far:
import .....
public class DocTestClient{
public static void main(String[] args) throws Exception {
String fileName = "C:\\Dev\\MyXmlFile.xml";
String uri = "file:" + new File(fileName).getAbsolutePath( );
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document doc = builder.parse(uri);
String endpointURL = "http://localhost:8080/axis/services/DocService";
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL(endpointURL) );
call.setOperationName(new QName("http://testing.webservices", "doSubmission") );
?????? WHAT DO I DO HERE to access the send the doc object and receive it back?????
}

Just thought I'd post an update. We figured out how to stream the required data as a string so I OK now. We ended up going with java:RPC to string data back and forth.
Thanks
J-Rod

ANT task wsgen error while deploying RPC style web service

Hi
I am trying to assemble/deploy an rpc style weblogic web service using the 'wsgen'
Ant task and the build.xml scripts provided with the samples. I get this error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>

WLS6.1, service pack 2? I didn't know there were any service packs for 6.1 and
6.0 didn't support wsgen and web services??
simon.
manoj cheenath <[email protected]> wrote:
>
>
This is a known bug which is fixed in WLS 6.1 SP2.
The workaround is to change the complex data types
to have more than one level package names.
for eg: change ....
package foo;
class Data{}
to :
package foo.bar;
class Data{}
-manoj
Praveen wrote:
Hi
I am trying to assemble/deploy an rpc style weblogic web service usingthe 'wsgen'
Ant task and the build.xml scripts provided with the samples. I getthis error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>
-----------------------------------------------------------------<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
This is a known bug which is fixed in WLS 6.1 SP2.
<p>The workaround is to change the complex data types
<br>to have more than one level package names.
<p>for eg: change ....
<p><font color="#3366FF">package foo;</font>
<br>class Data{}
<p>to :
<p><font color="#3333FF">package foo.bar;</font>
<br>class Data{}
<p>-manoj
<p>Praveen wrote:
<blockquote TYPE=CITE>Hi
<br>I am trying to assemble/deploy an rpc style weblogic web service
using
the 'wsgen'
<br>Ant task and the build.xml scripts provided with the samples. I get
this error:
<br>Please help
<br>Thanks,
<br>Praveen
<br>-----------------------------------------------------------------
<br>C:\test>ant
<br>Buildfile: build.xml
<p>webservice:
<p>clean:
<br>   [delete] Deleting directory C:\test\build
<p>init:
<br>    [mkdir] Created dir: C:\test\build
<br>    [mkdir] Created dir: C:\test\build\META-INF
<br>     [copy] Copying 5 files to C:\test\build\META-INF
<p>compile_ejb:
<br>    [javac] Compiling 5 source files to C:\test\build
<p>jar_ejb:
<br>      [jar] Building jar: C:\test\a_statelessSession.jar
<p>ejbc:
<p>all:
<p>wsgen:
<br>Error at line:8 col:12 ':' Already got a ':' in name
<br>        at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
<br>on(SAXElementFactory.java:60)
<br>        at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
<br>        at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
<br>EventStream.java:28)
<br>        at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
<br>        at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
<br>        at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
<br>)
<br>        at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
<br>:1125)
<br>        at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
<br>)
<br>        at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
<br>a:1415)
<br>        at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
<br>        at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
<br>        at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
<br>        at org.apache.tools.ant.Target.execute(Target.java:153)
<br>        at org.apache.tools.ant.Project.runTarget(Project.java:898)
<br>        at org.apache.tools.ant.Project.executeTarget(Project.java:536)
<br>        at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
<br>        at org.apache.tools.ant.Target.execute(Target.java:153)
<br>        at org.apache.tools.ant.Project.runTarget(Project.java:898)
<br>        at org.apache.tools.ant.Project.executeTarget(Project.java:536)
<br>        at org.apache.tools.ant.Project.executeTargets(Project.java:510)
<br>        at org.apache.tools.ant.Main.runBuild(Main.java:421)
<br>        at org.apache.tools.ant.Main.main(Main.java:149)
<p>BUILD SUCCESSFUL
<p>Total time: 34 seconds
<p>C:\test>
<br>-----------------------------------------------------------------</blockquote>
</html>

RPC style web service client

hi,
i am new to web service technology. i want to create dynamic web service client for a "rpc" style web service in Netbeans.
please, can anybody guide me for this?
thanks in advance.

Hi,
To avoid creating new topic I will put my question here.
I try to create new web service (rpc-style) client in netbeans. I have rpc plugin installed. In ejb module node I right click > new > web service client >
I fill all filds, chose rpc-style and > after clicking finish - error occur:java.lang.LinkageError: com/sun/xml/rpc/processor/generator/Names
     at org.netbeans.modules.websvc.registry.util.Util.getParameterType(Util.java:856)
     at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.printOperations(WrapperClientWriter.java:275)
     at org.netbeans.modules.websvc.registry.jaxrpc.WrapperClientWriter.writeClass(WrapperClientWriter.java:219)
     at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.createWrapperClients(Wsdl2Java.java:305)
     at org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java.execute(Wsdl2Java.java:229)
     at org.netbeans.modules.websvc.registry.util.Util.createWSJar(Util.java:493)
     at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:221)
     at org.netbeans.modules.websvc.registry.RegistryViewImpl.registerService(RegistryViewImpl.java:159)
     at org.netbeans.modules.websvc.registry.netbeans.RegisterViewImplNetBeansSide.registerService(RegisterViewImplNetBeansSide.java:91)
     at org.netbeans.modules.websvc.jaxrpc.client.wizard.ClientBuilder.generate(ClientBuilder.java:330)
     at org.netbeans.modules.websvc.jaxrpc.client.wizard.JaxRpcClientCreator$2.run(JaxRpcClientCreator.java:319)
     at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
I use netbeans 6.5. In my project I choose java ee 5 as in 1.4 there is no web service client option
Any ideas?
I found some rpc tutorils for netbeans 4.0 but I wonder why it couldn't be done in netbean 6.5
Regards,
Lech

RPC Style webservice

Hi Experts,
Could you please tell how to create RPC Style webservice from XI or SAP R/3 System?
Regards
Sara

Hi Sara !
Are you talking about this:
/people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi
Regards,
Matias

Differences between Document Style vs RPC style WS.

Hello All,
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received.
In either way of writing services using JAX-WS, I currently annotate the service with @Webservice, generage the WSDL and from that WSDL I generate the client side artifacts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here.

user13126996 wrote:
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received. no, asynchronous vs. synchronous responses have nothing to do with rpc style vs. document style. they are two orthogonal concepts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.the difference is basically in how the data is encoded over the transport layer. in theory, you can encode some complex data structures more efficiently in the rpc style. in reality, no one ever uses these features. and since the document style is more strongly typed and much more "straightforward", most people tend to prefer the document style to the rpc style these days. (in fact, i don't think jaxws actually supports rpc style).
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here. none really. SOAP over HTTP is XML over HTTP. XML over HTTP has no strong specification, whereas SOAP puts lots of specs around what the XML should look like. also, obviously, SOAP can theoretically be sent over other transport layers besides HTTP (not that i've ever seen that).

An RPC-style message

Similar Messages

Maybe you are looking for