Re: client for document-style WebService

2005-10-12 Thread Brian Bonner 
It will create a proxy with the necessary entities. that reflect how the 
XML document is supposed to appear. You can then use these entities to 
craft a msg to submit to the appropriate operation.


i.e. if your WSDL is expecting a PriceCheckRequest document (and 
includes the appropriate schema info) as a parameter to an operation 
(for example: checkPrice) then it will generate the 
PriceCheckRequest.java class that knows how to serialize itself and it 
generates the proxy with the methods identified in the WSDL.


I hope that gives you what you want. try it out. It's nice. (btw, I 
can't guarantee that your Web Service that your consuming is defined 
correctly or has the appropriate corresponding WSDL to accommodate this).


Brian



Carmine Gargiulo wrote:

Whaat??? sure?? :D

WSDL2Java generate a client in java with call functions??


In data Wed, 12 Oct 2005 19:22:25 +0200, Brian Bonner 
<[EMAIL PROTECTED]> ha scritto:


If you have the WSDL for a document-style webservice, you can use 
WSDL2Java to generate yourself a client that you can work with. Then 
you can call the service using the generated client.


Brian



Carmine Gargiulo wrote:

Hi

i've a BIG problem

for my work i MUST ask infodata to document-style WebService.

In the net i've found a lot of example of clients for RPC-style 
WS...but not for document-style WebService.


In general the code was:

String nameWS = "http://localhost:8080/axis/services/wsRemote";;
URL endPointWS = new URL(nameWS);

// init
Service service = new Service();
Call call = (Call) service.createCall();

call.setTargetEndpointAddress(endPointWS);
call.setOperationName("getFileToString");

String op1 = new String(myParam);

call.addParameter("op1", XMLType.XSD_STRING, ParameterMode.IN);

call.setReturnType(XMLType.XSD_STRING);

ret = String.valueOf(call.invoke(new Object[] {op1}));



I'm junior of axis and WebService.and I think that for 
document-style WebService the cose above not is rith.


The WS give me a XML but i don't know ...how take this xmland if 
this XML is in HD or in memory or other.


Please help me!! I'S VERY URGENT

--Carmine Gargiulo

Carmine Gargiulo usa il rivoluzionario client e-mail di Opera: 
http://www.opera.com/m2/



-- Email.it, the professional e-mail, gratis per te: 
http://www.email.it/f


Sponsor:
Digitalpix stampa le tue migliori foto digitali* su vera carta 
fotografica professionale.

Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1532&d=12-10






--Carmine Gargiulo

Carmine Gargiulo usa il rivoluzionario client e-mail di Opera: 
http://www.opera.com/m2/



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Problemi di Liquidità? Con Logos Finanziaria 30.000 � in 24 ore a 
dipendenti e lavoratori autonomi con rimborsi fino a 120 mesi, clicca qui

*Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2911&d=12-10

Re: client for document-style WebService

2005-10-12 Thread Brian Bonner 
If you have the WSDL for a document-style webservice, you can use 
WSDL2Java to generate yourself a client that you can work with.  Then 
you can call the service using the generated client.


Brian



Carmine Gargiulo wrote:

Hi

i've a BIG problem

for my work i MUST ask infodata to document-style WebService.

In the net i've found a lot of example of clients for RPC-style 
WS...but not for document-style WebService.


In general the code was:

  String nameWS = "http://localhost:8080/axis/services/wsRemote";;
  URL endPointWS = new URL(nameWS);

  // init
  Service service = new Service();
  Call call = (Call) service.createCall();

  call.setTargetEndpointAddress(endPointWS);
  call.setOperationName("getFileToString");

  String op1 = new String(myParam);

  call.addParameter("op1", XMLType.XSD_STRING, ParameterMode.IN);

  call.setReturnType(XMLType.XSD_STRING);

  ret = String.valueOf(call.invoke(new Object[] {op1}));



I'm junior of axis and WebService.and I think that for 
document-style WebService the cose above not is rith.


The WS give me a XML but i don't know ...how take this xmland if 
this XML is in HD or in memory or other.


Please help me!! I'S VERY URGENT

--Carmine Gargiulo

Carmine Gargiulo usa il rivoluzionario client e-mail di Opera: 
http://www.opera.com/m2/



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Digitalpix stampa le tue migliori foto digitali* su vera carta 
fotografica professionale.

Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1532&d=12-10

Re: WSDL2Java Serialized XML missing xsd declaration

2005-09-15 Thread Brian Bonner 
I stand corrected. I see that the Soap Envelope actually contains the 
xsd declaration.  So it appears that when the message is pulled out of 
the envelope, the declaration is being lost.


Brian



Brian Bonner wrote:

The WSDL2Java generated code is including xsi:type attributes on the 
beans, the value of the xsi:types includes:  xsi:type="xsd:string", 
but does not include the xsd declaration.


