The right way is to write a interface which includes all
the Methods your webservice should offer.
Then you use java2wsdl to generate your wsdl. You have to correct
your parameternames in your auto generated wsdl, cause the the
params looks like in0, in1, in2... .
Then you use wsdl2java to
rosely kumoi wrote:
I already highlight this issue long ago and no one until now have the
solution. The aforementioned JROM is obselete (last updated June 7, 2002), I
think the guy who create the API already drop the project which is sad. I
already try JROM but its using an obselete version of
Hi,
I think the problem isn't the size of the soap message, but the number of elements it
has.
I had a problem with messages around 1 MB whose were formed by an Array of strings
with 80.000 items, so I had memory DoS problems.
The solution was to implement an Axis Handler to Limit the Request
If instead of writing an interface you write a class then java2wsdl will
include your parameter definitions in the generated wsdl
e.g. instead of
public String getFoo(String myParam);
public String getFoo(String myParam) return null;
All best
Andy P
-Original Message-
From: Dorner
I disagree, the right way is to start with your WSDL and schema files. If
you want any hope of being WS-I compliant or using doc/literal this is your
best bet. As soon as you start with an interface, you start dealing Java
types that do not correlate to schema types very well. For example, if you
You are right - if you will do a interoperable webservice
that deal with other clients (.Net ...) its better to go from the
wsdl.
But when i use String, int and so on and i generate a wsdl by
java2wsdl, I hope the wsdl i get, depends on the standard spec.
for wsdl!
So there should no problem
Hi all,
I need some help with the following problem:
Overview:
My java object receives and parses a SOAP message (on a TCP/IP socket)
then calls an appropriate operation/method on a remote web service using
a client stub (RPC HTTP Request).
The remote web service returns a SOAP response message
Hi,
I'm an Axis newbie struggling away not very successfully at the moment :(
What I want to do is create a range of services that send images. I was
hoping to use Axis as the server, java code as the provider and to be able
to send the images using attachments to both .NET clients and other
My first attemps have started with a WSDL/Schema then I generate everything.
I was able to find an example at W3.org and I just manipulate it to the way
I need it. I thought this to be the best way at the time because of
interoperability.
From what I've been finding thus far there are no Standard
I will be out of the office starting 05/12/2004 and will not return until
05/25/2004.
I will respond to your message when I return.
Not fully answering your question, but you might want to consider
returning only URL's to the image, instead of the image itself.
Configure your http server to serve the image url's with or without
authentication (embedded into the url for example).
That way, whoever consumes your web service
Hi.,
I have done few samples using axis.Everything went on well.
Now i'm trying to do my real application.
My situation is.,
I have developed DAO and VO object.
I need to publish my DAO as a webservice and I have to write a client.
I just published my DAO as webservice.that is fine.
while
If the service is defined as a request/response pattern, then I don't think
that's possible. You should return a SOAP Fault, but you might consider
sending back an HTTP error instead.
Anne
-Original Message-
From: Robert Mecklenburg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 11, 2004
If the service is defined as a request/response pattern, then I don't think
that's possible. You should return a SOAP Fault, but you might consider
sending back an HTTP error instead.
Anne
-Original Message-
From: Robert Mecklenburg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 11, 2004
My portal app runs fine on my WSAD 5.1 with WebSphere portal tool kit 5.0 (test portal
server) running on XP, but when it's deployed on WebSphere portal server 5 on Win2000
server, it caused class not found exception on classes appear to be used by axis.
The app uses soap package Axis 1.1
I believe we have used AXIS from within WPS5 here, I can check with the
person(s) involved.
Which classes are not found when you run your app on WPS?
Also, you can set PARENT_LAST on either or both of the EAR and the WAR in
the WAS5 administration tool. Make sure it's set on the WAR (web
Thanks for the answer.
Hmmm. No documentation is a bit of a drawback. The Java2WSDL tool will
need to improve to compete with .NET
[EMAIL PROTECTED] wrote:
Hey Stuart,
AXIS uses reflection to generate the WSDL. As such, it does not have
access to the JavaDoc, which is only contained within the
Mike:
We were getting the org.apache.acess.client... I'll check with my server admin to
make sure PARENT_LAST is set on the war file also. I would greatly appreciate if you
can share/find out what's done to get axis working in WPS5. The IBM tech support
wasn't much helpful, all they
Thanks for reply,
Unfortunately the images are kept in a database, so this is not possible.
Andrew
-Original Message-
From: easterguest [mailto:[EMAIL PROTECTED]
Sent: 12 May 2004 15:13
To: [EMAIL PROTECTED]
Subject: Re: Attachments Axis and .NET
Not fully answering your question,
I would venture to say that 80% of the complications and frustrations
implementing interoperable (WS-I compliant Doc/Literal) SOAP web services on
Java platforms stem from the XML datatype to Java datatype binding problem.
If you take the time to learn W3C XML Schema, you'll see the problem: it's
Should be easy enough to write a little servlet to proxy the http:get
requests from a JDBC connection?
But anyway.
Andrew Premdas wrote:
Thanks for reply,
Unfortunately the images are kept in a database, so this is not possible.
Andrew
-Original Message-
From: easterguest
http://cvs.apache.org/dist/axis/nightly/
-- dims
As long as you're sending only simple types, it's easy, and you should be
able to get by generating the WSDL from your Java interface -- just make
sure you specify the wrapped option.
When you're using complex types, you need to be a lot more cautious. If you
generate the WSDL from a Java
As long as you're sending only simple types, it's easy, and you should be
able to get by generating the WSDL from your Java interface -- just make
sure you specify the wrapped option.
When you're using complex types, you need to be a lot more cautious. If you
generate the WSDL from a Java
DIME attachments work. You need to use the .NET WSE package to use
attachments.
-Original Message-
From: Andrew Premdas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 10:00 AM
To: [EMAIL PROTECTED]
Subject: Attachments Axis and .NET
Hi,
I'm an Axis newbie struggling away not
DIME attachments work. You need to use the .NET WSE package to use
attachments.
-Original Message-
From: Andrew Premdas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 10:00 AM
To: [EMAIL PROTECTED]
Subject: Attachments Axis and .NET
Hi,
I'm an Axis newbie struggling away not
I want to implement a service that authenticates the caller (using a
certificate in the message). If the user is not authorized to invoke
the service, I want *no response* sent at all. No return value, no
exception, nothing. Is this possible?
I agree with Anne, this is a somewhat unnatural
+1!!!
-Original Message-
From: Anderson Jonathan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 11:03 AM
To: [EMAIL PROTECTED]
Subject: RE: Best Practices?
I would venture to say that 80% of the complications and frustrations
implementing interoperable (WS-I compliant
+1!!!
-Original Message-
From: Anderson Jonathan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 11:03 AM
To: [EMAIL PROTECTED]
Subject: RE: Best Practices?
I would venture to say that 80% of the complications and frustrations
implementing interoperable (WS-I compliant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'd like to serialize an application context(not an axis context) with the
responses to the calls to my services. I can now call my handler at the good
time. My problem is that I have services that are returning differentt
things. The services
Cape Clear's WSDL/Schema editor is free?
I was under the impression that it was only available as a component
of their Cape Clear 4 product.
I evaluated CC awhile back, and was
impressed with Cape Clear Studio...but found it cost prohibitive. Although
we eventually chose a different SOAP
Hi People,
I encountered a few problems installing Axis. The happyaxis testpage
mentioned errors like :
could not find class javax.xml.soap.SOAPMessage from file saaj.jar
Like noted on the happyaxis-page, this is because on Tomcat 4.x and Java1.4,
you need to put libraries that contain java.*
Hi,
I defined an interface: com.idx.lw.webservices.inbox.InboxRetrievalService like the following:
public interface InboxRetrievalService {
public String getInboxList(CISContext cisContext, InboxRetrievalBean inboxRetrieval) throws CISException;
}
where class CISException extends
Hi,
I'm completely stumped on this problem. Short version: AxisServlet lists
my service and its methods, but I can't generate WSDL or use the methods
(via GET requests, anyway.)
Long version: I've taken Axis and tried to retrofit it into an existing
application with several servlets. I copied
This is something I don't understand - I have two services published each
with one method. Two separate classes.
But, no matter which call I make, only one of the operation is being called.
Here is the descriptor :
service name=ComInfo provider=java:MSG
I have generated a WSDL for my webservice manually using the Java2WSDL tool
and compared it against the WSDL I get when I query the webservice.
They look very different. The manually generated one contains my beanmapped
classes and extended custom datatypes, whereas the dynamic one doesn't.
Thanks for the advice! This is exactly what I've been looking for.
It almost seems that people end up using Axis inspite of itself. But, it's
just too dang easy to get something up and running. I imagine JWS files have
lead many people astray with their simplicity. If all services could work
like
Let's twist this discussion on its head
- Is there a list of bugs hiding in there somewhere? (bug reports)
- What would you do if you were to write/re-write parts of axis?
(enhancements requests)
If we can't create new bug reports / enchancements to tell axis
developers how axis should behave
See http://marc.theaimsgroup.com/?l=axis-userm=108247433123185w=2
For C# the code would be (it's for other service but you'll get the
idea):
localhost1.fileserveService filese = new
localhost1.fileserveService();
localhost1.FileAttributes[] fa =
Exactly, that is why Jonathan Anderson is on the wrong track. He describes what he
currently has to do. The real question is in the long run what is the right way to
do things and push for that and get Axis to migrate in that direction. I personally
still believe that writing wsdl files
Lerena, Alberto wrote:
Hi,
I think the problem isn't the size of the soap message, but the number of elements it has.
I had a problem with messages around 1 MB whose were formed by an Array of strings with 80.000 items, so I had memory DoS problems.
Alberto,
could you specify exactly what
Greeting Folks,
I have what seems like a question which many might ask, but after searching
through the various Axis docs, along w/ some of the reccommended reading,
as well as perusing the archives of this list, I remain unclear on the
answer, so at the risk of proving myself an idiot for
I'm fairly new to web-services (and axis), but am a seasoned programmer.
Comparing web-services to other technologies, CORBA for instance, you always
started with the interface definition, never the code. I personally don't
find WSDL to be all that difficult to work with, even by hand, and there
But many people already have a service in use internally that they would like to
expose to the outside world.
They have already decided what that service was supposed to do, the arguments, etc
before coding it during their initial development process.
Jan
-Original Message-
From:
Goldstein, Scott wrote:
Alek,
Thank you for your reply!
So, from your message, it appears that this is a feature in Axis 1.2 and
you're not sure whether it's available in 1.1.
i do not have 1.1 source code around to check.
Also, it's still unclear
exactly what the feature is.
you can
I think factoring out the XML-Java Language binding into pluggable
components would help - kinda like people are using Castor. I guess
that means some WSDL generation parts need to be extensible too but...
I like XmlBeans for XML-Java-XML but I'm not sure its practical to add
support for it
Perhaps it would be possible to put a ServletFilter in front of Axis that
filters out the response body under certain conditions?
Best regards,
Robert Lowe
http://RMLowe.com/
-Original Message-
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 11:31 PM
To:
Point taken. I suppose that's part of the confusion and complexity of a
product like Axis - there are many different usage scenarios and supporting
them all well is a daunting task to say the least. All in all, I applaud
the Axis developers for an excellent product!
Russ
-Original
I've looked through the 1.1 source code and the feature exists on the
server side. Though, when I try to turn streaming on, the parsing
fails. So, I suppose the following questions still remain:
1. Is this feature supported for Axix 1.1. Would it be a bug if the
feature doesn't work as
Hi,
After more digging and diffing, I realized that I misunderstood the
deployment system.
I had placed a server-config.wsdd in my webapp's WEB-INF directory with a
description of my service. This overrode the default one, which includes:
handler
Jim,
JAX-RPC 2.0 mandates JAXB
-- dims
On Wed, 12 May 2004 13:58:50 -0400, Jim Murphy [EMAIL PROTECTED] wrote:
I think factoring out the XML-Java Language binding into pluggable
components would help - kinda like people are using Castor. I guess
that means some WSDL generation parts need
No. I don't think Jonathan is on the wrong track...It's just that we
need to understand existing situation better which is always the right
thing to do. What i was suggesting was how do we learn from what he
have and turn it into what we want it to be.
-- dims
On Wed, 12 May 2004 10:30:23 -0700,
I have not yet read the JAX-RPC 2.0 spec but if it does mandate JAXB
will a future version of axis that implements JAX-RPC 2.0 allow the user
to plugin any JAXB implementation he wants or will Axis ship with a JAXB
implementation that will have to be used?
-Original Message-
From:
Any JAXB Impl. default to JaxMe (http://ws.apache.org/jaxme/)
On Wed, 12 May 2004 14:43:56 -0400, Keith Bohnenberger
[EMAIL PROTECTED] wrote:
I have not yet read the JAX-RPC 2.0 spec but if it does mandate JAXB
will a future version of axis that implements JAX-RPC 2.0 allow the user
to
Mandates JAXB 1.0 or 2.0?
Jim
Davanum Srinivas wrote:
Jim,
JAX-RPC 2.0 mandates JAXB
-- dims
On Wed, 12 May 2004 13:58:50 -0400, Jim Murphy [EMAIL PROTECTED] wrote:
I think factoring out the XML-Java Language binding into pluggable
components would help - kinda like people are using
http://www.jcp.org/en/jsr/detail?id=224
On Wed, 12 May 2004 14:45:13 -0400, Jim Murphy [EMAIL PROTECTED] wrote:
Mandates JAXB 1.0 or 2.0?
Jim
Davanum Srinivas wrote:
Jim,
JAX-RPC 2.0 mandates JAXB
-- dims
On Wed, 12 May 2004 13:58:50 -0400, Jim Murphy [EMAIL
Thanks for the link and the sample code, Paulo.
And to clarify my last statement, you use WSE with .NET to enable DIME
attachments. (Standard .NET doesn't support attachments.)
See also this paper by Steve.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08732/Fear_of_Attach
ments.pdf
Anne
Thanks for the link and the sample code, Paulo.
And to clarify my last statement, you use WSE with .NET to enable DIME
attachments. (Standard .NET doesn't support attachments.)
See also this paper by Steve.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08732/Fear_of_Attach
ments.pdf
Anne
Okay -- so you've already defined your interface. But if that interface
contains Java-specific types that don't map well to XML Schema types, then
you can't directly expose your current interface. You'll need to build a
wrapper.
There is an impedance mismatch between Java types and XML types.
Okay -- so you've already defined your interface. But if that interface
contains Java-specific types that don't map well to XML Schema types, then
you can't directly expose your current interface. You'll need to build a
wrapper.
There is an impedance mismatch between Java types and XML types.
Dims,
Thanks for clarifying - I noticed: SOAP 1.2, WSDL 1.2 - is there a
roadmap for this yet?
Jim
Davanum Srinivas wrote:
http://www.jcp.org/en/jsr/detail?id=224
On Wed, 12 May 2004 14:45:13 -0400, Jim Murphy [EMAIL PROTECTED] wrote:
Mandates JAXB 1.0 or 2.0?
Jim
Davanum Srinivas
But assume you use a java interface or class, the tools should warn you that
what you did is not compatible outside of the Java realm. Maybe there should be an
option to check for compatibility or not? What about the -WSIBP option that generates
wsdl for the WS-I BP and gives you errors if
I have two services: Service1 and Service2. I have a class that methods in both
services
accept and return: CommonClass. These classes are in one package.
If I use Java2WSDL to produce .wsdl files for both services, Service1 puts CommonClass
in its
namespace, and Service2 puts CommonClass in
RM I want to implement a service that authenticates the caller (using a
RM certificate in the message). If the user is not authorized to invoke
RM the service, I want *no response* sent at all. No return value, no
RM exception, nothing. Is this possible?
Anne Thomas Manes writes:
ATM If the
It sounds like what you want is HTTP DIGEST authentication, which supplies
a client certificate outside the realm of SOAP. Or am I lost (again)?
Have you looked into it? Doing so would not simply drop the connection,
it would return a standard HTTP 401 (unauthorized), however...
Russ
Ross,
Ok, let me try to rephrase my point. Your WSDL+XSD (let's assume HTTP
binding using doc/lit) defines the document oriented messaging exchange
contract that your service adheres to.
Now implement that service with Perl.
Or C#.
Or Java.
You're a Java developer, and naturally you're used to
If I understand what you are saying, you want to take the servers response
and re-package it as a SOAP Message and send it somewhere else?
If so, then you would need to write your own class which creates a SOAP
Message. The following book will tell you how to create your own SOAP
Message
Whenever I have had a SAXException: there are two things I do:
1) Make sure the type has an entry in the deploy.wsdd, so Axis knows what
deserializer to use.
2) Turn on TCPMon to see exactly what is coming back from the server
- Original Message -
From: Malai [EMAIL PROTECTED]
To:
Hi,
I am a novice Axis user; so, please bear with me if I am
asking a very basic question.
I am trying to deploy a service and write a client (not an auto
generated stub). It will be great if someone can tell me what this exception
means
AxisFault
faultCode:
Don't get me wrong Dims - I have a lot of high hopes for the JAX-RPC
2.0/JAXB 2.0 marriage.
I'm just wondering what Axis can productively do until they start dropping
draft specs. I think all you realistically hope for is to shore up JAX-RPC
1.1/WS-I BP 1.0a support as best you can in Axis 1.x,
This is covered in the Axis Users's Guide. You need to register the
your serializers/deserializers both on the Server as well as the
client. You do this by adding a line to the WSDD file for the server.
And, making a call to "registerTypeMapping" on the Call object for the
client.
Good Luck,
I believe it means that there is no "typeMapping" entry in the
deploy.wsdd for ResultsetType.
- Original Message -
From:
Saritha Bhandarkar
To: [EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 7:05
PM
Subject: could not find deserializer
error
Hi,
I
72 matches
Mail list logo
