RE: iSeries web service error from .Net application

What happens when a different language or application needs to consume
the web service and then wouldn't have access to your config file (which
you are storing in CVS or SourceSafe I am assuming)?  You could have
each language/application carry the URL's with them through the
development cycle, but that will put you into maintenance mode to make
sure you have all of the consumers updated with the latest URL, won't
it?

>I shouldn't have to re-examine the WSDL to call the web service each
time.
I agree with you here.  That would be a waste of CPU cycles, bandwidth
and time.

I think we are just choosing between the lesser of two evils.  I will
have to look into Ant like Matt Haas suggested.  JNDI might also be the
solution given that a company will most likely have different server
instances for development, testing, and production.  You can read about
JNDI here:
http://java.sun.com/products/jndi/tutorial/getStarted/concepts/naming.ht
ml

I am guessing .NET also has a similar technology to JNDI.

Aaron Bartell

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] 
Sent: Wednesday, October 20, 2004 12:31 PM
To: Web Enabling the AS400 / iSeries
Subject: RE: [WEB400] iSeries web service error from .Net application

>(assuming from your response that you are challenging my method)

Challenge is such a strong word... <G>

>You are still hard coding just as much as I am.   

Not so sure. I'm simply changing the .config file as I move from
environment to environment. Unless I grossly misunderstand what .NET is
doing with the WSDL .NET doesn't look at the WSDL once the stub is
generated. So changing the location is the WSDL doesn't buy me anything.
And even if the WSDL is reevaluated each time, how do you tell the
application where to look for the WSDL? 

I'm drawing a line between the WSDL which I consider part of the
development side of the world and the URL for the implementation of the
web service which I consider part of the runtime side of the world. I
shouldn't have to re-examine the WSDL to call the web service each time.


If I understand what your saying, you change the location in the WSDL as
you move from environment to environment. However, how do you tell the
application where to look for the WSDL?

-Walden 


------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com