[jira] Closed: (AXIS2-4215) How can I add a namespace definition to SOAP Envelope

[ https://issues.apache.org/jira/browse/AXIS2-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-4215. Resolution: Invalid I believe you should be able to achieve this with

[jira] Commented: (AXIS2-4188) JMSSender not extendable

[ https://issues.apache.org/jira/browse/AXIS2-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12658950#action_12658950 ] David Illsley commented on AXIS2-4188: -- I could claim that it's that way to encourage

[jira] Closed: (AXIS2-3785) Axis2 1.4 ships servlet-api-2.3.jar which gives a conflict in Tomcat 6

[ https://issues.apache.org/jira/browse/AXIS2-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-3785. Resolution: Fixed Looks like the fix for AXIS2-3914 is still in head so resolving this as fixed.

[jira] Closed: (AXIS2-3946) Create a ws client from an xml document

[ https://issues.apache.org/jira/browse/AXIS2-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-3946. Resolution: Invalid Probably the simplest mechanism is a JAX-WS Dispatch client in message mode.

[jira] Closed: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ https://issues.apache.org/jira/browse/AXIS2-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-1327. Resolution: Fixed Incorrect operation selected when no SOAPAction specified

[jira] Commented: (AXIS2-4123) org.apache.axis2.AxisFault: First Element must contain the local name, Envelope

[ https://issues.apache.org/jira/browse/AXIS2-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657506#action_12657506 ] David Illsley commented on AXIS2-4123: -- Please let us know which exact version of

[jira] Closed: (AXIS2-2840) When there is an error on a response with a SeparateListener, the fault gets sent back with addressing marked none

[ https://issues.apache.org/jira/browse/AXIS2-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-2840. Resolution: Fixed Assignee: David Illsley (was: Deepal Jayasinghe) Fixed in r727497 When

[jira] Closed: (AXIS2-3944) conn't delete xml file OMElement WebService

[ https://issues.apache.org/jira/browse/AXIS2-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-3944. Resolution: Invalid This doesn't look like an Axis2/Axiom problem as it's a file handle that's

[jira] Closed: (AXIS2-3801) Incorrect HTTP response message on axis fault for in-only messages

[ https://issues.apache.org/jira/browse/AXIS2-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-3801. Resolution: Won't Fix This is intentional, and I don't think anything has changed since that

[jira] Closed: (AXIS2-2110) How to get WS-A info from transport layer

[ https://issues.apache.org/jira/browse/AXIS2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-2110. Resolution: Invalid The wsa:From value is available in the service. Try messageContext.getFrom()

[jira] Closed: (AXIS2-4002) AxisService.removeOperation does not remove action from invalidOperationsAliases

[ https://issues.apache.org/jira/browse/AXIS2-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-4002. Resolution: Fixed Assignee: David Illsley (was: Brian DePradine) Fixed in r727532

[jira] Commented: (AXIS2-3795) Unqualified SOAP Action no longer works

[ https://issues.apache.org/jira/browse/AXIS2-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595921#action_12595921 ] David Illsley commented on AXIS2-3795: -- It looks like there are 2 distinct problems

[jira] Commented: (AXIS2-3766) Maven POM has many dependencies that could well be declared optional

[ https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594290#action_12594290 ] David Illsley commented on AXIS2-3766: -- Alex, we use the geronimo jars at least in

[jira] Created: (AXIS2-3769) Reinstate the MessageContextChangeTest

Reinstate the MessageContextChangeTest -- Key: AXIS2-3769 URL: https://issues.apache.org/jira/browse/AXIS2-3769 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Reporter:

[jira] Commented: (AXIS2-3742) Use actaul message to determine the outbound wsa action

[ https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589110#action_12589110 ] David Illsley commented on AXIS2-3742: -- Jarek, this sounds good.. but are you planning

[jira] Commented: (AXIS2-3704) SOAP Action is not set by service Client when its invoked via a WSDL

[ https://issues.apache.org/jira/browse/AXIS2-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585609#action_12585609 ] David Illsley commented on AXIS2-3704: -- After a quick offline discussion with Brian, I

[jira] Resolved: (AXIS2-3683) AddressingOutHandler may omit wsa:To on 2004/08 despite it being mandatory

[ https://issues.apache.org/jira/browse/AXIS2-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-3683. -- Resolution: Fixed Fix Version/s: 1.4 Assignee: David Illsley Fixed in r643041

[jira] Created: (AXIS2-3683) AddressingOutHandler may omit wsa:To on 2004/08 despite it being mandatory

AddressingOutHandler may omit wsa:To on 2004/08 despite it being mandatory -- Key: AXIS2-3683 URL: https://issues.apache.org/jira/browse/AXIS2-3683 Project: Axis 2.0 (Axis2)

[jira] Commented: (AXIS2-3624) Addressing reference parameter issue

[ https://issues.apache.org/jira/browse/AXIS2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581935#action_12581935 ] David Illsley commented on AXIS2-3624: -- Deepal, If you have implementations of these

[jira] Commented: (AXIS2-3567) Support role/actor based mustUnderstand header processing

[ https://issues.apache.org/jira/browse/AXIS2-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575025#action_12575025 ] David Illsley commented on AXIS2-3567: -- Jeff, It's worth noting that the core engine

[jira] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559511#action_12559511 ] David Illsley commented on AXIS2-3449: -- My understanding was that it is a combination

[jira] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559526#action_12559526 ] David Illsley commented on AXIS2-3449: -- Hmm, there's WS-Policy, but I'm not sure

[jira] Resolved: (AXIS2-3283) No access to the operationContextMap in the ConfigurationContext class

[ https://issues.apache.org/jira/browse/AXIS2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-3283. -- Resolution: Fixed Fix Version/s: nightly Assignee: David Illsley (was: Deepal

[jira] Assigned: (AXIS2-2873) WS-Addressing EndpointReference elements not getting added in the outgoing soap message

[ https://issues.apache.org/jira/browse/AXIS2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reassigned AXIS2-2873: Assignee: David Illsley (was: Amila Chinthaka Suriarachchi) WS-Addressing

[jira] Resolved: (AXIS2-2873) WS-Addressing EndpointReference elements not getting added in the outgoing soap message

[ https://issues.apache.org/jira/browse/AXIS2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2873. -- Resolution: Fixed Fix Version/s: nightly This should be fixed in the latest nightly.

[jira] Resolved: (AXIS2-3150) AddressingValidationHandler requires MessageId Header also with Final Namespace

[ https://issues.apache.org/jira/browse/AXIS2-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-3150. -- Resolution: Won't Fix Assignee: David Illsley Matthias, If you read a little further to

[jira] Commented: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512961 ] David Illsley commented on AXIS2-2895: -- Apologies, that was me, I'd forgotten I'd lent Tom my laptop!. David

[jira] Commented: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512965 ] David Illsley commented on AXIS2-2895: -- Nick, Thanks, sorry, I just read the comment and didn't look closely

[jira] Commented: (AXIS2-2829) WSA None handling incorrect

[ https://issues.apache.org/jira/browse/AXIS2-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509042 ] David Illsley commented on AXIS2-2829: -- Paul, Are you using vanilla Axis2, or is it using a non-standard

[jira] Commented: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ https://issues.apache.org/jira/browse/AXIS2-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509044 ] David Illsley commented on AXIS2-1327: -- Dims, I no longer know what the problem is here. The incorrect dispatch

[jira] Commented: (AXIS2-2110) How to get WS-A info from transport layer

[ https://issues.apache.org/jira/browse/AXIS2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509045 ] David Illsley commented on AXIS2-2110: -- John, Please add sender.gngageModule(addressing); to your client code

[jira] Assigned: (AXIS2-2876) ReplyTo header (wsa submission) is always set to anonymous in fire-and-forget messages

[ https://issues.apache.org/jira/browse/AXIS2-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reassigned AXIS2-2876: Assignee: Brian DePradine (was: David Illsley) Brian, I think you have more of a grasp of

[jira] Commented: (AXIS2-2830) Premature Optimization of ReplyTo = Anon

[ https://issues.apache.org/jira/browse/AXIS2-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506881 ] David Illsley commented on AXIS2-2830: -- Paul, I agree. Brian, will you object if I make the change? David

[jira] Closed: (AXIS2-948) Extract and support wsaw:Anonymous values

[ https://issues.apache.org/jira/browse/AXIS2-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-948. --- Resolution: Won't Fix Thw wsaw:Anonymous element has been removed from the spec, so I won't bem

[jira] Commented: (AXIS2-2615) integration module needs a working m2 pom.xml

[ https://issues.apache.org/jira/browse/AXIS2-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502235 ] David Illsley commented on AXIS2-2615: -- Hi Dims, We're nearly there, all that was left to do (last week,

[jira] Resolved: (AXIS2-2721) axis 2.0 parent jar missing on ibiblio.org for maven 2

[ https://issues.apache.org/jira/browse/AXIS2-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2721. -- Resolution: Invalid Assignee: David Illsley There is no axis2-parent jar, it's a maven2

[jira] Commented: (AXIS2-2721) axis 2.0 parent jar missing on ibiblio.org for maven 2

[ https://issues.apache.org/jira/browse/AXIS2-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499834 ] David Illsley commented on AXIS2-2721: -- I'd characterise it more as suggesting that people walk on top of a

[jira] Created: (AXIS2-2719) PolicyReference can't be resolved from the binding level in a WSDL 1.1 File

PolicyReference can't be resolved from the binding level in a WSDL 1.1 File --- Key: AXIS2-2719 URL: https://issues.apache.org/jira/browse/AXIS2-2719 Project: Axis 2.0 (Axis2)

[jira] Updated: (AXIS2-2719) PolicyReference can't be resolved from the binding level in a WSDL 1.1 File

[ https://issues.apache.org/jira/browse/AXIS2-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley updated AXIS2-2719: - Attachment: PolicyTest.wsdl Driver.java Simple testcase which demonstrates the

[jira] Commented: (AXIS2-2657) Addressing Issue :Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.

[ https://issues.apache.org/jira/browse/AXIS2-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495977 ] David Illsley commented on AXIS2-2657: -- Could you provide the request message captured using tcpmon. That

[jira] Commented: (AXIS2-2657) Addressing Issue :Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.

[ https://issues.apache.org/jira/browse/AXIS2-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495729 ] David Illsley commented on AXIS2-2657: -- That suggests that the addressing isn't being found. Can you look at

[jira] Commented: (AXIS2-2657) Addressing Issue :Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.

[ https://issues.apache.org/jira/browse/AXIS2-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495170 ] David Illsley commented on AXIS2-2657: -- Please ensure that the addressing module is engaged... Try something

[jira] Commented: (AXIS2-2511) Response invalidly delivered even ReplyTo is absent in Header

[ https://issues.apache.org/jira/browse/AXIS2-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490833 ] David Illsley commented on AXIS2-2511: -- Hi Gee, My reading of the submission spec has always been a bit

[jira] Commented: (AXIS2-2569) Cyclic depedency to axis2-mar-maven-plugin from the maven2 build ??

[ https://issues.apache.org/jira/browse/AXIS2-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490249 ] David Illsley commented on AXIS2-2569: -- Yep, this is a problem and why the initial maven2 build files I did

[jira] Commented: (AXIS2-2569) Cyclic depedency to axis2-mar-maven-plugin from the maven2 build ??

[ https://issues.apache.org/jira/browse/AXIS2-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490255 ] David Illsley commented on AXIS2-2569: -- Sorry, I meant it would be easy to separate out the build process for

[jira] Commented: (AXIS2-2569) Cyclic depedency to axis2-mar-maven-plugin from the maven2 build ??

[ https://issues.apache.org/jira/browse/AXIS2-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490318 ] David Illsley commented on AXIS2-2569: -- The problem is that the mar defines a packaging format which maven

[jira] Closed: (AXIS2-2361) oldMsgCtx 'From' does not copied to newMsgCtx 'From' when the MEP is IN_OUT

[ https://issues.apache.org/jira/browse/AXIS2-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-2361. Resolution: Won't Fix The current WS-Addressing spec does not define any copying of the wsa:From

[jira] Closed: (AXIS2-2350) AddressingValidation prevents other dispatchers from executing

[ https://issues.apache.org/jira/browse/AXIS2-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-2350. Resolution: Fixed Glen fixed this a while back see AddressingConstants.ADDR_VALIDATE_ACTION

[jira] Created: (AXIS2-2359) PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger

PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger Key: AXIS2-2359 URL: https://issues.apache.org/jira/browse/AXIS2-2359 Project: Axis 2.0 (Axis2)

[jira] Resolved: (AXIS2-2359) PERF: AddressingOutHandler.WSAHeaderHandler does not need its own logger

[ https://issues.apache.org/jira/browse/AXIS2-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2359. -- Resolution: Fixed Fixed in SVN r520799 PERF: AddressingOutHandler.WSAHeaderHandler does not

[jira] Created: (AXIS2-2345) EndpointReference.readObject doesn't close the stream or reader created which causes a memory leak.

EndpointReference.readObject doesn't close the stream or reader created which causes a memory leak. --- Key: AXIS2-2345 URL:

[jira] Resolved: (AXIS2-2345) EndpointReference.readObject doesn't close the stream or reader created which causes a memory leak.

[ https://issues.apache.org/jira/browse/AXIS2-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2345. -- Resolution: Fixed Fixed in SVN r 519926 EndpointReference.readObject doesn't close the

[jira] Resolved: (AXIS2-2291) Unable to set the action for a Fault message generated when throwing an AxisFault

[ https://issues.apache.org/jira/browse/AXIS2-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2291. -- Resolution: Fixed Fix Version/s: nightly FIx in SVN r517730 Unable to set the action

[jira] Closed: (AXIS2-2039) Allow WS-* protocol faults to be thrown to client code with clearer messages

[ https://issues.apache.org/jira/browse/AXIS2-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley closed AXIS2-2039. Resolution: Fixed Fix Version/s: nightly I put the code in for this a while back. It's used

[jira] Resolved: (AXIS2-2070) sendRobust throws null pointer exception when a fault is reported from ws

[ https://issues.apache.org/jira/browse/AXIS2-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2070. -- Resolution: Fixed Fix Version/s: nightly I've just committed the fix to svn r517216

[jira] Assigned: (AXIS2-2291) Unable to set the action for a Fault message generated when throwing an AxisFault

[ https://issues.apache.org/jira/browse/AXIS2-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reassigned AXIS2-2291: Assignee: David Illsley Unable to set the action for a Fault message generated when

[jira] Resolved: (AXIS2-2147) Class cast exception due to overloaded use of a constant

[ https://issues.apache.org/jira/browse/AXIS2-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-2147. -- Resolution: Fixed Assignee: David Illsley Fix in SVN r510896 Class cast exception due

[jira] Commented: (AXIS2-2154) org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests fails on Solaris

[ https://issues.apache.org/jira/browse/AXIS2-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472735 ] David Illsley commented on AXIS2-2154: -- Trace from last week at [1] (For some reason, everything is traced

[jira] Commented: (AXIS2-2070) sendRobust throws null pointer exception when a fault is reported from ws

[ https://issues.apache.org/jira/browse/AXIS2-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469372 ] David Illsley commented on AXIS2-2070: -- Initial Analysis: The RobustOperationClient is sending a message

[jira] Commented: (AXIS2-1585) findService () implementation for SOAPActionBasedDispatcher

[ https://issues.apache.org/jira/browse/AXIS2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469083 ] David Illsley commented on AXIS2-1585: -- I'm -1 to the patch.txt because it does the same thing that was

[jira] Resolved: (AXIS2-1834) AddressingBasedDispatcher doesn't dispatch according to the wsa:Action

[ https://issues.apache.org/jira/browse/AXIS2-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-1834. -- Resolution: Won't Fix I don't believe that dispatching the service based on the action is the

[jira] Created: (AXIS2-2039) Allow WS-* protocol faults to be thrown to client code with clearer messages

Allow WS-* protocol faults to be thrown to client code with clearer messages Key: AXIS2-2039 URL: https://issues.apache.org/jira/browse/AXIS2-2039 Project: Axis 2.0 (Axis2)

[jira] Assigned: (AXIS2-1972) Enable Sandesha to control reliable sync 2-way clients

[ https://issues.apache.org/jira/browse/AXIS2-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reassigned AXIS2-1972: Assignee: David Illsley Enable Sandesha to control reliable sync 2-way clients

[jira] Assigned: (AXIS2-1969) SOAPAction based routing does not route correctly based on wsdl:binding/wsdl:operation/soap:operation soapAction

[ https://issues.apache.org/jira/browse/AXIS2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reassigned AXIS2-1969: Assignee: David Illsley I just ran into this as well. Looks like a pretty simple fix...

[jira] Resolved: (AXIS2-1969) SOAPAction based routing does not route correctly based on wsdl:binding/wsdl:operation/soap:operation soapAction

[ https://issues.apache.org/jira/browse/AXIS2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-1969. -- Resolution: Fixed Put a simple fix to add calls to mapActionToOperation when soapAction is

[jira] Reopened: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ https://issues.apache.org/jira/browse/AXIS2-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley reopened AXIS2-1327: -- Hi, sorry I've not been keeping up with JIRA for the last couple of weeks so I missed this. I

[jira] Commented: (AXIS2-1879) Deploying services on the client side

[ http://issues.apache.org/jira/browse/AXIS2-1879?page=comments#action_12458968 ] David Illsley commented on AXIS2-1879: -- I'm sorry, I'm a little confused... how would client code use these 'client deployed' aars? Deploying services on

[jira] Closed: (AXIS2-1870) Enable the WS-RM anonymous URI template

[ http://issues.apache.org/jira/browse/AXIS2-1870?page=all ] David Illsley closed AXIS2-1870. Resolution: Fixed Applied patch in r487151 The patch looked reasonable and reinforces the discussion in the WS-A Working Group about the problems of having

[jira] Updated: (AXIS2-1564) Incoming SOAPFault on client side flows though InFlow *and* InFaultFlow

[ http://issues.apache.org/jira/browse/AXIS2-1564?page=all ] David Illsley updated AXIS2-1564: - Attachment: AXIS2-1564.patch Here's a patch that I think fixes the issue. However, it does cause a test failure in

[jira] Commented: (AXIS2-1834) AddressingBasedDispatcher doesn't dispatch according to the wsa:Action

[ http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456045 ] David Illsley commented on AXIS2-1834: -- Hi, Thanks for the patch. I've had a quick look and have a couple of thoughts: 1. Why is service dispatch based on

[jira] Commented: (AXIS2-1834) AddressingBasedDispatcher doesn't dispatch according to the wsa:Action

[ http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456107 ] David Illsley commented on AXIS2-1834: -- OK. I'm totally in favour of a fix for AXIS2-1665 but totally against the approach put forward in this issue which I

[jira] Created: (AXIS2-1829) Threading problem with SOAPMessageBodyBasedDispatcher

Threading problem with SOAPMessageBodyBasedDispatcher - Key: AXIS2-1829 URL: http://issues.apache.org/jira/browse/AXIS2-1829 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug

[jira] Updated: (AXIS2-1829) Threading problem with SOAPMessageBodyBasedDispatcher

[ http://issues.apache.org/jira/browse/AXIS2-1829?page=all ] David Illsley updated AXIS2-1829: - Attachment: AXIS2-1829-patch.txt Patch to fix issue on 1.1 branch Threading problem with SOAPMessageBodyBasedDispatcher

[jira] Closed: (AXIS2-1829) Threading problem with SOAPMessageBodyBasedDispatcher

[ http://issues.apache.org/jira/browse/AXIS2-1829?page=all ] David Illsley closed AXIS2-1829. Resolution: Fixed Committed fix to branch r482655 per comment from Dims Threading problem with SOAPMessageBodyBasedDispatcher

[jira] Closed: (AXIS2-1764) Improve trace for the Handler.InvocationResponse class

[ http://issues.apache.org/jira/browse/AXIS2-1764?page=all ] David Illsley closed AXIS2-1764. Resolution: Fixed Patch applied Improve trace for the Handler.InvocationResponse class --

[jira] Closed: (AXIS2-1517) The org.apache.axis2.handlers.addressing.AddressingHandler class provides nothing of value and the code should be refactored to allow it to be deleted

[ http://issues.apache.org/jira/browse/AXIS2-1517?page=all ] David Illsley closed AXIS2-1517. Fix Version/s: nightly Resolution: Fixed The org.apache.axis2.handlers.addressing.AddressingHandler class provides nothing of value and the code

[jira] Closed: (AXIS2-1159) Explicit ReplyTo should not be set on responses unless SOAP Session Scope has been enabled

[ http://issues.apache.org/jira/browse/AXIS2-1159?page=all ] David Illsley closed AXIS2-1159. Fix Version/s: nightly Resolution: Fixed Explicit ReplyTo should not be set on responses unless SOAP Session Scope has been enabled

[jira] Assigned: (AXIS2-1517) The org.apache.axis2.handlers.addressing.AddressingHandler class provides nothing of value and the code should be refactored to allow it to be deleted

[ http://issues.apache.org/jira/browse/AXIS2-1517?page=all ] David Illsley reassigned AXIS2-1517: Assignee: David Illsley The org.apache.axis2.handlers.addressing.AddressingHandler class provides nothing of value and the code should be refactored

[jira] Commented: (AXIS2-1457) RequestURIBasedDispatcher incorrectly resolves the WS-RM operations

[ http://issues.apache.org/jira/browse/AXIS2-1457?page=comments#action_12445104 ] David Illsley commented on AXIS2-1457: -- I committed slight modifications of these patches to trunk a couple of days ago. I included AXIS2-1457 in the first

[jira] Assigned: (AXIS2-1457) RequestURIBasedDispatcher incorrectly resolves the WS-RM operations

[ http://issues.apache.org/jira/browse/AXIS2-1457?page=all ] David Illsley reassigned AXIS2-1457: Assignee: David Illsley RequestURIBasedDispatcher incorrectly resolves the WS-RM operations

[jira] Commented: (AXIS2-1457) RequestURIBasedDispatcher incorrectly resolves the WS-RM operations

[ http://issues.apache.org/jira/browse/AXIS2-1457?page=comments#action_12444325 ] David Illsley commented on AXIS2-1457: -- I agree that separating out the dispatch of services and operations entirely is probably the cleanest solution to

[jira] Closed: (AXIS2-1282) wsa:Action setting in client side

[ http://issues.apache.org/jira/browse/AXIS2-1282?page=all ] David Illsley closed AXIS2-1282. Resolution: Fixed Fix in SVN r465527 wsa:Action setting in client side - Key: AXIS2-1282

[jira] Assigned: (AXIS2-1282) wsa:Action setting in client side

[ http://issues.apache.org/jira/browse/AXIS2-1282?page=all ] David Illsley reassigned AXIS2-1282: Assignee: David Illsley wsa:Action setting in client side - Key: AXIS2-1282 URL:

[jira] Commented: (AXIS2-1282) wsa:Action setting in client side

[ http://issues.apache.org/jira/browse/AXIS2-1282?page=comments#action_12443224 ] David Illsley commented on AXIS2-1282: -- OK, I'm not keen on having preferences to enable bugs in general but I appreciate the request so how about the

[jira] Commented: (AXIS2-1376) Use of ReplyTo in session mechanism considered harmful

[ http://issues.apache.org/jira/browse/AXIS2-1376?page=comments#action_12442534 ] David Illsley commented on AXIS2-1376: -- Glen, With regards to using the anonymous address, I believe that Brian changed that recently so that in the 2005/08

[jira] Commented: (AXIS2-1347) Review WSDL 1.1 Binding Extension for SOAP 1.2 and SOAP 1.1 Binding for MTOM 1.0

[ http://issues.apache.org/jira/browse/AXIS2-1347?page=comments#action_12441754 ] David Illsley commented on AXIS2-1347: -- I think (need to check) the WSDL4J 1.6 update may have introduced support for the SOAP 1.2 extension which may help.

[jira] Commented: (AXIS2-948) Extract and support wsaw:Anonymous values

[ http://issues.apache.org/jira/browse/AXIS2-948?page=comments#action_12441767 ] David Illsley commented on AXIS2-948: - No it isn't, the WG is still working on a solution. David Extract and support wsaw:Anonymous values

[jira] Assigned: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ http://issues.apache.org/jira/browse/AXIS2-1327?page=all ] David Illsley reassigned AXIS2-1327: Assignee: David Illsley I'm pretty familiar with this code so I'll take a look. Incorrect operation selected when no SOAPAction specified

[jira] Resolved: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ http://issues.apache.org/jira/browse/AXIS2-1327?page=all ] David Illsley resolved AXIS2-1327. -- Resolution: Fixed I've added code to ignore empty actionMapping elemenets and to reduce the chances of one being generated. trunk: r454186 branch: r454188

[jira] Commented: (AXIS2-1282) wsa:Action setting in client side

[ http://issues.apache.org/jira/browse/AXIS2-1282?page=comments#action_12439748 ] David Illsley commented on AXIS2-1282: -- There are 4 options which spring to mind for what we can do in the client when there is no action available: 1. Send

[jira] Commented: (AXIS2-1263) WS-Addressing Interop tests are failing

[ http://issues.apache.org/jira/browse/AXIS2-1263?page=comments#action_12439625 ] David Illsley commented on AXIS2-1263: -- I'd be happy to help given my experience with the test suite. Can you publish the application you used somewhere so I

[jira] Updated: (AXIS2-1227) [RPC] Deserializing a array parameter is invalid

[ http://issues.apache.org/jira/browse/AXIS2-1227?page=all ] David Illsley updated AXIS2-1227: - Component/s: (was: Addressing) Moving to component 'Unknown' as this doesn't look addressing related [RPC] Deserializing a array parameter is invalid

[jira] Commented: (AXIS2-1162) Build Failure: testScenarioOne(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest): Caused an ERROR

[ http://issues.apache.org/jira/browse/AXIS2-1162?page=comments#action_12434912 ] David Illsley commented on AXIS2-1162: -- Sorry I missed that out. Java: [EMAIL PROTECTED] jars]$ echo $JAVA_HOME /opt/ibm/java2-i386-50 [EMAIL PROTECTED]

[jira] Created: (AXIS2-1159) Explicit ReplyTo should not be set on responses unless SOAP Session Scope has been enabled

Explicit ReplyTo should not be set on responses unless SOAP Session Scope has been enabled -- Key: AXIS2-1159 URL: http://issues.apache.org/jira/browse/AXIS2-1159

[jira] Created: (AXIS2-1162) Build Failure: testScenarioOne(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest): Caused an ERROR

Build Failure: testScenarioOne(org.apache.axis2.wsdl.codegen.extension.SchemaUnwrapperExtensionTest): Caused an ERROR Key: AXIS2-1162

[jira] Created: (AXIS2-1096) org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null

org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null Key: AXIS2-1096 URL: http://issues.apache.org/jira/browse/AXIS2-1096 Project: Apache Axis 2.0 (Axis2) Issue

[jira] Resolved: (AXIS2-1036) The property WS_ADDRESSING_VERSION is currently overloaded.

[ http://issues.apache.org/jira/browse/AXIS2-1036?page=all ] David Illsley resolved AXIS2-1036. -- Resolution: Fixed Patch committed. The property WS_ADDRESSING_VERSION is currently overloaded.

[jira] Closed: (AXIS2-1046) AddressingOutHandler.processReplyTo may add an invalid ReplyTo on an outbound client invoke in certain circumstances

[ http://issues.apache.org/jira/browse/AXIS2-1046?page=all ] David Illsley closed AXIS2-1046. Resolution: Fixed Committed fix. AddressingOutHandler.processReplyTo may add an invalid ReplyTo on an outbound client invoke in certain circumstances

[jira] Assigned: (AXIS2-1036) The property WS_ADDRESSING_VERSION is currently overloaded.

[ http://issues.apache.org/jira/browse/AXIS2-1036?page=all ] David Illsley reassigned AXIS2-1036: Assignee: David Illsley The property WS_ADDRESSING_VERSION is currently overloaded. ---

[jira] Assigned: (AXIS2-1016) EndpointReference serialization/deserialization should be consolidated in the EndpointReference class

[ http://issues.apache.org/jira/browse/AXIS2-1016?page=all ] David Illsley reassigned AXIS2-1016: Assignee: David Illsley EndpointReference serialization/deserialization should be consolidated in the EndpointReference class

  1   2   >