[jira] Commented: (AXIS-1978) Invalid code generated in JavaServiceImplWriter w/multiple ports

2005-05-23 Thread Venkat Reddy (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1978?page=comments#action_66136 ] Venkat Reddy commented on AXIS-1978: The locator code generated currently (from the bug report): if ("hooxEndpoint3".equals(portName)) { sethooxEndpo

Re: [Axis2] Changed OMNode

2005-05-23 Thread Eran Chinthaka
Yes, we wanted to make this immutable, so do namespaces.   Regards, Chinthaka - Original Message - From: Shahi, Ashutosh To: axis-dev@ws.apache.org Sent: Monday, May 23, 2005 8:46 PM Subject: RE: [Axis2] Changed OMNode OK, I have managed to overcome this i

Re: [Axis2] Changed OMNode

2005-05-23 Thread Eran Chinthaka
Hi Shahi,   Well, getValue and setValue of the OMNode was bit weird for me. Yes, I agree that I put that method, and I got that method from DOM Node.   I'm repeating, what this method does is bit weird for me. What do u think ? can't we do some other thing to get the same functioanlity.   -

[jira] Created: (AXIS-2012) Call swallows exceptions when serializing input

2005-05-23 Thread David Jencks (JIRA)
Call swallows exceptions when serializing input --- Key: AXIS-2012 URL: http://issues.apache.org/jira/browse/AXIS-2012 Project: Axis Type: Bug Versions: 1.2.1 Reporter: David Jencks Calling MessageFactory.

[jira] Commented: (AXIS-1836) ClassCastException in SoapFaultBuilder reading fault

2005-05-23 Thread Henrik Nordberg (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1836?page=comments#action_66086 ] Henrik Nordberg commented on AXIS-1836: --- Faults from Axis-C 1.6a cause this problem too. Here is a sample fault: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd

[jira] Commented: (AXIS-2008) Axis HttpSender can cause a socket resource leak

2005-05-23 Thread Tom Jordahl (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2008?page=comments#action_66080 ] Tom Jordahl commented on AXIS-2008: --- Wouldn't closing the socket on all exceptions make sense since we are sending a fault back in any case? > Axis HttpSender can cause a

[jira] Updated: (AXIS-2011) Multi Dimensional Array Serilization

2005-05-23 Thread Guillaume Sauthier (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2011?page=all ] Guillaume Sauthier updated AXIS-2011: - Attachment: axis-src.jar src/ modified files [cvs.apache.org is not reachable now] > Multi Dimensional Array Serilization > --

[jira] Updated: (AXIS-2011) Multi Dimensional Array Serilization

2005-05-23 Thread Guillaume Sauthier (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2011?page=all ] Guillaume Sauthier updated AXIS-2011: - Attachment: axis-test.jar / modified test files > Multi Dimensional Array Serilization > > > Key: AXIS-2

[jira] Created: (AXIS-2011) Multi Dimensional Array Serilization

2005-05-23 Thread Guillaume Sauthier (JIRA)
Multi Dimensional Array Serilization Key: AXIS-2011 URL: http://issues.apache.org/jira/browse/AXIS-2011 Project: Axis Type: Improvement Components: Serialization/Deserialization, Deployment / Registries Versions: 1.2

[jira] Commented: (AXIS-1978) Invalid code generated in JavaServiceImplWriter w/multiple ports

2005-05-23 Thread Eric Hardesty (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1978?page=comments#action_66067 ] Eric Hardesty commented on AXIS-1978: - How can this be a code optimization? The currently generated code is wrong. The code only works if one endpoint is specified, in

[jira] Commented: (AXIS-1998) server.userexception on adminclient deploy

2005-05-23 Thread David Rhodes (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1998?page=comments#action_66065 ] David Rhodes commented on AXIS-1998: Sorry, I didn't show the soap implementation (RFPServerSoapBindingImpl.java) generated by wsdl2java, as an example, here is the begin

Re: [Axis2] Changed Call method?

2005-05-23 Thread Srinath Perera
On 5/23/05, Shahi, Ashutosh <[EMAIL PROTECTED]> wrote: > > Guys, > Any words on this? I would personally prefer the ability to send/receive > SOAPEnvelope as well along with the existing capability to send/receive > OMElement. I am not dead agienst the giving both. Yet seems we can live with only

[jira] Commented: (AXIS-1998) server.userexception on adminclient deploy

2005-05-23 Thread David Rhodes (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1998?page=comments#action_66064 ] David Rhodes commented on AXIS-1998: Thanks for the response! I attached the generated wsdl from version 1.2 to this issue, but still get the same server.userexception al

[jira] Updated: (AXIS-1998) server.userexception on adminclient deploy

2005-05-23 Thread David Rhodes (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1998?page=all ] David Rhodes updated AXIS-1998: --- Attachment: RFPServer.wsdl This is the wsdl from the 1.2 axis version which is a good bit different than the one generated by 1.2-RC3. It seems that the target se

RE: [Axis2] Changed OMNode

2005-05-23 Thread Shahi, Ashutosh
OK, I have managed to overcome this issue by calling the get/set methods based on the NodeType. I think that should be the correct way as well. But I still have a question. There are no setter methods in OMText. We just have constructor and get methods. The way I am doing right now is ca

[Axis2] Proposal to add a new method in OMFactory API

2005-05-23 Thread jayachandra
Hi devs! OMFactory API has methods to create OMElement, OMNamespace and Text nodes but the functionality to create OMAttribute somehow is missing in there. something like... + public OMAttribute createOMAttribute(String localName, OMNamespace ns, String value) Adding this would allow to create an

[jira] Commented: (AXIS-1960) 1.2Rc3: Changes to body or header do not get serialized

2005-05-23 Thread Venkat Reddy (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1960?page=comments#action_66058 ] Venkat Reddy commented on AXIS-1960: Applied a patch for SOAPPart.java. Try running your code again. And remmeber to call SOAPMessage.saveChanges(). My previous comment s

Axis 1.2 and transport "jms"

2005-05-23 Thread Jitu Patel
We have been successfully using Axis 1.1 with our transport. The URL for our transport uses "jms" as the protocol. All this worked fine - our transport code was 'invoked'  when a client made a request with a URL starting jms:. We are now trying to move to Axis 1.2. What I am seeing is that instead

[jira] Commented: (AXIS-2002) Problem using OUT-parameters

2005-05-23 Thread JIRA
[ http://issues.apache.org/jira/browse/AXIS-2002?page=comments#action_66056 ] Cédric Chabanois commented on AXIS-2002: same as http://issues.apache.org/jira/browse/AXIS-1975?page=all > Problem using OUT-parameters >

[jira] Commented: (AXIS-1992) WSDL2Java causes NullPointerException

2005-05-23 Thread Ryan Bell (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1992?page=comments#action_66055 ] Ryan Bell commented on AXIS-1992: - I think q should stay the element name. From what I understand of WS-I and doc/lit, there needs to be one and only one element part in a m

wsdl generated for extension (on string) omits basetype

2005-05-23 Thread Remco Poortinga
Hello, My apologies if the following is a known issue, but I was unable to find it in recent emails: I have a WSDL file to generate (server-side) java from using the wsdl2java ant task. This wsdl file contains the following snippet (full wsdl etc. at the end of the mail):

[jira] Created: (AXIS-2010) Wrong xsi:type handling with derived types

2005-05-23 Thread Yves Langisch (JIRA)
Wrong xsi:type handling with derived types -- Key: AXIS-2010 URL: http://issues.apache.org/jira/browse/AXIS-2010 Project: Axis Type: Bug Components: Serialization/Deserialization Versions: 1.2 Reporter: Yves Lan

RE: [Axis2] Changed Call method?

2005-05-23 Thread Shahi, Ashutosh
Guys, Any words on this? I would personally prefer the ability to send/receive SOAPEnvelope as well along with the existing capability to send/receive OMElement. Also, Srinath isn't it that if we are sending a SOAPEnvelope we should know the operation name from it irrespective of the style/use?

[Axis2] Changed OMNode

2005-05-23 Thread Shahi, Ashutosh
Hi Eran,     The OMNode getValue() and setValue() methods have been removed in the new API. I had been using it extensively in the SAAJ implementation which has similar methods for Node class. How do you expect the get/set values now given a OMNode? I could not find any alternative

[jira] Commented: (AXIS-1990) ClassLoader ClassCastException

2005-05-23 Thread Rene wortelboer (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1990?page=comments#action_66052 ] Rene wortelboer commented on AXIS-1990: --- I made some other files in Java which uses Axis. They can be found here : http://www.rkpn.nl/java/ There are also some screens

[jira] Commented: (AXIS-1983) How can I transfer javax.activation.DataHandler to .NET soap client?

2005-05-23 Thread Venkat Reddy (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-1983?page=comments#action_66047 ] Venkat Reddy commented on AXIS-1983: The DataHandler object should get serialzed as an attachment in the SOAP message. Do you have issue with the response (on-the-wire me