I am trying to validate a signature produced using AXIS+WSS4J client.
The validation is performed by using AXIS+WSS4J on the provider side.
The signature is performed on the body element in soap message
However during signature validation process I am getting an error
"digest value mismatch". I t
Try this:
-Ted
-Original Message-
From: Nirmit Desai [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 2:35 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2 1.0] WSDL2Java: WSDL for operations without params
Hi
As I said, for unwrapped document style, you don't need to use a void
type. Instead, you should specify a message with no parts:
You should use WS-Addressing and the Action parameter to indicate the
method you want to invoke.
For a oneway message, you define an operation with an input mes
Hi William,
it creates a getScheduledReports.java in data bindings and puts that as the
parameter type of the method.
I suspect it is impossible to have it generate an empty parameter list for
methods in WSDL2Java. Maybe this is a bug.
-Nirmit
Hi, I implemented a web service by generating stub and
skeleton from wsdl. Now I want to turn them into stateful. I have been looking
through mailing list and found that I need to set service scope to soapsession
and store state in the service group context. I did set the service scope to
s
Hi Anne,
thanks a lot for a detailed response.
I am doing document/literal services in Axis2 ( I am assuming document and
unwrapped are identical). I start by defining a WSDL, doing WSDL2Java,
flesh out business logic and then deploy. But,
creates a VoidType.java during codeGen for me in ADB a
I am trying to debug an Axis client by turning on debug logging in
org.apache.axis.transport.http.HTTPSender to see the SOAP requests and
responses.
A SOAP fault I am getting as logged by Axis debug logging looks something
like this:
The actual complete SOAP response as requested from
This wouldn't give you the benefit of having the service pre-initialized
when the container starts. It would still have to initialize on first
request.
- Doug
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 10:23 PM
To: axis-user@ws.apa
All I can think of is that one of your handlers is munging the
message. Notice that the soapenv namespace declaration has also been
removed.
Anne
On 7/27/06, Faucher, Christian <[EMAIL PROTECTED]> wrote:
Greetings,
I have a Message-type Web Service, in which I look into the SOAPEnvelope to
r
I've never seen such a document. I do recommend using a WSDL authoring
tool, such as xmlspy, Sonic Stylus, or .
Guidelines for operations with no argument (input or output) will be
different depending on the message style, programming model, and
message exchange pattern (MEP) you're using.
Typic
Hi Ajith,
when I run the client I dont see any messages in the tcpmon may be coz
their is no message exchange yet between the client and server.
In my ClientRegistrationStub.java class I am getting exception at this point
private org.apache.axiom.soap.SOAPEnvelope toEnvelope(
org.apache
Hi all,
I was wondering if anyone has a pointer a good comprehensive WSDL authoring
guidelines.
For now, I am wondering how to write WASDL for an operation that doesn't
take any arguments. Or for an operation that returns void. I want these to
be asynchronous. I would like to call the void retur
Hello again.
I’ve read some old message on the list about ‘wsi:swaRef’,
and how map it to ‘javax.activation.DataHandler’ and not to ‘org.apache.axis.types.URI’,
but with no answer…
Is there any AXIS example of attachments in
document/literal form with ‘wsi:swaRef’ that maps to a mul
Hi ajith,
As you suggest me, I look into the code and I found
the exception is raised by the method:
if
(extraNamespaces!=null){ return
com.example.transfer_xsd.AnyXmlTypeInputParamDocument.Factory.parse(
param.getXMLStreamReaderWithoutCaching(), new
org.apache.xmlbean
Tony,
Absolutely +1. Please open a jira enhancement issue.
thanks,
dims
On 7/28/06, Tony Dean <[EMAIL PROTECTED]> wrote:
I think users will want an option (load-on-startup=on|off) to either load
scope="application" services on container startup or upon the first request. I
personally would
I think users will want an option (load-on-startup=on|off) to either load
scope="application" services on container startup or upon the first request. I
personally would want my service loaded and ready to go before the first
request is issued. Users will certainly be willing to take the hit w
Thanks Ruchith for the prompt response!
I thought that I can only add the parameters to the service and not to
each operation. Awesome! Will try this!
Thanks you
Carsten
Ruchith Fernando wrote:
> Hi Carsten,
>
> Yes this is possible.
>
> First the rampart configuration parameters MUST be includ
Hi Carsten,
Yes this is possible.
First the rampart configuration parameters MUST be included within the
"operation" element of the particular operation you want to secure.
Then you MUST add an action mapping into that particular operation to
specify the soapAction value to expect in the messag
Hi Harbath,
Which version of Axis2 are you using?
If(AXIS2_VERSION < 1.0){
// please switch to Axis2 1.0 or later
} else {
Seems there is a problem in the document. For the time being, you first
invoke the web service using SOAP call, then add the following line. You
will get REST invocation ov
Hi,Yep - it does - I am not really sure of the problem in your case though. Can you inspect the code inside the message receiver as to what it is trying to do ?On 7/28/06,
Fabien Couble <[EMAIL PROTECTED]> wrote:
Just for information,
is xmlbeans works properly with AXIS2?
- Original
Hi,
I have one service (wsdl) with several methods, but I want to secure
only one of them using ws-security. As far as I understand the current
configuration of rampart, I can only secure the whole service.
Is it possible to just secure a part? Or are there perhaps any workarounds?
Thanks
Carste
Just for information,
is xmlbeans works properly with AXIS2?
- Original Message -
From:
Fabien Couble
To: axis-user@ws.apache.org
Sent: Friday, July 28, 2006 9:36 AM
Subject: Re: [AXIS2] parsing
problem
I still have the same problem.
This is the exception raised:
Hi,
I am still struggeling to compile the REST POST sample contained in
the Axis2 docu page 'RESTful Web services Support', see
http://ws.apache.org/axis2/0_94/rest-ws.html.
I tried my best to add appropriate import statements, but failed.
My current imports are:
import org.apache.axis2.*;
Hello.
I’m trying to build a simple service with
attachment, and it seems a bit more difficult than I thought !
The first problem is not directly about axis but
eclipse WTP wsdl validator that rejects the multipartRelated section of my wsdl,
pretending that the is unexpected in the
michael mclaughlin schrieb:
would something like
import org.apache.axis2.userguide.xsd.*
make the sample files compile OK?
Yes, at least they *should* be ok then.
-Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Thanks, Christian.
Could you give me more details...would something like
import org.apache.axis2.userguide.xsd.*
make the sample files compile OK?
Mike
--- Christian Pöcher <[EMAIL PROTECTED]> wrote:
> michael mclaughlin schrieb:
> > * The problem comes when I fill in the skeleton
> > function
I still have the same problem.
This is the exception raised: (I forgot to join it
yesterday!)
http://schemas.xmlsoap.org/soap/envelope/">
/>soapenv:ClientData
binding
errororg.apache.axis2.AxisFault:
Data binding error; nested exception is: java.lang.RuntimeException:
Data binding error
27 matches
Mail list logo
