Bill,
If you use the WSDD file when you change machines, you don't have to bother
with the WSDL. Just re-deploy the WSDD file (which doesn't contain
machine-specific information) on whatever machine you like and voila, you'll
get a WSDL that contains that machine's information.
The specs for web
ervice,
: > you have no way to search for services that use one format versus another
: > without doing a detailed analysis of each WSDL file.
: >
: > Anne
: >
: > -Original Message-
: > From: Anand Natrajan [mailto:[EMAIL PROTECTED]
: > Sent: Tuesday, November 16, 2004 1
On Tue, 16 Nov 2004, Jim Murphy wrote:
: Anand Natrajan wrote:
:
: > So what's my approach? Much as there is talk about writing WSDLs first, I
: > prefer generating them automatically. I can do all the refactoring I want in
: > my Java code and trust the java2wsdl generator to gener
D, deploy. I think the step of generating the WSDL from the class
: and then generating the server side "clutters" the process up a little
: bit. It's another source of potential error.
:
: Anand Natrajan wrote:
: > I agree with Joe's analysis overall, but I would be a bit m
I agree with Joe's analysis overall, but I would be a bit more positive
about approach #2. In this approach, you generate a Java class and use that
you deploy your service. That's Joe's preferred approach and mine as well.
However, the developer really doesn't have to diddle with WSDDs... or even
While I understand the attraction to factor out common definitions into a
separate schema file, I am a bit conflicted about the use of schema files
within a WSDL for describing a service.
If your WSDL imports a schema, you can no longer hand out a single file to
your customers and ask them to gene
Suzy,
It's possible, legitimate and reasonable to return arrays of complex objects
using SOAP. In other words, your Java objects should have fields that are
simple types, e.g., String, int, boolean, etc. Your method should return an
array of this type of object (not ArrayList). Doing so will make
Agreed re: port number change, but re: IP change, there's no real difference
which one you use. If that address is on the public internet, then anyone
can nslookup the IP address and get the machine name. If it's on an
intranet, then knowing the machine name gives you little advantage. Security
thr
Anup,
One of the major features of web services is that it does not require the
client to know much about the server's implementation. All the client needs
to know about is the interface to the server's operations, which is what the
WSDL encapsulates.
Accordingly, your request is, in theory, inad
Andrea,
Absolutely correct analysis. In general, the big overheads with web services
are:
- serialisation of the request on the client side
- parsing the XML on the server side
- deserialisation of the request on the server side
and the whole thing repeated symmetrically for the response.
By send
Morten,
I assume you're building your WAR file using Ant. If so, then you can use
the same trick I do. As part of my Ant tasks, I "deploy" my web services by
constructing the server-config.wsdd file at compile-time. This approach is
not only automatic, but also doesn't require Axis to be running w
Hi!
I tried something like this about a year ago - it's tricky. I'll try to
explain what I did using your terminology.
In my case as well, the client would invoke a method on MyService, but I
wanted the same method to be forwarded to CommonService. What I found out
quickly was that unless MyServi
Update on this issue: I have started getting time-outs on methods that
return less data as well. When I revert to 1.2beta2, everything is back to
normal and working condition.
Should I enter a bug?
Anand
On Sun, 12 Sep 2004, Anand Natrajan wrote:
: All,
:
: As part of the web services I am
All,
As part of the web services I am deploying, I have some methods that take a
while to complete (in truth, they return so much data that it takes a while
to accumulate all of that).
When I was deploying Axis 1.2beta2 on the server and client side, everything
worked well with whatever defaults
r both .NET and java?
:
: Raul
:
: -Original Message-
: From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
: Sent: Wednesday, August 25, 2004 8:58 PM
: To: [EMAIL PROTECTED]; 'Anand Natrajan'
: Subject: RE: What's the right WSDL for MIME?
:
:
: Btw -- WS-I just published the Attachments Pr
All,
I have a web service implemented in Java using Axis. In this service, I have
a method that takes some simple params and returns a single attachment.
Following the Axis examples, I have defined the signature of this method as:
public DataHandler fileReadAttach(AvakiPrincipal principal,
Dexter, Henry:
Axis 1.2b2 works just fine with doc/lit. From the error you're reporting, it
looks like java2wsdl cannot find a way to serialise some of your custom data
types. I have a similar situation, and I use the Ant task below. Perhaps you
can start from that to construct your command-line i
ds of the many.
Anand
On Wed, 18 Aug 2004, Elliot Metsger wrote:
: Anand et. al,
:
: Can you offer your perspective on the interoperability of rpc/lit in the
: future? Dosen't the WS-I Basic Profile 1.0 go a ways to reducing
: opportunities for interoperability issues?
:
: Thanks,
: Elli
Charles and Steve,
Mostly for my curiousity, are you using an rpc/encoded service or a
document/literal service? My information may be wrong, but I believe the
latter doesn't support overloaded methods. Given that the web services
world is moving to doc/lit, having overloaded methods may be ill-ad
I have a similar problem - I simply rename the files when necessary. I have
the additional problem that Axis isn't up and running when I compile, but my
services have to be deployed by the time the app server comes up. As a
result, I do a lot of filterchain tasks in Ant in order to "deploy" the
ser
Shashi,
I am very familiar with that problem (I entered the bug report to which you
allude in your email). Yes, this is a serious interoperability problem.
However, I now agree with Davanum Srinivas that Axis 1.2 is actually doing
the correct thing when it assigns the soapenc namespace to string.
Marc,
I had a similar problem, but some details are different. In my case, I had
to send a single binary, not an array of them. Also, I was retrieving the
binary from the server, not sending them to the server.
When I exposed the operation within a doc/lit service, I saw exactly what
you see - ea
. i'm not concerned with the server side at all though. my client is running
against a test server right now and will need to switch to a production server soon.
instead of recompiling my client code, i would like to be able to read the url from a
config file and use code to point to the
The classes that have the web server hard-coded in them are purely
client-side stub classes. They are not necessary on the server side.
After you deploy your services on the production server, your clients can
get a WSDL, run wsdl2java and generate the stubs themselves. You should not
have to hand
Things to try:
1. Instead of deploying with the AdminClient tool, try this. Edit Axis's
server-config.wsdd file (in axis.war/WEB-INF). Check if the XML snippet
for your deployment is actually part of server-config.wsdd. If it's not
there, that's a problem, perhaps with AdminClient or the
rviceLocator.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
: >hostname, that's a different issue.
: >
: &
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
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
Suzy,
WSDDs are Axis artifacts - they're present just to tell Axis what service
you intend deploying. Subsequent to deploying a WSDD you have a web service
(running inside Axis), and can get to the service's WSDL.
JWS files also are Axis artifacts, I believe (this one I not so sure about).
If you
ideas I would appreciate them.
: *
:
: In terms of interoperability with different clients, .Net 1.1 clients are my
: main focus at the moment, however inter-operability with other clients, be
: they php, perl, VB or whatever, is still important.
:
: *
: * Anand, can you expand on any interoperabil
: Anand Natrajan [mailto:[EMAIL PROTECTED]
: Sent: 28 July 2004 18:02
: To: [EMAIL PROTECTED]
: Subject: Re: Trouble with live deployment
:
: Seems like you don't have Axis deployed at all on the liver server. Can you
: try opening http://:8080/axis ? Does that work? If no, that's
: the probl
Seems like you don't have Axis deployed at all on the liver server. Can you
try opening http://:8080/axis ? Does that work? If no, that's
the problem. If yes, try the Happy Axis page to see if Axis's deployment was
copacetic.
Anand
On Wed, 28 Jul 2004, Ciaran Hanley wrote:
: We are having troubl
Marc and Brian,
Forgive me if this is a naive question, but won't your actions below make it
hard to write non-Java clients targetting your web services? It may be hard
for Perl and VB clients to duplicate the complex data structures you're
planning, even if you manage to make Java clients work. M
Arnaud,
Are you generating a document/literal WSDL? If so, what you're seeing is not
surprising. I was surprised myself when I first saw this behaviour, but all
my web service clients seem to know what to do with such a WSDL. They
generate proper stubs/proxies and consume the SOAP responses just a
Absolutely. I tried deploying the service with the same name but in
rpc/encoded mode as well as document/literal - didn't work. In retrospect,
duh! only the last deployment took effect. As a result, I deploy the same
service under two different names - MySvcRpcEnc and MySvcDocLit - reflecting
the t
at I need to do.
:
: Does anyone know how to force this behavior?
:
: Thanks again.
:
: Tony Piazza
:
:
: --- On Wed 07/21, Anand Natrajan < [EMAIL PROTECTED] > wrote:
: From: Anand Natrajan [mailto: [EMAIL PROTECTED]
: To: [EMAIL PROTECTED], [EMAIL PROTECTED]
: Date: Wed, 21 Jul 2004 13:00:59 -040
Anthony,
I'll pass on some wisdom I learnt just a day or so ago that may be worth
trying. Find out your Axis client's client-config.wsdd file. In that, there
may be a tag called . Inside that, add the following
XML segment.
Can't guarantee whether it'll work or not, but itmay rem
Follow-up: I'm seeing the same problem as below with Axis 1.2beta2,
the July 15th release. I've entered a bug report (AXIS-1467).
Anand
On Mon, 19 Jul 2004, Anand Natrajan wrote:
: Hello,
:
: I'm seeing some client-side serialisation errors when I try to access my
: Axis 1.2 rpc/
Vikas,
Yes, I am in the process of doing so - actually, I am providing an
rpc/encoded version as well as a document/literal version of the same
service.
The basic process is mostly identical, but one gotcha is that you should use
Axis's wrapped/literal mode in order to get better interoperability
and 1.2 in this respect.
I plan to enter a bug regarding this issue shortly.
Thank you!
Anand Natrajan
import com.abc.api.common.MyPrincipal;
public class MyAPIRpcEnc
{
public String[] whoami(MyPrincipal principal)
throws
l after this experience;
: : : perhaps you could do the same.
: : :
: : : Anand
: : :
: : : On Wed, 14 Jul 2004, Anand Natrajan wrote:
: : :
: : : : Is your web service exposed as adocument/literal?
: : : : If yes, I face a similar problem - Axis 1.2 beta
: : : : (June 14th release) make
he spec for doc/lit indicates, but
: : it seems unintuitive to me.
: :
: : I'm moving over to wrapped/literal after this experience;
: : perhaps you could do the same.
: :
: : Anand
: :
: : On Wed, 14 Jul 2004, Anand Natrajan wrote:
: :
: : : Is your web service exposed as a document/litera
me.
:
: Anand
:
: On Wed, 14 Jul 2004, Anand Natrajan wrote:
:
: : 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
On Wed, 14 Jul 2004, Anand Natrajan wrote:
: 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
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
ava.lang.String path) throws java.rmi.RemoteException;
Although not identical, they're close enough that I can work with them.
Anand Natrajan
Azmi,
I had a similar problem, although on carefully reading it, it looks to be
the reverse case.
When my service and client were both in Axis 1.1, my service sent a
DataHandler, but my client had to use AttachmentPart to get at it.
AttachmentPart is part of the org.apache package structure.
Whe
e types between services.
Sadly, that's not possible... I do want some complex types to be used by
multiple services.
Thanks!
Anand
: - Arent-Jan
:
: -Original Message-
: From: Anand Natrajan [mailto:[EMAIL PROTECTED]
: Sent: Tuesday, June 29, 2004 7:14 PM
: To: [EMAIL PROTECTED]
: Sub
On Tue, 29 Jun 2004, [iso-8859-1] Göran Andersson wrote:
: > Anand Natrajan wrote:
: >
: > >Hello!
: > >As part of my .NET and Axis interoperability work, I am
: > facing a piquant
: > >situation. I have written multiple web services using Axis.
: > Each of these >
t.
Thanks for responding though! Although your suggestion isn't ideal, it's
still the best I've got, and it made me think. (:
Anand
On Tue, 29 Jun 2004, Vy Ho wrote:
: Is it possible to merge all your wsdls into a same wsdl file? Or
: specify a same namespace for all of them
y help, and for even reading this. I will peruse this group
regularly for any response, but I'd also appreciate a copy sent to
[EMAIL PROTECTED]
Anand Natrajan
51 matches
Mail list logo
