date:20030801




These jars were developed by Apache and are 
licensed under the Apache License.
 

  - Original Message - 
  From: 
  [EMAIL PROTECTED] 
  
  To: [EMAIL PROTECTED] 
  Cc: [EMAIL PROTECTED] 
  Sent: Friday, August 01, 2003 3:24 
  AM
  Subject: License question
  I have a need to identify the 
  license for each component included in axis. Most of the jars are easy, 
  however I'm in doubt about a few of the jar files included in the distribution 
  namely jax-rpc.jar and saaj.jar. Since they don't contain the implementation I 
  don't think they fall under the EA license of the Sun WSDP. But if they don't 
  then which license do they fall under, I can't find any reference on the Sun 
  site about the specification license ? -Erik Vanherck  -  System Programmer & 
  DesignerInventive Designers Visit 
  http://www.inventivedesigners.comVisist 
  http://www.inventivedesigners.com/scriptura for Scriptura information 
  !Phone: +32 - 3 - 8210170Fax: +32 - 3 - 8210171Email: 
  [EMAIL PROTECTED]"Computers in the future may weigh 
  no more than 1.5 tons." - Popular Mechanics, forecasting the relentless march 
  of science, 1949

License question

2003-08-01 Thread Erik_Vanherck


I have a need to identify the license
for each component included in axis. Most of the jars are easy, however
I'm in doubt about a few of the jar files included in the distribution
namely jax-rpc.jar and saaj.jar. Since they don't contain the implementation
I don't think they fall under the EA license of the Sun WSDP. But if they
don't then which license do they fall under, I can't find any reference
on the Sun site about the specification license ?

-

Erik Vanherck  -  System Programmer & Designer
Inventive Designers 
Visit http://www.inventivedesigners.com
Visist http://www.inventivedesigners.com/scriptura for Scriptura information
!

Phone: +32 - 3 - 8210170
Fax: +32 - 3 - 8210171
Email: [EMAIL PROTECTED]

"Computers in the future may weigh no more than 1.5 tons." -
Popular Mechanics, forecasting the relentless march of science, 1949

RE: running wsdl2java with https

2003-08-01 Thread Mike Perham

Title: RE: running wsdl2java with https






Sounds like it's complaining about the server's digital certificate being expired.  Check the web server's certificate - you might need to renew it.  Your browser might be configured to accept the certificate anyways which is why it doesn't display a problem.  At any rate, this is not an axis problem.

 -Original Message-

From:   Leslie Zhang [mailto:[EMAIL PROTECTED]] 

Sent:   Thursday, July 31, 2003 11:14 PM

To: [EMAIL PROTECTED]; [EMAIL PROTECTED]

Subject:    running wsdl2java with https



Hi Guys, 

I have a problem of running the wsdl2java program with https. Does any one have an idea of how to run wsdl2java with https. 

Although my machine was able to connect to https://punto-bt.act.cmis.csiro.au/hdi/LinkageStandardisationService.wsdl  when I invoked: 

java org.apache.axis.wsdl.WSDL2Java https://punto-bt.act.cmis.csiro.au/hdi/LinkageStandardisationService.wsdl

WSDL2java threw the following exception: 

javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Dec 27 08:56:04 EST 2001 

I have no idea which certificate it was referred to and why that exception was thrown. 

Help please !

Les

RE: Office 2003 Research Pane services in Axis...

2003-08-01 Thread Roman Rytov

> Ok, I've played a little more but I'm still at a loss.  I 
> wrote a asp.net web service that works.  My axis one still 
> doesn't.  I've sniffed the traffic and here's what comes back:
> ...

It sounds much worse I thought. What you said means I have nothing to
play now with. You did all the job and it still doesn't work.  

> 
> You'll notice that the payload is the same.  Well, it is 
> unless I'm missing something because I've been staring at it 
> for too long.  The only differences are:
> 1. The Microsoft  has a default namespace of 
> urn:Microsoft.Search.  Axis
>   names the namespace ns1 and prefixes it.
> 2. Axis has an encoding style attribute that MS doesn't.

Semantically both responces are the same but except for you mentioned
about prefix difference there is also discrepancy in between return
parameter tag name. Axis calls it QueryReturn and MS QueryResult. Since
they both are described in corresponding WSDL correctly it mustn't
influence on the situation but who knows?


I have no idea what to test and if you read my previous post you'll get
more confused. What MSOffice _really_ checks I don't know. Mysticism! 

Should we try asking on a MS forum? 




> Now, then, all of that being said, can anyone tell me why the 
> two bits of xml aren't functionally equivelent?
> 
> Thanks!
> 
> 
> 
>

Re: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message

Wendy,

As I said, your  definitions must 
reference an  definition rather than a  
definition. When you are using Document style, you must define the actual 
structure of the soap:body -- and you do that by defining a schema 
. When using RPC style, the SOAP runtime system dynamically 
constructs the soap:body based on the method name and the types of the 
parameters. 

So let me give you an example:
Let's assume that you want to invoke operation 
foobar with two parameters -- foo and bar.

When using Document style, your  
definition looks something like this:

where element="foobar" refers to an  
definition in the  section. There are multiple ways to define an 
element, but here's an example:

To ensure that Axis produces a WRAPPED service, you 
have to give the operation the same name as the input message:

When using RPC style, your  
definition looks something like this:

You define a different  for each 
parameter, and you assign each parameter a type. Since you're using simple types, you don't need to define anything in the 
 section.

Now, what's really interesting is that both of 
these definitions will produce a SOAP message that looks like this:

foo

bar

So getting back to your WSDL file -- you must 
define your  elements like this:

Anne

  - Original Message - 
  From: 
  Wendy Smoak 

  To: '[EMAIL PROTECTED]' 
  Sent: Thursday, July 31, 2003 7:19 
  PM
  Subject: RE: Need WSDL for this SOAP 
  message

  Anne wrote: > When using 
  doc/literal, your message  definitions must reference an element 
  > definition rather than a type definition. 
  > So in your  section you also need to 
  define an  definition for each message part. 
  I can't get this to work.  Or rather, I _can_ get it to 
  work when referring to a complexType, but not when referring to an 
  element.
  Here's a working (WSDL2Java will run without error and 
  generate code, I'm not yet sure it's correct but at least it does something) 
  WSDL document:  http://www.public.asu.edu/~wsmoak/xml/webauth2.wsdl
  You can see the    
  and    In the  section. 
  But if I try to use SubscriptionAttributes instead of 
  subscription further down in this part:    

  Then WSDL2Java says: G:\IRM\SharedSource\services>java org.apache.axis.wsdl.WSDL2Java -v 
  src/wsdl/webauth2.wsdl -osrc Parsing XML file:  
  src/wsdl/webauth2.wsdl java.io.IOException: Type 
  {urn:servicehandler-ns-type}SubscriptionAttributes is referenced but not 
  defined. 
  Here's the broken-but-seemingly-correct one:   http://www.public.asu.edu/~wsmoak/xml/webauth.wsdl 

  In the original message, the namespace for the type attribute 
  looked like it was external.  It had:   

  where xsd1 was:   
  xmlns:xsd1="http://www.tlr.bis.com/rating.xsd1" 
  And yet PriceInfoType was defined in the same 
  . 
  I'm confused again (still!), can anyone make sense of this for 
  me? 
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: Intro to Web Services and Apache Axis Presentation

