[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-tabpanel&focusedCommentId=12694955#action_12694955 ] Dobri Kitipov commented on AXIS2-4288: -- Hi Amila, 1) Yes it is HttpConstants. I am so

[jira] Closed: (AXIS-2782) AttachmentPart does not remove its temporary Axis???.att file, created by ManagedMemoryDataSource, if this file is created by its flushToDisk method

[ https://issues.apache.org/jira/browse/AXIS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida closed AXIS-2782. -- Resolution: Invalid I created this issue but upon further analysis, It seems attribute attachme

[jira] Commented: (AXIS2-4199) Axis client does not apply timeout from axis2 configuration

[ https://issues.apache.org/jira/browse/AXIS2-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695005#action_12695005 ] Balaji Kalaimani commented on AXIS2-4199: - Hi, This has been a problem for us as t

Re: First Element must contain the local name, Envelope , but found definitions

Hi you are right inasfar as that "wsdl" is not correct (invalid) sorry no way to to dynamic webservices without valid wsdl-document you could contact the source very well IMHO cause all other consumers will have the same problem - Cheers, Wolfgang --- On Thu, 4/2/09, Clifton B. Sothoron Jr. wro

[jira] Created: (AXIS2-4297) java org.apache.axis2.wsdl.WSDL2Java -d jaxbri creates unreachable code in MessageReceiverInOut.java

java org.apache.axis2.wsdl.WSDL2Java -d jaxbri creates unreachable code in MessageReceiverInOut.java - Key: AXIS2-4297 URL: https://issues.apache.org/j

Re: Releasing transports 1.0 - dependency resolutions

On Wed, Apr 1, 2009 at 5:50 PM, Glen Daniels wrote: > Jarek Gawor wrote: >>> Also, I'd really like to get 1.5 out the door ASAP, it's lingered way too >>> long already.  So whatever solution gets us there soonest with consensus is >>> the one I'll be happy with. >> >> Yes, I agree. Sounds like we

[jira] Created: (AXIS2-4298) Code generation plugins casing "Oracle OC4J Standalone Server 10.1.3" publishing functionality to hang .

Code generation plugins casing "Oracle OC4J Standalone Server 10.1.3" publishing functionality to hang . Key: AXIS2-4298 URL: https://issues.apache.org/jira/b

Re: Releasing transports 1.0 - dependency resolutions

Note that the tests applied to the (default Axis2) HTTP transport initially were not meant to test the transport but to validate the generic HTTP tests in the testkit. The purpose was to apply these generic tests to the NIO HTTP transport. This allows to compare the behavior of both transports. Fro

Re: Releasing transports 1.0 - dependency resolutions

Heh, ok. Jarek On Thu, Apr 2, 2009 at 12:07 PM, Andreas Veithen wrote: > Note that the tests applied to the (default Axis2) HTTP transport > initially were not meant to test the transport but to validate the > generic HTTP tests in the testkit. The purpose was to apply these > generic tests to t

Re: Releasing transports 1.0 - dependency resolutions

Hi folks: First, many thanks to Jarek for getting the transport move going - I got sucked into other stuff today and probably won't be able to dive back in for real until Sunday. Just talked to Jarek on IRC and he's hoping to finish the move tonight or tomorrow. That said I'm not very happy

Re: Releasing transports 1.0 - dependency resolutions

I see two things that need to be done to solve the testkit->base dependency issue: * Move the message builders and formatters that are located in base to axis2-kernel. That was already discussed back in December, but at that time we decided to do a complete review of the whole builder/formatter st