[jira] Created: (AXIS2C-689) Add Axis2ServiceURLPrefix to Apache http config docs

Add Axis2ServiceURLPrefix to Apache http config docs Key: AXIS2C-689 URL: https://issues.apache.org/jira/browse/AXIS2C-689 Project: Axis2-C Issue Type: Task Affects Versions: Current

Re: Changing the web service end point

I forgot to mention that I fixed this for simple Axis server as well. But in that case, you have to recompile the source. Only the httpd module support the config based deployment. I hope we can live with that as simple axis server would hardly be used in production. Thanks, Samisa... Samisa

[jira] Resolved: (AXIS2C-410) custom URL prefixes not allowed

[ https://issues.apache.org/jira/browse/AXIS2C-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-410. -- Resolution: Fixed Fix Version/s: 1.1.0 Assignee: Samisa Abeysinghe

[jira] Commented: (AXISCPP-966) WSDL2WS generate wrong code: redundant value reference * in Wrapper

[ https://issues.apache.org/jira/browse/AXISCPP-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525884 ] Matthew Metke commented on AXISCPP-966: --- https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2?wsdl I'm

[jira] Created: (AXISCPP-1039) Code Generation re-initializes array variables with the same name.

Code Generation re-initializes array variables with the same name. -- Key: AXISCPP-1039 URL: https://issues.apache.org/jira/browse/AXISCPP-1039 Project: Axis-C++ Issue Type:

[jira] Created: (AXISCPP-1040) Method declarations that have array parameters do not match method implementation

Method declarations that have array parameters do not match method implementation - Key: AXISCPP-1040 URL: https://issues.apache.org/jira/browse/AXISCPP-1040 Project:

Re : Re : Re : Re : Tr : Axis problem returning byteArray

Hello, My problem is solved. Thanks very much for your help. Cheers Thomas - Message d'origine De : WJ Krpelan [EMAIL PROTECTED] À : axis-dev@ws.apache.org Envoyé le : Mercredi, 5 Septembre 2007, 11h05mn 52s Objet : Re: Re : Re : Re : Tr : Axis problem returning byteArray Hello,

[jira] Created: (AXIS2-3185) org.apache.axis2.description.AxisService#setLastupdate() is a typo.

org.apache.axis2.description.AxisService#setLastupdate() is a typo. --- Key: AXIS2-3185 URL: https://issues.apache.org/jira/browse/AXIS2-3185 Project: Axis 2.0 (Axis2) Issue

[jira] Created: (AXIS2-3186) getSchematargetNamespace and setSchematargetNamespacePrefix are typos

getSchematargetNamespace and setSchematargetNamespacePrefix are typos - Key: AXIS2-3186 URL: https://issues.apache.org/jira/browse/AXIS2-3186 Project: Axis 2.0 (Axis2)

[jira] Updated: (AXIS-2695) 'No such operation' error appears after previous successful requests

[ https://issues.apache.org/jira/browse/AXIS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Carlstedt updated AXIS-2695: --- Attachment: debug_startup.log Debug log from startup 'No such operation' error appears

[jira] Created: (AXIS-2695) 'No such operation' error appears after previous successful requests

'No such operation' error appears after previous successful requests Key: AXIS-2695 URL: https://issues.apache.org/jira/browse/AXIS-2695 Project: Axis Issue Type: Bug

[jira] Commented: (AXIS2-3184) Databinding cannot parse itself (Unexpected subelement)

[ https://issues.apache.org/jira/browse/AXIS2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525690 ] Jose Antonio commented on AXIS2-3184: - I've attached a WSDL and XSD file of one of the specifications that I'm

[jira] Updated: (AXIS2-3184) Databinding cannot parse itself (Unexpected subelement)

[ https://issues.apache.org/jira/browse/AXIS2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Antonio updated AXIS2-3184: Attachment: wsctx-specification.zip The WSDL I'm using. I'm invoking the ContextService service.

[jira] Created: (AXIS2-3184) Databinding cannot parse itself (Unexpected subelement)

Databinding cannot parse itself (Unexpected subelement) --- Key: AXIS2-3184 URL: https://issues.apache.org/jira/browse/AXIS2-3184 Project: Axis 2.0 (Axis2) Issue Type: Bug

[Axis2] Changing default SOAP version to 1.2

Hi Devs, Sorry if this was discussed before. Any reason not to do $subject ? Chamikara

[jira] Updated: (AXIS-2695) 'No such operation' error appears after previous successful requests

[ https://issues.apache.org/jira/browse/AXIS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Carlstedt updated AXIS-2695: --- Attachment: paymentvalidation.wsdl WSDL used for web service. NS to package mappings:

[jira] Updated: (AXIS-2695) 'No such operation' error appears after previous successful requests

[ https://issues.apache.org/jira/browse/AXIS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Carlstedt updated AXIS-2695: --- Attachment: debug_failed_request.log Debug log of failed request 'No such operation' error

[jira] Updated: (AXIS-2695) 'No such operation' error appears after previous successful requests

[ https://issues.apache.org/jira/browse/AXIS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Carlstedt updated AXIS-2695: --- Attachment: server-config.wsdd Axis server configuration. 'No such operation' error appears

[jira] Commented: (AXIS2-3028) Generated ADBBean: Issue with getPullParser() method for optional attributes

[ https://issues.apache.org/jira/browse/AXIS2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525619 ] Amila Chinthaka Suriarachchi commented on AXIS2-3028: - use getOMElement().getXMLStreamReader()

[jira] Updated: (AXIS2-3183) Client stub generation fails for WSDL's with wsdl:import

[ https://issues.apache.org/jira/browse/AXIS2-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Jörg Hessmann updated AXIS2-3183: -- Attachment: WSDLdocument.zip This is the WSDL as provided from the server. Client

Re: axis cpp service from axis2 Client

Thanks for your reply and my mistake for posting on the wrong list. But I already posted it in the user list and get no helping answer - so I decided to use the develper list. Regards Michael Original-Nachricht Datum: Thu, 06 Sep 2007 23:51:24 -0400 Von: Eran Chinthaka

[jira] Created: (AXIS2-3183) Client stub generation fails for WSDL's with wsdl:import

Client stub generation fails for WSDL's with wsdl:import Key: AXIS2-3183 URL: https://issues.apache.org/jira/browse/AXIS2-3183 Project: Axis 2.0 (Axis2) Issue Type: Bug

[jira] Updated: (AXIS2-3184) Databinding cannot parse itself (Unexpected subelement)

[ https://issues.apache.org/jira/browse/AXIS2-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Antonio updated AXIS2-3184: Attachment: Begin.java I've been playing with the generated Begin class and debugging how it

[jira] Commented: (AXIS2-3028) Generated ADBBean: Issue with getPullParser() method for optional attributes

[ https://issues.apache.org/jira/browse/AXIS2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525772 ] Jose Antonio commented on AXIS2-3028: - Well, that would work if it weren't because of this bug:

[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style

[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525627 ] Amila Chinthaka Suriarachchi commented on AXIS2-2389: - it seems you are using tomcat with a

[jira] Commented: (AXIS2-352) Support for multiple Services specified in WSDL

[ https://issues.apache.org/jira/browse/AXIS2-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525631 ] Stefan Lischke commented on AXIS2-352: -- @Amila: That does not make any sense to me. Why not generating all

Re: Problem with Adding Namespace Declaration and Attribute

basically, axis 1.1 is hardly being used in production. are you referring to the jboss implementation? --- Ghaznavi, Syed [EMAIL PROTECTED] wrote: Hi, I have been trying to resolve this problem for some time but have not been able to get my code to work!! I a sample WSClient

Re: Transactional JMS.

Hi maciej, comments inline. On 9/5/07, Maciej Szefler [EMAIL PROTECTED] wrote: Hi Rajith, See my commments inline. On 9/4/07, Rajith Attapattu [EMAIL PROTECTED] wrote: Sorry if I was not clear enough. When I said session per service, I meant session per service instance (where

[Axis2] SOAP 1.1 Validation is missing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, If we a receive a SOAP 1.1 message, via http, it MUST contain a SOAP action [1]. It can be empty but the header must be there. I just looked at our AxisServlet code and that validation code seems to be missing now. It identifies the SOAP version