2003-08-01 Thread Irazabal, Alex

Awesome dude! I wish I saw this a few months ago... it would have save lots
of time :)
Alex
ps: You may want to use ant and accompanying task to do the compilation,
code generation and the like.. it's much easier.












]>























&properties;

&paths;

&taskdefs;

&taskdefs_post_compile;

&targets;





































http://localhost:8080/axis/services/${short.componentName}";

typeMappingVersion="1.1"

location="http://localhost:8080/axis/services/${short.componentName}";>

http://localhost:8080/axis/services/${short.componentName}";
package="${package.name}"/>











http://localhost:8080/axis/services/${short.componentName}";
package="${package.name}"/>





















 

























 









































 

-Original Message-
From: Sivakumar Jagadeesan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 4:48 AM
To: [EMAIL PROTECTED]
Subject: Intro to Web Services and Apache Axis Presentation


Hey Guys!
I have put a presentation in "Intro to Web Services and Apache Axis" that I
presented to Austin JUG.
http://java2simple.blog-city.com/read/162200.htm
 
Take a look at it and let me know what you guys think.
Let me also know if I need to add some more information

Rgds
--Siva Jagadeesan



  _  

Do you Yahoo!?
Yahoo!  
SiteBuilder - Free, easy-to-use web site design software

RE: Deserializing XML with AXIS

2003-08-01 Thread Irazabal, Alex

Can you share the classes you've done? I am trying to do the same and any
help is welcomed!
Alex

