Configuring Message builders at URL level

2011-07-26 Thread Supun Kamburugamuva
At the moment Axis2 message builders are at a global level. We cannot configure specific message builders for specific URLs. It would be nice if we can configure the builders at specific URL's in a transport dependent way. For example for a transport like HTTP, it is suitable to have different mess

Re: WSDL generation for the services exposed only in local transport

2011-07-26 Thread Amila Suriarachchi
On Wed, Jul 27, 2011 at 10:45 AM, Amila Suriarachchi < amilasuriarach...@gmail.com> wrote: > > > On Tue, Jul 26, 2011 at 6:07 PM, Andreas Veithen < > andreas.veit...@gmail.com> wrote: > >> So, the bottom line is that it is OK to introduce a component into >> Axis2 that violates the Axis2 API (NonB

Re: WSDL generation for the services exposed only in local transport

2011-07-26 Thread Amila Suriarachchi
On Tue, Jul 26, 2011 at 6:07 PM, Andreas Veithen wrote: > So, the bottom line is that it is OK to introduce a component into > Axis2 that violates the Axis2 API (NonBlockingLocalTransportSender > sets an incorrect value for the serverSide property) and it is not > worth trying to understand how th

Re: Introducing a new feature to enable MTOM attachment streaming

2011-07-26 Thread Sadeep Jayasumana
Hi, > Whether streaming is possible or not depends on how the > MIME parts are accessed, but you always need to support buffering if > necessary. Yes, existing functionality will not be broken. In fact, building the Part in memory will be the default behavior. Streaming will kick in only if it is

[jira] [Created] (AXIS2-5101) java2wsdl plugin is not invoked in generate-resources phase

2011-07-26 Thread Robert Lieske (JIRA)
java2wsdl plugin is not invoked in generate-resources phase --- Key: AXIS2-5101 URL: https://issues.apache.org/jira/browse/AXIS2-5101 Project: Axis2 Issue Type: Bug Components

Re: WSDL generation for the services exposed only in local transport

2011-07-26 Thread Andreas Veithen
So, the bottom line is that it is OK to introduce a component into Axis2 that violates the Axis2 API (NonBlockingLocalTransportSender sets an incorrect value for the serverSide property) and it is not worth trying to understand how this can be fixed such that it works both in a pure Axis2 context a

Re: WSDL generation for the services exposed only in local transport

2011-07-26 Thread Amila Suriarachchi
On Mon, Jul 25, 2011 at 10:55 PM, Andreas Veithen wrote: > Just to summarize: > > * We have added a NonBlockingLocalTransportSender into the Axis2 code > base that doesn't respect the Axis2 APIs and that only works in > Synapse (see AXIS2-4944). > * I took us 5 JIRA issues (AXIS2-4967, AXIS2-5035

[jira] [Closed] (AXIS2-5100) AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is not thread safe

2011-07-26 Thread Igor Kamyshnikov (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov closed AXIS2-5100. --- Resolution: Fixed Fix Version/s: 1.6.0 It appears this is not an issue at least since

[jira] [Created] (AXIS2-5100) AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is not thread safe

2011-07-26 Thread Igor Kamyshnikov (JIRA)
AbstractHTTPSender.initializeTimeouts changes timeouts for shared HttpClient which is not thread safe - Key: AXIS2-5100 URL: https://issues.apache.org/jira/browse/