yes, I want to unsubscribe
.
thanks,
nandana
[1] - http://www.packtpub.com/article/handler-and-phase-in-apache-axis
On Sat, Oct 25, 2008 at 4:17 AM, Mary Thompson [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I ran into the same problem when I switched to ws-policy. First I
had to add the security phase
causing it to be ignored.
I wonder if the piece of code that insists you add a security phase when
you don't want any security is wrong. Or if there is some way to
indicate a null security phase.
Mary Thompson
RonnieMJ wrote:
Ok I added an axis2.xml file in my repo, however commenting out
Thanks, Nandana,
With the help of a working example, I was eventually able to figure
out what I had done wrong. It was error in the policy that I was
attempting to attach to the message that caused it to be ignored.
I also learned a lot studying the various WS02 tutorials on this and
Nandana,
Your example services looks like mine except for the inclusion of the
rampart encryption stuff and the fact that I pass the x509 certificate
in the message.
I write both a services.xml and OSCARS.wsdl and then use wsdl2java. As
a side effect a new services.xml and OSCARS.wsdl are
Nandana,
Your example works correctly in my tomcat/axis environment. Now I
just have to figure out why mine doesn't. Maybe there is something
missing in our service skeleton class.
Mary
Nandana Mihindukulasooriya wrote:
Hi,
I've tried it with SignedSupportingTokens (or even just
how.
I'm using axis 1.4.1 and the Rampart nightly build from Oct 1 .
Mary Thompson
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
and it worked for
me with Axis2 1.4.1. http://1.4.1. If the message level policies are
not attached to the stub correctly, it is a bug that should be fixed.
thanks,
nandana
On Thu, Oct 2, 2008 at 7:38 AM, Mary Thompson [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
When switching to ws
to add the message specific stuff (e.g. sp:SignedParts), but
it would be nice if wsld2java did it all.
Mary Thompson
-
Mary R. Thompson[EMAIL PROTECTED]
Lawrence Berkeley National Lab
past this, I think I will be
on my way.
Thanks.
Steve
Mary Thompson wrote:
If you mean axis2 1.4, the Rampart module will do that for you. The
Axis pages link to some documentation and to the rampart 1.3 module.
Go to http://ws.apache.org/rampart/download/1.4/download.cgi for
rampart 1.4
is
rejected for a missing timestamp.
I'm running with Java 1.5.0_16, Mac OS X 10.4.11
Mary Thompson
-
Mary R. Thompson[EMAIL PROTECTED]
Lawrence Berkeley National Lab http
If you mean axis2 1.4, the Rampart module will do that for you. The Axis
pages link to some documentation and to the rampart 1.3 module. Go to
http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4
and more documentation.
After you have read the overviews, look at the
for Thilana]
You could go to the jira page and vote for it and the WSCOMMONS bug :-)
Mary
thanks
Rishi
On 1/2/07, *Mary Thompson* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Yes you do need Rampart 1.1. I have been using rampart 1.1 with the
nightly builds for about a month now
the release
notes give a clue as to what bugs have been fixed. A reference to the
specific jira's would be great.
Mary Thompson
Previous mail about the version bug
Hi Gul;
Yes we a had a problem in 1.1 release with HTTPS , but now we have fixed
th issue
the soap 1.1 fault message
handling. There is a jira about this, AXIS2-1643. The cause is evidently
caused by a bug in WSCOMMONS-104.
Using SOAP 1.2 gets around this.
Mary Thompson
Rishi krish wrote:
Hi
I have downloaded the axis2 1.1.1 rc1 and I have some setup questions:
1What version
Javier,
Did you ever figure this out? There is a faulthandling example in the
axis2-1.1 release that generates code that looks like yours and does
work. I have also been using the same wsdl/code pattern with success.
My cases all fail as soon as I engage the rampart1.1 module on the
client
] at
example.BankServiceStub.withdraw(BankServiceStub.java:173)
[java] at example.BankClient.main(BankClient.java:59)
It seems like it is caused by some confusion of classes, but I haven't
figured which ones yet.
Mary Thompson
-
Mary R
/browse/WSCOMMONS-104
If you can use SOAP 1.2 then this issue can be avoided.
Thanks,
Ruchith
On 12/16/06, Mary Thompson [EMAIL PROTECTED] wrote:
I have been fighting with SoapFaults failing to parse once rampart 1.1
is deployed ever since I moved to Axis2.1.1. It did work in axis2.1.0.
I am
I finally narrowed it down to an interaction with enumerated types and
rampart.1.1-RC1. I have submitted a JIRA under the component Modules
Mary Thompson
Davanum Srinivas wrote:
Mary,
Please create an issue in JIRA and upload your wsdl and sample
service/client.
thanks,
dims
On 11/29/06
. setclasspath.sh
java -Daxis2.xml=repo/axis2.xml QueryReservationClient repo
https://domain.name/axis2-1.1.1/services/OSCARS
where the repo/modules contains the rampart.mar, and repo contains the
sec.properties and jks files.
Mary Thompson
Ruchith,
I picked up the rampart-1.1.RC1 release and am having library
problems. I have copies of wss4j-SNAPSHOT.jar and bcprov.jar in my
service.aar file because my application needs them. I copied the
versions of those jars from the rampart-1.1-RC1.mar and put them in my
aar file.
Ever since I switched to axis2-1-1 my client stubs have generated the
following exception whenever they receive a soap fault from the server.
(the stub code is generated by WSDL2java)
OSCARSStub threw exception
org.apache.axiom.om.impl.llom.OMElementImpl
java.lang.ClassCastException:
One more thing that broke when I moved from 2.1 to 2.1.1. In 2.1
enumerated types based on strings were just treated as ordinary strings.
In 2.1.1 a class was created (by wsdl2java) for each enumerated type and
the values were checked. So far, an improvement. But when the type is
put in or out
trouble with Axis2.1-1 recognizing the operations in the
second service.
Mary Thompson
fer wrote:
Hi all!
I have a service with more than one operation. I´m trying to assign
different flows (request and response) to this operations in this way:
(client-config.wsdd)
service name=serviceName
24 matches
Mail list logo