-Original Message-
From: Airline Pedestal [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 5:31 PM
To: [EMAIL PROTECTED]
Subject: Deserializing XML with AXIS

Hi Everyone,

   I've written several deserializer classes which
extends the DeserializerImpl class.  All these
classes together get called based on the typemappings
that I have defined.  In that regard, all is well
and the XML gets marshalled correctly.

Although, I'd like to reuse this deserialization
code in other ways (independent of axis).
What I have is so intermixed with axis code, it
is difficult to reuse.  Is there some way I
could reuse this deserialization code?  Could I
just get handed an XML document to deserialize
outside the context of axis?

Thanks,

Airline

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

RE: wrapped services && soapenc:Array

Anyone aware of an outstanding bug report on this?

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 5:36 PM
To: [EMAIL PROTECTED]
Subject: Re: wrapped services && soapenc:Array


Sounds like a bug. For doc/lit, Axis should generate an element with
unbounded content.

Anne

- Original Message -
From: "Cory Wilkerson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 6:06 PM
Subject: RE: wrapped services && soapenc:Array


> Well, this is what Axis is generating by default -- and I've told it it's
a wrapped service --- it's interpreting everything else as doc/lit...just
not this.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 31, 2003 5:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: wrapped services && soapenc:Array
>
>
>
> Java2WSDL has options to produce doc/lit wsdl files, but I believe the
> default is rpc.
>
>
>
>
>   "Cory Wilkerson"
>   <[EMAIL PROTECTED]To:
<[EMAIL PROTECTED]>
>   lnow.com>cc:
>Subject:  wrapped services
&& soapenc:Array
>   07/31/2003 03:59
>   PM
>   Please respond to
>   axis-user
>
>
>
>
>
> Why does my wrapped service (doc/literal) define extensions of
> soapenc:Array?  Shouldn't Axis generate wsdl that just describes an
element
> with unbounded content of a given type?  .Net won't swallow this sort of
> declaration.
>
> So, given a class "FooService" with method "fooMethod(String[] args)"
>
> I'd expect to see wsdl that looks something like:
>
> 
>  
>  
>   minOccurs="0" maxOccurs="unbounded"/>
>  
>  
> 
>
> I've seen some stuff moving across the mailing list in regards to this as
> well as a few bug reports -- is the issue stagnant?
>
> Thanks,
> Cory
>
>
>
>
>
>
>

RE: client-config.wsdd

2003-08-01 Thread Yakulis, Ross (Ross)

Try
System.setProperty("axis.ClientConfigFile", "\\client-config.wsdd");

-Original Message-
From: Sunil Iyengar [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 4:22 AM
To: [EMAIL PROTECTED]; Sunil Iyengar
Subject: client-config.wsdd

Hi,
I have created somew handlers which work on the server side. I tried to
register the use of these handlers on the client side using
client-config.wsdd and running the client application from the same
directory. The client handlers are just not invoked. I tried a few
things and am stumped. Please do provide some insight into this. What do
i do if i decide to make changes to the client-config.wsdd file. Does
this file have to be deloyed juast as we deploy the server side .wsdd
file.

Cheers
Sunny

--
***
Sunil Iyengar,
Research Fellow, Networks Group,
Centre For Communication And Systems Research(CCSR),
School of Electronics, Computing & Mathematics,
University Of Surrey, Guildford GU2 7XH,
Surrey, England, United Kingdom.
Office: +44 (0)1483 876008
http://www.ee.surrey.ac.uk/Personal/S.Iyengar
***

RE: Office 2003 Research Pane services in Axis...

2003-08-01 Thread Carey Nation

Hi Roman,


> Ok, I've played a little more but I'm still at a loss.  I
> wrote a asp.net web service that works.  My axis one still
> doesn't.  I've sniffed the traffic and here's what comes back:
> ...

>It sounds much worse I thought. What you said means I have nothing to
>play now with. You did all the job and it still doesn't work.

...Well, I'm going to have a go with the sun thing.  If it works, I'll let
you know... :-(

Passing two parameters as attachments

Hi,

I've successfully used attachments to pass one input String parameter and 
get a String returned, for example:

 class MultipleSOAPAttachmentsService, method DataHandler 
reverseString(DataHandler)

But when I try to pass two input String parameters, for example:

 class MultipleSOAPAttachmentsService, method DataHandler 
concatenateStrings(DataHandler, DataHandler)

The RPCProvider(JavaProvider).invoke(MessageContext) throws an 
AxisFault with detailMessage "No such method 'concatenateStrings'", even 
though when I run AxisServlet it shows that 
MultipleSOAPAttachmentsService defines functions reverseString and 
concatenateStrings.

I think the parameter matching part of the invocation is not matching the 
two attachments I've sent in with the call with the two parameters defined 
for the service.  At first I thought I got the containment relationship wrong 
when I added the second attachment.  But the SOAP message seems to 
be constructed correctly.

Here's what TCPMON shows for the successful reverseString call and for 
the unsuccessful concatenateStrings call, followed by the deployment 
wsdd.

Anyone know what I'm doing wrong here?  Thanks!

 . . Phil

___

reverseString request


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:CC92E5192DD9117AA5B5CA9362A0D8F5"; xmlns=""/>
  
 


 --=_Part_0_1499478125.1059751870377
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id:   

How about this? 
--=_Part_0_1499478125.1059751870377-- 

reverseString response


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  http://schemas.xmlsoap.org/soap/encoding/";>
   cid:9D1D602142978B268B75A35D37982F16"; 
xmlns:ns1="MultipleSOAPAttachmentsService"/>
  
 
 
--1927951303.1059751871008.JavaMail.javamailuser.localhost 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id: <9D1D602142978B268B75A35D37982F16>  

?siht tuoba woH 
--1927951303.1059751871008.JavaMail.javamailuser.localhost-- 
___

concatenateStrings request


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:908314EFC7686E7DC9CA8975989F5405"; xmlns=""/>
   cid:B53BFC8397913CEC44BB00C929C73D34"; xmlns=""/>
  
 
 
--=_Part_0_653523790.1059753343405 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id: <908314EFC7686E7DC9CA8975989F5405>  

One 
--=_Part_0_653523790.1059753343405 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id:   

Two 
--=_Part_0_653523790.1059753343405-- 

concatenateStrings response


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'
   
  
 

___

wsdd

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; 
xmlns:ns1="MultipleSOAPAttachmentsService">
















http://schemas.xmlsoap.org/soap/encoding/"; />

Passing two parameters as attachments

Hi,

I've successfully used attachments to pass one input String parameter and 
get a String returned, for example:

 class MultipleSOAPAttachmentsService, method DataHandler 
reverseString(DataHandler)

But when I try to pass two input String parameters, for example:

 class MultipleSOAPAttachmentsService, method DataHandler 
concatenateStrings(DataHandler, DataHandler)

The RPCProvider(JavaProvider).invoke(MessageContext) throws an 
AxisFault with detailMessage "No such method 'concatenateStrings'", even 
though when I run AxisServlet it shows that 
MultipleSOAPAttachmentsService defines functions reverseString and 
concatenateStrings.

I think the parameter matching part of the invocation is not matching the 
two attachments I've sent in with the call with the two parameters defined 
for the service.  At first I thought I got the containment relationship wrong 
when I added the second attachment.  But the SOAP message seems to 
be constructed correctly.

Here's what TCPMON shows for the successful reverseString call and for 
the unsuccessful concatenateStrings call, followed by the deployment 
wsdd.

Anyone know what I'm doing wrong here?  Thanks!

 . . Phil

___

reverseString request


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:CC92E5192DD9117AA5B5CA9362A0D8F5"; xmlns=""/>
  
 


 --=_Part_0_1499478125.1059751870377
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id:   

How about this? 
--=_Part_0_1499478125.1059751870377-- 

reverseString response


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  http://schemas.xmlsoap.org/soap/encoding/";>
   cid:9D1D602142978B268B75A35D37982F16"; 
xmlns:ns1="MultipleSOAPAttachmentsService"/>
  
 
 
--1927951303.1059751871008.JavaMail.javamailuser.localhost 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id: <9D1D602142978B268B75A35D37982F16>  

?siht tuoba woH 
--1927951303.1059751871008.JavaMail.javamailuser.localhost-- 
___

concatenateStrings request


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:908314EFC7686E7DC9CA8975989F5405"; xmlns=""/>
   cid:B53BFC8397913CEC44BB00C929C73D34"; xmlns=""/>
  
 
 
--=_Part_0_653523790.1059753343405 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id: <908314EFC7686E7DC9CA8975989F5405>  

One 
--=_Part_0_653523790.1059753343405 
Content-Type: text/plain 
Content-Transfer-Encoding: binary 
Content-Id:   

Two 
--=_Part_0_653523790.1059753343405-- 

concatenateStrings response


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'
   
  
 

___

wsdd

http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; 
xmlns:ns1="MultipleSOAPAttachmentsService">
















http://schemas.xmlsoap.org/soap/encoding/"; />

RE: Passing two parameters as attachments


Something went wrong when I copied and pasted the TCPMON output for 
the concatenateStrings request and response.  Here's how it looks (hope 
this looks right this time!):

concatenateStrings request:

POST /SOAPAttachmentsMultipleParametersDemoProjectWeb/services/Multi
pleSOAPAttachmentsService HTTP/1.0

Content-Type: multipart/related; type="text/xml"; 
start="<7E082A9FA4847AD320EEE5EF16FD3703>"; boundary="---
-=_Part_0_637696601.1059752868488"

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.2dev

Host: 127.0.0.1

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: ""

Content-Length: 977





--=_Part_0_637696601.1059752868488

Content-Type: text/xml; charset=UTF-8

Content-Transfer-Encoding: binary

Content-Id: <7E082A9FA4847AD320EEE5EF16FD3703>




http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:BE1EB543BDEB3822AA993DFB69458264"; xmlns=""/>
   cid:902EC24FCE3A0B0398A6D949E8578100"; xmlns=""/>
  
 


--=_Part_0_637696601.1059752868488

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Id: 



One

--=_Part_0_637696601.1059752868488

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Id: <902EC24FCE3A0B0398A6D949E8578100>



Two

--=_Part_0_637696601.1059752868488--

concatenateStrings response:

HTTP/1.1 500 Internal Server Error

Server: WebSphere Application Server/4.0

Content-Type: text/xml; charset=utf-8

Content-Language: en

Connection: close




http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'

RE: Passing two parameters as attachments


Something went wrong when I copied and pasted the TCPMON output for 
the concatenateStrings request and response.  Here's how it looks (hope 
this looks right this time!):

concatenateStrings request:

POST /SOAPAttachmentsMultipleParametersDemoProjectWeb/services/Multi
pleSOAPAttachmentsService HTTP/1.0

Content-Type: multipart/related; type="text/xml"; 
start="<7E082A9FA4847AD320EEE5EF16FD3703>"; boundary="---
-=_Part_0_637696601.1059752868488"

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.2dev

Host: 127.0.0.1

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: ""

Content-Length: 977





--=_Part_0_637696601.1059752868488

Content-Type: text/xml; charset=UTF-8

Content-Transfer-Encoding: binary

Content-Id: <7E082A9FA4847AD320EEE5EF16FD3703>




http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   cid:BE1EB543BDEB3822AA993DFB69458264"; xmlns=""/>
   cid:902EC24FCE3A0B0398A6D949E8578100"; xmlns=""/>
  
 


--=_Part_0_637696601.1059752868488

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Id: 



One

--=_Part_0_637696601.1059752868488

Content-Type: text/plain

Content-Transfer-Encoding: binary

Content-Id: <902EC24FCE3A0B0398A6D949E8578100>



Two

--=_Part_0_637696601.1059752868488--

concatenateStrings response:

HTTP/1.1 500 Internal Server Error

Server: WebSphere Application Server/4.0

Content-Type: text/xml; charset=utf-8

Content-Language: en

Connection: close




http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'

AxisFault from server not detected by client

Hi,

When the server sends back an Axis Fault such as:


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'
   
  
 


org.apache.axis.soap.SOAPConnectionImpl.call(SOAPMessage, Object) 
does not detect the AxisFault in the response message and therefore 
throws no exception as a result.

Is it the responsibility of my client code (that invokes 
SOAPConnectionImpl.call(...)) to inspect the response message to detect a 
server error?  If so, what is the recommended technique for digging into 
the SOAPMessage in search for an error?

This happens in Axis 1.1 builds from July 9 and July 28.

Thanks,

 . . Phil

AxisFault from server not detected by client

Hi,

When the server sends back an Axis Fault such as:


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
 
  
   Server.userException
   No such operation 'concatenateStrings'
   
  
 


org.apache.axis.soap.SOAPConnectionImpl.call(SOAPMessage, Object) 
does not detect the AxisFault in the response message and therefore 
throws no exception as a result.

Is it the responsibility of my client code (that invokes 
SOAPConnectionImpl.call(...)) to inspect the response message to detect a 
server error?  If so, what is the recommended technique for digging into 
the SOAPMessage in search for an error?

This happens in Axis 1.1 builds from July 9 and July 28.

Thanks,

 . . Phil

Re: running wsdl2java with https

2003-08-01 Thread Sanjay Krishnamurthi

 Sometimes a browser is lot more tolerant of expired
certificates that an average java client. When you
view the WSDL in the browser, you can check the
certificate and its expiry date(click on the lock icon
at the bottom if using IE) Server cert may indeed have
expired. I don't know if wsdl2java has any option that
lets you ignore expired certs.

  It should be possible for you to proceed by saving
the WSDL file locally once you are able to get it via
the browser and then run WSDL2Java on it.

  Cheers,

   Sanjay

--- Leslie Zhang <[EMAIL PROTECTED]> wrote:
> 
> Hi Guys, 
> I have a problem of running the wsdl2java program
> with https. Does any one
> have an idea of how to run wsdl2java with https. 
> Although my machine was able to connect to
>
https://punto-bt.act.cmis.csiro.au/hdi/LinkageStandardisationService.wsdl
> when I invoked: 
> java org.apache.axis.wsdl.WSDL2Java
>
https://punto-bt.act.cmis.csiro.au/hdi/LinkageStandardisationService.wsdl
> WSDL2java threw the following exception: 
> javax.net.ssl.SSLHandshakeException:
> java.security.cert.CertificateExpiredException:
> NotAfter: Thu Dec 27
> 08:56:04 EST 2001 
> I have no idea which certificate it was referred to
> and why that exception
> was thrown. 
> Help please !
> Les
> 
> 
> ==
> Leslie ZHANG
> E - Service Integration
> Mathematical and Information Sciences
> CSIRO
> GPO Box 664, Canberra, ACT 2601, Australia
> Ph: (02) 6216 7072, Fax: (02) 6216 7111
> == 
> "The future doesn't belong to the fainthearted; it
> belongs to the brave."
> --- Ronald Reagan 
> 
> 

> ATTACHMENT part 2 application/ms-tnef
name=winmail.dat

__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

SALESForce.com with AXIS

2003-08-01 Thread priyada2


Has any body in this group worked with the SalesForce.com Axis API ? 

Regards
Ashok Priyadarshan
Applications Specialist
Gartmore Global Investments
1200 River Road
Conshohocken, PA 19428
(484) 530-1503
http://www.gartmore.us

RE: SALESForce.com with AXIS

2003-08-01 Thread Colin Ma

Yes. I worked with both 1.8 and 2.0 SFDC SOAP API. Both are working.
Salesforce.com has a developer site www.sforce.com 
where you can post questions and get sample codes.
 
Colin Ma
 
MedImpact.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 11:05 AM
To: [EMAIL PROTECTED]
Subject: SALESForce.com with AXIS



Has any body in this group worked with the SalesForce.com Axis API ? 

Regards
Ashok Priyadarshan
Applications Specialist
Gartmore Global Investments
1200 River Road
Conshohocken, PA 19428
(484) 530-1503
http://www.gartmore.us

How does Axis handle soapAction?

Title: How does Axis handle soapAction?






I picked this up from the example that Richard Hansen posted on 7/30:





However, the string "RatingPortType" does not appear anywhere else in the WSDL document.  And the examples in the http://www.w3.org/TR/wsdl.html document always have a URL in the soapAction element.

I recognize the string after the # sign as the method to be called, but what does "RatingPortType" mean in this case?


Should it possible match the portType name from this section?
 
    
    
    
    
    


Thanks for your help,


-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

RE: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message






Anne, thanks once again for your patience.  I am having a terrible time figuring out where the following belong:  RPC, Wrapped, Document, Literal, Message.

Here's the WSDD I'm using:
http://xml.apache.org/axis/wsdd/" 
    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
   
  
  
  /webauth.wsdl
   



I think the confusion is over the "document" part of document/literal.  On one hand, it's "document" as opposed to RPC, a style, as you discussed.  

On the other hand, it's the companion to 'wrapped' indicating that Axis will pass all the parameters on the command line rather than wrapping them as a Java object.

So am I imagining things, or are there two definitions of "document", one used by the wider world, and one used within Axis WSDD?

I'm trying to work from the Axis Users Guide.  Under "Individual Service Configuration" it says:
  Style - whether to use RPC:enc or doc/lit encoding 
But it doesn't say what to put in the style attribute for each one.


And right now I'm uncertain which one I need to use, even if I knew what to put.  Is there a page with a table that lists all the parameters to  and all the possible values?  I can find documentation on WSDL, but not on WSDD as that appears to be Axis specific.

-- 
Wendy Smoak 
Applications Systems Analyst, Sr. 
Arizona State University, PA, IRM

wsdlFile not working

Title: wsdlFile not working






I'm trying to use the  tag in my WSDD, but it's not working:


subscription.wsdd:


http://xml.apache.org/axis/wsdd/" 
    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
   
  
  
  /webauth.wsdl
   



Deployed (on Win2000 with Axis running as the 'svcdev' context under Tomcat 4.1.24):
> java org.apache.axis.client.AdminClient -lhttp://localhost/svcdev/servlet/AxisServlet src\wsdd\subscription.wsdd


I can then see the service listed at http://localhost/svcdev/servlet/AxisServlet as "MySubscriptionService (wsdl)" but if I click on the 'wsdl' link, I get "HTTP 500 - Internal server error".

'webauth.wsdl' file is placed directly under WEB-INF as suggested in this article:
http://www.ftponline.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp


Thanks for any ideas,


-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

RE: Need WSDL for this SOAP message

2003-08-01 Thread Mike Perham

Title: Message



In all 
likelihood, you want:
 
provider="java:RPC" style="wrapped" use="literal"
 
MSG is 
used if you want to deal with the XML elements directly rather than as java 
beans.  RPC does not mean the style has to be "rpc".  Yeah, it's an 
unfortunate name.

  
  -Original Message-From: Wendy Smoak 
  [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2003 1:17 
  PMTo: '[EMAIL PROTECTED]'Subject: RE: Need WSDL 
  for this SOAP message
  Anne, thanks once again for your patience.  I am having a 
  terrible time figuring out where the following belong:  RPC, Wrapped, 
  Document, Literal, Message.
  Here's the WSDD I'm using: http://xml.apache.org/axis/wsdd/"     
  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> 
              
  /webauth.wsdl      
  I think the confusion is over the "document" part of 
  document/literal.  On one hand, it's "document" as opposed to RPC, a 
  style, as you discussed.  
  On the other hand, it's the companion to 'wrapped' indicating 
  that Axis will pass all the parameters on the command line rather than 
  wrapping them as a Java object.
  So am I imagining things, or are there two definitions of 
  "document", one used by the wider world, and one used within Axis 
  WSDD?
  I'm trying to work from the Axis Users Guide.  Under 
  "Individual Service Configuration" it says:   
  Style - whether to use RPC:enc or doc/lit encoding But 
  it doesn't say what to put in the style attribute for each one. 
  And right now I'm uncertain which one I need to use, even if I 
  knew what to put.  Is there a page with a table that lists all the 
  parameters to  and all the possible values?  I can find 
  documentation on WSDL, but not on WSDD as that appears to be Axis 
  specific.
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: wsdlFile not working

2003-08-01 Thread Carter, John G

Title: wsdlFile not working



Wendy,
 
The article 
you referenced about the location of user-written WSDL states that it is 
typically placed in the WEB-INF/classes directory, not the WEB-INF 
directory.

  -Original Message-From: Wendy Smoak 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 1:39 
  PMTo: '[EMAIL PROTECTED]'Subject: wsdlFile not 
  working
  I'm trying to use the  tag in my WSDD, but 
  it's not working: 
  subscription.wsdd: 
  http://xml.apache.org/axis/wsdd/"     
  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> 
              
  /webauth.wsdl      
  Deployed (on Win2000 with Axis running as the 'svcdev' context 
  under Tomcat 4.1.24): > java 
  org.apache.axis.client.AdminClient 
  -lhttp://localhost/svcdev/servlet/AxisServlet 
  src\wsdd\subscription.wsdd 
  I can then see the service listed at http://localhost/svcdev/servlet/AxisServlet as 
  "MySubscriptionService (wsdl)" but if I click on the 'wsdl' link, I get "HTTP 
  500 - Internal server error".
  'webauth.wsdl' file is placed directly under WEB-INF as 
  suggested in this article: http://www.ftponline.com/javapro/2003_02/online/WSDL_kjones_02_27_03/default_pf.asp 
  
  Thanks for any ideas, 
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: How does Axis handle soapAction?

Title: How does Axis handle soapAction?



Wendy,
 
The attribute "header" of element "operation" in the soap 
namespace http://schemas.xmlsoap.org/wsdl/soap:
 
A) Appears as an HTTP header
B) I believe it's sole purpose is to assist the consuming framework 
in routing the incoming request to the appropriate 
"service".
 
