File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes Axis2/Rampart compatability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Axis2/Rampart compatability" Watch "Axis2/Rampart compatability" New topic
Author

Axis2/Rampart compatability

Bai Shen
Ranch Hand

Joined: Sep 24, 2008
Posts: 323
I'm creating a web service using Axis2 and I want to secure it with Rampart. My question is how compatible is this with other systems? Will I be able to hand the wsdl to someone and have them connect and authenticate without using Axis2 or Rampart?
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 39543
    
  27
Yes. The beauty of using standards like SOAP, WSDL and WS-Security is that you don't need the same software -or even the same language- on both ends of the connection.


Ping & DNS - updated with new look and Ping home screen widget
Bai Shen
Ranch Hand

Joined: Sep 24, 2008
Posts: 323
-nods- I knew that was the case with SOAP and WSDL, but I wasn't sure about the security part.
Bai Shen
Ranch Hand

Joined: Sep 24, 2008
Posts: 323
Also, how does the user know what the security settings are for Rampart? The WSDL doesn't change AFAIK, and the return messages aren't very helpful.

Also, I just sent a message with the wrong user name to my web service, and it gave back a 202 Accepted message. No indication that anything was wrong on the client side.

Do I have to give users all the implementation info for the security?
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 39543
    
  27
Also, I just sent a message with the wrong user name to my web service, and it gave back a 202 Accepted message. No indication that anything was wrong on the client side.

That doesn't sound right - it should result in an exception (and normally does). Make sure the server-side security handler class does the right thing.
Bai Shen
Ranch Hand

Joined: Sep 24, 2008
Posts: 323
Well, the server threw an exception, but nothing made it back to the client. I'm using the PWHandlerServer class from your examples.
Taariq San
Ranch Hand

Joined: Nov 20, 2007
Posts: 192
Originally posted by Bai Shen:
Well, the server threw an exception, but nothing made it back to the client. I'm using the PWHandlerServer class from your examples.


I think he means put in a breakpoint, or some logs to see what the code is doing.
Is it even being called at all?
Bai Shen
Ranch Hand

Joined: Sep 24, 2008
Posts: 323
Originally posted by Taariq San:


I think he means put in a breakpoint, or some logs to see what the code is doing.
Is it even being called at all?


It's being called, and throwing an exception on the server side. The problem is that on the client side, there's no way to tell the difference. The client gets back a 202 Accepted code whether there was an exception or not.
Taariq San
Ranch Hand

Joined: Nov 20, 2007
Posts: 192
Originally posted by Bai Shen:


It's being called, and throwing an exception on the server side. The problem is that on the client side, there's no way to tell the difference. The client gets back a 202 Accepted code whether there was an exception or not.


Can you use tcpmon and post the soap response from the server?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Axis2/Rampart compatability
 
Similar Threads
Programmatically setting user name with Rampart
Axis2: MTOM and Rampart
SSL in standalone axis2 1.4.1
Error implementing Rampart
Axis2, client handler not getting called