Is there any way to include this declaration in the message generated 
by the BeanSerializer?


I previously asked a question on how to turn off XSITypeGeneration 
because this thing is "still" giving me fits.


Thanks.

WSDL2Java Serialized XML missing xsd declaration

2005-09-15 Thread Brian Bonner 
The WSDL2Java generated code is including xsi:type attributes on the 
beans, the value of the xsi:types includes:  xsi:type="xsd:string", but 
does not include the xsd declaration.


Is there any way to include this declaration in the message generated by 
the BeanSerializer?


I previously asked a question on how to turn off XSITypeGeneration 
because this thing is "still" giving me fits.


Thanks.

[Fwd: Re: Way to turn off XSITypeGeneration?]

2005-09-14 Thread Brian Bonner 
Does anyone have a chance to validate that the stub generated by this 
WSDL is in fact missing the xsd prefix namespace declaration, or is 
there something that I mangled in the WSDL.


Thanks.

Sure.  I've attached it.

Brian



Anne Thomas Manes wrote:


Can you provide the WSDL?

On 9/8/05, *Brian Bonner* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


I did more research and it looks like org.apache.axis.message.RPCParam
is generating the XSIType info.  There's a method to turn this
generation on/off, but it looks like the Call class doesn't use it.

Is there anyway to turn this off or include the schema in the outer
element?  Thanks.

    Brian



Brian Bonner wrote:

> I also wonder why xsi:type="xsd:string"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>" is being
> generated in the instance document that is being sent from the Stub.
> This doesn't need to be there.  Is there a way to not have this be
> generated?  Is there a WSDL2Java switch that I'm unaware of?
>
> Brian
>
>
>
> Brian Bonner wrote:
>
>> I used WSDL2Java to create a client of a Document/Literal Web
>> Service.  When I use the generated Proxy to call the service, the
>> document that ends up being generated includes:
>> xsi:type="xsd:string"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>"
>>
>> in the elements,  however, xsd is not declared anywhere and
>> validation of the document at the server is failing.  If I declare
>> the xsd namespace in either the root element or in each of the
>> elements where it's used, it succeeds.  i.e.
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>>
>> I've been searching for what is causing this.  I noticed that
the ns1
>> namespace *IS* included in the Body tag below.
>>
>> Any thoughts?
>>
>> Here's the example:
>>
>> 
>> >
xmlns="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
>> xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
>>

xsi:schemaLocation="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest
<http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest>
>> xsd/paraware/priceAndAvailabilityRequest.xsd ">
>>  
>>
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>T
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";

<http://www.w3.org/2001/XMLSchema-instance%22>>2005-09-08T13:20:27.375Z
>>
>>
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>383401
>>
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>383401
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

<http://www.w3.org/2001/XMLSchema-instance%22>>parawarePA/parawarePA1
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>OKI
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>45215
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>OKI
>>
>>  
>>  > xmlns:ns1="
http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>>
>>  3M 1100
>>
>>  
>> 
>>
>





--
Brian


http://selfservice.webservice.paraware.com";
	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
	xmlns:ns1="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
	xmlns:ns2="http://www.paraware.com/2005/PriceAndAvailabilityCheckResponse";
	xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
	xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
	xmlns:tns="http://selfservice.webservice.paraware.com";
	xmlns:wsdlsoap="http:

Re: Way to turn off XSITypeGeneration?

2005-09-10 Thread Brian Bonner 

Sure.  I've attached it.

Brian



Anne Thomas Manes wrote:


Can you provide the WSDL?

On 9/8/05, *Brian Bonner* <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


I did more research and it looks like org.apache.axis.message.RPCParam
is generating the XSIType info.  There's a method to turn this
generation on/off, but it looks like the Call class doesn't use it.

Is there anyway to turn this off or include the schema in the outer
element?  Thanks.

    Brian



Brian Bonner wrote:

> I also wonder why xsi:type="xsd:string"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>" is being
> generated in the instance document that is being sent from the Stub.
> This doesn't need to be there.  Is there a way to not have this be
> generated?  Is there a WSDL2Java switch that I'm unaware of?
>
> Brian
>
>
>
> Brian Bonner wrote:
>
>> I used WSDL2Java to create a client of a Document/Literal Web
>> Service.  When I use the generated Proxy to call the service, the
>> document that ends up being generated includes:
>> xsi:type="xsd:string"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>"
>>
>> in the elements,  however, xsd is not declared anywhere and
>> validation of the document at the server is failing.  If I declare
>> the xsd namespace in either the root element or in each of the
>> elements where it's used, it succeeds.  i.e.
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>>
>> I've been searching for what is causing this.  I noticed that
the ns1
>> namespace *IS* included in the Body tag below.
>>
>> Any thoughts?
>>
>> Here's the example:
>>
>> 
>> >
xmlns="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
>> xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
>>