Cory

  -Original Message-From: Wendy Smoak 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 1:23 
  PMTo: '[EMAIL PROTECTED]'Subject: How does Axis 
  handle soapAction?
  I picked this up from the example that Richard Hansen posted 
  on 7/30: 
   
  However, the string "RatingPortType" does not appear anywhere 
  else in the WSDL document.  And the examples in the http://www.w3.org/TR/wsdl.html document always have a URL in 
  the soapAction element.
  I recognize the string after the # sign as the method to be 
  called, but what does "RatingPortType" mean in this case? 
  Should it possible match the portType name from this 
  section?            
       
        
       
  Thanks for your help, 
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message



If you're attempting to deploy a "document/literal" style service via 
style="document" use="literal" in your wsdd, you'll see that the 
soap:operation's style attribute will read "document" and the soap:body elements 
of your operation will have attribute "use" with value = "literal".  

 
This is basically telling the world to send me a straight up document 
that conforms to the types that are defined in the wsdl's "types" section.  

 
If you're attempting to deploy a "document/literal" style service via 
style="wrapped" and use="literal" in your wsdd, you'll again see that the 
soap:operation's style attribute will read "document" and the soap:body elements 
of your operation will have attribute "use" with value = "literal" -- just like 
the above.  The thing with wrapped services is the way in which the types 
(in the  section of your WSDL) are constructed as well as 
the message elements and their respective names.  From discussions on 
this board over the past few days, I think it's safe to say that "wrapped" 
services are basically a way to afford you the convenience of Axis 
marshaling/unmarshaling your data into actual object represenation (ie, giving 
you RPC like functionality) via some assumptions it makes and publishes in 
your service description. 
 
