How can I get a service specific exception with a String-argument
constructor to be catch-able in my client with the message intact?
I have a service with a method from which I want to throw a service-specific
exception with a message, i.e. the exception constructor has a String
argument:
class
Hi Naresh,
This is exactly what the Web Service Invocation Framework(WSIF) is for.
Now, you describe your service with a WSDL file which includes a SOAP
binding, with WSIF you can add bindings other than SOAP to the WSDL file,
for example a Java binding. In your application you then uses the
IBM has donated WSIF to the Apache Foundation so WSIF is freely available
under the Apache license. For details of the Apache license see
http://cvs.apache.org/viewcvs.cgi/xml-axis-wsif/LICENSE?rev=HEAD. This is
the same for WSIL which IBM also donated to the Apache Foundation.
Early on there
Title: Setting Mime Header - Content-Transfer-Encoding
Hi,
I am using SOAP with attachments and have created a DataSource class to handle Base64 Encoding of ByteArrayInput/Output streams. I can successfully create the attachments but cannot work out how to set the Mime Header for the
Very interesting. I will take a look at WSIF. One quick question - how does WSIF
compare with JSR-109 (Web Services for J2EE), which seems to addressing similar
issues? Is there an overlap?
Thanks.
Naresh
-Original Message-
From: Anthony Elder [mailto:[EMAIL PROTECTED]]
Sent: Monday,
While trying to read SOAP 1.2 I came accross the term
Infoset. I could get a good idea from the pages
returned by google on xml infoset. Does anyone know of
good documents explaining xml infoset by example?
Thank you
Rf.
Sorry, I meant I could *not* get a good idea of xml
infoset.
Rf
--- rf [EMAIL PROTECTED] wrote: While trying to
read SOAP 1.2 I came accross the
term
Infoset. I could get a good idea from the pages
returned by google on xml infoset. Does anyone know
of
good documents explaining xml infoset
JSR-109 deals mainly with the deployment of web services in a J2EE
environment and relies on the JAX-RPC specification to describe the WSDL
to Java representation mappings. JAX-RPC only mentions SOAP but the JAX-RPC
API does not exclude the use of other protocols. One of our goals is for
WSIF to
On Sun, 2003-02-02 at 13:52, Anne Thomas Manes wrote:
A servlet container is a container within an application server that can
host Java servlets and JavaServer Pages (JSPs). All J2EE application
services include a servlet container. They also include an EJB container.
There are a number of
That sounds like what I want. Are you saying that I could just put that parameter tag
in the config and it would start working? Or are you saying there is still more coding
to do in Axis before that will work. Also, which version of Axis would that work in?
Thank you,
Joel Shellman
How does WSIF and Apache AXIS handle internationalization and localization
of data and messages? I see that Log4J is used as a logging mechanism, and
from that I understand how messages are localized, or can be. However, as
for data, what assumptions are made by both WSIF and Apache AXIS? What
Hi
Would this work with Java2WSDL as well?
Thanks
Mark
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 3:30 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Make beanMapping default
Hi Joel!
There is some unfinished support in Axis for
Hello Paul,
WSIF also has an asynchronous invocation
model with correlation. You can find more details about the async model
from http://www.mail-archive.com/axis-user@xml.apache.org/msg07607.html,
and more information on WSIF itself at http://ws.apache.org/wsif
Thanks,
Nirmal.
Paul
Hi Markus,
Markus Doss schrieb:
I wrote some services which transports image data to a server. I've done
this with apache soap. Now I transported a 8 MB tif image to the server
and run out of memory. Actually I don't use attachments for the service.
I code the image data base64 and sent this
Hi Mark:
It would work for auto-generated WSDL (?wsdl) from a running Axis engine, but we'd
have to put in an option to do it when using Java2WSDL from the command line.
--Glen
-Original Message-
From: Mark Rowell [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 11:13 AM
Cool... Any chance that could/would be configurable (both config files
and/or via API) such that a different default serializer could be explicitly
set (eg, if someone with a particular need wanted to replace or wrap
BeanSerializer with one that had it's own logic for determining whether
Thanks for the quick response. BTW, have done some testing here of interop
between .NET and Java and it works both ways...
(with custom types being serialized) which is great!
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 4:24 PM
To:
Hi Mike:
That kind of support doesn't exist currently, but could be added. For instance, YOU
could add it and submit a patch... :)
--Glen
-Original Message-
From: Mike Burati [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 11:25 AM
To: '[EMAIL PROTECTED]'
Subject: RE:
First I increased the memory to 128M. After increasing up to 256 the my soap client
doesn't throw any exception. But now the out of memory comes from tomcat (with 256M
memory, on linux).
Fault Code = SOAP-ENV:Server.Exception:
Fault String = java.lang.OutOfMemoryError
Any further
Hi Markus,
Markus Doss schrieb:
First I increased the memory to 128M. After increasing up to 256 the
my soap client doesn't throw any exception. But now the out of memory
comes from tomcat (with 256M memory, on linux).
Fault Code = SOAP-ENV:Server.Exception: Fault String =
The tomcat configuration with 256 and 384 doesn't work either.
-Ursprüngliche Nachricht-
Von: Elmar Fasel [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 3. Februar 2003 17:41
An: [EMAIL PROTECTED]
Betreff: Re: AW: Out of Memory problem
Hi Markus,
Markus Doss schrieb:
First I increased
If the problem is the message rather than the handling of it, have you considered
applying ZIP/UNZIP algorithms in the serializer/deserializer for your object? TIFF is
quite a compressible format.
Keith
-Original Message-
From: Praveen Peddi [mailto:[EMAIL PROTECTED]]
Sent: 03
Hi Markus,
Markus Doss schrieb:
Increase the memory allocation pool size of tomcat?
The tomcat configuration with 256 and 384 doesn't work either.
Well, than you should probably investigate the usage of attachments, as
Praveen mentioned.
Regards,
Elmar
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 07:30
Subject: RE: Make beanMapping default
Hi Joel!
There is some unfinished support in Axis for autoTyping, which sounds
like what you want. AutoTyping, when switched
send it as an attachment. That works for files that size. base64 encoding is
very slow as well as being inefficient; XML parsers dont like strings that
size.
- Original Message -
From: Doss Markus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 08:14
Subject: Out
Hi Doss,
I am using Apache SOAP tool kit. Even though the server code is same, client
code differs. Look at the Axis samples for attchments. It has some basic
programs on how to write soap with attachments. Look at the Echo example.
Praveen
- Original Message -
From: Doss Markus [EMAIL
Title: RE: training for axis
I've created a web services course that covers Axis in a fair amount of detail and uses it for all the SOAP and WSDL-related lab exercises. You can find information on it at http://www.ociweb.com/education/course_description.cgi?courseCode=ESXM03-01. Travelling to
- Original Message -
From: Brian Ewins [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 09:48
Subject: Re: Out of Memory problem
Steve Loughran wrote:
send it as an attachment. That works for files that size. base64
encoding is
very slow as well as being
For all those people who want to do attachments, here is an early draft of
something I'm writing to look at attachments properly, including for .NET
and other platforms. Here is the Axis coverage; the code was working against
the CVS version of Axis this weekend; there have been changes in
Hi All,
I have a soap method on the server side that
implements soap with attachments (method takes DataHandler as an argument). we
have clients implemented in different programming languages like Java, C, VB and
accessing soap services. With Java everything works perfect. Now we are trying
Very nice presentation, Mark - I just downloaded it and took a look. In
case anyone else on the list is interested in Axis training or mentoring
I should mention that I also provide these services, with the emphasis
more on mentoring and getting projects off the ground quickly. The
Reading
- Original Message -
From: Dennis Sosnoski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 10:44
Subject: Re: standalone vs. servlet
Just in passing, one particular area that I suspect causes performance
problems is the SAX event stream buffering that gets done
Hummm..
You could try generating the WSDL2Java Bean from the WSDL, then editing the meta-data
in the Bean to remove the properties that you don't want exposed. Axis uses this meta
data in WSDL generation.
You could also try adding a BeanInfo class, which I believe the code that Axis uses
- Original Message -
From: Mark Mueller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 14:32
Subject: Re: Fear of Attachments
Hi Steve,
Thanks for the paper, it is helpful. I gather that it
makes sense to support both MIME and DIME attachments
in order to
Title: RE: Keep-alive SOAP connections are disabled in Axis; Axis hangs if they are enabled
Hi
Betsy, I looked at the several messages posted by Sebastian on 12/17 but didn't
find the changes you referred to. I would appreciate it if you would forward
that message to me. Re Chen's patches,
As of now, my deploy.wsdd file is topping 477kB, and I notice that a lot of
the bean mappings for each service are simply repeats.
Is there a way to either:
a) tell AXIS that for a service, map all incoming items of name X to
class package.to.X
b) put the mappings in a block outside
option b is good . You can specify all the bean mappings inside
deployment. It need not be inside the service defintion. and you need
not reference the mappings inside of a service as long as the mappings
are in the same wsdd.
Vidyanand.
-Original Message-
Hi all.
I want to install axis with services already preinstalled (instead of
hotdeployed). So, I think of editing axis config file directly.
Which parts of the axis config file may I delete (e.g. JWSHandler etc.)?
Or, to ask the other way around: Which parts of the server-config.wsdd may not
This usually happens when
a) the URL that clients uses for a service is wrong .
or
b) the service is not deployed in the server.
Vidyanand.
-Original Message-
From: Ray S. Karkera
Sent: Sun 2/2/2003 1:10 PM
To: [EMAIL PROTECTED]
Hi I have made a web service, a very simple jws file. This is the code:
public class HelloWorldService
{
private java.lang.String sGreeting = ;
public String getMessage()
{
return(sGreeting);
}
40 matches
Mail list logo