xsi:schemaLocation="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest
<http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest>
>> xsd/paraware/priceAndAvailabilityRequest.xsd ">
>>  
>>
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>T
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";

<http://www.w3.org/2001/XMLSchema-instance%22>>2005-09-08T13:20:27.375Z
>>
>>
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>383401
>>
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>383401
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

<http://www.w3.org/2001/XMLSchema-instance%22>>parawarePA/parawarePA1
>>
>>  > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>OKI
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>45215
>>  > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance%22>>OKI
>>
>>  
>>  > xmlns:ns1="
http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>>
>>  3M 1100
>>
>>  
>> 
>>
>



http://selfservice.webservice.paraware.com";
	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
	xmlns:ns1="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
	xmlns:ns2="http://www.paraware.com/2005/PriceAndAvailabilityCheckResponse";
	xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
	xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
	xmlns:tns="http://selfservice.webservice.paraware.com";
	xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
	xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
	
		http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest";
			elementFormDefault="qualified"

Way to turn off XSITypeGeneration?

2005-09-08 Thread Brian Bonner 
I did more research and it looks like org.apache.axis.message.RPCParam 
is generating the XSIType info.  There's a method to turn this 
generation on/off, but it looks like the Call class doesn't use it.


Is there anyway to turn this off or include the schema in the outer 
element?  Thanks.


Brian



Brian Bonner wrote:

I also wonder why xsi:type="xsd:string" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; is being 
generated in the instance document that is being sent from the Stub.  
This doesn't need to be there.  Is there a way to not have this be 
generated?  Is there a WSDL2Java switch that I'm unaware of?


Brian



Brian Bonner wrote:

I used WSDL2Java to create a client of a Document/Literal Web 
Service.  When I use the generated Proxy to call the service, the 
document that ends up being generated includes:   
xsi:type="xsd:string" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";


in the elements,  however, xsd is not declared anywhere and 
validation of the document at the server is failing.  If I declare 
the xsd namespace in either the root element or in each of the 
elements where it's used, it succeeds.  i.e. 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";


I've been searching for what is causing this.  I noticed that the ns1 
namespace *IS* included in the Body tag below.


Any thoughts?

Here's the example:


xmlns="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest 
xsd/paraware/priceAndAvailabilityRequest.xsd ">

 
   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>T
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>2005-09-08T13:20:27.375Z 


   
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401 


   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401 

 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>parawarePA/parawarePA1 

 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>45215
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI

   
 
 xmlns:ns1="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

   
 3M 1100

Re: xsd declaration is not included in XML instance by the generated client proxy

2005-09-08 Thread Brian Bonner 
I also wonder why xsi:type="xsd:string" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; is being generated 
in the instance document that is being sent from the Stub.  This doesn't 
need to be there.  Is there a way to not have this be generated?  Is 
there a WSDL2Java switch that I'm unaware of?


Brian



Brian Bonner wrote:

I used WSDL2Java to create a client of a Document/Literal Web 
Service.  When I use the generated Proxy to call the service, the 
document that ends up being generated includes:   
xsi:type="xsd:string" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";


in the elements,  however, xsd is not declared anywhere and validation 
of the document at the server is failing.  If I declare the xsd 
namespace in either the root element or in each of the elements where 
it's used, it succeeds.  i.e. 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";


I've been searching for what is causing this.  I noticed that the ns1 
namespace *IS* included in the Body tag below.


Any thoughts?

Here's the example:


xmlns="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest 
xsd/paraware/priceAndAvailabilityRequest.xsd ">

 
   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>T
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>2005-09-08T13:20:27.375Z 


   
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401

   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>parawarePA/parawarePA1 

 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>45215
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI

   
 
 xmlns:ns1="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

   
 3M 1100

xsd declaration is not included in XML instance by the generated client proxy

2005-09-08 Thread Brian Bonner 
I used WSDL2Java to create a client of a Document/Literal Web Service.  
When I use the generated Proxy to call the service, the document that 
ends up being generated includes:   xsi:type="xsd:string" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";


in the elements,  however, xsd is not declared anywhere and validation 
of the document at the server is failing.  If I declare the xsd 
namespace in either the root element or in each of the elements where 
it's used, it succeeds.  i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema";


I've been searching for what is causing this.  I noticed that the ns1 
namespace *IS* included in the Body tag below.


Any thoughts?

Here's the example:


xmlns="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest 
xsd/paraware/priceAndAvailabilityRequest.xsd ">

 
   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>T
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>2005-09-08T13:20:27.375Z

   
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401

   
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>383401
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>parawarePA/parawarePA1
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>45215
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>OKI

   
 
 xmlns:ns1="http://www.paraware.com/2005/PriceAndAvailabilityCheckRequest"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

   
 3M 1100
   
 


--
Brian