I may have strayed from the path here in answering your question.  
Using "document" in the wsdd is just telling Axis that when it generates the 
WSDL for this thing, it should tell the world (via soap:operation 
style="document") that the the message's that are sent to you should NOT be 
fashioned as RPC style messages but instead, sent exactly as defined in your 
*types* section.  If you dig into the SOAP specification you'll see how RPC 
style messages are fashioned according to certain rules set for th in that 
spec.  If you're deploying with with "wrapped" in your wsddAxis will 
generate different WSDL for you that will create your types (and messages I 
believe) in such a way so as to still afford you rpc-like 
functionality.
 
Hope this helps and didn't just serve to confuse 
you...
 
Cory
 

  -Original Message-From: Wendy Smoak 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 1:17 
  PMTo: '[EMAIL PROTECTED]'Subject: RE: Need WSDL 
  for this SOAP message
  Anne, thanks once again for your patience.  I am having a 
  terrible time figuring out where the following belong:  RPC, Wrapped, 
  Document, Literal, Message.
  Here's the WSDD I'm using: http://xml.apache.org/axis/wsdd/"     
  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> 
              
  /webauth.wsdl      
  I think the confusion is over the "document" part of 
  document/literal.  On one hand, it's "document" as opposed to RPC, a 
  style, as you discussed.  
  On the other hand, it's the companion to 'wrapped' indicating 
  that Axis will pass all the parameters on the command line rather than 
  wrapping them as a Java object.
  So am I imagining things, or are there two definitions of 
  "document", one used by the wider world, and one used within Axis 
  WSDD?
  I'm trying to work from the Axis Users Guide.  Under 
  "Individual Service Configuration" it says:   
  Style - whether to use RPC:enc or doc/lit encoding But 
  it doesn't say what to put in the style attribute for each one. 
  And right now I'm uncertain which one I need to use, even if I 
  knew what to put.  Is there a page with a table that lists all the 
  parameters to  and all the possible values?  I can find 
  documentation on WSDL, but not on WSDD as that appears to be Axis 
  specific.
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message

