RE: client-config.wsdd

2002-10-02 Thread Glen Daniels
Hi Rajal: I'm not sure what you mean by your question, but here's a little info about handlers: 1) In general, you don't want to keep state in the Handler itself. However, you can control things by selecting one of three "scopes" for the handler in the WSDD - "per-request", "per-access", and "s

Interop talk in portland, oct 3

2002-10-02 Thread Steve Loughran
Hi all, Axis users in the Portland (Oregon, not Dorset) area may be interested in a little talk I'm giving this thursday on the subject of Web Service Interoperability. Its organised by the Portland .NET users goup, so I'm focusing on .NET as the server, but Axis will be the stress test for the c

RE: expections got lost _call.invokeOneWay()

2002-10-02 Thread Russell Butek
Oneway operations are defined in WSDL 1.1 section 2.4.1. A oneway operation ONLY has an input message. Oneway operations are not supposed to have faults, so this WSDL is bad. WSDL2Java is accepting this WSDL when it should have rejected it. Russell Butek [EMAIL PROTECTED] "Alex Gugel" <[

RE: expections got lost _call.invokeOneWay()

2002-10-02 Thread Alex Gugel
Hi, instead of solved the problem. Where is definied that the first operation is non-"oneWay" and the second "oneWay" ? bye alex > -Original Message- > From: Alex Gugel > Sent: Mittwoch, 2. Oktober 2002 15:57 > To: [EMAIL PROTECTED] > Subject: expections go

RE: client-config.wsdd

2002-10-02 Thread Rajal Shah
How would you do performance monitoring on the client side.. using client-config.wsdd.. I was unable to invoke the same handler for request and response to calculate response time. Any ideas? I've asked this question earlier too. -- Rajal -Original Message- From: James Casey [mailto:[

Re: Output parameter in AXIS

2002-10-02 Thread Russell Butek
Yes. See out inout test: http://cvs.apache.org/viewcvs.cgi/xml-axis/java/test/wsdl/inout/inout.wsdl?rev=1.2.6.1 &content-type=text/vnd.viewcvs-markup Russell Butek [EMAIL PROTECTED] Tomasz Piontek <[EMAIL PROTECTED]> on 10/02/2002 10:13:24 AM Please respond to [EMAIL PROTECTED] To:[E

Re: SAXException Bad types

2002-10-02 Thread Daniel Hägg
James Black wrote: >setOperationStyle is rpc, so I will assume rpc/encoded. > I have given up on rpc/encoded (for the moment), because I cannot get WSDL2Java to generate deserializers for the array. And I also have problem with C# in rpc mode. Microsoft says that literal is "preferred" somewhe

Output parameter in AXIS

2002-10-02 Thread Tomasz Piontek
Hi, I'm not an expert in Axis and Web Services, so let me ask maybe a stupid question. Is it possible to write a simple Axis WebService, with OUT or INOUT parameter? It means a service which will modify its input parameter like it is possible in languages supporting passing values via reference

RE: very simple bean serialization not working

2002-10-02 Thread Jan-Olav Eide
That is *de*serialization, obviously... > I get a NullPointerException on the client when trying to > serialize a bean >

Re: SAXException Bad types

2002-10-02 Thread James Black
Daniel Hägg wrote: > Is that document/literal or rpc/encoded ? setOperationStyle is rpc, so I will assume rpc/encoded.

Re: SAXException Bad types

2002-10-02 Thread Daniel Hägg
James Black wrote: >In my wsdl file (generated by java2wsdl) it uses type. > > > > > > > > > > > > > Is that document/literal or rpc/encoded ? / / Daniel

RE: Adding an EngineConfigurationFactory

2002-10-02 Thread Joseph Carew
I figured it out. Found the comment in the source to add a file called META-INF/services/org.apache.axis.EngineConfigurationFactory. The first line of that file should be the implementation of the EngineConfigurationFactory you want to use. Thanks for the reply. Joe -Original Message-

very simple bean serialization not working

2002-10-02 Thread Jan-Olav Eide
I get a NullPointerException on the client when trying to serialize a bean as a return value of a web-service call. TCPMonitor shows a correct response XML on the wire, so the problems lies in the client. Am I messing up with namespaces ? Any help appreciated. java.lang.NullPointerException

expections got lost _call.invokeOneWay()

2002-10-02 Thread Alex Gugel
Hi, Exceptions thrown by my web service got lost. the soap messages look healthy. My method does not have a return value but it may throw some exceptions. I created the client with wsdl2java. For this method wsdl2java generates a _call.invokeOneWay(). So thrown exceptions get ignored. How must

Re: client-config.wsdd

2002-10-02 Thread James Casey
Whenever you need to modify any aspect of the request or response flow on the client side, for instance to add a client side handler that might modify/monitor the request/response. Examples include * client side logging/debugging * Performance moitoring * adding authorization/ digital signat

client-config.wsdd

2002-10-02 Thread Jan-Olav Eide
Under what circumstances is such a configuration file required on the client side ?

Re: SAXException Bad types

2002-10-02 Thread James Black
Daniel Hägg wrote: > Yeah, I have tried that too. > It currently seems impossible to create a "real world" WSDL file that > both .NET > and Axis can handle. :-( I am trying to figure out the problem I am having with rc2, but with rc1 I had interoperability between C# and my web service. Now

Re: SAXException Bad types

2002-10-02 Thread James Black
Daniel Hägg wrote: > Schie, Sjaak van wrote: > > >When I changed element=xxx to type=xxx, it all works (both toolkits). > > > Can you please show me what your type definition looks like. > It cannot be the same as when element=xxx is used. In my wsdl file (generated by java2wsdl) it uses type.

Re: SAXException Bad types

2002-10-02 Thread Daniel Hägg
Schie, Sjaak van wrote: >Sorry I used rpc/encoded that gave problems on both toolkits. >.Net would not import it and AXIS RC1 created bad stub code. > Yeah, I have tried that too. It currently seems impossible to create a "real world" WSDL file that both .NET and Axis can handle. :-( >James sug

RE: SAXException Bad types

2002-10-02 Thread Schie, Sjaak van
Sorry I used rpc/encoded that gave problems on both toolkits. .Net would not import it and AXIS RC1 created bad stub code. James suggested to use the Xerces XML parser in stead. Further I don't have a clue :-( Sjaak > -Original Message- > From: Daniel Hägg [mailto:[EMAIL PROTECTED]] >

Re: SAXException Bad types

2002-10-02 Thread Daniel Hägg
Schie, Sjaak van wrote: >You are revering to element name in the part like: > > > > > > > >This is all correct WSDL, but I have bad experience with this (both .Net & >.AXIS). > Really? But I have copied this from how .NET generates WSDL. >When I changed element=xxx to type=xxx,

BIG XML CONSUMER

2002-10-02 Thread Carlos González
Title: BIG XML CONSUMER Hi All! I have to make a webservice that consumes big XML's (i.e. 80 mb's). Do you have some hints/practices about the best way to do it?. Carlos Gonzalez-Cadenas e-xtendnow

RE: SAXException Bad types

2002-10-02 Thread Schie, Sjaak van
Daniel, SDK/JRE 1.4(.1) has its own XML parser. SDK/JRE <1.4 doesn't have a XML parser. Removing the XML parser is not an option, because a XML parser is needed. James, however, stated that he stopped using crimsom (XML parser) and used the xerces one instead. However I think that your problem

Re: SAXException Bad types

2002-10-02 Thread Daniel Hägg
James Black wrote: >You may want to rename crimson.jar to crimson.jar.old, but also look in >java_home/jre/lib/ext and see what is there. You will want to only refer to one xml >parser. > I have tried renaming crimson.jar, but it did not help. I have also tried to remove the classpath to crim