getting incoming soap message as string - weblogic.developer.interest.webservices.general(Archived)

I am developing a weblogic web service for WLS9.2.2 and I need to access the soap message directly inside a web-service method. Any ideas on how to do this? Which classes I should be looking at?

Related

document/literal web service

Currently I deployed an rpc/encoded ejb web service.
The ejb handles the request and response using Java methods. I can change this web service to document/literal by changing the style=document in Servicegen. Does this mean that I have to handle the
SOAP/XML message programmatically? In other words, more work on my part. Any input would be much appreciated.
Micx

Question on SOAP Handler

Hi all,
I developed a webservice using SLSB as point of entry. SLSB, has two methods one
for Online Req and other for Batch requests.
Now I need access to SOAP header. So I am now implementing a message Handler.
My questions is this:
I want the same two methods in SLSB exposed to the clients, without them knowing
I have put a SOAP Handler.
How to do this? Just implementing the SOAP Handler and calling the SLSB takes
care of this.
In other words I want WSDL file look same.
Any info will be appreciated.
I am on WLS 7.0 Sp2.
Thanks
---Radhe
Hi Radhe,
The fact that you are using a Handler will not appear in the WSDL, but the description
of the XML schema types that make up the SOAP header elements will. This is so
the Web Services stack that consumes your WSDL, knows which web service operations
use SOAP headers, and which don't. Without this information, the web service consumer's
Web Services stack, won't be able to generate a proper SOAP request.
Regards,
Mike Wooten
"Radhe" <adsfdsl#djkslk.com> wrote:
>
Hi all,
I developed a webservice using SLSB as point of entry. SLSB, has two
methods one
for Online Req and other for Batch requests.
Now I need access to SOAP header. So I am now implementing a message
Handler.
My questions is this:
I want the same two methods in SLSB exposed to the clients, without them
knowing
I have put a SOAP Handler.
How to do this? Just implementing the SOAP Handler and calling the SLSB
takes
care of this.
In other words I want WSDL file look same.
Any info will be appreciated.
I am on WLS 7.0 Sp2.
Thanks
---Radhe

Accepting a SOAP message that contains fault elements

Hi,
I am trying to create a webservice that will accept a valid soap messages that
contains faults. Actual functionality required is to accept a valid soap message
with or without faults. For this, I created separate methods in my java class
(one for normal flow and one that will handle fault elements) that implements
my web service. I need to manipulate the soap message for both cases. Hence, I
created separate handlers to do this task. I created two handler chains in my
web-services.xml one for handling soap messages that contains faults and one for
handling soap messages that doesn't contain faults. The web services was successfully
deployed and works fine for soap messages that doesn't contain fault. But, if
I send a soap message with faults the client (that calls my webservice) is not
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran
Hi Ganesh,
Which version of weblogic server you are using? Can you turn on verbose in
client side? You can give a "-Dweblogic.webservice.verbose=true" to client
side JVM. We need to see what your soap message with fault looks like.
Thanks,
-Neal
"Ganesh" <abinesh_2000#yahoo.com> wrote in message
news:3f0066eb#newsgroups.bea.com...
>
Hi,
I am trying to create a webservice that will accept a valid soap messagesthat
contains faults. Actual functionality required is to accept a valid soapmessage
with or without faults. For this, I created separate methods in my javaclass
(one for normal flow and one that will handle fault elements) thatimplements
my web service. I need to manipulate the soap message for both cases.Hence, I
created separate handlers to do this task. I created two handler chains inmy
web-services.xml one for handling soap messages that contains faults andone for
handling soap messages that doesn't contain faults. The web services wassuccessfully
deployed and works fine for soap messages that doesn't contain fault. But,if
I send a soap message with faults the client (that calls my webservice) isnot
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

EJB calling SOAP service

I'm experiencing a problem on 61.sp3.
I have an EJB that utilizes an API toolkit to access SOAP services on a
Tomcat server. The SOAP service sends back a SOAP exception which is
correct in what I am asking
in to do. However, the weblogic app server is returning a SOAP
exception to my EJB rather than passing the SOAP exception to the API
toolkit that I am using to make my SOAP calls.
Has anyone seen something like this?
Sandy Mustard

Are JWS Message Handlers possible?

Does anybody know if it is possible to implement SOAP message handlers for a
web services that had been developed using the Workshop BETA.
With the JWS files produced by workshop I am unable to get access to the
web-services.xml file where I would need to register a SOAP message handler
to get it to intercept the message.
Any idea if there is there a mechanism by which I can place the appropriate
<handler-chains>...</handler-chains> element within the dynamically created
JWS web service?
The reason for all this is that I am trying to implement a SAML
authentication mechanism and I wish to intercept and validate the SAML
ticket from the SOAP message header as the SOAP request comes in and
authenticate with the container so that all EJB calls are performed using
the credentials of the SOAP request.
Any pointers would be greatly appreciated....
Many thanks,
Martin.
Hi Martin,
javax.xml.rpc.handler.Handler is part of JAX-RPC, which is not currently being used
by WebLogic Workshop. The web-services.xml file is not currently used as a deployment
descriptor for a JWS-based web service. This being the case, I don't think you'll
be able to use the Handler framework with a JWS-based web service :-)
However, there may be a way to use a Web Application Filter (http://edocs.bea.com/wls/docs70/webapp/filters.html#165478),
in front of the servlet that WLS uses to handle the "*.jws" <url-pattern> :-) I haven't
looked lately, but I think this is the weblogic.knex.dispatcher.KnexServlet class.
You can verify all of this by referring to the web.xml files (in the exploded Web
Application that you are using).
BTW: The SAML thing you trying to do sounds "kool"! Nice to see folks out there "thinking
like that" :-)
Hope this helps,
Mike Wooten
"Martin Woodward" <martin#remove-this-woodwardweb.com> wrote:
Does anybody know if it is possible to implement SOAP message handlers for
a
web services that had been developed using the Workshop BETA.
With the JWS files produced by workshop I am unable to get access to the
web-services.xml file where I would need to register a SOAP message handler
to get it to intercept the message.
Any idea if there is there a mechanism by which I can place the appropriate
<handler-chains>...</handler-chains> element within the dynamically created
JWS web service?
The reason for all this is that I am trying to implement a SAML
authentication mechanism and I wish to intercept and validate the SAML
ticket from the SOAP message header as the SOAP request comes in and
authenticate with the container so that all EJB calls are performed using
the credentials of the SOAP request.
Any pointers would be greatly appreciated....
Many thanks,
Martin.

Categories

Resources