[jira] Resolved: (AXIS2C-865) It didn't mention where to copy mod_axis2 shared library On MS Windows

[ https://issues.apache.org/jira/browse/AXIS2C-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-865. --- Resolution: Fixed This issue fixed. It didn't mention where to copy mod_axis2

[jira] Resolved: (AXIS2C-852) Build breaks if user has older version of Winsock2.h

[ https://issues.apache.org/jira/browse/AXIS2C-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-852. --- Resolution: Fixed Assignee: Sanjaya Ratnaweera Patch applied. Thanks Senaka

[jira] Resolved: (AXIS2C-296) tcpmon fails to operate correctly with dual clients

[ https://issues.apache.org/jira/browse/AXIS2C-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-296. --- Resolution: Fixed Assignee: Sanjaya Ratnaweera Patch applied. Thanks senaka

[jira] Updated: (AXIS2C-929) Support for HTTP HEAD Method

[ https://issues.apache.org/jira/browse/AXIS2C-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-929: --- Attachment: (was: diff.txt) Support for HTTP HEAD Method

[jira] Updated: (AXIS2C-929) Support for HTTP HEAD Method

[ https://issues.apache.org/jira/browse/AXIS2C-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-929: --- Attachment: diff.txt Support for HTTP HEAD Method

[jira] Resolved: (AXIS2C-929) Support for HTTP HEAD Method

[ https://issues.apache.org/jira/browse/AXIS2C-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dushshantha Chandradasa resolved AXIS2C-929. Resolution: Fixed Assignee: Dushshantha Chandradasa applied the

Unsubscribe not working

I apologize for bothering the group as a whole, but... Is there someone who can help unsubscribe my address from this group? I've emailed the link provided ([EMAIL PROTECTED]) multiple times over several weeks and I continue to receive group emailings. Thank you, Horst

RESTful services, services.xml

Hi all, After discussing with Axis2/Java folk, I believe that we should improve the services.xml to support RESTful Services as we don't have a WSDL2.0 mode. This is the proposed scheme. [1]. Adding a local http_location mapping for each operation: operation name=foo parameter

Re: RESTful services, services.xml

Senaka Fernando wrote: Hi all, After discussing with Axis2/Java folk, I believe that we should improve the services.xml to support RESTful Services as we don't have a WSDL2.0 mode. This is the proposed scheme. [1]. Adding a local http_location mapping for each operation: operation

Re: version incompatibilities

Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. Thanks, Samisa... Michael Sutter wrote: Hello list, I have found two incompatibilities in version 1.2. First one is in

Re: version incompatibilities

On Jan 24, 2008 10:37 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. +1 -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG

Re: RESTful services, services.xml

Senaka Fernando wrote: Hi all, After discussing with Axis2/Java folk, I believe that we should improve the services.xml to support RESTful Services as we don't have a WSDL2.0 mode. This is the proposed scheme. [1]. Adding a local http_location mapping for each operation: operation

RE: RESTful services, services.xml

I agree that for a given operation, multiple HTTP methods need to be supported. For my update item operation, I want to support taking a big XML chunk with lots of data to update (PUT), or allow the caller to simply specify one or two pieces of data in the query string to update (GET). I know

RE: RESTful services, services.xml

Hi Dave, I guess it is not done that way. Your GET operation would target the GET call and the PUT operation would target the PUT call. The engine is not supposed to relay the operation's behavior depending on the HTTP Method. You can have multiple operations doing multiple tasks of course, as

Axis2C support for dynamic operations

Hi All, I have a requirement to support dynamically generated wsdls. Each wsdl will contain a core set of operations, but will then have additional operations defined. I want to use the wsdl with the core set of operations as my service in Axis2C, but then write code in my invoke method that

Re: Axis2C support for dynamic operations

Hi Devs, I believe we are still working on WSDL support. But, even if we do, is this possible without hot-deployment? Thanks, Senaka Hi All, I have a requirement to support dynamically generated wsdls. Each wsdl will contain a core set of operations, but will then have additional

Re: RESTful services, services.xml

Senaka Fernando wrote: Senaka Fernando wrote: Hi all, After discussing with Axis2/Java folk, I believe that we should improve the services.xml to support RESTful Services as we don't have a WSDL2.0 mode. This is the proposed scheme. [1]. Adding a local http_location mapping for each

Re: version incompatibilities

On Jan 24, 2008 10:37 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. +1 thanks, Dinesh -- http://nethu.org/

Accessing the SOAP headers at the svc_client side

Hi, Is it possible to access the SOAP headers from the client side in Axis2/c. In service side, we have the access to SOAP headers in 'invoke' method using axis2_msg_ctx_t, where we can get in_msg_ctx through axis2_op_ctx_t. Can we do this kind of thing in svc_client side? axis2_svc_client

Re: Accessing the SOAP headers at the svc_client side

I think you can get the last response SOAP envelope from axis2_svc_client_get_last_response_soap_envelope() method. From the SOAP envelope you can get SOAP headers. You can't access the msg_ctx directly from svc_client. For that you need to get axis2_op_client from,

Re: Accessing the SOAP headers at the svc_client side

Hi Kasun, Kasun Indrasiri [EMAIL PROTECTED] writes: Hi, Is it possible to access the SOAP headers from the client side in Axis2/c. In service side, we have the access to SOAP headers in 'invoke' method using axis2_msg_ctx_t, where we can get in_msg_ctx through axis2_op_ctx_t. Can we do

Re: version incompatibilities

Hi Devs, Samisa Abeysinghe [EMAIL PROTECTED] writes: So looks devs are OK to do a patch release. I am a bit occupied, can we have a RM volunteer to do the job, preferably a PMC. I can work on this next week. thanks, Dinesh -- http://nethu.org

Re: version incompatibilities

Samisa Abeysinghe wrote: Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. +1 -Kau Thanks, Samisa... Michael Sutter wrote: Hello list, I have found two incompatibilities in

[Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

Hi All, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.2.1 release. Since we have identified few glitches, it is worth to fix them with a patch release, along with any bugs we have fixed since the release of 1.2.0. Dinesh was volunteered to be

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

+1 Thanks ~sanjaya Samisa Abeysinghe wrote: Hi All, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.2.1 release. Since we have identified few glitches, it is worth to fix them with a patch release, along with any bugs we have fixed since the

Re: [Axis2] Can we make Guththila the default parser?

Hi devs, I tested Rampart/C with Axis2/c (guththila enabled). All the secpolicy samples were successful. I think above mentioned fix by supun has fixed the bugs in guththila when working with Rampart/C. Thanks, Milinda On Jan 24, 2008 11:30 AM, Supun Kamburugamuva [EMAIL PROTECTED] wrote: On

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

Samisa Abeysinghe wrote: Hi All, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.2.1 release. Since we have identified few glitches, it is worth to fix them with a patch release, along with any bugs we have fixed since the release of 1.2.0.

Re: [Axis2] Can we make Guththila the default parser?

Let us *not* do this change for the 1.2.1 patch release. Because we did 1.2.0 with libxml. Thanks, Samisa... Milinda Pathirage wrote: Hi devs, I tested Rampart/C with Axis2/c (guththila enabled). All the secpolicy samples were successful. I think above mentioned fix by supun has fixed the

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

+1 Nandika On Jan 25, 2008 11:47 AM, Dumindu Pallewela [EMAIL PROTECTED] wrote: +1 On Jan 25, 2008 11:25 AM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Hi All, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.2.1 release. Since we have

Re: [Axis2] Can we make Guththila the default parser?

Hi, Tested and works fine... :) -Kau Milinda Pathirage wrote: Hi devs, I tested Rampart/C with Axis2/c (guththila enabled). All the secpolicy samples were successful. I think above mentioned fix by supun has fixed the bugs in guththila when working with Rampart/C. Thanks, Milinda On Jan

[jira] Commented: (AXIS2-3364) RESTFul serivce problem when parameters are short

[ https://issues.apache.org/jira/browse/AXIS2-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12561980#action_12561980 ] Chris Hyzer commented on AXIS2-3364: This occurs not only when using a restful input,

[jira] Commented: (AXIS2-3339) axis2-wsdl2code-maven-plugin-1.3.jar is not available in the suggested mirror

[ https://issues.apache.org/jira/browse/AXIS2-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562000#action_12562000 ] David Bull commented on AXIS2-3339: --- FYI also not available on

[jira] Created: (AXIS2-3470) AAR maven2 plugin should depend upon java2wsdl maven2 plugin

AAR maven2 plugin should depend upon java2wsdl maven2 plugin Key: AXIS2-3470 URL: https://issues.apache.org/jira/browse/AXIS2-3470 Project: Axis 2.0 (Axis2) Issue Type:

[jira] Created: (AXIS2-3471) When deploying a POJO service my services.xml action mapping is used in the generated WSDL

When deploying a POJO service my services.xml action mapping is used in the generated WSDL -- Key: AXIS2-3471 URL: https://issues.apache.org/jira/browse/AXIS2-3471

[jira] Created: (AXIS2-3472) Multidimensional Array or Collections

Multidimensional Array or Collections - Key: AXIS2-3472 URL: https://issues.apache.org/jira/browse/AXIS2-3472 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment:

[jira] Created: (AXIS2-3469) java2wsdl maven 2 plugin default behaviour incorrect

java2wsdl maven 2 plugin default behaviour incorrect Key: AXIS2-3469 URL: https://issues.apache.org/jira/browse/AXIS2-3469 Project: Axis 2.0 (Axis2) Issue Type: Bug Components:

[jira] Created: (AXIS2-3473) HTTP NIO fails to process response

HTTP NIO fails to process response -- Key: AXIS2-3473 URL: https://issues.apache.org/jira/browse/AXIS2-3473 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects Versions: 1.3

RE: Axis2 Webservices error : Caused by: java.lang.InstantiationException: java.io.FileInputStream

Hi Azeez, Thanks. So I better go with fileinputstream. Thanks. From: Afkham Azeez [mailto:[EMAIL PROTECTED] Sent: Thursday, January 24, 2008 9:29 AM To: axis-dev@ws.apache.org Subject: Re: Axis2 Webservices error : Caused by: java.lang.InstantiationException:

Re: Axis2 Webservices error : Caused by: java.lang.InstantiationException: java.io.FileInputStream

You are populating an InputStream Object on the client side and passing it to the service. While deserializing the POJO, Axis2 tries to instantiate the InputStream, which cannot be done because InputStream in an abstract class. You will have to change your code to make it work properly. Azeez On

[jira] Updated: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine updated AXIS2-2722: --- Attachment: jaxws-api.txt jaxws.txt addressing.txt Diffs

[jira] Updated: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine updated AXIS2-2722: --- Attachment: metadata.txt kernel.txt More diffs between revision 614841 of

[jira] Updated: (AXIS2-3469) java2wsdl maven 2 plugin user guide incorrect

[ https://issues.apache.org/jira/browse/AXIS2-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bull updated AXIS2-3469: -- Priority: Minor (was: Major) Summary: java2wsdl maven 2 plugin user guide incorrect (was:

[jira] Updated: (AXIS2-3469) java2wsdl maven 2 plugin user guide incorrect

[ https://issues.apache.org/jira/browse/AXIS2-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bull updated AXIS2-3469: -- Comment: was deleted java2wsdl maven 2 plugin user guide incorrect

[jira] Updated: (AXIS2-3469) java2wsdl maven 2 plugin user guide incorrect

[ https://issues.apache.org/jira/browse/AXIS2-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bull updated AXIS2-3469: -- Description: The user guide for this plugin

[jira] Updated: (AXIS2-3470) AAR maven2 plugin: request to change default location of service.xml

[ https://issues.apache.org/jira/browse/AXIS2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bull updated AXIS2-3470: -- Description: The plugin guide states that By default, it is assumed that [services.xml] is already

[jira] Commented: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562104#action_12562104 ] Nick Gallardo commented on AXIS2-2722: -- Here's a quick write up of the changes in the

java.lang.reflect.InvocationTargetException - Using RPCServiceClient

We are trying to connect to an axis web service through RPCServiceClient. On the server side we are using hibernate and spring. The object we are trying to retrieve is a complex java object. I see that the function on the server side is being called but unable to return the object on the client

[jira] Created: (AXIS2-3474) Problem with multidimensional arrays

Problem with multidimensional arrays Key: AXIS2-3474 URL: https://issues.apache.org/jira/browse/AXIS2-3474 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, wsdl Affects

[jira] Commented: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562119#action_12562119 ] Brian DePradine commented on AXIS2-2722: Changes in the addressing and kernel

Re: [Axis2] JAXWS version in Axis2 1.4

Hello devs, Given that jax-ws 2.1 seems to be an important deliverable for Axis2 1.4, and that people other than myself are starting to contribute to the development effort. I propose to merge the contents of the jax-ws 2.1 branch into the trunk and to continue development in the trunk from

[jira] Created: (AXIS2-3475) No warning/error displayed when a wsdl:message is missing

No warning/error displayed when a wsdl:message is missing - Key: AXIS2-3475 URL: https://issues.apache.org/jira/browse/AXIS2-3475 Project: Axis 2.0 (Axis2) Issue Type: Bug

howto build Axis2 with Continuum

I just installed Continuum 1.1 and tried to build Axis2. On the Add Maven 2.0+ project panel, in the POM URL field I put http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/pom.xml and changed the Build Definition Template to default maven2 template and pressed Add. I get the following

[jira] Commented: (AXIS-865) attributes from super class are not serialized

[ https://issues.apache.org/jira/browse/AXIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562127#action_12562127 ] Alexey Zavizionov commented on AXIS-865: Attribute from super class serialized in out

[jira] Commented: (AXIS-865) attributes from super class are not serialized

[ https://issues.apache.org/jira/browse/AXIS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12562127#action_12562127 ] Alexey Zavizionov commented on AXIS-865: Attribute from super class serialized in out

Re: howto build Axis2 with Continuum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom, When you use Add Maven 2.0+ Project. Click on the check box marked - For multi modules project, load only root as recursive build. Oh, delete all the projects you have now before you try again. - -- dims Tom Seelbach wrote: | I just

[jira] Created: (AXIS2-3476) Client-side processing of asynchronous requests with void return type is flawed.

Client-side processing of asynchronous requests with void return type is flawed. Key: AXIS2-3476 URL: https://issues.apache.org/jira/browse/AXIS2-3476 Project: Axis 2.0

running axis2 from eclipse

Hi All, I already checkout the axis2 source code from subversion to my Eclipse IDE! All dependencies are OK and the all code was built by Eclipse Build Automatically. Now, I want run axis2 server from eclipse IDE, how I do that ? br, Marlon Luz

how to deploy axis2 from Eclipse IDE ?

Hi all, I checkout axis2 source code from svn How I can deploy axis2 from Eclipse IDE ? Run a ant build.xml? wich build.xml and wich module ? br, Marlon Luz

Re: [Axis2] JAXWS version in Axis2 1.4

+1 from me Brian De Pradine [EMAIL PROTECTED] om

Re: [Axis2] JAXWS version in Axis2 1.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me. Nicholas L Gallardo wrote: | +1 from me | | | | | | Brian De Pradine | [EMAIL PROTECTED] | omTo |

Re: [Axis2] JAXWS version in Axis2 1.4

+1 David On Jan 24, 2008 7:01 PM, Davanum Srinivas [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me. Nicholas L Gallardo wrote: | +1 from me | | | | | | Brian De Pradine | [EMAIL PROTECTED] | om

[axis2] proposal: jaxws-integration module

All, As we start the process of integrating the JAX-WS runtime into the Axis2 deployment model, it seems like a good time to revisit the existing structure for the jaxws module. I'm specifically interested in improving the structure of how function or end-to-end tests are added in. Right now,

[jira] Created: (AXIS-2721) SoapEnvelope serialization generates incorrect attribute xmlns:ns1= for elements

SoapEnvelope serialization generates incorrect attribute xmlns:ns1= for elements -- Key: AXIS-2721 URL: https://issues.apache.org/jira/browse/AXIS-2721 Project: Axis

Re: [axis2] proposal: jaxws-integration module

Sounds good to me. The big JAXWSTest driver has always bugged me, and I've always found the JAX-WS tests pretty impenetrable (more so than the implementation!) David On Jan 24, 2008 8:55 PM, Nicholas L Gallardo [EMAIL PROTECTED] wrote: All, As we start the process of integrating the JAX-WS

Re: how to deploy axis2 from Eclipse IDE ?

Hi Marlon, These will help you, http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebService/bu_tutorial.html http://wso2.org/library/1719 http://wso2.org/library/2839 Thanks Lahiru Sandakith On Jan 25, 2008 12:07 AM, Marlon Luz [EMAIL PROTECTED] wrote: Hi all, I checkout

Re: running axis2 from eclipse

Hi Marlon, I select a module where normally all the dependencies are set, ex integration will be good because it has all the dependencies set to run integration test. then I execute this part of the code inside a class main method , ConfigurationContext confContext =

Re: [axis2] proposal: jaxws-integration module

+1 for moving the tests in to an independent module jaxws-integration. Thanks Lahiru Sandakith On Jan 25, 2008 2:25 AM, Nicholas L Gallardo [EMAIL PROTECTED] wrote: All, As we start the process of integrating the JAX-WS runtime into the Axis2 deployment model, it seems like a good time to

Re: About the WS-Policy support

Hi Kokie, WSDL4J does not identify policy expressions separately. That is WSDL4J doesn't implement a component like WSDL4J policy extension element. However that information is preserved in the WSDL4J object model as Unknown extension element. WSDL2AxisServiceBuilder use this information when

Re: [Axis2] JAXWS version in Axis2 1.4

Hi Devs, +1 for the total JAXWS support on Axis2 1.4. And also +1 for going with JAXWS 2.1, lets merge it to the trunk. I have done some testing with the sample available in the and as I saw it now the AAR based model works with JAXWS MR. Also JSR 181 annotated pojos are working with the POJO

Urgent help needed to solve HTTP SSL problem

Hi, all, I asked help from axis2-user group, but so far nobody responded, I need help from the experts here. I have deployed an Axis2 Webservice onto a web server, it worked well on the HTTP connection, after I configured my web server to use HTTP SSL, my other web applications worked, but I