Mike wrote:
> In all likelihood, you want:
> provider="java:RPC" style="wrapped" use="literal"

Yes, I've changed back to that.  I posted one of the "try all possible combinations and see what works" versions. ;)

> MSG is used if you want to deal with the XML elements directly rather than as java beans.  

This is most likely what I'll eventually want.  I'd rather update the schema and the guts of the method that gets called, and not have to generate yet another bean-- I've already got Struts Form beans and DTO's floating around.  I don't need another class full of almost identical get and set methods.

So WSDL2Java won't be necessary, AFAICT.  Right now I'm discarding everything it generates except for the JavaBeans that match the input/output message, and soon I won't need those either.  I still don't understand what all the RMI junk it generates is for.  Nothing I've ready even _mentions_ RMI wrt web services.

So, a week later, I have finally come up with a new and exciting error message!

g:\irm\sharedsource\services>java edu.asu.vpia.webauth.SubscriptionClient -lhttp
://localhost/svcdev/services/MySubscriptionService
Using endpointURL:  http://localhost/svcdev/services/MySubscriptionService
org.xml.sax.SAXException: Bad types (class java.lang.String -> class edu.asu.vpi
a.webauth.Subscription)

I think this means that the method is being called, but somehow Axis didn't get the hint to do "wrapped" and pass a JavaBean rather than individual parameters.

Thanks to everyone who has been so patient with me this week.  I think I'm almost there...

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

complexType not found by WSDL2Java in imported schema

2003-08-01 Thread steve . s . maring

I may be doing something wrong here.

I have an existing set of schemas from which I use Castor to generate
JavaBeans.  I then specify a typeMapping in the WSDD to use Castor
serializers.

I need these schemas available to the WSDL for message definition, however,
I do not want WSDL2Java to try and regenerate these JavaBeans based on the
default typeMapping.  Therefore, it would seem that I should import these
schemas into my WSDL and give a "-n" option to WSDL2Java so that it does
not generate files for the imported types.

Here is what I have:


http://ws.domino.mw.us.pwc.com";
  xmlns:apachesoap="http://xml.apache.org/xml-soap";
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
  xmlns:tns1="http://dto.ws.domino.mw.us.pwc.com";
  xmlns:dto="http://dto.common.mw.us.pwc.com";
  xmlns:intf="http://ws.domino.mw.us.pwc.com";
  xmlns:impl="http://ws.domino.mw.us.pwc.com";
  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
  xmlns="http://schemas.xmlsoap.org/wsdl/";>

  http://dto.common.mw.us.pwc.com"; location=
"allDataTypes.xsd"/>

  

http://www.w3.org/2001/XMLSchema";
  xmlns:dto="http://dto.common.mw.us.pwc.com";
  xmlns:tns1="http://dto.ws.domino.mw.us.pwc.com";
  targetNamespace="http://dto.ws.domino.mw.us.pwc.com";>


  

  

  
  ...


...



allDataTypes.xsd:

http://www.w3.org/2001/XMLSchema";
  xmlns:dto="http://dto.common.mw.us.pwc.com";
  targetNamespace="http://dto.common.mw.us.pwc.com";>

  
  ...



personDetail.xsd:

http://www.w3.org/2001/XMLSchema";
  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
  xmlns:dto="http://dto.common.mw.us.pwc.com";
  targetNamespace="http://dto.common.mw.us.pwc.com";>



  
...
  






WSDL2Java says:

wsdl2java:
 [java] Parsing XML file:  schema/firmDirectoryService.wsdl
 [java] java.io.IOException: Type
{http://dto.common.mw.us.pwc.com}PersonDetail is referenced but not
defined.
 [java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:522)
 [java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:422)
 [java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:408)
 [java] at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:393)
 [java] at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
 [java] at java.lang.Thread.run(Thread.java:536)
 [java] Java Result: 1


Any thoughts would be greatly appriciated.

Cheers.
Steve Maring



_
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.

Setting default namespace for service... Was Office2003 Research Pain. That's not a typo...

2003-08-01 Thread Carey Nation

How can I set the default namespace for a service?  It has to render as the
default xmlns, thus:  xmlns="thing", not xmlns:ns1="thing" with ns1
propagated.  The office docs say that it will ignore messages without the
default namespace.  I can get Axis to put the namespace in the second form,
but not the first.

Thanks!
Carey

How to map mime-extentions to mime-types in an Axis service (fwd)

2003-08-01 Thread William Barber

Greetings again,

I'm wondering if I sent this query to the wrong list, or if no one knows the
answer to the question?  People generally answer questions so quickly here.
Perhaps there is a more appropriate list for this question? Any help would be
appreciated!

Thanks! Bill

Bill Barber
Scientific Software Group (CCN-12)
Los Alamos National Laboratory
505-667-8616

-- Forwarded message --
Date: Wed, 30 Jul 2003 12:16:16 -0600 (MDT)
From: William Barber <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: How to map mime-extentions to mime-types in an Axis service

Greetings,

I've written an Axis client/service pair that uses "soapConnection.call()" to
send SOAP attachments to the service, along with parameters specifying input and
output mime-extensions. The client will not know the actual mime-type of the
response attachment that the server will return after converting the request
file.

The service end is not a servlet, but just a SOAP service.
The service needs to map the request mime-extensions to mime-types according to
 elements in the Axis web.xml file.

The only call I can find in any docs that does this mapping is the
Context.findMimeMapping(String extension) call.

But its not clear to me how the service end can get a reference to the
appropriate Context so it can make this mapping call. Can someone point me to
the correct methods? Or if I'm just on the wrong path here, point me in a better
direction?

Many thanks! Bill

Bill Barber
Scientific Software Group (CCN-12)
Los Alamos National Laboratory
505-667-8616

RE: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message






Cory wrote:
> Using "document" in the wsdd is just telling Axis that when it generates the WSDL for this thing, 
> it should tell the world (via soap:operation style="document") that the the message's that are sent 
> to you should NOT be fashioned as RPC style messages


I'm not letting Axis generate the WSDL, and I do have 
   


