RE: iSeries web service error from .Net application -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: [WEB400] iSeries web service error from .Net application
From: "Haas, Matt" <Matt.Haas@xxxxxxxxxxx>
Date: Wed, 20 Oct 2004 13:41:34 -0400
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

<snip>
I think what we can both agree on though is that it would be nice if
within the Dynamic Web Project Properties there were settings for how to
deploy a WSDL through a development lifecycle.  But then you start
<snip>

Can you use Ant (or something like it) to do this? We have a lot of the same 
issues with our Java apps that are hitting various things (databases, LDAP, web 
services) that change during the devolvement/deployment life cycle and with 
Ant, it's relatively easy to change the configuration files.

Matt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.