Hi Vineet Singh,
I am sorry, I cant help you.
But I have a question. How do you reference the client-config.wsdd
and where do you reference the client...wsdd?
Can you give me an example???
To your Problem - are you sure you kill the handler in the used
client-config.wsdd?
Thanks Tomi
-Urs
Hi all
I need some help in undeploying handlers on the client side. I had
deployed some handlers on the client side by adding the information of
the handler in the axis.jar clinet-config.wsdd. now in order to undeploy
the handlers I had deleted the handler part from the client-config.wsdd,
but even
Hi Glen,
Thanks a lot for your efforts for releasing 1.2 beta 2 !
When I was making an announcement page for the release,
I found a problem on the package. It's a versioning matter
of the release.
It seems that you set not '1.2beta2' but '1.2beta' as the
axisVersion when you built the releas
Try setting the classpath for the java2wsdl task with a taskdef tag:
http://localhost:8080/axis/services/dataservice";
output="${build.home}/generated/MyGenerated.wsdl"
namespace=
Hi,
Can't seem to get the java2wsdl task in the new 1.2beta2 package to run
appropriatly. Below is a portion of an ant file, and the output it
generates. I think the second part of the task (the one that uses the axis
ant task) should have the same results as the first part, but it dies with a
c
James,
I'll back off from my claim that there's a problem.
When I write a class/interface that has a method
that returns a string array, the WSDL seems to indicate
that the return is a single xsd:string. Even the
stubs generated from the WSDL show a return of String.
However, when I actually invok
I am using a client application built
with WSDL2Java derived code to communicate with Axis 1.1 server under WebLogic
Fairly regularly, when I terminate the
client Java application with ctrl-c the WebLogic Managed Server (under
which Axis is running) crashes hard & completely with the message "Bro
Is your web service exposed as a document/literal?
If yes, I face a similar problem - Axis 1.2 beta
(June 14th release) makes the return type of the
method a String, instead of String[]. The problem
is right where I do java2wsdl - even the WSDL, I
think, is incorrrect. The problem does not occur
wi
I have a very nice Axis Web Service running in which I call a "query"
function which returns an arbitrarily sized array of type String[].
I call the axis implementation file with the following call (Assume all
setup of service is correct):
java.lang.String[] yes_list = (java.lang.String[]
Yes, It's on my todo list.
-- dims
On Wed, 14 Jul 2004 11:19:51 -0700, Peter Molettiere
<[EMAIL PROTECTED]> wrote:
>
> The out-of-memory during object serialization bug is the single most
> important bug fix to our application. Any chance you'll be able to look
> at it dims? I know you've been b
Is there anyone who can tell me why the nightly build axis source code
creates axis.jar file with 1285 KB size in ~/build/lib directory but the
axis1.2beta2 has axis.jar file with 1589 KB? That maybe the reason I
failed to bring up axis in the Tomcat by copying all jar file from the
nightly built ~
The out-of-memory during object serialization bug is the single most
important bug fix to our application. Any chance you'll be able to look
at it dims? I know you've been busy with other things since I posted
the test case to jira, but maybe now you can take a look?
I notice it is marked as
Hi Glen,
Yes you are right. I want to completely turn it off and not customize it.
Waiting for your response.
Thanks a lot.
-Riken
Glen Daniels <[EMAIL PROTECTED]> wrote:
>Hi Riken:
>
>I'm sorry, just to be clear, your problem is that you want to completely
>turn off the query string handling,
Since i've got no responses i wrote to the dev list, they answered me the
problem i was reporting was caused from the fact i didn't have the
wsdl4j.jar in the classpath: i was misleaded by the fact that in the AXIS
guide these are the library to put in the AXIS PATH:
set AXIS_HOME=c:\tomcat
Hi,
I am continuing to have problems in jav2wsdl and wsdl2java programs. Here is the
latest of the problems, which makes me wonder what I am doing wrong. I am working
with some 30 services. I use similar ant scripts for generating wsdls and then
proxies from wsdls using java2wsdl and wsdl2ja
The SOAP specification does not define the behavior for how to request
multiple operations in a single SOAP request. Therefore the folks at WS-I
decided to disallow it. The WS-I Basic Profile specifies that a SOAP Body
may contain only one child element (which indicates the operation). This is
true
The SOAP specification does not define the behavior for how to request
multiple operations in a single SOAP request. Therefore the folks at WS-I
decided to disallow it. The WS-I Basic Profile specifies that a SOAP Body
may contain only one child element (which indicates the operation). This is
true
The HTTP 500 status code is mandated by
the SOAP specification.
See http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383529
“In case of a SOAP
error while processing the request, the SOAP HTTP server MUST issue an HTTP 500
"Internal Server Error" response and include a SOAP mess
The HTTP 500 status code is mandated by
the SOAP specification.
See http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383529
“In case of a SOAP
error while processing the request, the SOAP HTTP server MUST issue an HTTP 500
"Internal Server Error" response and include a SOAP mess
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 sure there is enough
information (a test case) to recreate the bug
- Make sure you try lat
Hi All,
Is there something that mandates a 500 return when a SOAP/HTTP web service returns a Server.userException (a wsdl:fault representing an application exception)?
Can I change Axis without having to recompile, to return 200 when application exceptions are thrown?
Is there any specific reaso
Hi Riken:
I'm sorry, just to be clear, your problem is that you want to completely
turn off the query string handling, not customize it, right?
--Glen
- Original Message -
From: "Riken Shah" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 9:00 AM
Subject: RE: ho
Hi y'all:
The Axis team would like to announce that Axis 1.2 beta 2 has been released.
This version has passed both the JAX-RPC 1.1 and the SAAJ 1.2 TCKs, and is
just about ready to ship. There are a few other bugs we're considering
fixing, and we do expect some further doc updates in the next w
Hi,
I'm looking for a possibility to serialise an Axis wsdl2java-generated type
to XML and back into its Java object representation. This would allow a
simple file-based management of test cases.
I managed the first step, transforming the object into XML, by using the
Axis BeanSerializer and a S
I was under the impression that a SOAP server should be able to
execute multiple methods in a single SOAP call, but I do not seem
to get it working.
This code (java/SAAJ)
String namespace = "http://mynamespace";;
String endpoint = "http://myserver/myservice";;
MessageFactory mf = MessageFactory.
Hi, just subscribed to the list but i searched all archived message at
http://marc.theaimsgroup.com/
before making this question:
I installed axis 1.1 on tomcat 4.1.30 correctly, used happyaxis pages and
all the test reported in the "Axis Installation
Guide"
I used the AdminClient to deploy s
26 matches
Mail list logo
