Help -- Need to figure out what has changed in source code

Hi All, I am using axis2/c 1.5+ (checked out from trunk roughly one and half month before 1.6 release) for ws client. I have built my application first using 1.3. I notice that one piece of my code for freeing resources goes working fine in 1.3, crashes in 1.5+ and now working again in 1.6.

Re: How to send more than one soap envelope in one request

I assume you mean HTTP Request? That really breaks the HTTP model. I know the Comet architecture does this, but its not supported by any SOAP stacks I know of. Also since there is HTTP 1.1 connection caching this sort of happens anyway: The HTTP connection is used for more than one SOAP request.

Re: How to send more than one soap envelope in one request

Hi Paul, Thanks for reply. Can you please give me more information on HTTP Connection. How can we use it to send more than one soap request at a time Thanks, Swapna Soni. pzfreo wrote: I assume you mean HTTP Request? That really breaks the HTTP model. I know the Comet architecture does

Re: How to send more than one soap envelope in one request

Can you please explain the need of having multiple soap envelopes. If you need to send binary content , then you can send it as an separate body part(attachment). On Thu, Jun 18, 2009 at 10:54 AM, Senthil Sona sws...@cisco.com wrote: Hi Team, I have a requirement to send more than one

Re: How to send more than one soap envelope in one request

Hi Paul, The requirement is, when server sends a response to the client it checks in the database whether any pending response is present to be send. If yes, then it takes those responses also and send all the responses as one response. The pending responses present in the database is

Re: How to send more than one soap envelope in one request

Aha. I see you are basically polling for responses. There are two approaches I can point you at. The first is WS-MakeConnection which is implemented in Sandesha2: http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.0-spec-os-01.pdf The second is to use WS-Transfer which we did in the PEPPOL

[jira] Created: (AXIS2-4394) transportsession scope doesn't work with spring

transportsession scope doesn't work with spring --- Key: AXIS2-4394 URL: https://issues.apache.org/jira/browse/AXIS2-4394 Project: Axis 2.0 (Axis2) Issue Type: Bug Components:

[jira] Commented: (AXIS2-4394) transportsession scope doesn't work with spring

[ https://issues.apache.org/jira/browse/AXIS2-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721190#action_12721190 ] Martin Gainty commented on AXIS2-4394: -- You can control not only the various

[Axis2] Make RPCUtil more flexible

Hi, For various reasons, I have on several occasions wanted to modify the behavior of ADB. Unfortunately, in many cases the only way to do this is to change the ADB source code and recompile, because most of the relevant bits of ADB is composed of static methods that can't be overridden. Here

[jira] Commented: (AXIS2-4394) transportsession scope doesn't work with spring

[ https://issues.apache.org/jira/browse/AXIS2-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721202#action_12721202 ] Ofer Deitelzweig commented on AXIS2-4394: - I've added the listener and the session

Re: How to send more than one soap envelope in one request

You can try including more than one response node in SOAP body. Chinmoy On 6/18/09, Paul Fremantle pzf...@gmail.com wrote: Aha. I see you are basically polling for responses. There are two approaches I can point you at. The first is WS-MakeConnection which is implemented in Sandesha2:

[jira] Created: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure

JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure - Key: AXIS2-4396 URL:

[jira] Created: (AXIS2-4397) JAX-WS: The port-name-pattern regular expression processing is incorrect

JAX-WS: The port-name-pattern regular expression processing is incorrect Key: AXIS2-4397 URL: https://issues.apache.org/jira/browse/AXIS2-4397 Project: Axis 2.0 (Axis2)

[jira] Resolved: (AXIS2-4395) JAX-WS: Consistent code across the invoke apis

[ https://issues.apache.org/jira/browse/AXIS2-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4395. --- Resolution: Fixed Committed Revision:786046 JAX-WS: Consistent code across the invoke apis

[jira] Created: (AXIS2-4398) Poor error handling when a request parameter of the wrong type is sent to a POJO web service

Poor error handling when a request parameter of the wrong type is sent to a POJO web service Key: AXIS2-4398 URL: https://issues.apache.org/jira/browse/AXIS2-4398

[jira] Updated: (AXIS2-4398) Poor error handling when a request parameter of the wrong type is sent to a POJO web service

[ https://issues.apache.org/jira/browse/AXIS2-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pétur Runólfsson updated AXIS2-4398: Attachment: services.xml Server.wsdl Server.java Poor

[jira] Resolved: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure

[ https://issues.apache.org/jira/browse/AXIS2-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4396. --- Resolution: Fixed Committed Revision: 786049 JAX-WS:@XmlSeeAlso annotations are not being

[jira] Resolved: (AXIS2-4397) JAX-WS: The port-name-pattern regular expression processing is incorrect

[ https://issues.apache.org/jira/browse/AXIS2-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4397. --- Resolution: Fixed Committed Revision:786055 JAX-WS: The port-name-pattern regular

[jira] Reopened: (AXIS2-4391) JAX-WS: Two Services Cannot Have the Same Name Error

[ https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle reopened AXIS2-4391: --- Jeff Barrett has another fix for a slightly different scneario, but the same symptom. His fix

[jira] Updated: (AXIS2-4397) JAX-WS: The port-name-pattern regular expression processing is incorrect

[ https://issues.apache.org/jira/browse/AXIS2-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4397: --- Fix Version/s: 1.6 JAX-WS: The port-name-pattern regular expression processing is incorrect

Re: [Axis2] Make RPCUtil more flexible

Pétur, I didn't look in detail at your suggestion, but I have some doubts from an architecture point of view. I don't think that taking an existing utility class and promote that to an API or extension point will improve the quality of the Axis2 architecture. If there are aspects that need to be

[jira] Updated: (AXIS2-4395) JAX-WS: Consistent code across the invoke apis

[ https://issues.apache.org/jira/browse/AXIS2-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4395: --- Fix Version/s: 1.6 JAX-WS: Consistent code across the invoke apis

[jira] Updated: (AXIS2-4396) JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which causes an application failure

[ https://issues.apache.org/jira/browse/AXIS2-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4396: --- Fix Version/s: 1.6 JAX-WS:@XmlSeeAlso annotations are not being processed on an SEI, which

[jira] Resolved: (AXIS2-4391) JAX-WS: Two Services Cannot Have the Same Name Error

[ https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4391. --- Resolution: Fixed Second Revision:786126 JAX-WS: Two Services Cannot Have the Same Name

RE: [Axis2] Make RPCUtil more flexible

Hi Andreas, I agree that just taking RPCUtil and making the methods non-static doesn't result in a great design. On the other hand it's a quick way to get some more flexibility without changing much code. Anyway, in order to get started on an API, here are the things called by

[jira] Commented: (AXIS2-4099) ConverterUtil.convertToDateTime() is to lenient

[ https://issues.apache.org/jira/browse/AXIS2-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721522#action_12721522 ] Maite Clay commented on AXIS2-4099: --- Followup for anyone seeing this issue with IBM JVM:

Re: [Axis2] Make RPCUtil more flexible

Hi ... I'm a bit confused. Do you want to modify the behavior of ADB or the behavior of JavaBeans - XML mapping? The follow-up email proposal suggests the latter. If its the latter, the design approach in Axis2 was that you'd have your own message receiver that did whatever you want. I guess your