Re: Axis2 1.5.1 and the default HttpClient reuse

Hi all, thank you Glen for the comprehensive answer. I will do some tests at my side with this. In fact the question of Amila is one that I am really interested in. I have a similar scenario over here. We have a use case when different clients are created in different threads and all of them are

Axis2 1.5.1 and the default HttpClient reuse

Hi guys, I read in Axis2 1.5.1 RC anounce that: We now share an instance of HTTPClient across each ConfigurationContext (i.e. each Axis2 server or ServiceClient) - connection reuse is now automatic. This means the REUSE_HTTP_CLIENT flag is no longer necessary or useful, nor is creating your own

[jira] Updated: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

[ https://issues.apache.org/jira/browse/AXIS2-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4456: - Attachment: ArrayServiceSimple.aar Attaching ArrayServiceSimple.aar as a sample AAR that can

[jira] Created: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

- Key: AXIS2-4456 URL: https://issues.apache.org/jira/browse/AXIS2-4456 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: 1.5, 1.5.1 Reporter: Dobri

[jira] Commented: (AXIS2-4456) Cannot process a POJO-based Web Service (i.e. uses RPCMessageReceiver). If any of its operations take Array of NON-OMelement parameters when requested with Wrapped-Array

[ https://issues.apache.org/jira/browse/AXIS2-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737488#action_12737488 ] Dobri Kitipov commented on AXIS2-4456: -- Patches created are for the one-dimensional

[jira] Commented: (AXIS2-3843) httpFrontendHostUrl does not affect auto-generated WSDL

[ https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733150#action_12733150 ] Dobri Kitipov commented on AXIS2-3843: -- Thank you for the reply. I will try to spend

Pyton Problem accessing links in the Subversion Commits section of Axis2 JIRA

Hi guys, I have notice a problem when accessing some of the links in the Subversion Commits section of Axis2 JIRA. As a reference of the problem please access: https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel Then try to

[jira] Commented: (AXIS2-3843) httpFrontendHostUrl does not affect auto-generated WSDL

[ https://issues.apache.org/jira/browse/AXIS2-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12732502#action_12732502 ] Dobri Kitipov commented on AXIS2-3843: -- Hi Andreas, I would like to share some

Redundant code into the patch related to https://issues.apache.org/jira/browse/AXIS2-3843 ?

Hi all, Andreas, I have added a comment to https://issues.apache.org/jira/browse/AXIS2-3843JIRA. Looking the patch provided some questions rose. I think that there is a redundant code into the patch related to the JIRA. I will be glad if you can look at the comment, in your free time, and give me

[jira] Resolved: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov resolved AXIS2-4288. -- Resolution: Fixed All patches and the documentation have been committed. Support HttpState

[jira] Closed: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov closed AXIS2-4288. Support HttpState object association with a client and use it when invoking

[jira] Commented: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12715950#action_12715950 ] Dobri Kitipov commented on AXIS2-4288: -- The documentation is committed. Support

Re: [VOTE] Release Axis2 1.5

My +1, too. Thanks, Dobri On Sun, May 17, 2009 at 7:46 PM, Glen Daniels g...@thoughtcraft.com wrote: Hi Axis Developers: The 1.5 release candidate has been stable for a couple of weeks now, and thus I'd like to kick off a VOTE to officially release 1.5. The usual 72 hour window applies.

[jira] Commented: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12710330#action_12710330 ] Dobri Kitipov commented on AXIS2-4288: -- Hi, I would like to provide some documentation

Re: [jira] Commented: (AXIS2-3670) Problem using REUSE_HTTP_CLIENT - Application stalls

to do more testing to confirm the fix. Not a very clean solution, but a workaround for now. Thanks Jay Dobri Kitipov-3 wrote: Hi Jayashree, you can check if: _messageContext.getTransportOut().getSender().cleanup(_messageContext); is really invoked. AFAI can remember

[jira] Created: (AXIS2-4337) Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2 1.5 WAR

) Issue Type: Bug Affects Versions: 1.5, nightly Reporter: Dobri Kitipov Hi everybody, I found out that we are missing the org.apache.axis2.transport.tcp.TCPTransportSender class into the distribution. You can check the impact pretty easy. You should go and modify

Re: [jira] Commented: (AXIS2-3670) Problem using REUSE_HTTP_CLIENT - Application stalls

Hi, just for the test you can modify the stub and move the _messageContext. getTransportOut().getSender().cleanup(_messageContext); into a finally block. So with or without exceptions the connection close should be triggered. Regards, Dobri On Fri, May 1, 2009 at 10:22 PM, jay25

Re: [jira] Commented: (AXIS2-3670) Problem using REUSE_HTTP_CLIENT - Application stalls

#action_12682033 ] Dobri Kitipov commented on AXIS2-3670: -- I think that this issue has a solution. You can solve it doing one of the following: - Call the cleanupTransport in service client (client.cleanupTransport()); - setting

Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2 1.5 RC

Hi everybody, I found out that we are missing the org.apache.axis2.transport.tcp.TCPTransportSender class into the distribution. You can check that pretty easy. Just deploy the axis2-1.5-war in Tomcat. Before that you should go and modify the axis2\WEB-INF\conf\axis2.xml and uncomment the:

[jira] Updated: (AXIS2-4313) Some MTOMPolicy module improvements are not merged to Axis2 1.5 branch

[ https://issues.apache.org/jira/browse/AXIS2-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4313: - Attachment: MTOMOutHandler_setDoingMTOM.patch Attaching a fix for the optional scenario. Some

Re: MTOM Policy in Axis2 1.5

. thanks, Nandana [1] - https://issues.apache.org/jira/browse/AXIS2-4313 On Mon, Apr 13, 2009 at 6:55 PM, Dobri Kitipov kdobrik.ax...@googlemail.com mailto:kdobrik.ax...@googlemail.com wrote: Hi Nandana, do you plan to include MTOM policy functionality into Axis2 1.5

Re: MTOM Policy in Axis2 1.5

cross cutting issues. But let's wait for Glen's opinion. thanks, Nandana [1] - https://issues.apache.org/jira/browse/AXIS2-4313 On Mon, Apr 13, 2009 at 6:55 PM, Dobri Kitipov kdobrik.ax...@googlemail.com mailto:kdobrik.ax...@googlemail.com wrote: Hi Nandana, do you plan

[jira] Commented: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12700044#action_12700044 ] Dobri Kitipov commented on AXIS2-4288: -- Hi Amila, I am applying the modified patches

[jira] Updated: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4288: - Attachment: ProxyConfiguration_AXIS2-4288_1.1.patch AbstractHTTPSender_AXIS2

Re: [ANNOUNCE] Axis2 1.5 Release Candidate ready for testing

Hi Glen, all, I want to notify you that I am missing: java\modules\mtompolicy-mar\src\org\apache\axis2\mtompolicy\MTOMInHandler.java and the corresponding entry about the in handler into the java\modules\mtompolicy-mar\src\META-INF\module.xml These both are available into the trunk but not

Re: MTOM Policy in Axis2 1.5

, Nandana [1] - https://issues.apache.org/jira/browse/AXIS2-4313 On Mon, Apr 13, 2009 at 6:55 PM, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi Nandana, do you plan to include MTOM policy functionality into Axis2 1.5? Thank you, Dobri

MTOM Policy in Axis2 1.5

Hi Nandana, do you plan to include MTOM policy functionality into Axis2 1.5? Thank you, Dobri

[jira] Commented: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12696067#action_12696067 ] Dobri Kitipov commented on AXIS2-4288: -- Hi Amila, thank you for clarifying this. I

[jira] Updated: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

[ https://issues.apache.org/jira/browse/AXIS2-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4288: - Attachment: HTTPConstants_AXIS2-4288_1.patch ProxyConfiguration_AXIS2-4288_1

[jira] Created: (AXIS2-4288) Support HttpState object association with a client and use it when invoking httpClient.executeMethod(...)

/jira/browse/AXIS2-4288 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: kernel, transports Reporter: Dobri Kitipov Hi all, I am opening a new JIRA related to the HttpState association with a given Axis client. The use case I want to point

Re: HTTP connection leak and other related issues

and a new HttpConnectionManager instance on every invocations. So multiple invocations should have step on each other in the default case. That's why I said MultiThreadedHttpConnectionManager seems overkill to me. Alexis On Wed, Mar 25, 2009 at 3:11 AM, Dobri Kitipov kdobrik.ax

Reuse of HttpClient and HttpState proposal

Hi all, I am opening a new mail thread related to the following one HTTP connection leak and other related issues [1]. Since this became really long and hairy discussion I decided not to post there this mail. The use case I want to point out a concrete use case I have. I want to reuse a

Re: HTTP connection leak and other related issues

, Feb 27, 2009 at 12:19, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi Andreas, thank you for the comment. I think you get the question. Quick test shows that setting the following line of code into the client: options.setCallTransportCleanup(true); forces

Re: HTTP connection leak and other related issues

finally method calls _messageContext.getTransportOut().getSender().cleanup(_messageContext); to clean up the transport. thanks, Amila. Andreas On Fri, Feb 27, 2009 at 12:19, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi Andreas, thank you for the comment. I think

Re: HTTP connection leak and other related issues

: hi Dobri, Thank you very much for your response. On Mon, Mar 23, 2009 at 2:50 PM, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi Amila, I want to share some knowledge about this since these days I am doing some tests with HttpClient reuse. What I want to achieve is to reuse

Re: TransportListener and AxisEngine#sendFault(faultContext) tightly coupled

, 2009 at 12:33, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Tue, Mar 17, 2009 at 3:52 PM, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi everyone, I want to direct your attention to how OUT_FAULT_FLOW is triggered in Axis2. 1) The short story When a request

TransportListener and AxisEngine#sendFault(faultContext) tightly coupled

Hi everyone, I want to direct your attention to how OUT_FAULT_FLOW is triggered in Axis2. 1) The short story When a request is received by the TransportListener (TL) (e.g. AxisServlet) then it invokes the AxisEngine (i.e. AxisEngine#receive(msgContext)). If there is a fault condition it is

Re: TransportListener and AxisEngine#sendFault(faultContext) tightly coupled

Hi Amila, I will put this on my queue. Thank you, Dobri On Tue, Mar 17, 2009 at 1:33 PM, Amila Suriarachchi amilasuriarach...@gmail.com wrote: On Tue, Mar 17, 2009 at 3:52 PM, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi everyone, I want to direct your attention to how

[jira] Commented: (AXIS2-3670) Problem using REUSE_HTTP_CLIENT - Application stalls

[ https://issues.apache.org/jira/browse/AXIS2-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682033#action_12682033 ] Dobri Kitipov commented on AXIS2-3670: -- I think that this issue has a solution. You

[jira] Commented: (AXIS2-3265) AxisCallback#onComplete is not called in OutInAxisOperation.NonBlockingInvocationWorker#run

[ https://issues.apache.org/jira/browse/AXIS2-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681321#action_12681321 ] Dobri Kitipov commented on AXIS2-3265: -- Hi everybody, I think this is fixed. I can see

Re: HTTP connection leak and other related issues

Hi all, I have observed absolutely the same thing these days. I need some more time to analyze the whole picture, but here is my current synthesis of the issue. It seems that http connection release is tightly coupled with the Axis2 builder used to handle and process the response body and the

Re: HTTP connection leak and other related issues

. Andreas On Fri, Feb 27, 2009 at 10:10, Dobri Kitipov kdobrik.ax...@googlemail.com wrote: Hi all, I have observed absolutely the same thing these days. I need some more time to analyze the whole picture, but here is my current synthesis of the issue. It seems that http connection

[jira] Commented: (AXIS-2777) Error occurs only in Java 6 but it is fine in Java 1.4: SAAJ0007: Bad endPoint type (endPoint instance of URL)

[ https://issues.apache.org/jira/browse/AXIS-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676567#action_12676567 ] Dobri Kitipov commented on AXIS-2777: - Hi William, can you please provide me

[jira] Commented: (AXIS2-3893) Broken JavaDoc link

[ https://issues.apache.org/jira/browse/AXIS2-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676574#action_12676574 ] Dobri Kitipov commented on AXIS2-3893: -- This problem seems to persist for half an year

Re: [Vote] Dobri Kitipov as a committer

Hi Glen, all, thank you very much for trusting me :) I am really happy to become a Web Service commiter. Special thanks to Nandana who is really responsive and cooperative whenever I approach him. Big thanks! Since I am back from a vacation I need some time to fill in the documents needed and

[jira] Commented: (AXIS2-4216) Axis2, SOAP 1.2 SOAP Fault and the Subcode element issue

[ https://issues.apache.org/jira/browse/AXIS2-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671070#action_12671070 ] Dobri Kitipov commented on AXIS2-4216: -- A JIRA at Apache Commons AXIOM was created

[jira] Created: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: mtompolicy Reporter: Dobri Kitipov The idea is to make use of MTOM policy assertions (for both the versions 1.0 and 1.1(latter is still a working draft)) for configuring usage of MTOM

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MessageContext.patch MessageContext.patch: Fixes the getParameter method so

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: moduleXML.patch moduleXML.patch: Add supported-policy-namespaces tags for both MTOM

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: module.xml module.xml: The first prototype of the module.xml Consistent

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: moduleXML_Updated.patch moduleXML_Updated.patch: merge the two namespaces

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: mtomBuilder.patch mtomBuilder.patch: Logger is added. Consistent implementation

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: mtomAssertion.patch mtomAssertion.patch: Fixes the policy assertion for the optional

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMOutHandler.java MTOMOutHandler.java: The out handler that checks the policy

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMPolicy.patch MTOMPolicy.patch: Fixes the isOptional check and adds logging

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: sample-mtom-policy-extWSDL.aar sample-mtom-policy-extWSDL.aar: Sample that can

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: Util_update1.patch Util_update1.patch: Fixes the calculation of the effective policy

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: Utils.patch Utils.patch: Fixes the calculation of the effective policy needed

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: InHandler.patch InHandler.patch: Adds the configuration of the inHandler

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: mimeBinaryProperty.patch mimeBinaryProperty.patch: Sets the mimeBinary property, so

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOM11AssertionBuilder_patchJavaDoc.patch MTOM11AssertionBuilder_patchJavaDoc.patch

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOM10Assertion_patchJavaDoc.patch MTOM10Assertion_patchJavaDoc.patch: Adds JavaDoc

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMAssertion_patchJavaDoc.patch MTOMAssertion_patchJavaDoc.patch: Adds JavaDoc

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOM11Assertion_patchJavaDoc.patch MTOM11Assertion_patchJavaDoc.patch: Adds JavaDoc

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOM10AssertionBuilder_patchJavaDoc.patch MTOM10AssertionBuilder_patchJavaDoc.patch

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMInHandler_2.java MTOMInHandler_2.java: Edited version. A comment is added

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMInHandler.java MTOMInHandler.java: edited version Consistent implementation

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMInHandler_patchJavaDoc.patch MTOMInHandler_patchJavaDoc.patch: Adds JavaDoc

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMOutHandler_patchJavaDoc.patch MTOMOutHandler_patchJavaDoc.patch: Adds JavaDoc

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMInHandler_3.java MTOMInHandler_3.java: Contetent type check is fixed

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: Utils_patchJavaDoc.patch Utils_patchJavaDoc.patch: Adds JavaDoc Consistent

[jira] Updated: (AXIS2-4220) Consistent implementation of MTOM compliant with MTOM policy assertion v1.0 and 1.1 in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4220: - Attachment: MTOMPolicy_patchJavaDoc.patch MTOMPolicy_patchJavaDoc.patch: Adds JavaDoc

[jira] Created: (AXIS2-4216) Axis2, SOAP 1.2 SOAP Fault and the Subcode element issue

Components: kernel Affects Versions: nightly Reporter: Dobri Kitipov Fix For: nightly Hi everybody, What I have observed is that the Axis2 interpretation of subcodes is not compliant with the SOAP 1.2 spec (ref. http://www.w3.org/TR/soap12-part1/#faultsubcodeelement

[jira] Updated: (AXIS2-4216) Axis2, SOAP 1.2 SOAP Fault and the Subcode element issue

[ https://issues.apache.org/jira/browse/AXIS2-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4216: - Attachment: MessageContextBuilder_patch1.patch Applying the patch. This patch could be done more

Axis2 and SOAP 1.2 SOAP Fault and the Subcode element issues

Hi everybody, first of all I wish you health and love during year 2009. Currently I am doing a research over exception handling and SOAP Fault (1.1 and 1.2). I am interested in using codes that the could be transfered to the client and interpreted over there. Doing so I expect that based on the

Maven artifacts are jarred into the axis2-xx.jar files for Axis2 1.4.1

Hi, I want to ask what is the intent to have some maven artifacts jarred into all axis2-xx.jars included into the latest official release of Axis2 1.4.1.If you open these jars you can see that they contain maven folder with pom.xml file into it. Thank you, Dobri

Axis2 1.4.1 axis2-1.4.1-bin.zip and axis2-1.4.1-war.zip have different versions for MARs and AARs which are not correct

Hi, I have noticed that there are some inconsistencies with the versions into the officially released axis2-1.4.1-bin.zip (look into axis2-1.4.1-bin.zip\axis2-1.4.1\repository\ services and modules) and axis2-1.4.1-war.zip (look into axis2-1.4.1-war.zip\axis2.war\WEB-INF\ services and modules). If

Re: Axis2 1.4.1 axis2-1.4.1-bin.zip and axis2-1.4.1-war.zip have different versions for MARs and AARs which are not correct

, This was discussed in the [1] thread. thanks, nandana [1] - http://markmail.org/message/ipmuistnxwpzzyej?q=list:org%2Eapache%2Ews%2Eaxis-dev+1%2E4%2E1+nandana+RM+module+saminda On Fri, Nov 21, 2008 at 5:08 PM, Dobri Kitipov [EMAIL PROTECTED] wrote: Hi, I have noticed that there are some

[jira] Commented: (AXIS2-4114) Problem to retrieve the effective policy from MessageContext when we have policy attachment at binding level

[ https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646835#action_12646835 ] Dobri Kitipov commented on AXIS2-4114: -- Hi, I suppose that this JIRA should be closed

Axis2 1.5 with HttpClient 4.0-beta1 ?

Hi, I am interested if you have planned to migrate from HttpClient 3.1 to the lately released HttpClient 4.0-beta1 for the next Axis2 version 1.5? HttpClient 4.0-beta1 has a much better and robust connection management code compared to HttpClient 3.x I know there are some issues (JIRAs

[jira] Created: (AXIS2-4114) Problem to retrieve the effective policy from MessageContext when we have policy attachment at binding level

://issues.apache.org/jira/browse/AXIS2-4114 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Reporter: Dobri Kitipov Hi, I have a problem when I try to get the effective policy from a MessageContext when I have a policy attached at the binding level of a Web

Problem to retrieve the effective policy from MessageContext when we have wsp:PolicyAttachment/ into the services.xml

Hi, I have a problem when I try to get the effective policy from a MessageContext when I have a policy attached at the binding level of a Web Service. I am using Axis2 1.4.0 Let me explain a little bit the scenario I have. I am using an AAR that has into its services.xml: parameter

[jira] Commented: (AXIS2-1790) schemaLocation element of import statements should contain URI reference to schema document.

[ https://issues.apache.org/jira/browse/AXIS2-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637023#action_12637023 ] Dobri Kitipov commented on AXIS2-1790: -- Hi Amila, It seems that the fix you have

[jira] Updated: (AXIS2-1790) schemaLocation element of import statements should contain URI reference to schema document.

[ https://issues.apache.org/jira/browse/AXIS2-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-1790: - Attachment: AxisService.patch Attaching the latest patch needed to fix the xsd related part

[jira] Issue Comment Edited: (AXIS2-1790) schemaLocation element of import statements should contain URI reference to schema document.

[ https://issues.apache.org/jira/browse/AXIS2-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637025#action_12637025 ] dobri edited comment on AXIS2-1790 at 10/6/08 12:26 AM:

[jira] Issue Comment Edited: (AXIS2-1790) schemaLocation element of import statements should contain URI reference to schema document.

[ https://issues.apache.org/jira/browse/AXIS2-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637023#action_12637023 ] dobri edited comment on AXIS2-1790 at 10/6/08 12:27 AM: Hi

Proposal for a fix in Axis2 1.4.X related to import location and schemaLocation set in a WSDL. Patch available

Hi guys, we have a patch done for org.apache.axis2.description.AxisService related to the JIRA https://issues.apache.org/jira/browse/AXIS2-1790. With this patch Axis2 can be configured to set all location and schemaLocation paths to absolute URI paths if they are relative. As we know this URI may

Re: MTOM, WS-MTOMPolicy and MTOM configuration extension

://thilinag.blogspot.com/2007/07/improved-apache-axis2-attachment.html thanks, Thilina On Thu, Jul 17, 2008 at 6:00 AM, Dobri Kitipov [EMAIL PROTECTED] wrote: Hi all, currently I am researching the possibilities to make MTOM configuration more advanced, than just saying that enableMTOM=true

Re: MTOM, WS-MTOMPolicy and MTOM configuration extension

] wrote: Axis2 has a mtom-policy implementation and I hope it works, but I have not tested it personally... We went a little bit further with enableMTOM... http://thilinag.blogspot.com/2007/07/improved-apache-axis2-attachment.html thanks, Thilina On Thu, Jul 17, 2008 at 6:00 AM, Dobri Kitipov

Problem printing a WSDL (when we have useOriginalwsdl = true and wsdlImportLocationAdjusted = true)

Hi all, I am using latest Axis2 1.4.1. In my axis2.xml I have set useOriginalwsdl = true. The AAR I am deploying has a WSDL that in turn imports another WSDL. This is specified in the following way: import namespace= http://multiarray.interoperability.wsstack.softwareag.com/ext/;

WS-MTOMPolicy module

Hi all, I want to share my thoughts about having MTOM Serialization Policy Assertion specification implemented as a module into Axis2. I have asked a similar question some time ago. You can see it here: http://www.mail-archive.com/axis-dev@ws.apache.org/msg43257.html Current situation in Axis2

Re: MTOM, WS-MTOMPolicy and MTOM configuration extension

, but I have not tested it personally... We went a little bit further with enableMTOM... http://thilinag.blogspot.com/2007/07/improved-apache-axis2-attachment.html thanks, Thilina On Thu, Jul 17, 2008 at 6:00 AM, Dobri Kitipov [EMAIL PROTECTED] wrote: Hi all, currently I am researching

MTOM, WS-MTOMPolicy and MTOM configuration extension

Hi all, currently I am researching the possibilities to make MTOM configuration more advanced, than just saying that enableMTOM=true. For example it will be nice to specify a threshold that defines the size of the binary when MTOM to be activated etc. I want to ask and if there are any plans to

MTOM and XPath

Hi all, I am researching at the moment the possibility to specify throughout XPath expression what to be MTOM'ized into a given SOAP message? I have successfully tested the MTOM Databinding Using ADB ( http://ws.apache.org/axis2/1_3/mtom-guide.html#24) where there is a possibility to specify into

Re: Custom WSDL generation

to be a string classname. If we find one of *those* (as in the config examples you have below), we'll create one using a default constructor, and if that succeeds we load the result into the WSDLSupplier param. Sound good? --Glen Dobri Kitipov wrote: Hi Saminda, I am not sure I get everything

Re: Custom WSDL generation

, and if that succeeds we load the result into the WSDLSupplier param. Sound good? --Glen Dobri Kitipov wrote: Hi Saminda, I am not sure I get everything right. So let's clarify it. 1) My understanding is that I should create a JIRA about WSDLSupplier parameter, right? But I think

Re: Custom WSDL generation

. In this case Test1. Please do log a JIRA to prevent class cast exception. Thank you Saminda Reference: [1] . https://wso2.org/repos/wso2/trunk/commons/deployers/axis1deployer/src/main/java/a1deployer/ On Feb 4, 2008 8:52 PM, Dobri Kitipov [EMAIL PROTECTED] wrote: Hi

[jira] Created: (AXIS2-3492) WSDLSupplier configuration and/or check is not proper/obvious

Components: kernel Reporter: Dobri Kitipov Hi everybody, There is one mail thread http://marc.info/?l=axis-devm=118399944531093w=2 that talks about using WSDLSupplier that gives you the possibility to hook your own WSDL on the fly. This is done implementing an interface

Custom WSDL generation

Hi everybody, There is one mail thread http://marc.info/?l=axis-devm=118399944531093w=2that talks about using WSDLSupplier that gives you the possibility to hook your own WSDL on the fly. This is done implementing an interface org.apache.axis2.dataretrieval.WSDLSupplier. What I am currently trying

Stable release of Axis2 1.4 version ?

Hi all, I have read the plans for post 1.3 version at http://wiki.apache.org/ws/FrontPage/Axis2 I am really interested to know are there some expectations when we will have release of Axis2 1.4? Thank you in advance, Dobri

  1   2   >