Re: [VOTE] Release Axis2 1.7.9

+1 Thanks, Kishanthan On Sat, Nov 17, 2018 at 1:48 AM Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.9. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.9/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1019

Re: [VOTE] Release Axis2 1.7.8

+1 Thanks, On Sun, May 20, 2018 at 1:03 AM, Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.7. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.8/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1018/ > Distrib

Re: [VOTE] Release Axis2 1.7.7

+1 Thanks, Kishanthan. On Wed, Nov 22, 2017 at 4:56 PM, Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.7. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.7/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-101

Re: [VOTE] Release Axis2 1.7.5

+1 Thanks, Kishanthan. On Sat, May 6, 2017 at 9:34 PM Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.5. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.5/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1011

Re: [VOTE] Release Axis2 1.7.4

+1 Thanks, Kishanthan. On Sat, Oct 22, 2016 at 4:19 AM, Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.4. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.4/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-101

Re: [VOTE] Release Axis2 1.7.3

+1 Thanks, Kishanthan. On Mon, May 30, 2016 at 10:44 PM, Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.3. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.3/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-10

Re: [VOTE] Release Axis2 1.7.2

+1 Thanks, Kishanthan. On Tue, May 3, 2016 at 1:09 AM, Andreas Veithen wrote: > This is a vote to release Apache Axis2 1.7.2. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.2/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1008

Re: [VOTE] Release Axis2 and Rampart 1.7.0

+1 Thanks, Kishanthan. On Tue, Jan 19, 2016 at 4:40 AM, Andreas Veithen wrote: > This is a combined vote for the release of Axis2 and Rampart 1.7.0. > > ** SVN tags: > > http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.0/ > http://svn.apache.org/repos/asf/axis/axis2/java/rampart/ta

Re: [VOTE] Release Axis2 1.6.3

+1, Thanks, On Sun, Jun 28, 2015 at 5:35 AM, Andreas Veithen wrote: > Here is the vote for the Axis2 1.6.3 release. > > SVN tag: https://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.6.3/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1000/ > Distr

Re: Retiring Sandesha2 from 1.7.0 release

+1 Thanks, Kishanthan. On Sun, Jan 26, 2014 at 10:21 PM, Sagara Gunathunga wrote: > I believe this is the right time to bring this discussion due to > following reasons. > > 1. For many years I never see any user mail that indicate real use of > Sandesha2, It's a question to me whether anyone st

Re: Build failed in Jenkins: Axis2 #2534

Thanks. Yes, the build is back to stable now. Shouldn't we also update xmlschema trunk version? On Sun, Jan 26, 2014 at 4:07 PM, Sagara Gunathunga wrote: > I just updated Neethi version and build should be OK now. > > Thanks ! > > On Sun, Jan 26, 2014 at 8:29 AM, Kishanthan

Re: Build failed in Jenkins: Axis2 #2534

Neethi trunk version should be updated. This will be case for xmlschema as both of these dependencies are now undergoing a new release. On Sun, Jan 26, 2014 at 4:37 AM, Apache Jenkins Server wrote: > See > > Changes: > > [kishanthan] fixing test

Re: Build failed in Jenkins: Axis2 » Apache Axis2 - ADB Codegen #2533

tyHashMap? > > Andreas > > On Sat, Jan 25, 2014 at 1:03 PM, Kishanthan Thangarajah > wrote: >> There are changes to XmlSchemaElement object. This class now overrides >> both equals and hashcode methods. We are currently using this as a >> hashmap key in SchemaCompile

Re: Build failed in Jenkins: Axis2 » Apache Axis2 - ADB Codegen #2533

and use the QName of XmlSchemaElement when adding/retrieving values to/from the map. All tests are passing with this change. But will this have any major impact? Because we have been using the XmlSchemaElement as the key for all these years. Thoughts? On Sat, Jan 25, 2014 at 1:31 PM, Kishanthan

Re: Build failed in Jenkins: Axis2 » Apache Axis2 - ADB Codegen #2533

Yes, looks like most of the core elements' equals and hashcode methods have been overridden : http://mail-archives.apache.org/mod_mbox/ws-commits/201401.mbox/%3c20140121165919.6c5392388...@eris.apache.org%3E We need to fix this from that aspect. On Wed, Jan 22, 2014 at 8:10 PM, Sagara Gunathunga

