Hi all,
I am using Axis 1.1 Java for creating my WS app (using WebObjects).
When I create a fault in my app (AxisFault), I always get a stack trace.
I have tried aFault.setFaultDetail(null) and other things to no avail.
What I would really like to do is this :
When a fault situation occurs, return
FYI, both implement JAX-RPC 1.1 so what u can do with SUN, you can do
with Axis...
-- dims
On Fri, 30 Jul 2004 16:44:14 -0700, rob rowntree
<[EMAIL PROTECTED]> wrote:
> i looked into this a little more and read about Sun's new JAXRPC 1.1.2 which
> is contained in the JWSDP 1.4
>
> see it at:
>
Hello,
The classes in:
org/apache/axis/transport/jms
exist in the source but are not in axis.jar in Axis 1.2 Beta distribution.
Is there a reason behind this or is it just missing from the jar file in
error?
Regards,
Len Takeuchi
i looked into this a little more and read about Sun's new JAXRPC 1.1.2 which
is contained in the JWSDP 1.4
see it at:
https://jax-rpc.dev.java.net/whitepaper/1.1.2/attachments.html
With respect to some detailed features concerning SAAJ and MIME types for
SOAP attachments, it seems as though the
Hi,
Java2wsdl and wsdl2java programs seem to have an System.exit() of some
kind. This makes it difficult to execute this command in a loop
repeatedly. Is this true? What is the way around it?
Regards
Sagar
Hi,
Java2wsdl and wsdl2java programs seem to have an System.exit() of some
kind. This makes it difficult to execute this command in a loop
repeatedly. Is this true? What is the way around it?
Regards
Sagar
I'm trying to use org.apache.axis.client.Call to invoke a doc/lit service, and I would
like it to send the xsi:type attributes of the parameters (I'm using WRAPPED style).
Using TCPMonitor, I notice that Axis doesn't send the xsi:type attributes. So, I dug
into the org.apache.axis.client.Call
Sorry to post this Tomcat question on this list. Is there a way to have
Tomcat auto reload jar files under webapps/myapp/WEB-INF/lib directory?
Thanks for any help!
-David
Hello friends -
I'm in the process of integrating two systems, I am using the AXIS SOAP
engine and my counterpart at another organization is using the .NET SOAP
engine. I have managed to create some stubs based on the other parties
.WSDLs. They provided the following WSDL for one of our transac
Rory,
If you use the admin client to deploy your
wsdd and don’t see that on the server-config.wsdd
Then cutting and pasting would work. But
if you want to also find the reason why that didn’t work you can try
seeing the webserver logs
In our case we are using tomcat. Errors didn’
That
should do it. You can also safely copy server-config.wsdd file generated on one
server to another (assuming same services are supported).
Jai
-Original Message-From: rory galvin
[mailto:[EMAIL PROTECTED]Sent: Friday, July 30, 2004 12:43
PMTo: [EMAIL PROTECTED]Subject: RE:
Thomas,
Thanks again for ur reply. In the mean time I've added the service element from my deploy.wsdd file to the server-config.wsdd under WEB-INF and it has appeared to have deployed. Has this had the same effect as using the AdminClient? or does the admin client do more than update server-confi
Rory,
you
have mentioned in original message you are deploying using:
java
org.apache.axis.client.AdminClient deploy.wsdd
Are
you specifying Adminservice url using -l parameter? Service won't get added to
the web app. without that.
Your
command must be something like:
java org.apache.ax
Thomas,
I did as you said and checked server-config.wsdd but the web service is still not listed. Im deploying my web services remotely using telnet. Could this be one of the problems? The annoying thing is is that the admin client keeps telling me that service has been deployed i.e. Done processi
Im having the same trouble Suzy. Even though the Admin client is telling me that the web service has been deployed its not appearing as a deployed web service. If you have any joy finding out what the problem is let me know...
>From: "Suzy Fynes" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
hi egemen,
i think you can look into:
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/
this article describes how to integrate the code generated by castor and axis
wsdl2java.
regards, aki
> -Original Message-
> From: egemen kalyoncu [mailto:[EMAIL PROTECTED]
> Sent:
Title: RE: Class Loaders and axis
Do
you have any examples of ClassUtils usage.
sagar
-Original Message-
From: Sagar Pidaparthi
Sent: Thursday, July 29, 2004 4:51
PM
To: [EMAIL PROTECTED]
Subject: RE: Class Loaders and
axis
Thanks for your
message. After reading the A
24044 [main] DEBUG org.apache.axis.encoding.DeserializationContextImpl -
Pushing element address2
24044 [main] DEBUG org.apache.axis.utils.NSStack - NSPush (32)
24044 [main] DEBUG org.apache.axis.encoding.DeserializationContextImpl -
Exit: DeserializationContextImpl::startElement()
24114 [main
Thanks very much!!!
Anand Natrajan wrote:
The java2wsdl that requires a location generates a static, "compile-time"
WSDL file that you can use to generate server skeletons (using wsdl2java).
The skeletons generated do NOT contain machine-specific code. Once you've
filled in the skeletons, you can d
Java Web Service
-Dug
"Somerville, Michael
S" <[EMAIL PROTECTED]>
07/30/2004 11:33 AM
Please respond to
axis-user
To
[EMAIL PROTECTED]
cc
Subject
RE: wsdd and jws services
Newbie question -- does the .jws extension stand for:
a) Java Web Start
b) Java Web Services
c) J
Newbie question -- does the .jws extension stand for:
a) Java Web Start
b) Java Web Services
c) Just Weird Stuff
d) none of the above
Thanks!
-mike somerville.
-Original Message-
From: Makesh Rao [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 29, 2004 7:34 PM
To: [EMAIL PROTECTED]
Subje
It looks strange how you build your java2wsdl.classpath.
I am not sure that the fileset should be use. You can use it to include jar
files, but for classes you just specified the root location.
So if you have such a structure
src/uk/bl/bspa/estar/EstarMatcherService.java
classes/uk/bl/bspa/estar/
some posting I had found said that you do BASE64 encoding and then decoding
on the client side. I have not tried that either. I have not found any
other solution some where.
We are having a similiar problem with 0x0 character. Earlier we had
similiar problems but on the BEA web logic we set the
Hi all,
I have been struggling for days trying to get Java2WSDL to work so that I
can fully automate my build process. The closest I have got is the
following:
The java2wsdl that requires a location generates a static, "compile-time"
WSDL file that you can use to generate server skeletons (using wsdl2java).
The skeletons generated do NOT contain machine-specific code. Once you've
filled in the skeletons, you can discard that WSDL file if you like because
Hi,
I’m trying to deploy my
wsdd file and have been having trouble. I can view
the current list of deployed webservices in axis from
the main page but when I tried deploying my deploy.wsdd,
after running the adminclient on it, the page is just
blank from “And now some web services” down
As
step 1, I would open up server-config.wsdd under web-app and see your services
are listed.
Jai
-Original Message-From: rory galvin
[mailto:[EMAIL PROTECTED]Sent: Thursday, July 29, 2004 11:54
AMTo: [EMAIL PROTECTED]Subject: deployment
problems
Hey guys,
I'm h
Thanks, but what about:
1) the java2wsdl requiring a location
2) the MyWebserviceServiceLocator.java that is generated - it has the
location of the service as a public final String?
Jason
Anand Natrajan wrote:
Jason,
Axis does not require recompilation. If your application itself requires the
hos
Rob,
WSDP and Axis are different implementations of the same standards - JAX-RPC
and SAAJ. Naturally, you's expect the implementations to look different.
Axis stows its implementations in jars such as axis.jar, leaving interfaces
in jaxrpc.jar. WSDP on the other hand, stows both interfaces (same
I think you should be able to achieve this by using message syle service and
using the service signature:
public void method(SOAPEnvelope req, SOAPEnvelope resp);
Whatever you add to the response will be sent back, in your case nothiing.
Thanks
Jai
-Original Message-
From: Chandrasega
Jason,
Axis does not require recompilation. If your application itself requires the
hostname, that's a different issue.
Let's say you develop your webservices on the machine batman. When doing so,
you will write Java interface/classe, java2wsdl them to get a WSDL,
wsdl2java that to get a WSDD and
Sun's recent release of the 1.4 version of JWSDP has some very different jar
files in these 2 areas:
jaxrpc jar list
saaj jar list
Can anyone provide some guidance on this general issue?
Im looking at upgrade paths for system using following and i am confused by
this divergence between Axi
Does Axis1.2 beta support the new SOAP1.2 fault format? It it does, does
anyone have or know where I can find some sample Java code that illustrates
how to generate faults using the new format.
Thanks,
George
Just a quickie folks, I need to deploy the same webservice onto many
different servers, so my question is:
Do I have to recompile my code for every server with an 'ant
-Dserver.hostname=my.server.com'-type compilation, using the
server.hostname property in the java2wsdl Ant script, or is there
I am fairly new to axis and WSDL/WSDD, but there seems to me two ways to go
about setting up a web service with the three technologies axis, WSDL and
WSDD:
1) Create the Java classes to act as your web service. Create a WSDD to
deploy the classes as a web service on Axis. Use Java2WSDL or the axis
hi Akitoshi,
thnaks for your suggest.but i'm not allowed to change schema.
i want to know something else. i want to generate method parameters from
tag not tag.
i.e;
public SubmitRsp mm7_response(SubmitReq) ==> method that i want to
generate
public submitRspType mm7_response(submitReqTy
36 matches
Mail list logo