fault message

Hi, In beta2 WSDL2Java generates for each fault in a portType a class that extends AxisFault. This class is thrown from a service call. Since beta3 WSDL2Java does not generate this class. It just throws a ComplexType that is a part of a fault message which results in compilation errors. Here is

Hotspot classloading prob and tt-bytecode.jar *was* AW: JBoss.net deployment stopped by java.lang.LinkageError

Matt, The longer I look at this stacktrace, the more I am convinced that it is not a particular tt-bytecode or axis problem, but could be related to the hotspot classloading bugs that we were discovering with the jboss-unified classloaders (e.g., Class.forName() can deliver ugly class references

URL's in generated WSDL

Hi there, I have a question regarding the URL's contained in the generated WSDL document. I have a webservice that is accessed through a load balancer. The public URL to retrieve the WSDL (and to access the webservice) would look like this: http://jaguar/is-bin/Intershop.servlet/WFS/WAPI/Catalog

NS_URI_LITERAL_XML in AXIS

Hi I guess this is the right list to ask my question. I have a client that receives a dom.Element as a string (this did not required any serializes or tricks) using pure SOAP 2.2. But then I tried to do the same call to the service using AXIS and I was left with the problem that AXIS does not hav

RE: MOMs using axis

I came in this morning and was going to look for an open source MOM implementation. I just need a simple P2P so the client can receive a 'message received ok' type indicator and then go on to do other processing while the server processes the message and eventually returns the results of processi

Re: fault message

See JSR 101 version 1.0 chapter 4.3.6 The mapping fo WSDL faults has changed several times during the development of the specification. If you still think that the Axis is in error, please open a bugzilla defect. Thanks, Rich 'Shirley' Scheuerle IBM WebSphere & Axis Web Services Development

Bean data not serialized

Hi all. I'm new to this. So, probably I missed out on something. After following thru the userguide examples I tried to send a Bean via Axis SOAP. No exceptions, no AxisFault. The Application runs and requests, the Service returns a BeanObject, Axis seems to serialize the Bean, soap envelope is

Re: Bean data not serialized

Please post your code for the 'SimpleItem' bean itself. I'm guessing you don't have getters/setters required by bean serializer/deserializer in your bean. == On Wed, 2002-07-17 at 10:14, (RV) Buchberger, Jörg wrote: > Hi all. > > I'm new to this. So, pr

re: returning arrays of beans

Hello, I can't get my program to work when I try to send an array of objects, but when I turn that array into an xml file it works. It dawned on me that my problem may be that some of the attributes are null, so I am working on trying to correct that. I have an object that has an attribute

AW: Bean data not serialized

Hi all, sorry, I introduced a typo when I simplified the method of the Service bean: Here is the snippet with correct line 5. 1public SimpleObject getIt() 2{ 3int id = this.getSomeId(); 4String name = this.getName(id); 5SimpleObject anItem = new SimpleObject(id, name); 6 7System.out

How to invoke example 6?

Hi, I managed to carry out Steps 1 to 3 of example 6 and all the files listed in the tutorial were successfully generated. I then deployed the service using AdminClient. How do I now invoke the service? I tried the following command: java samples.userguide.example6.WidgetPrice And I did this

AW: Bean data not serialized

> Please post your code for the 'SimpleItem' bean itself. > I'm guessing you don't have getters/setters required by bean > serializer/deserializer in your bean. > > == > > package my.packg; public class SimpleObject { public SimpleObject() {

Writing and deploying Serializer

Hello, can anybody tell me how I can write my own Serializer/Deserializer? Please don't give me the answer that I should use BeanSerializer, I want to write my own Serializer, because BeanSerializer doesn't work. And I also want to know what to write in the Deploymentdescriptor to activate the

Client param NS problem

Title: Client param NS problem Hey list,   I think I've found a bug in the client implementation of Axis Beta 3. (I know, I should submit this to Bugzilla, but I don't want to spend time messing with it on the company clock. Sorry) It appears that the client does not set the namespace of the

RE: fault message

Hi Milos, I've seen that beta 2 doesn't (always) create the Holders for the complex types. It only refers to them, so the code doesn't compile. However beta 3 creates the Holders. I suggest you test it with beta 3 first. Sjaak > -Original Message- > From: Milos Cekovic [mailto:[EMAI

re: returning arrays of beans

just confirming that bean with attribute of array of beans can be handled correctly by axis, though will be serialized/de. via multiref unless that is toggled false. Some attributes of my beans have been null and that's worked, but I've never had null bean array elements. On Wed, 2002-07-17 at

Re: returning arrays of beans

Heitzso wrote: > just confirming that bean with attribute of array of beans > can be handled correctly by axis, though will be serialized/de. > via multiref unless that is toggled false. Some attributes > of my beans have been null and that's worked, but I've never > had null bean array elements

ERROR : Could not convert java.util.GregorianCalendar to bean field xxx, type java.util.Date

I have the same problem, How to resolve it ? It works with the beta 2, not with the beta 3 ... [prev in list] [next in list] [prev in thread] [next in thread] List: axis-user Subject: RE: How to use DateSerializer? (Naresh Bhatia) From: Christian Schmitz <[EMAIL PROTECTED]> Date:

Re: ERROR : Could not convert java.util.GregorianCalendar to bean fieldxxx, type java.util.Date

Could you try a recent nightly build? There have been some fixes to the Calendar (de)serializer since beta 3 that may have fixed your problem. Russell Butek [EMAIL PROTECTED] Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: ERROR : Could not convert java.util.G

RE: Error loading AXIS beta 3 in WebLogic 6.1 SP2

I believe this problem is related with '-' in jar filenames and the manifest file validation. SP3 for WL 6.1 corrects this problem. -Original Message- From: Jeff Drost [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 13, 2002 8:51 PM To: [EMAIL PROTECTED] Subject: Re: Error loading AXIS be

Asynchronous Messaging

I'm wondering how I can have our SOAP client call our JAX-RPC web service, receive only a "receipt acknowledged" type message, and continue processing without waiting for the web service to finish. Then when our web service finishes, we would notify the client somehow that their either their requ

RE: How to invoke example 6?

Title: RE: How to invoke example 6? You need to invoke from the /home/sup/programs/xml-axis-beta2 directory due to the package that the class is in... Greg -Original Message- From: Supriyo Chatterjea [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 10:33 AM To: [EMAIL PROT

Re: Asynchronous Messaging

I had a similar question a while back, and the answer was "not in Axis version 1." If you can live without the "receipt acknowledged" message, you could probably write a client that behaves in an asynchronous way. For instance, if you're writing a .NET client, asynchronous method calls to s

RE: returning arrays of beans

We have an axis service that returns arrays of beans that include null array element values and it does work. FYI: This may not be related to your problem but our axis client is setting the org.apache.axis.AxisEngine.PROP_DOMULTIREFS property to false like so: stub._setProperty( org.apache.axis.

Re: returning arrays of beans

Alan Moore wrote: > We have an axis service that returns arrays of beans that include null array > element values and it does work. The problem I had was fixed, it appears. So, I need to see about getting rid of the bug report. Thank you. I can now pass arrays of beans around without any

RE: NS_URI_LITERAL_XML in AXIS

Boris - "http://xml.apache.org/xml-soap":"Element"; is the QName for org.w3c.dom.Element when using Apache Axis -- Source Code References: Org/apache/axis/Constants.java public static final String NS_URI_XMLSOAP = "http://xml.apache.org/xml-soap";; public static final QName SOAP_ELEMEN

Axis Config

I have recently download the beta3 version of axis and walked through the (beta2) Installation documentation on axis’ site. I am trying to become familiar with axis, but every time I try to access my server using the examples or the validation page I get the Following error:   org.apache.

RE: Asynchronous Messaging

I read your thread. We will be using Java clients. The intro to the example in "AXIS Next Generation Java SOAP" book states that JMS allows you to exchange messages asynchronously, which leads me to believe I can at least continue processing on the client instead of waiting for a reply. In the

Question on replacing SimpleAuthenticationHandler with my own

Hi, Can anyone help me on providing my own custom replacement for the SimpleAuthenticationHandler? I have set the the handler tag in my deploy.wedd file as below: http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>

Package Name in Method Parameter and Return Types

I'm using Java2WSDL and WSDL2Java. WSDL2Java places the fully qualified class name in method parameters and return types. For example, if I have an Integer being passed to method myMethod which returns an Integer, WSDL2Java would gen: public java.lang.Integer myMethod(java.lang.Integer in0) {.

Re: Package Name in Method Parameter and Return Types

Using fully qualified names in generated code is because it prevents collisions. If it generated: public Integer myMethod(Integer in0) {...} there would be the possiblity that an Integer class in the same package would be used. There is no way to turn this off. Rich 'Shirley' Scheuerle IBM

RE: Hotspot classloading prob and tt-bytecode.jar *was* AW: JBoss.net deployment stopped by java.lang.LinkageError

CGJ, > Class.forName() can deliver ugly class references that > have been wrongly cached inside your VM An interesting lead... I'll have to look into this further. Could it be that even though there is only one instance of the class on the classpath, the JVM thinks there are two, and throws a

Re: Bean data not serialized

I assume the code snippet of the getIt method is from your source MyService class. This class only defines the interface. Axis will generate a new class called MyServiceSoapBindingImpl, which is where you have to implement the getIt method. By default, the getIt method in the generated MyServiceS

ByteArrayDataSource with PipedInputStream

Hi there, I created a web service that returns DataHandler created by ByteArrayDataSource. The DataSource has PipedInputStream as its member field. I fill in the stream in a different thread. The main thread returns as soon as the new thread is created. The stream is closed after it is filled