[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650889#action_12650889
]
Mary Thompson commented on AXIS2-4114:
--
There is still another case of NPE
In
OUT_FAULT_FLOW case it just
goes to RampartSender. I don't know if WSDoAllSender would have created
the axis message.
Mary Thompson
Nandana Mihindukulasooriya wrote:
Mary,
Yes, I applied the patch [1] and resolved the issue and it is in the
trunk. It seems we need to include s
point me to the right
way to do things?
Also are all the commits mailed to this list? I tried the wiki, but the
commit info there seems to have stopped after June 2008.
Thanks for any suggestions
Mary Thompson
-
Mary R. Tho
/browse/AXIS2-4065
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.4.1
Environment: java 1.5, mac os 1.4, rampart 1.4
Reporter: Mary Thompson
Priority: Minor
I am using ws-policy elements attached
[
http://issues.apache.org/jira/browse/AXIS2-1811?page=comments#action_12455380 ]
Mary Thompson commented on AXIS2-1811:
--
I had copied all the rampart jars into the axis server lib, but not the
client side. But I was not even engaging
[ http://issues.apache.org/jira/browse/AXIS2-1811?page=all ]
Mary Thompson updated AXIS2-1811:
-
Attachment: OSCARSSample.tar
wsdl, client and server code.
> Enumerated types fail to map into return messages when rampart-1.1 has been
> e
generated by Axis
2-1.1.1 wsdl2java.
Reporter: Mary Thompson
I have a service that returns an enumerated type. In the absence of the rampart
module, it works correctly, but once the rampart 1.1 module is engaged by axis2
it fails in the following way. It doesn't matter