StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10905290
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-05T21:33:09.253
FavoriteCount
0
LastActivityDate
2015-09-21T12:20:38.327
LastEditDate
2015-09-21T12:20:38.327
LastEditorUserId
4824159
OwnerUserId
46716
ParentId
10855451
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
It looks as if the error isn't with the outbound request, but with handling the response. The response doesn't have a security header and when we're trying to unencrypt it, an exception occurs. I need to somehow change my Rampart configuration to only do outbound security, not inbound I'll report back :) <hr> Ok the problem was that once Rampart is engaged, it expects the response to have the same security header. The way I solved the problem was by removing the handler to the Inflow security in the Rampart.mar file. I'm not sure if this is the best fix, but it worked for us. To remove the inflow handler: Unpack the rampart.mar file Comment out the Inflow section Zip up the META_INF folder. Then rename the .zip file to be .mar Now when you use this as there are no handlers defined for inflow, it will just use the standard Axis2 response handler. I guess if you had several projects using Rampart where some had the security header in the response and some didn't you would need a different approach. <hr> Another approach is detailed here. It's probably a better approach : <a href="http://blog.rampartfaq.com/2009/11/how-to-generate-non-secure-response-to.html" rel="nofollow">http://blog.rampartfaq.com/2009/11/how-to-generate-non-secure-response-to.html</a> Exception: <blockquote> org.apache.axis2.AxisFault: Missing wsse:Security header in request at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99) at org.apache.axis2.engine.Phase.invoke(Phase.java:318) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAxis 2 and Rampart- why does service return wsse:Security header in request?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGribbler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAxis 2 and Rampart- why does service return wsse:Security header in request?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.