(The latest version is here: http://www.public.asu.edu/~wsmoak/xml/webauth.wsdl)


So yes, I hope I'm announcing to the world that I want a plain old XML file in the body of the message, one that matches one of the schemas in the  section.

I'm down to a new and improved error message:


g:\irm\sharedsource\services>java edu.asu.vpia.webauth.SubscriptionClient -lhttp
://localhost:81/svcdev/services/MySubscriptionService
Using endpointURL:  http://localhost:81/svcdev/services/MySubscriptionService
org.xml.sax.SAXException: Bad types (class java.lang.String -> class edu.asu.vpi
a.webauth.Subscription)


And by using tcpmon, I think I've determined that my Client class is the problem.  It's based on the Client from example3, and it's sending this:


http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 
  http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="MySubscriptionService">
   nobody
   passwd
  
 



Pretty close, actually.   should be , but that's controlled by the line:
  call.setOperationName( new QName("MySubscriptionService", "subscribe") );
If I change it, I get:
  No such operation 'subscription'


It's not sending the SOAPAction either.  What does the Java client code look like for a document/literal message, one that has XML matching something in the  section of the wsdl?  Can you do it with the Call class, or is that only for RPC calls?  Client code is here:  http://www.public.asu.edu/~wsmoak/xml/SubscriptionClient.java

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

Re: How does Axis handle soapAction?

Title: How does Axis handle soapAction?

The attribute is "SOAPAction", not
"header".
The value specified in the attribute must be
specified in the SOAPAction: HTTP header on the SOAP request message. It gives
the SOAP server a hint on how to process the message.

- Original Message -
From:
Cory
Wilkerson
To: [EMAIL PROTECTED]
Sent: Friday, August 01, 2003 3:07
PM
Subject: RE: How does Axis handle
soapAction?

Wendy,
The attribute "header" of
element "operation" in the soap namespace http://schemas.xmlsoap.org/wsdl/soap:
A) Appears as an HTTP header
B) I believe it's sole purpose is to assist the consuming
framework in routing the incoming request to the appropriate
"service".
Cory

-Original Message-From: Wendy Smoak
[mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 1:23
PMTo: '[EMAIL PROTECTED]'Subject: How does Axis
handle soapAction?
I picked this up from the example that Richard Hansen posted
on 7/30:

However, the string "RatingPortType" does not appear
anywhere else in the WSDL document. And the examples in the http://www.w3.org/TR/wsdl.html
document always have a URL in the soapAction element.
I recognize the string after the # sign as the method to be
called, but what does "RatingPortType" mean in this case?
Should it possible match the portType name from this
section?
Thanks for your help,
-- Wendy Smoak Applications Systems Analyst, Sr. Arizona
State University, PA, IRM

RE: How does Axis handle soapAction?

Title: How does Axis handle soapAction?



Sorry about that Wendy -- got carried away in my 
response.

  -Original Message-From: Anne Thomas Manes 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 2:18 
  PMTo: [EMAIL PROTECTED]Subject: Re: How does Axis 
  handle soapAction?
  The attribute is "SOAPAction", not 
  "header".
  The value specified in the attribute must be 
  specified in the SOAPAction: HTTP header on the SOAP request message. It gives 
  the SOAP server a hint on how to process the message. 
   
  
- Original Message - 
From: 
Cory Wilkerson 
To: [EMAIL PROTECTED] 
Sent: Friday, August 01, 2003 3:07 
PM
Subject: RE: How does Axis handle 
soapAction?

Wendy,
 
The attribute "header" 
of element "operation" in the soap namespace http://schemas.xmlsoap.org/wsdl/soap:
 
A) Appears as an HTTP header
B) I believe it's sole purpose is to assist the consuming 
framework in routing the incoming request to the appropriate 
"service".
 
Cory

  -Original Message-From: Wendy Smoak 
  [mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 1:23 
  PMTo: '[EMAIL PROTECTED]'Subject: How does 
  Axis handle soapAction?
  I picked this up from the example that Richard Hansen 
  posted on 7/30: 
   
  However, the string "RatingPortType" does not appear 
  anywhere else in the WSDL document.  And the examples in the http://www.w3.org/TR/wsdl.html document always have a 
  URL in the soapAction element.
  I recognize the string after the # sign as the method to 
  be called, but what does "RatingPortType" mean in this case? 
  Should it possible match the portType name from this 
  section?            
       
       
       
   
  Thanks for your help, 
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona 
  State University, PA, IRM

Re: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message



Wendy, 
 
Based on your current WSDL file (which looks 
correct), I would expect the client to send a SOAP message that looks like 
this:
 

   
  
nobody
  
passwd
   

 
Anne

  - Original Message - 
  From: 
  Wendy Smoak 
  
  To: '[EMAIL PROTECTED]' 
  Sent: Friday, August 01, 2003 5:37 
  PM
  Subject: RE: Need WSDL for this SOAP 
  message
  
  Cory wrote: > Using "document" in 
  the wsdd is just telling Axis that when it generates the WSDL for this thing, 
  > it should tell the world (via soap:operation 
  style="document") that the the message's that are sent > to you should NOT be fashioned as RPC style messages 
  I'm not letting Axis generate the WSDL, and I do have 
      
  
  (The latest version is here: http://www.public.asu.edu/~wsmoak/xml/webauth.wsdl) 
  
  So yes, I hope I'm announcing to the world that I want a plain 
  old XML file in the body of the message, one that matches one of the schemas 
  in the  section.
  I'm down to a new and improved error message: 
  g:\irm\sharedsource\services>java 
  edu.asu.vpia.webauth.SubscriptionClient -lhttp ://localhost:81/svcdev/services/MySubscriptionService Using endpointURL:  http://localhost:81/svcdev/services/MySubscriptionService 
  org.xml.sax.SAXException: Bad types (class java.lang.String 
  -> class edu.asu.vpi a.webauth.Subscription) 
  
  And by using tcpmon, I think I've determined that my Client 
  class is the problem.  It's based on the Client from example3, and it's 
  sending this:
   http://schemas.xmlsoap.org/soap/envelope/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      
  http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:ns1="MySubscriptionService">    
  nobody    passwd       
  Pretty close, actually.   should be 
  , but that's controlled by the line:   call.setOperationName( new QName("MySubscriptionService", 
  "subscribe") ); If I change it, I get: 
    No such operation 'subscription' 
  It's not sending the SOAPAction either.  What does the 
  Java client code look like for a document/literal message, one that has XML 
  matching something in the  section of the wsdl?  Can you do 
  it with the Call class, or is that only for RPC calls?  Client code is 
  here:  http://www.public.asu.edu/~wsmoak/xml/SubscriptionClient.java
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

RE: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message

Anne wrote:
> Based on your current WSDL file (which looks correct), I would expect the 
> client to send a SOAP message that looks like this:
> 
>    
>   nobody
>   passwd
>    
> 

Hmmm... I was expecting the element just inside  to be  not .  Axis generated Subscription and SubscriptionResponse classes from that WSDL, the complexTypes.  (Not SubscriptionAttributes and SubscriptionResponse, the element names.)

In any case Axis complains unless it's  which matches the method name.  Anything else, and I get:
   No such operation 'tagname'

