× 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.



>The .Net application can actually execute the service I think.
>It seems to be complaining about the return data type. 

That exception looks like a connection error, but I might be reading it
wrong. Can you post the WSDL? 

If the WSDL returns a type that isn't defined to .NET then it might have
a problem. Simple types (int, string, etc.) are well-known, but complex
types need to be defined in the WSDL (or something the WSDL refers to).
I know if I allow .NET to generate a WSDL for a class that returns a
DataSet another .NET program will consume it fine since it knows what a
DataSet is, but a Java program would choke. Perhaps you're seeing the
reverse issue.

-Walden


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

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Thursday, 21 October, 2004 10:39
To: web400@xxxxxxxxxxxx
Subject: RE: [WEB400] iSeries web service error from .Net application

Aaron,

Sorry for the delay I was unexpectedly our of the office yesterday.

>What type of web service is it?
I'm not sure what you are asking for.  I have two Java classes, one for
the iSeries server functions, and one to handle the business logic.  I
right-clicked on the business logic class and had WDSc create the web
services for me.

>Are you using SOAP?
Kind of a personal question isn't it? :-)
Seriously, I think so.  At least that's what the .Net developer keeps
talking about.  I have displayed the graphical representation of the
WSDS file and it looks like it contains SOAP messages.


>Is the .NET program consuming a WSDL file?
Again, I think so.  We may have made a mistake here though.  I sent the
WSDL file to the .Net developer.  Should he be accessing if from the
server on my PC instead? 

The .Net application can actually execute the service I think.  It seems
to be complaining about the return data type.

Rick

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]On
Behalf Of Bartell, Aaron L. (TC)
Sent: Wednesday, October 20, 2004 8:32 AM
To: Web Enabling the AS400 / iSeries
Subject: RE: [WEB400] iSeries web service error from .Net application

What type of web service is it?  Are you using SOAP?  Is the .NET
program consuming a WSDL file?  One thing that got me when one of our
.NET programmers tried to consume a web service from my local box was
the URL specified in the WSDL.  It had 'localhost' specified and it
should have been my IP address.  Here is the line of code you need to
change in your WDSL file:

<wsdlsoap:address
location="http://192.99.99.155:9080/CustomerWeb/services/Doorway"/>

HTH,
Aaron Bartell
 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] 
Sent: Wednesday, October 20, 2004 8:23 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] iSeries web service error from .Net application

We are trying our first iSeries web service.  It's been slow going but
we've finally got it.  Almost.  When the .Net application tries to use
the service it gets an error.  The developer can access the service
using IE so we know the connection is good and the service will work.
The service hasn't been published to the iSeries yet.  It is currently
running on a WDSc WAS test server on my PC.  I can provide source code
if necessary.  The .Net error information is shown below.  Any help
would be greatly appreciated.

"System.Net.WebException: The underlying connection was closed: Unable
to connect to the remote server.\r\n   at
System.Net.HttpWebRequest.CheckFinalStatus()\r\n   at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)\r\n   at System.Net.HttpWebRequest.GetRequestStream()\r\n
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)\r\n   at
TestI5Service.WebReference.ARSWebSvcService.getFormattedField(String
fieldName) in C:\\Documents and Settings\\mhill2\\My Documents\\Visual
Studio Projects\\TestI5Service\\Web
References\\WebReference\\Reference.cs:line 38\r\n   at
TestI5Service.Form1.button1_Click(Object sender, EventArgs e) in
c:\\documents and settings\\mhill2\\my documents\\visual studio
projects\\testi5service\\form1.cs:line 93"

Rick
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To
post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.


_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.