RE: Problems returning void in document-literal operation

Sabrina, I am working like this: I declare the xml schema in a separate file togheter with the soap messages, I wrote the wsdl file also by hand, wsdl file which includes my shema, and I generate the data structures and the webz service interface using wdsl to java and everything goes well.

RE: Sending a String

Better try to encode first as Base64 your class file, before yous end it.(And decode after you received) -Original Message- From: Sandeep [mailto:[EMAIL PROTECTED] Sent: Monday, June 14, 2004 4:09 PM To: [EMAIL PROTECTED] Subject: Sending a String Hello, I have deployed a web-service wh

axis happiness page - activation.jar

the happiness page tells me it can't find javax.activation.DataHandler from file activation.jar but it seems to work anyway? Do I need it? where do I get it? I am totally new to this stuff so be gentle --- ABS Web Site: www.abs.gov.au

Re: Q: making JWS use wrapped instead of RPC

Thank you VERY much! -Matt http://nagoya.apache.org/jira/browse/AXIS-1393 On Sat, 12 Jun 2004 13:55:08 -0400, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Please open up a bug report for enhancement and i will add a switch. > > thanks, > dims > > > On Fri, 11 Jun 2004 23:11:34 -0500, Matt P

RE: Invalid XML Character Unicode

Gary, I had the same exception. Looks to me that the data producing this exception is binary and probably needs Base64 encoding. I tried sending byte codes wrapped in a String object and landed in the same pool. Sandeep Advani Grid Research Lab, Binghamton University -Original Message- F

Invalid XML Character Unicode

Hello , First Time I got the following faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found in the value of attribute "href". faultActor: faultNode: faultDetail

Sending a String

Hello, I have deployed a web-service which accepts a string argument from my client and saves it to the local file system. This string is actually a class file which I plan to load it at the server on the fly. In doing so, I receive an error as org.xml.sax.SAXParseException: An invalid XML chara

RE: Exposing an EJB as a doc-literal web service

The following article is short and to the point: Which style of WSDL should I use? RPC/encoded, RPC/literal, document/literal? Which one? By: Russell Butek Software Engineer, IBM 31 October 2003 http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/ Raul Flores -Origina

RE: Posting XML to AxisServlet

I have successfully posted to Axis, using the following snippet: StringBuffer buf; // populate buf here... URL url = new URL(location); HttpURLConnection con = (HttpURLConnection) url.openConnection(); con.setRequestMethod("POST"); con.setDoOutput(true); con.setRequestProperty("Conte

RE: Posting XML to AxisServlet

To answer your last question- you can try out Anteater (http://aft.sourceforge.net/) for functional testing. For performance testing, try JMeter (http://jakarta.apache.org/jmeter/usermanual/build-ws-test-plan.html). - Vivek -Original Message- From: Deppen, Jeff [mailto:[EMAIL PROTECTED]

Posting XML to AxisServlet

Help! I'm trying to write an automated testing tool that will post Soap messages to the AxisServlet. When I attempt to post the XML directly to the AxisServlet, I receive an AxisFault with a faultString: "no SOAPAction header!" The soap call works fine when I use the AXIS client side libraries.

RE: I have deployed an Axis service. Now what?

Take a look at the following:   http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page=1 -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Sent: Monday, June 14, 2004 3:33 PMTo: [EMAIL PROTECTED]Subject: I have deployed an Axis service. Now what?  

I have deployed an Axis service. Now what?

  I have developed a correct WSDL file, and have generated the appropriate classes with WSDL2Java. I did a small amount of tinkering with the classes, ran AdminClient and have my Web Service running on the local TomCat server. I have added some handlers and written a messager service.   What

RE: Exposing an EJB as a doc-literal web service

Hi, Sorry...here is the attachd WSDL for the non-wrapped doc-literal service. Rahul. From: "Rahul Jain" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: Exposing an EJB as a doc-literal web service Date: Mon, 14 Jun 2004 11:28:16 -0700 Hi Anne, Attached is the WSD

RE: Exposing an EJB as a doc-literal web service

Hi Anne, Attached is the WSDL file. Your hunch was right. And as soon as I changed the service to a wrapped-literal, it started working. I don't know why the Java2WSDL tool would generate the wrong WSDL when I used the flags ( --style DOCUMENT --use LITERAL). I then changed the style to WRAPPED

Re: Security Token Service - wsdl2java generated code

Please open a JIRA bug report... thanks, dims - Original Message - From: Malinda Kaushalye <[EMAIL PROTECTED]> Date: Mon, 14 Jun 2004 11:37:09 +0600 Subject: Security Token Service - wsdl2java generated code To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED

Global Type Mapping

Hi Axis Users,   I´m new to Axis and I want to deploy a Web Service. I want to do a Global Type Mapping. A type mapping not to a particular service but available to any service. I used the Data example that defines an Object (Data) and have the Serializer/Deserializer Factory for this objec

RE: Problems returning void in document-literal operation

Thanks for the suggestion, Romulus - I have tried this workaround, but it doesn't look like it is going to give me what I want. When I follow this model, Axis generates an additional class called "_void" and then my methods return that object, rather than actually returning void. It seems like

RE: Problems returning void in document-literal operation

Hi, I am usin too documnet literal ws style and for all my methods which returns void or are having no parameters I made a declaration of the follwing type: were void, is

Problems returning void in document-literal operation

I have seen a few postings about this problem, but no resolution. I am working on a document-literal service and several of the operations should have a "void" return type. We are following the top-down model, writing the WSDL first and then using WSDL2Java to generate the Java classes. For t

Security Token Service - wsdl2java generated code

Hi All,   I could generate the Security Token Service using wsdl2java tool with ws-trust.wsdl and other related .xsd files.  But there are some bugs (I guess so) in the generated code.   //   In the RequestTypeEnum class there is

1.1 -> 1.2 Wsdl2Java differences

I recently upgraded from 1.1 to 1.2beta.   Wsdl2Java no longer generates java classes for certain schema types, namely string types with certain restrictions.  Example:            

Re: WS-I doc-literal ,wscompile and Vector

please pick up the nightly - http://cvs.apache.org/dist/axis/nightly/ :) http://marc.theaimsgroup.com/?l=axis-dev&m=108695707315913&w=2 -- dims On Mon, 14 Jun 2004 16:31:16 +0200, Pascal Prioux <[EMAIL PROTECTED]> wrote: > > I've changed the method signature from Vector to Collection > the soap

Axis deployment problem

Hi, I wrote a wsdl HelloServer.wsdl using Cape Clear SOA Editor and then deployed the service using the deploy.wsdd generated by WSDL2Java tool. This service was available at http://localhost:8080/axis/services/HelloServerPort Now I have another wsdl file ShoutSpaceWebApp.wsdl, which I worte i

Naming the returned values from Apache Axis server

Hi All, Currently we have this server-side web service that uses Axis to return a double-array of String values: public static String[][] myMethod() throws AxisFault { ... } which Axis serializes as something like http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/

Re: javax.ejb.EJBException: Second thread call to stateful session bean

[EMAIL PROTECTED] wrote: The settup you want is the normal way for stateful session beans to work. A reference to the stateful session remote interface for each client will resolve to the original instance. thus, statefull session beans serve a single client as opposed to stateless session beans

Re: WS-I doc-literal ,wscompile and Vector

I've changed the method signature from Vector to Collection the soapenc namespace is not defined is the generated wsdl error from wscompile: error: modeler error: model error: undeclared namespace prefix: "soapenc" the new wsdl: http://xml.apache.org/xml-soap"

Re: WS-I doc-literal ,wscompile and Vector

try changing the method signature to from Vector to Collection -- dims On Mon, 14 Jun 2004 15:55:59 +0200, Pascal Prioux <[EMAIL PROTECTED]> wrote: > > > Hi, > Evething works fine now > (http://marc.theaimsgroup.com/?l=axis-user&m=108695341411607&w=2) > Thanks for the responses > > Except for

WS-I doc-literal ,wscompile and Vector

Hi, Evething works fine now (http://marc.theaimsgroup.com/?l=axis-user&m=108695341411607&w=2) Thanks for the responses Except for a method wich returns a Vector .(getVectorOfMIDPRecordStoreRecord) the wscompile tool (bundled with JME SDK 2.1) generates the following error: error: Found unknown

Re: javax.ejb.EJBException: Second thread call to stateful session bean

The settup you want is the normal way for stateful session beans to work. A reference to the stateful session remote interface for each client will resolve to the original instance. thus, statefull session beans serve a single client as opposed to stateless session beans which are served up by t

Re: How crazy is it to use Axis 1.2 beta in production?

Please open up a bug report - http://issues.apache.org/jira/ thanks, dims On Mon, 14 Jun 2004 08:44:09 -0400, Henry Lu <[EMAIL PROTECTED]> wrote: > > I have experienced a lot problems with this 1.2 beta version for > Doc/literal. It DID NOT work even for a very simple example I post > coulple da

Ensure Axis 1.2 final will work for you

Currently we are working on TCK compliance (SAAJ 1.2 and JAXRPC 1.1). In the meanwhile...If there's a bug you wish to see fixed in Axis 1.2 final, read on... - If there is no bug currently in JIRA (http://issues.apache.org/jira), please create one. - If there is a bug existing in JIRA, then Make s

Re: How crazy is it to use Axis 1.2 beta in production?

vh wrote: From your experience with Axis 1.2 beta, and other experiences, what you do you think about this? When I use it, it works well. With regard to 1.1, I have no problem with it, but think if 1.2 is as good as the way I have been used it, why not make the jump. We've asked this in the

Re: How crazy is it to use Axis 1.2 beta in production?

I have experienced a lot problems with this 1.2 beta version for Doc/literal. It DID NOT work even for a very simple example I post coulple days ago (I have not got any anwser yet). I think it too early to release for production. -Henry >>> [EMAIL PROTECTED] 6/14/2004 8:35:17 AM >>> From your e

How crazy is it to use Axis 1.2 beta in production?

From your experience with Axis 1.2 beta, and other experiences, what you do you think about this? When I use it, it works well. With regard to 1.1, I have no problem with it, but think if 1.2 is as good as the way I have been used it, why not make the jump. Thank you for all advices.

javax.ejb.EJBException: Second thread call to stateful session bean

Hi axis users, I'm new to Axis and I've got a problem using it. I would like to know if someone had already experimented it : In a nutshell, I've created and deployed a service S1 that acts like a mediator. This service creates and use a stateful session EJB E1. When my client C1 invoke one metho

About the serialization of the xsd:simpleRestrictionModel

Hi, It seems that the axis wsdl2java can not serilization the xsd:simpleRestrictionModel into the appropriate java types. I don't know how to handle this type. Any ideas? Thank u very much jiadao