I'm closer than I've ever been, but not quite there yet!  I think it's the client code that's broken now.  I don't know how to get it to make a  or  tag around the userId and password tags.

I was hoping that by sending the SOAPAction, which now appears in the header and matches the SOAPAction in the WSDL file, that would tell Axis which service I was trying to call.  Instead, Axis is picking the first tag inside  as the name of the method.

But I'm running on guesses and assumptions at this point.  I'm sticking with the WSDL as-is since it's been blessed by Anne, and will try to adjust the wsdd and the client code to match.

The wsdl, wsdd, and client code are here:
http://www.public.asu.edu/~wsmoak/xml/

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

Re: Need WSDL for this SOAP message

Title: RE: Need WSDL for this SOAP message



Wendy,
 
I'm not sure I understand why you're using the call 
interface. The main reason that you want to use WRAPPED is so that you can 
invoke your service using something like this:
 
   string 
ResponseInfo = service.SubscriptionRequest( usedId, password 
);
 
You 
should compile your WSDL file with wsdl2java and generate your client 
interface.
 
Anne

  - Original Message - 
  From: 
  Wendy Smoak 
  
  To: '[EMAIL PROTECTED]' 
  Sent: Friday, August 01, 2003 5:37 
  PM
  Subject: RE: Need WSDL for this SOAP 
  message
  
  Cory wrote: > Using "document" in 
  the wsdd is just telling Axis that when it generates the WSDL for this thing, 
  > it should tell the world (via soap:operation 
  style="document") that the the message's that are sent > to you should NOT be fashioned as RPC style messages 
  I'm not letting Axis generate the WSDL, and I do have 
      
  
  (The latest version is here: http://www.public.asu.edu/~wsmoak/xml/webauth.wsdl) 
  
  So yes, I hope I'm announcing to the world that I want a plain 
  old XML file in the body of the message, one that matches one of the schemas 
  in the  section.
  I'm down to a new and improved error message: 
  g:\irm\sharedsource\services>java 
  edu.asu.vpia.webauth.SubscriptionClient -lhttp ://localhost:81/svcdev/services/MySubscriptionService Using endpointURL:  http://localhost:81/svcdev/services/MySubscriptionService 
  org.xml.sax.SAXException: Bad types (class java.lang.String 
  -> class edu.asu.vpi a.webauth.Subscription) 
  
  And by using tcpmon, I think I've determined that my Client 
  class is the problem.  It's based on the Client from example3, and it's 
  sending this:
   http://schemas.xmlsoap.org/soap/envelope/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      
  http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:ns1="MySubscriptionService">    
  nobody    passwd       
  Pretty close, actually.   should be 
  , but that's controlled by the line:   call.setOperationName( new QName("MySubscriptionService", 
  "subscribe") ); If I change it, I get: 
    No such operation 'subscription' 
  It's not sending the SOAPAction either.  What does the 
  Java client code look like for a document/literal message, one that has XML 
  matching something in the  section of the wsdl?  Can you do 
  it with the Call class, or is that only for RPC calls?  Client code is 
  here:  http://www.public.asu.edu/~wsmoak/xml/SubscriptionClient.java
  -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State 
  University, PA, IRM

Re: Need WSDL for this SOAP message

RE: Need WSDL for this SOAP messageAhah! I think I found your problem.

Your WSDD says:

But your WSDL says"


I believe that these two values must be the same.

Anne

- Original Message -
From: Wendy Smoak
To: '[EMAIL PROTECTED]'
Sent: Friday, August 01, 2003 6:33 PM
Subject: RE: Need WSDL for this SOAP message


Anne wrote:
> Based on your current WSDL file (which looks correct), I would expect the
> client to send a SOAP message that looks like this:
> 
>
>   nobody
>   passwd
>
> 
Hmmm... I was expecting the element just inside  to be 
not .  Axis generated Subscription and
SubscriptionResponse classes from that WSDL, the complexTypes.  (Not
SubscriptionAttributes and SubscriptionResponse, the element names.)
In any case Axis complains unless it's  which matches the method
name.  Anything else, and I get:
   No such operation 'tagname'
I'm closer than I've ever been, but not quite there yet!  I think it's the
client code that's broken now.  I don't know how to get it to make a
 or  tag around the userId and
password tags.
I was hoping that by sending the SOAPAction, which now appears in the header
and matches the SOAPAction in the WSDL file, that would tell Axis which
service I was trying to call.  Instead, Axis is picking the first tag inside
 as the name of the method.
But I'm running on guesses and assumptions at this point.  I'm sticking with
the WSDL as-is since it's been blessed by Anne, and will try to adjust the
wsdd and the client code to match.
The wsdl, wsdd, and client code are here:
http://www.public.asu.edu/~wsmoak/xml/
--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

Re: How does Axis handle soapAction?

2003-08-01 Thread Medha Vashi

Title: How does Axis handle soapAction?



 

  - Original Message - 
  From: 
  Cory 
  Wilkerson 
  To: [EMAIL PROTECTED] 
  Sent: Friday, August 01, 2003 2:43 
  PM
  Subject: RE: How does Axis handle 
  soapAction?
  
  Sorry about that Wendy -- got carried away in my 
  response.
  
-Original Message-From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 2:18 
PMTo: [EMAIL PROTECTED]Subject: 
Re: How does Axis handle soapAction?
The attribute is "SOAPAction", not 
"header".
The value specified in the attribute must be 
specified in the SOAPAction: HTTP header on the SOAP request message. It 
gives the SOAP server a hint on how to process the message. 
 

  - Original Message - 
  From: 
  Cory Wilkerson 
  To: [EMAIL PROTECTED] 
  Sent: Friday, August 01, 2003 3:07 
  PM
  Subject: RE: How does Axis handle 
  soapAction?
  
  Wendy,
   
  The attribute "header" 
  of element "operation" in the soap namespace http://schemas.xmlsoap.org/wsdl/soap:
   
  A) Appears as an HTTP header
  B) I believe it's sole purpose is to assist the consuming 
  framework in routing the incoming request to the appropriate 
  "service".
   
  Cory
  
-Original Message-From: Wendy Smoak 
[mailto:[EMAIL PROTECTED]Sent: Friday, August 01, 2003 
1:23 PMTo: '[EMAIL PROTECTED]'Subject: How 
does Axis handle soapAction?
I picked this up from the example that Richard Hansen 
posted on 7/30: 
 
However, the string "RatingPortType" does not appear 
anywhere else in the WSDL document.  And the examples in the http://www.w3.org/TR/wsdl.html document always have a 
URL in the soapAction element.
I recognize the string after the # sign as the method to 
be called, but what does "RatingPortType" mean in this case? 
Should it possible match the portType name from this 
section?            
     
     
     
 
Thanks for your help, 
-- Wendy Smoak Applications Systems Analyst, Sr. Arizona 
State University, PA, IRM

RE: Need WSDL for this SOAP message