[jira] Commented: (AXIS2-2995) Codegen bug with different namespaces (including proposed fix)

[ https://issues.apache.org/jira/browse/AXIS2-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525010 ] Christian Meyer commented on AXIS2-2995: I found another problem in the generated code of EVBService2010Mess

[jira] Commented: (AXIS2-3164) wsdl2java ADB client creates 'staticabstract' instead of 'static abstract'

[ https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525011 ] Nikolaus Krismer commented on AXIS2-3164: - Using -u works. I do not have any problems when using this argumen

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

Hello, Here is the wsdl gnerated when I use the ?wsdl. The return object is GMDSRESPCT, adn the tag containing the byteArray is CONTENT. You will notice that CONTENT is defined as xsd:string type. This is weird because I generated the class using WSDL2java and when I first created the wsdl file

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

Hello, classical case of "WSDL first". I'd suggest alter the type of CONTENT to "base64Binary", then generate your java-code with WSDL2Java and use the resulting classes Worked with me. Cheers --- Thomas Beaujard <[EMAIL PROTECTED]> wrote: > Hello, > > Here is the wsdl gnerated when I use the ?w

handler: response message manipulation

I'm dealing with a service which sends back a response that's not complying with the service WSDL. In details, it sometimes sends an attribute set to " " (blank) while the attribute itself is defined as integer. The result is a "java.lang.reflect.InvocationTargetException" during deserialization p

handler: manipulating messages with DOM

I'm trying to manipulate a response message using DOM on Axis 1.1, but I'm not sure about the flow I should follow. I've tried the following: Message response = msgContext.getResponseMessage(); SOAPEnvelope responseEnvelope = response.getSOAPEnvelope(); SOAPBodyElement sbe = (SOAPBodyElement) re

What new in Axis2?

Hi All! I am new to apache Axis. Can someone tell me what is new in AXIS2 as compared to the previous version? Thanks in advance regards Ashish

[jira] Created: (AXIS-2694) Java Client on Axis Java 1.4

Java Client on Axis Java 1.4 Key: AXIS-2694 URL: https://issues.apache.org/jira/browse/AXIS-2694 Project: Axis Issue Type: Bug Affects Versions: 1.4 Environment: Windows Reporter: Sneha J

[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_12525107 ] Jose Antonio commented on AXIS2-3028: - It's not solved. Using Axis2 1.3 final with a schema with optional attribu

Re: What new in Axis2?

Do you mean between, Axis and Axis2 or Axis2 1.2 and the latest release Axis2 1.3? If you mean the latter, then the following is taken from the Axis2 1.3release note. Major Changes Since 1.2: - Moved to maven2 from maven1 - Significantly improved documentation - Significantly improved support for

[jira] Reopened: (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:all-tabpanel ] Jonas Boëthius reopened AXIS2-2389: --- Still not dispatching correct, now tested on Axis2, version 1.3. > Dispatching based on the SOAP

Re: Transactional JMS.

Hi Maciej I am traveling this week and will not be able to reply in detail until the weekend. However I have made some enhancements to the JMS code - esp to re-use sessions when sending out. Currently the code is under a module called Synapse-transports for you to take a peek

[jira] Updated: (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:all-tabpanel ] Jonas Boëthius updated AXIS2-2389: -- Attachment: EchoApi.wsdl WSDL of the tested service. > Dispatching based on the SOAP messag

[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_12525116 ] Jonas Boëthius commented on AXIS2-2389: --- Correct dispatching (with default configuration) to a service based on

[jira] Updated: (AXIS2-3159) Local types in schemes not supported

[ https://issues.apache.org/jira/browse/AXIS2-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyan Yurukov updated AXIS2-3159: - Description: I am trying to generate a web service from a wsdl that imports several schemes. Mos

Re: Transactional JMS.

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 it make sense). So no need to serialize > access. > Ex. If you have a service with sc

AXIS2 : JVM bursts when getting images in MB size

Guys, I dont know whether this is a AXIS2 problem. I am trying to get the Image files from the documentum server using web service. when i try to get say 4 image files in a go and if the total size of the file is in some MBs then the JVM goes bm. i have done follwong things to avoid 1. Set a e

[jira] Created: (AXIS2-3168) JAX-WS: A small performance improvement and some cleanup

JAX-WS: A small performance improvement and some cleanup Key: AXIS2-3168 URL: https://issues.apache.org/jira/browse/AXIS2-3168 Project: Axis 2.0 (Axis2) Issue Type: Bug Compo

[jira] Resolved: (AXIS2-3168) JAX-WS: A small performance improvement and some cleanup

[ https://issues.apache.org/jira/browse/AXIS2-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-3168. --- Resolution: Fixed Committed revision 573047 > JAX-WS: A small performance improvement and so

[jira] Created: (AXIS2-3169) JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled before reporting it as available

JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled before reporting it as available Key: AXIS2-3169 URL: https://issues.a

[jira] Resolved: (AXIS2-3169) JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled before reporting it as available

[ https://issues.apache.org/jira/browse/AXIS2-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-3169. --- Resolution: Fixed Committed changes: 573057 > JAX-WS: Fix to AsyncResponse to ensure that th

[jira] Created: (AXIS2-3170) Ensure content-type does not have a trailing ':'

Ensure content-type does not have a trailing ':' Key: AXIS2-3170 URL: https://issues.apache.org/jira/browse/AXIS2-3170 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel

[jira] Resolved: (AXIS2-3170) Ensure content-type does not have a trailing ':'

[ https://issues.apache.org/jira/browse/AXIS2-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-3170. --- Resolution: Fixed Committed the change: 573093 > Ensure content-type does not have a trailin

Re: AXIS2 : JVM bursts when getting images in MB size

You won't be able to send large data inside the envelope using Base64 binary, as it'll cause Axis2 to load the whole of data in to memory. You should use MTOM or SwA if your data are large. Are you getting the error on client or on server side. IIRC in the service code of your earlier posting you

[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_12525283 ] Amila Chinthaka Suriarachchi commented on AXIS2-3028: - can you send the full stack trace if there

Re: WS-Addr problem with Axis2 client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We do not support 2004/03 version of WS-Addressing. Any possibility of moving to 2004/08 or 2005/08? Thanks, Chinthaka David Bunzli wrote: > > Hi, > > I've developed a Java Axis2 1.1 client to talk to a dot net WS. My > client appears to have two

Re: Axis2-1.2+rampart1.2 ....policy sample03 problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ashique, First your exception is not that useful to track the problem. Can you please provide with soap messages exchanged and the wsdl you are using. Also, I've also encountered this meaningless exception couple of times. It would be good if this

Re: axis cpp service from axis2 Client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, The problem seems to be with the soap message. Can you post the response message that you got from the server. It seems to me that SOAP-ENV namespace is not defined in that. Chinthaka Michael Sutter wrote: > Hello list, > > I have a probl

Re: WS-Addressing info request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://wso2.org/library/2561 David Bunzli wrote: > > Hi, > > I've developed my client in Axis2 1.1. > Can anyone point me to information on how to programmatically set my > WS-Addr attributes/values? > > Thanks, > David > > > **

[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_12525289 ] Amila Chinthaka Suriarachchi commented on AXIS2-2389: - I invoke a service with your wsdl with thi

[jira] Updated: (AXIS-2694) Java Client on Axis Java 1.4

[ https://issues.apache.org/jira/browse/AXIS-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sneha Jain updated AXIS-2694: - Issue Type: Wish (was: Bug) > Java Client on Axis Java 1.4 > > >