Possible concurrent issue with deployerMap in DeploymentEngine

Hi Devs, There is a possible issue which can arise with the deployerMap (HashMap) object in deployment engine. The deplyerMap object is accessed in two places. 1. When adding a new deployer. 2. During the scheduler task run, which in turn calls RepositoryListener.loadOtherDirectories. If the add

[jira] [Comment Edited] (AXIS2-5615) NPE on java2wsdl

[ https://issues.apache.org/jira/browse/AXIS2-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819093#comment-13819093 ] Kishanthan Thangarajah edited comment on AXIS2-5615 at 11/11/13 4:3

[jira] [Commented] (AXIS2-5615) NPE on java2wsdl

[ https://issues.apache.org/jira/browse/AXIS2-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819093#comment-13819093 ] Kishanthan Thangarajah commented on AXIS2-5615: --- Can you tell the com

[jira] [Commented] (AXIS2-5593) Multi Port Client Generation from Axis2

[ https://issues.apache.org/jira/browse/AXIS2-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812394#comment-13812394 ] Kishanthan Thangarajah commented on AXIS2-5593: --- This is already discu

Re: Axis2 : org.apache.axis2.AxisFault: Read timed out

On Fri, Nov 1, 2013 at 2:33 AM, vittal wrote: > We have web service client generated from wsdl2jave - axis2-1.4.1, we are > getting an error on calling webservice operation org.apache.axis2.AxisFault: > Read timed out more frequently. > > please help me providing informaiton > > 1. I manually set

[jira] [Updated] (AXIS2-5482) getOMElement fails to properly set the counts on null/nil items

[ https://issues.apache.org/jira/browse/AXIS2-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5482: -- Fix Version/s: 1.7.0 > getOMElement fails to properly set the counts on n

[jira] [Commented] (AXIS2-5482) getOMElement fails to properly set the counts on null/nil items

[ https://issues.apache.org/jira/browse/AXIS2-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811871#comment-13811871 ] Kishanthan Thangarajah commented on AXIS2-5482: --- This is not a bloc

[jira] [Updated] (AXIS2-5482) getOMElement fails to properly set the counts on null/nil items

[ https://issues.apache.org/jira/browse/AXIS2-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5482: -- Priority: Major (was: Blocker) > getOMElement fails to properly set

[jira] [Assigned] (AXIS2-5482) getOMElement fails to properly set the counts on null/nil items

[ https://issues.apache.org/jira/browse/AXIS2-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah reassigned AXIS2-5482: - Assignee: Kishanthan Thangarajah > getOMElement fails to properly

[jira] [Commented] (AXIS2-5487) Attempted read on closed stream - II

[ https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811868#comment-13811868 ] Kishanthan Thangarajah commented on AXIS2-5487: --- As per HTTPCLIENT-910,

[jira] [Updated] (AXIS2-5487) Attempted read on closed stream - II

[ https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5487: -- Fix Version/s: 1.7.0 > Attempted read on closed stream -

[jira] [Updated] (AXIS2-5487) Attempted read on closed stream - II

[ https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5487: -- Priority: Major (was: Blocker) > Attempted read on closed stream -

[jira] [Commented] (AXIS2-5613) 'dependencies.dependency.version' is missing for org.apache.ws.xmlschema:xmlschema-core:jar

[ https://issues.apache.org/jira/browse/AXIS2-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811862#comment-13811862 ] Kishanthan Thangarajah commented on AXIS2-5613: --- All the dependencies

[jira] [Resolved] (AXIS2-5613) 'dependencies.dependency.version' is missing for org.apache.ws.xmlschema:xmlschema-core:jar

[ https://issues.apache.org/jira/browse/AXIS2-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5613. --- Resolution: Not A Problem > 'dependencies.dependency.version' i

[jira] [Commented] (AXIS2-5613) 'dependencies.dependency.version' is missing for org.apache.ws.xmlschema:xmlschema-core:jar

[ https://issues.apache.org/jira/browse/AXIS2-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811440#comment-13811440 ] Kishanthan Thangarajah commented on AXIS2-5613: --- Can you try again with

[jira] [Updated] (AXIS2-3776) CommonsTransportHeaders does not store 2 cookies due to map implementation

[ https://issues.apache.org/jira/browse/AXIS2-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-3776: -- Affects Version/s: 1.6.1 > CommonsTransportHeaders does not store 2 cook

[jira] [Updated] (AXIS2-3776) CommonsTransportHeaders does not store 2 cookies due to map implementation

[ https://issues.apache.org/jira/browse/AXIS2-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-3776: -- Component/s: (was: kernel) transports

[jira] [Updated] (AXIS2-3776) CommonsTransportHeaders does not store 2 cookies due to map implementation

[ https://issues.apache.org/jira/browse/AXIS2-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-3776: -- Affects Version/s: 1.6.2 > CommonsTransportHeaders does not store 2 cook

[jira] [Resolved] (AXIS2-5569) CommonTransportHeaders swallows all but the last of multiple Set-Cookies

[ https://issues.apache.org/jira/browse/AXIS2-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5569. --- Resolution: Duplicate This is a duplicate of AXIS2-3776

Re: svn commit: r1536061 - in /axis/axis2/java/core/trunk/modules: integration/pom.xml kernel/pom.xml parent/pom.xml tool/axis2-idea-plugin/pom.xml

On Sun, Oct 27, 2013 at 1:09 PM, Sagara Gunathunga < sagara.gunathu...@gmail.com> wrote: > Kishanthan, > > During your last commits you have overridden Woden dependencies into > incorrect old dependencies which cause build failures, with following > commit I have added correct Woden dependencies a

Re: Merge XMLSchema2 changes into Axis2 trunk

I have applied the patch to trunk. Thanks, Kishanthan. On Sat, Oct 26, 2013 at 11:53 PM, Deepal jayasinghe wrote: > Sure, let's do that. > > Deepal > > > Now Woden has upgraded to use XmlSchema2, since Kishanthan is a > committer now he can commit his patch himself now. > > Thanks ! > > On S

[jira] [Resolved] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5239. --- Resolution: Fixed Applied the patch to trunk with r1536050. > Upgrade Ax

[jira] [Commented] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806219#comment-13806219 ] Kishanthan Thangarajah commented on AXIS2-5239: --- With the resolutio

[jira] [Updated] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5239: -- Labels: (was: axis-gsoc gsoc2012) > Upgrade Axis2 to use xmlsche

[jira] [Commented] (AXIS2-5603) Exception occurred during code generation for WSDL using ADB Binding

[ https://issues.apache.org/jira/browse/AXIS2-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793590#comment-13793590 ] Kishanthan Thangarajah commented on AXIS2-5603: --- In order to reproduce

[jira] [Resolved] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5489. --- Resolution: Fixed This is fixed in trunk with r1531525. The proposed fix in

[jira] [Resolved] (AXIS2-5582) OperationClient class not accepting AxisCallback in 1.6.2

[ https://issues.apache.org/jira/browse/AXIS2-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5582. --- Resolution: Not A Problem > OperationClient class not accepting AxisCallb

[jira] [Resolved] (AXIS2-5184) Code working with Axis 2 1.5.x throws exception with 1.6.1

[ https://issues.apache.org/jira/browse/AXIS2-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5184. --- Resolution: Not A Problem > Code working with Axis 2 1.5.x throws except

[jira] [Updated] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5239: -- Fix Version/s: 1.7.0 > Upgrade Axis2 to use xmlsche

[jira] [Assigned] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah reassigned AXIS2-5239: - Assignee: Kishanthan Thangarajah > Upgrade Axis2 to use xmlsche

[jira] [Resolved] (AXIS2-5583) OperationClient class not accepting AxisCallback in 1.6.2

[ https://issues.apache.org/jira/browse/AXIS2-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5583. --- Resolution: Duplicate Duplicate of AXIS2-5582 > OperationClient class

[jira] [Commented] (AXIS2-5582) OperationClient class not accepting AxisCallback in 1.6.2

[ https://issues.apache.org/jira/browse/AXIS2-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783560#comment-13783560 ] Kishanthan Thangarajah commented on AXIS2-5582: --- OprationClient sup

[jira] [Resolved] (AXIS2-5608) Axis2 ignores cookie values other than JSESSIONID/axis_session from http response headers

[ https://issues.apache.org/jira/browse/AXIS2-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah resolved AXIS2-5608. --- Resolution: Fixed Added the proposed fix in r1527429. > Axis2 igno

[jira] [Updated] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5489: -- Fix Version/s: (was: 1.6.2) 1.7.0 > Encoding

[jira] [Commented] (AXIS2-4598) WSDL2Java fails when wsdl is a file with a space in the pathname

[ https://issues.apache.org/jira/browse/AXIS2-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781311#comment-13781311 ] Kishanthan Thangarajah commented on AXIS2-4598: --- @Maksim, the error you

[jira] [Commented] (AXIS2-5604) Configured the axis2 in existing web application but not able to access the Web service.

[ https://issues.apache.org/jira/browse/AXIS2-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779872#comment-13779872 ] Kishanthan Thangarajah commented on AXIS2-5604: --- Normally a 404 error w

[jira] [Created] (AXIS2-5608) Axis2 ignores cookie values other than JSESSIONID/axis_session from http response headers

Kishanthan Thangarajah created AXIS2-5608: - Summary: Axis2 ignores cookie values other than JSESSIONID/axis_session from http response headers Key: AXIS2-5608 URL: https://issues.apache.org/jira/browse

Axis2 ignores cookie values other than JSESSIONID/axis_session

Hi, Currently in HTTPSenderImpl#obtainHTTPHeaderInformation, the Session Cookie string is constructed by checking only JSEESIONID/axis_session from response headers and then adding them as cookie string. It ignores other values which are coming with Set-Cookie from response headers. This will caus

Re: Axis2 use of Apache Commons HTTP Client 3.1

Axis2 trunk is already upgraded to use HttpClient4 (for CommonsHTTPTransportSender) [1], along with still maintaining the support for HttpClient3. Thanks, Kishanthan [1] https://issues.apache.org/jira/browse/AXIS2-4318 On Mon, Aug 5, 2013 at 12:26 PM, David Dillard wrote: > I see that the Apach

[jira] [Updated] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5379: -- Attachment: helloWebServiceREST-kishanthan.aar > The third URL parame

[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664809#comment-13664809 ] Kishanthan Thangarajah commented on AXIS2-5379: --- Hi Sven, If you are s

[jira] [Updated] (AXIS2-4630) ADB generates code that doesn't compile when WSDL has abstract types.

[ https://issues.apache.org/jira/browse/AXIS2-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-4630: -- Attachment: AXIS2-4630.patch Attaching a patch which will fix the compilations

Re: Generate client from WSDL

mpiling code. My thoughts are > that there may be something wrong with the Wsdl or perhaps there is a > setting I need to pass into wsdl2Java to generate different stub code? Any > thoughts? > > Thanks, > Stephen > > > On Mon, May 6, 2013 at 11:44 PM, Kishanthan

[jira] [Updated] (AXIS2-5520) Extend the usage of hiddenService parameter to hide service from listServices

[ https://issues.apache.org/jira/browse/AXIS2-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5520: -- Attachment: AXIS2-5520.patch Attaching the patch for this improvement. I have

Re: Generate client from WSDL

On Mon, May 6, 2013 at 10:09 PM, Stephenson Ohimor wrote: > Hi, > I'm trying to create a client and embed it into a spring based web app. > The webservice is written with Axis2. When I try to generate a client > from the WSDL (via eclipse WSDL generation) I get a number of errors when > the 'c

[jira] [Commented] (AXIS2-4630) ADB generates code that doesn't compile when WSDL has abstract types.

[ https://issues.apache.org/jira/browse/AXIS2-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649323#comment-13649323 ] Kishanthan Thangarajah commented on AXIS2-4630: --- This is same as AXIS2-

[jira] [Created] (AXIS2-5520) Extend the usage of hiddenService parameter to hide service from listServices

Kishanthan Thangarajah created AXIS2-5520: - Summary: Extend the usage of hiddenService parameter to hide service from listServices Key: AXIS2-5520 URL: https://issues.apache.org/jira/browse/AXIS2-5520

[jira] [Commented] (AXIS2-5506) useOriginalwsdl + service exceptions = NullPointerException

[ https://issues.apache.org/jira/browse/AXIS2-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649290#comment-13649290 ] Kishanthan Thangarajah commented on AXIS2-5506: --- Can you add sample wsd

[jira] [Commented] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649264#comment-13649264 ] Kishanthan Thangarajah commented on AXIS2-5489: --- First, the patch will

[jira] [Updated] (AXIS2-5393) org.apache.axis2.databinding.ADBException: Unexpected subelement SendAndCommitResult > error on good response

[ https://issues.apache.org/jira/browse/AXIS2-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5393: -- Attachment: Service.aar > org.apache.axis2.databinding.ADBExcept

[jira] [Commented] (AXIS2-5393) org.apache.axis2.databinding.ADBException: Unexpected subelement SendAndCommitResult > error on good response

[ https://issues.apache.org/jira/browse/AXIS2-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649262#comment-13649262 ] Kishanthan Thangarajah commented on AXIS2-5393: --- What is the command

[jira] [Commented] (AXIS2-5341) Recursion within a extension causes an ADBException: Unexpected subelement XXXX

[ https://issues.apache.org/jira/browse/AXIS2-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648146#comment-13648146 ] Kishanthan Thangarajah commented on AXIS2-5341: --- I'm not gettin

[jira] [Comment Edited] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647243#comment-13647243 ] Kishanthan Thangarajah edited comment on AXIS2-5379 at 5/2/13 3:4

[jira] [Updated] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5379: -- Attachment: hello-rest-modified.wsdl > The third URL parameter can not

[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647243#comment-13647243 ] Kishanthan Thangarajah commented on AXIS2-5379: --- Since you are working

[jira] [Updated] (AXIS2-5516) ReST request always returns blank response

[ https://issues.apache.org/jira/browse/AXIS2-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5516: -- Attachment: TestService-modified.wsdl > ReST request always returns bl

[jira] [Commented] (AXIS2-5516) ReST request always returns blank response

[ https://issues.apache.org/jira/browse/AXIS2-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647232#comment-13647232 ] Kishanthan Thangarajah commented on AXIS2-5516: --- Again that is no

[jira] [Updated] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5489: -- Attachment: AXIS2-5489.patch > Encoding GET parameters with '+&#x

[jira] [Commented] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646348#comment-13646348 ] Kishanthan Thangarajah commented on AXIS2-5489: --- The change I propos

[jira] [Commented] (AXIS2-5516) ReST request always returns blank response

[ https://issues.apache.org/jira/browse/AXIS2-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645737#comment-13645737 ] Kishanthan Thangarajah commented on AXIS2-5516: --- Here is my observatio

[jira] [Commented] (AXIS2-5102) AntCodeGenTask fails for wsdl with xsd:import schemaLocation when build file path includes a space character

[ https://issues.apache.org/jira/browse/AXIS2-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644775#comment-13644775 ] Kishanthan Thangarajah commented on AXIS2-5102: --- This is same as AXIS2-

[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644502#comment-13644502 ] Kishanthan Thangarajah commented on AXIS2-5379: --- Sven,

[jira] [Commented] (AXIS2-5485) Axis2 v1.6.x: org.jdom.JDOMException: java.lang.NoClassDefFoundError: org/jdom/Parent

[ https://issues.apache.org/jira/browse/AXIS2-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644312#comment-13644312 ] Kishanthan Thangarajah commented on AXIS2-5485: --- This looks li

[jira] [Commented] (AXIS2-5184) Code working with Axis 2 1.5.x throws exception with 1.6.1

[ https://issues.apache.org/jira/browse/AXIS2-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644291#comment-13644291 ] Kishanthan Thangarajah commented on AXIS2-5184: --- This is same as AXIS2-

[jira] [Updated] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5379: -- Attachment: RESTSample_1.0.0.aar > The third URL parameter can not

[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643515#comment-13643515 ] Kishanthan Thangarajah commented on AXIS2-5379: --- I tried to reproduce

Re: ReST with Axis2

On Fri, Apr 26, 2013 at 9:09 PM, Jack Sprat wrote: > The ReST request looks like this: > https://www.example.com/test2/services/TestService/echo?echoRequest=ping If this is the URL format that you are going to use with REST requests, then you don't need wsdl 2.0. These kind of REST URL are supp

[jira] [Commented] (AXIS2-5501) Creating ServiceClient with ConfigContext created using createDefaultConfigurationContext() causes NullPointerException

[ https://issues.apache.org/jira/browse/AXIS2-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642528#comment-13642528 ] Kishanthan Thangarajah commented on AXIS2-5501: --- Your observatio

[jira] [Commented] (AXIS2-5496) Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case wsdl with xsd:import schemaLocation and path to xsd contains a space character

[ https://issues.apache.org/jira/browse/AXIS2-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640726#comment-13640726 ] Kishanthan Thangarajah commented on AXIS2-5496: --- Even-though the scen

[jira] [Updated] (AXIS2-5496) Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case wsdl with xsd:import schemaLocation and path to xsd contains a space character

[ https://issues.apache.org/jira/browse/AXIS2-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5496: -- Attachment: AXIS2-5496.patch > Code generation by axis2-wsdl2code-ma

[jira] [Updated] (AXIS2-5478) documantation has wrong config example

[ https://issues.apache.org/jira/browse/AXIS2-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5478: -- Attachment: AXIS2-5478.patch > documantation has wrong config exam

[jira] [Commented] (AXIS2-5478) documantation has wrong config example

[ https://issues.apache.org/jira/browse/AXIS2-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639465#comment-13639465 ] Kishanthan Thangarajah commented on AXIS2-5478: --- Yes, the documentatio

Re: [Axis2] wsdl2java with WSDL 2.0

de some direction. > I appreciate any help. > > [1] http://wso2.org/library/3726 > > ------ > *From:* Kishanthan Thangarajah > > *To:* java-u...@axis.apache.org; Jack Sprat > *Cc:* "java-dev@axis.apache.org" > *Sent:* Saturday, A

[jira] [Updated] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5489: -- Attachment: axis2-kernel-1.6.2.jar > Encoding GET parameters w

[jira] [Commented] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632910#comment-13632910 ] Kishanthan Thangarajah commented on AXIS2-5489: --- @Andreas: Ok, unders

Re: Problem encoding GET parameters with '+' character

Hi Devs, I tried to reproduce this [1] and it looks like a regression caused by [2] for me. The fix for [2] is addressing the case when a POST request is sent with " ", space character, and the java.util.URLEncoder encodes the space character as "+". So when decoding the string, the "+" character

[jira] [Updated] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

[ https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5239: -- Attachment: AXIS2-5239.patch I'm adding a patch which upgrades Axis2 t

Re: [Axis2] wsdl2java with WSDL 2.0

Check this [1]. It will be helpful on creating RESTful services with Axis2. Also you have to give WSDL version as 2 when running wsdl2java for WSDL 2.0. For example : ./wsdl2java.sh -uri /tmp/sample.wsdl -o /tmp/output *-wv 2* Thanks, Kishanthan. [1] http://wso2.org/library/3726 On Wed, Apr 10,

[jira] [Commented] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630066#comment-13630066 ] Kishanthan Thangarajah commented on AXIS2-5489: --- OK, I can now repro

[jira] [Commented] (AXIS2-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java

[ https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612959#comment-13612959 ] Kishanthan Thangarajah commented on AXIS2-5489: --- So if i understand

[jira] [Commented] (AXIS2-5502) Download link broken

[ https://issues.apache.org/jira/browse/AXIS2-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612930#comment-13612930 ] Kishanthan Thangarajah commented on AXIS2-5502: --- This link work

[jira] [Commented] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558558#comment-13558558 ] Kishanthan Thangarajah commented on AXIS2-5379: --- Can you take a look a

[jira] [Commented] (AXIS2-5474) DefaultSchemaGenerator : properly handle failure when a bean property has no getReadMethod()

[ https://issues.apache.org/jira/browse/AXIS2-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555902#comment-13555902 ] Kishanthan Thangarajah commented on AXIS2-5474: --- Philippe, You can add

[jira] [Commented] (AXIS2-5444) FileNotFound exception deploying to specific context on Tomcat 7

[ https://issues.apache.org/jira/browse/AXIS2-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554152#comment-13554152 ] Kishanthan Thangarajah commented on AXIS2-5444: --- This issue is not ther

[jira] [Commented] (AXIS2-5469) WstxIOException when trying to retrieve inbound envelope from last operation message context

[ https://issues.apache.org/jira/browse/AXIS2-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552150#comment-13552150 ] Kishanthan Thangarajah commented on AXIS2-5469: --- This is not a bug.

  1   2   >