AW: deploy trouble

2005-06-06 Thread Ferruh Zamangoer
Have you checked your server-config.wsdd if your service is there. When you
deploy your service you can see a new service part with.:


 


But I'am not sure if this is the problem.

Regards
Ferruh



-Ursprüngliche Nachricht-
Von: James Taylor [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 20:51
An: axis-user@ws.apache.org
Betreff: Fwd: deploy trouble


Hi there,
 I'm trying to deploy a service to axis using the admin client and
is
not listed in axis/server-config.wsdd. It seems to deploy and undeploy ok:
axisDeploy:
 [echo] doing deploy task...
 [java] Processing file
E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\deploy.wsdd
 [java] Done processing
 [echo] Done...

axisDeploy:
 [echo] doing deploy task...
 [java] Processing file
E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\undeploy.wsdd
 [java] Done processing
 [echo] Done...

...But it does not show up as deployed on axis "View the list of deployed
Web
services" link and this link does not complain about anything. Why is this?
thought it would throw an error if not deployed and one tried to undeploy
it.

Here's deploy.wsdd









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

  

  
  http://ie/tcd/taylorjw/flightbooking/wsdl"/>
  
  
  
  
  http://ie.tcd/taylorjw/flightbooking"; returnType="rtns:anyType"
xmlns:rtns="http://www.w3.org/2001/XMLSchema"; soapAction="bookFlights" >
http://ie.tcd/taylorjw/flightbooking"; type="tns:anyType"
xmlns:tns="http://www.w3.org/2001/XMLSchema"/>
  
  
  

  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Flight"
type="java: flightCompany.bookFlights.rpcservice.Flight"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Passenger"
type="java: flightCompany.bookFlights.rpcservice.Passenger"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Booking"
type="java: flightCompany.bookFlights.rpcservice.Booking"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />

  




document style client

2005-06-06 Thread Kiran Kumar


Hi, Can any of you please 
tell me what is wrong with my client code ?
 
I am trying to invoke a service (document 
type) but it was not able to construct the input object. I am sure the way I am 
constucting my input XML is not correct, but I am unable to get any exampe on 
how to do that.. 
 
I am here attaching my client code 
(SdeGcIndividualWsTest.java) , my schema definition (gcindividual.xsd) and wsdl 
(getcoordinate.wsdl).
 
Thanks for your time, Kiran
 

This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named.  If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone.  E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses.  ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission.  The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates.


SdeGcIndividualWsTest.java
Description: SdeGcIndividualWsTest.java

http://domain.cityofchicago.gis.gce/versions/1.0/gcindividual"; xmlns:gccommon="http://domain.cityofchicago.gis.gce/versions/1.0/gccommontypes"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; targetNamespace="http://domain.cityofchicago.gis.gce/versions/1.0/gcindividual"; elementFormDefault="qualified">
	http://domain.cityofchicago.gis.gce/versions/1.0/gccommontypes"; schemaLocation="gccommontypes.xsd"/>
	
		
			
			
			
		
	
	
	
	
	



http://schemas.xmlsoap.org/wsdl/http/"; 
	xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
	xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; 
	xmlns:apachesoap="http://xml.apache.org/xml-soap"; 
	xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
	xmlns:ws="http://www.example.com/webservice"; 
	xmlns:impl="http://domain.cityofchicago.gis.gce/versions/1.0/getcoordinate/wsdl"; 
	xmlns:gcindividualtypes="http://domain.cityofchicago.gis.gce/versions/1.0/gcindividual"; 
	xmlns:gcintersectiontypes="http://domain.cityofchicago.gis.gce/versions/1.0/gcintersection"; 
	xmlns:gconfromtotypes="http://domain.cityofchicago.gis.gce/versions/1.0/gconfromto"; 
	xmlns:gcrangetypes="http://domain.cityofchicago.gis.gce/versions/1.0/gcrange"; 
	xmlns:ns="http://domain.cityofchicago.gis.gce/versions/1.0/gccommontypes"; 
	targetNamespace="http://domain.cityofchicago.gis.gce/versions/1.0/getcoordinate/wsdl";>
	
		http://domain.cityofchicago.gis.gce/versions/1.0/gcindividual/wsdl/importtypes";>
			http://domain.cityofchicago.gis.gce/versions/1.0/gcindividual"; schemaLocation="gcindividual.xsd"/>
		
		http://domain.cityofchicago.gis.gce/versions/1.0/gcintersection/wsdl/importtypes";>
			http://domain.cityofchicago.gis.gce/versions/1.0/gcintersection"; schemaLocation="gcintersection.xsd"/>
		
		http://domain.cityofchicago.gis.gce/versions/1.0/gconfromto/wsdl/importtypes";>
			http://domain.cityofchicago.gis.gce/versions/1.0/gconfromto"; schemaLocation="gconfromto.xsd"/>
		
		http://domain.cityofchicago.gis.gce/versions/1.0/gconfromto/wsdl/importtypes";>
			http://domain.cityofchicago.gis.gce/versions/1.0/gcrange"; schemaLocation="gcrange.xsd"/>
		
	
	
		
	
	
		
	
	
		
	
	
		
	
	
		
	
	
		
	
	
		
	
	
		
	
	
		
		
			
			
		
		
		
			
			
		
		
		
			
			
		
		
		
			
			
		
	
	
		http://schemas.xmlsoap.org/soap/http"/>
		
			
			

			
			

			
		
		
			
			

			
			

			
		
		
			
			

			
			

			
		
		
			
			

			
			

			
		
	
	
		
			http://localhost:8080/gce/services/GetCoord"/>
		
	



RE: import schema to wsdl

2005-06-06 Thread Kiran Kumar
You don't have to specify any other changes in wsdl or WSDL2Java script. Once 
you run WSDL2Java, check the **SOAPBindingImpl.java, the method should return 
correct return type (Flight). 
 
Kiran  



From: James Taylor [mailto:[EMAIL PROTECTED]
Sent: Mon 6/6/2005 3:17 PM
To: axis-user@ws.apache.org
Subject: Re: import schema to wsdl





If I make the changes below will I have to specify anything else in the wsdl or
in wsdl2java to get wrapped-literal style?

Quoting James Taylor <[EMAIL PROTECTED]>:

>
> So I should just chang change types:bookFlightsRequest to types:bookFlights
> and
> reflect this in the external schema, will I have to change  message="tns:bookFlightsReq" />  also?
>
> ...heres the bit of the wsdl that would have to be changed...
>
> 
>   
>   
>   
>   
>   
>
>
>   
>  xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
>   elementFormDefault = "qualified"
>   targetNamespace = 
> "http://ie.tcd/taylorjw/flightbooking";>
>"http://ie.tcd/taylorjw/flightbooking";
> schemaLocation="BookFlights.xsd"/>
>"http://www.w3.org/2001/XMLSchema"; />
>
>   
>   
>
>   
>   
>   
>
>   
>   
>   
>
>   
>   
>   
>   
>   
>   
>
>
> Quoting Anne Thomas Manes <[EMAIL PROTECTED]>:
>
> > James,
> >
> > If you want an interface that accepts parameters rather than an
> > object, then you must define your WSDL so that it matches the
> > "wrapped" convention. What that means is that your input message
> > element name must be identical to your operation name. Currently your
> > input message element name is bookFlightsRequest and your operation
> > name is bookFlights. If you fix it so that they are the same, it
> > should give you what you want.
> >
> > Anne
> >
> > On 6/6/05, Jeff <[EMAIL PROTECTED]> wrote:
> > > In general, I wouldn't let Axis provide a WSDL file. Tell it to use your
> > > WSDL file by adding a  element to the WSDD file before you
> deploy
> > > so you wind up with something like:
> > >
> > >  > > xmlns="http://xml.apache.org/axis/wsdd/";
> > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> > >
> > >   /MyService.wsdl
> > >
> > >   http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort
> > >
> > >
> > > Jeff
> > >
> > >
> > >
> > > - Original Message -
> > > From: "James Taylor" <[EMAIL PROTECTED]>
> > > To: 
> > > Sent: Monday, June 06, 2005 5:02 AM
> > > Subject: Re: import schema to wsdl
> > >
> > >
> > > Thanks for your help jeff. The main problem was the conflicting target
> > > namespaces I was trying to import into my wsdl. I've gotten the wsdl2java
> > > tool
> > > to work fine now. Just a question on what will when the service gets
> > > deployed
> > > to axis. I presume axis will make a different wsdl then the one I gave to
> > > the
> > > tool as it has defined a method signature for the portType as
> > >  public java.lang.Object bookFlights(java.lang.Object parameters) throws
> > > java.rmi.RemoteException; would any one mind commenting on this as I
> > defined
> > > the method signature in the wsdl more specific then this... I know that I
> > > defined a custom collection bean that is of type object - I presume I'll
> > > cast
> > > the parameters to get at it.
> > > Regards,
> > > James.
> > >
> > > My wsdl and external schema...
> > >  > >   targetNamespace="http://ie/tcd/taylorjw/flightbooking/wsdl";
> > >   xmlns="http://schemas.xmlsoap.org/wsdl/";
> > >   xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
> > >   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > >   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > >   xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >
> > >
> > > 
> > >  > > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
> > > elementFormDefault = "qualified"
> > > targetNamespace = "http://ie.tcd/taylorjw/flightbooking";>
> > > http://ie.tcd/taylorjw/flightbooking";
> > > schemaLocation="BookFlights.xsd"/>
> > > http://www.w3.org/2001/XMLSchema"; />
> > >
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > >  > > transport="http://schemas.xmlsoap.org/soap/http"; />
> > > 
> > >  
> > >  
> > >   
> > >  
> > >  
> > >   
> > >  
> > > 
> > >   
> > >
> > >   
> > > > > binding="tns:BookFlightsSOAPBinding">
> > >  > > location="http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
> > >
> > >   
> > >
> > > 
> > >
> > >
> > > 
> > >
> > > 
> > > http://www.w3.org/2001/XMLSchema";
> > > targetNamespace = "htt

Re: import schema to wsdl

2005-06-06 Thread James Taylor


If I make the changes below will I have to specify anything else in the wsdl or
in wsdl2java to get wrapped-literal style?

Quoting James Taylor <[EMAIL PROTECTED]>:

>
> So I should just chang change types:bookFlightsRequest to types:bookFlights
> and
> reflect this in the external schema, will I have to change  message="tns:bookFlightsReq" />  also?
>
> ...heres the bit of the wsdl that would have to be changed...
>
> 
>   
>   
>   
>   
>   
>
>
>   
>  xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
>   elementFormDefault = "qualified"
>   targetNamespace = 
> "http://ie.tcd/taylorjw/flightbooking";>
>"http://ie.tcd/taylorjw/flightbooking";
> schemaLocation="BookFlights.xsd"/>
>"http://www.w3.org/2001/XMLSchema"; />
>
>   
>   
>
>   
>   
>   
>
>   
>   
>   
>
>   
>   
>   
>   
>   
>   
>
>
> Quoting Anne Thomas Manes <[EMAIL PROTECTED]>:
>
> > James,
> >
> > If you want an interface that accepts parameters rather than an
> > object, then you must define your WSDL so that it matches the
> > "wrapped" convention. What that means is that your input message
> > element name must be identical to your operation name. Currently your
> > input message element name is bookFlightsRequest and your operation
> > name is bookFlights. If you fix it so that they are the same, it
> > should give you what you want.
> >
> > Anne
> >
> > On 6/6/05, Jeff <[EMAIL PROTECTED]> wrote:
> > > In general, I wouldn't let Axis provide a WSDL file. Tell it to use your
> > > WSDL file by adding a  element to the WSDD file before you
> deploy
> > > so you wind up with something like:
> > >
> > >  > > xmlns="http://xml.apache.org/axis/wsdd/";
> > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> > >
> > >   /MyService.wsdl
> > >
> > >   http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort
> > >
> > >
> > > Jeff
> > >
> > >
> > >
> > > - Original Message -
> > > From: "James Taylor" <[EMAIL PROTECTED]>
> > > To: 
> > > Sent: Monday, June 06, 2005 5:02 AM
> > > Subject: Re: import schema to wsdl
> > >
> > >
> > > Thanks for your help jeff. The main problem was the conflicting target
> > > namespaces I was trying to import into my wsdl. I've gotten the wsdl2java
> > > tool
> > > to work fine now. Just a question on what will when the service gets
> > > deployed
> > > to axis. I presume axis will make a different wsdl then the one I gave to
> > > the
> > > tool as it has defined a method signature for the portType as
> > >  public java.lang.Object bookFlights(java.lang.Object parameters) throws
> > > java.rmi.RemoteException; would any one mind commenting on this as I
> > defined
> > > the method signature in the wsdl more specific then this... I know that I
> > > defined a custom collection bean that is of type object - I presume I'll
> > > cast
> > > the parameters to get at it.
> > > Regards,
> > > James.
> > >
> > > My wsdl and external schema...
> > >  > >   targetNamespace="http://ie/tcd/taylorjw/flightbooking/wsdl";
> > >   xmlns="http://schemas.xmlsoap.org/wsdl/";
> > >   xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
> > >   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> > >   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> > >   xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >
> > >
> > > 
> > >  > > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
> > > elementFormDefault = "qualified"
> > > targetNamespace = "http://ie.tcd/taylorjw/flightbooking";>
> > > http://ie.tcd/taylorjw/flightbooking";
> > > schemaLocation="BookFlights.xsd"/>
> > > http://www.w3.org/2001/XMLSchema"; />
> > >
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > >  > > transport="http://schemas.xmlsoap.org/soap/http"; />
> > > 
> > >  
> > >  
> > >   
> > >  
> > >  
> > >   
> > >  
> > > 
> > >   
> > >
> > >   
> > > > > binding="tns:BookFlightsSOAPBinding">
> > >  > > location="http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
> > >
> > >   
> > >
> > > 
> > >
> > >
> > > 
> > >
> > > 
> > > http://www.w3.org/2001/XMLSchema";
> > > targetNamespace = "http://ie.tcd/taylorjw/flightbooking";
> > > xmlns:fb="http://ie.tcd/taylorjw/flightbooking";>
> > >
> > > 
> > > 
> > > 
> > >  > > maxOccurs="unbounded"/>
> > > 
> > > 
> > >
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > >
> > >
> > >
> > > 
> > > 
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > 
> > >
> > >
> >

Re: Fwd: deploy trouble

2005-06-06 Thread Linus Kamb

Running on Tomcat, I have to reload axis.

Interestingly, in a "fresh" axis install in tomcat, I always have to:
deploy
reload_axis
deploy

before the service appears in the list.


James Taylor wrote:

Hi there,
 I'm trying to deploy a service to axis using the admin client and is
not listed in axis/server-config.wsdd. It seems to deploy and undeploy ok:
axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\deploy.wsdd
 [java] Done processing
 [echo] Done...

axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\undeploy.wsdd
 [java] Done processing
 [echo] Done...

...But it does not show up as deployed on axis "View the list of deployed Web
services" link and this link does not complain about anything. Why is this?
thought it would throw an error if not deployed and one tried to undeploy it.

Here's deploy.wsdd









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

  

  
  http://ie/tcd/taylorjw/flightbooking/wsdl"/>
  
  
  
  
  http://ie.tcd/taylorjw/flightbooking"; returnType="rtns:anyType"
xmlns:rtns="http://www.w3.org/2001/XMLSchema"; soapAction="bookFlights" >
http://ie.tcd/taylorjw/flightbooking"; type="tns:anyType"
xmlns:tns="http://www.w3.org/2001/XMLSchema"/>
  
  
  

  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Flight"
type="java: flightCompany.bookFlights.rpcservice.Flight"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Passenger"
type="java: flightCompany.bookFlights.rpcservice.Passenger"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Booking"
type="java: flightCompany.bookFlights.rpcservice.Booking"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />

  




Class Cast Exception

2005-06-06 Thread BVG
Hi people,

I have a problem!
I get a ClassCastException when I invoke a stub (created by the tool WSDL2Java) 
inside a JAAS module.
It crashes in this point (157/WSDDTargetedChain.class):
pivot = (Handler)ClassUtils.forName(pivotQName.getLocalPart()).newInstance();

It seems a problem of ClassLoader.
Any help in here?
There is any solution for this case?

Thanks people..

---
Bruno Vieira Gonçalves



Issue with 'wrapped' style webservice code generation - added the attachments

2005-06-06 Thread Kiran Kumar


I am very sorry. I missed the attachments in my last mail.
Thanks Kiran



From: Kiran KumarSent: 
Mon 6/6/2005 2:31 PMTo: axis-user@ws.apache.orgSubject: 
Issue with 'wrapped' style webservice code generation


Hello,
 
I am really stuck with this issue. I am 
using Axis 1.2 and trying to use wrapped style webservice. WSDL2Java is not 
generating the 'response' type Value Object and SoapBindingImpl class method 
return type is wrong.
 
Please have a look at identify.wsdl, 
operation 'individual' has an output parameter (response) whose return type is 
'geocode'. [look at the idindividual.xsd and idcommontypes.xsd].
 
It is supposed to generate 
IdentifySoapBindingImpl class with the following method signature
 
    public 
org.cityofchicago.gis.gce.service.axis.id.Geocode 
individual(java.lang.String address, int geoCodingtarget, java.lang.String 
targetlayers, boolean returnflag, boolean locatortype) throws 
java.rmi.RemoteException {    return 
null;    }
But it was generating the following method 
signature:
 
    public org.cityofchicago.gis.gce.service.axis.id.Outputs 
individual(java.lang.String address, int geoCodingtarget, java.lang.String 
targetlayers, boolean returnflag, boolean locatortype) throws 
java.rmi.RemoteException {    return 
null;    }
It is also not generating the 
Geocode Value Object.
 
PS:
Please observe that input message element 
name (individual) is matching with operation name (individual). If I change the 
input message element name to somename other than "individual" then it was 
generating the Geocode value Object but the method's input parameter will be 
object instead of individual parameters. Since I want the method signature to 
accept individual paramters I kept the input message element name is same as 
operation name.. But I am stuck with above explained problem (return type is not 
correct).
 

Thanks
Kiran
-
Ph: 312 742 9630
Email: [EMAIL PROTECTED]

This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named.  If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone.  E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses.  ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission.  The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates.


http://schemas.xmlsoap.org/wsdl/http/"; 
			xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
			xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
			xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; 
			xmlns:apachesoap="http://xml.apache.org/xml-soap"; 
			xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
			xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
			xmlns:ws="http://www.example.com/webservice"; 
			xmlns:impl="http://domain.cityofchicago.gis.gce/versions/1.0/identify/wsdl"; 
			xmlns:idindividualtypes="http://domain.cityofchicago.gis.gce/versions/1.0/idindividual"; 
			xmlns:ns="http://domain.cityofchicago.gis.gce/versions/1.0/idcommontypes"; 
			targetNamespace="http://domain.cityofchicago.gis.gce/versions/1.0/identify/wsdl";>
	
		http://domain.cityofchicago.gis.gce/versions/1.0/idindividual/wsdl/importtypes";>
			http://domain.cityofchicago.gis.gce/versions/1.0/idindividual"; schemaLocation="idindividual.xsd"/>
		
	
	
		
	
	
		
	
	
		
		
			
			
		
	
	
		http://schemas.xmlsoap.org/soap/http"/>
		
			
			

			
			

			
		
	
	
		
			http://localhost:8080/gce/services/Ident"/>
		
	


http://domain.cityofchicago.gis.gce/versions/1.0/idindividual"; 
	   xmlns:idcommon="http://domain.cityofchicago.gis.gce/versions/1.0/idcommontypes"; 
	   xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
	   targetNamespace="http://domain.cityofchicago.gis.gce/versions/1.0/idindividual"; elementFormDefault="qualified">
	http://domain.cityofchicago.gis.gce/versions/1.0/idcommontypes"; schemaLocation="idcommontypes.xsd"/>
	
		
			
			
			
			
			
		
	
	
	
	
	


http://domain.cityofchicago.gis.gce/versions/1.0/idcommontypes"; 
	   xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
	   targetNamespace="http://domain.cityofchicago.gis.gce/versions/1.0/idcommontypes"; 
	   elementFormDefault="qualified" attributeFormDefault="unqualified">
	
		

		
		
	
	
		
			
		
		
	
	   
		   
	   
	   
	
	
		
			
			
		
	
	
		
			
		
	



IdentifySoapBindingImpl.java
Description: IdentifySoapBindingImpl.java


Issue with 'wrapped' style webservice code generation

2005-06-06 Thread Kiran Kumar


Hello,
 
I am really stuck with this issue. I am 
using Axis 1.2 and trying to use wrapped style webservice. WSDL2Java is not 
generating the 'response' type Value Object and SoapBindingImpl class method 
return type is wrong.
 
Please have a look at identify.wsdl, 
operation 'individual' has an output parameter (response) whose return type is 
'geocode'. [look at the idindividual.xsd and idcommontypes.xsd].
 
It is supposed to generate 
IdentifySoapBindingImpl class with the following method signature
 
    public 
org.cityofchicago.gis.gce.service.axis.id.Geocode 
individual(java.lang.String address, int geoCodingtarget, java.lang.String 
targetlayers, boolean returnflag, boolean locatortype) throws 
java.rmi.RemoteException {    return 
null;    }
But it was generating the following method 
signature:
 
    public org.cityofchicago.gis.gce.service.axis.id.Outputs 
individual(java.lang.String address, int geoCodingtarget, java.lang.String 
targetlayers, boolean returnflag, boolean locatortype) throws 
java.rmi.RemoteException {    return 
null;    }
It is also not generating the 
Geocode Value Object.
 
PS:
Please observe that input message element 
name (individual) is matching with operation name (individual). If I change the 
input message element name to somename other than "individual" then it was 
generating the Geocode value Object but the method's input parameter will be 
object instead of individual parameters. Since I want the method signature to 
accept individual paramters I kept the input message element name is same as 
operation name.. But I am stuck with above explained problem (return type is not 
correct).
 

Thanks
Kiran
-
Ph: 312 742 9630
Email: [EMAIL PROTECTED]

This e-mail, and any attachments thereto, is confidential and is intended only for the individual(s) named.  If you are not the intended recipient, please let us know by e-mail reply and delete it from your system; do not copy/save this e-mail or disclose its contents to anyone.  E-mail transmissions cannot be guaranteed to be secure or error-free as the transmission could be interrupted, corrupted, lost, destroyed, altered, arrive late or contain viruses.  ObjectWave does not accept liability for any errors or omissions in the contents of this e-mail which arise as a result of e-mail transmission.  The views expressed in this e-mail do not necessarily reflect those of ObjectWave or its affiliates.


Fwd: deploy trouble

2005-06-06 Thread James Taylor

Hi there,
 I'm trying to deploy a service to axis using the admin client and is
not listed in axis/server-config.wsdd. It seems to deploy and undeploy ok:
axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\deploy.wsdd
 [java] Done processing
 [echo] Done...

axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\undeploy.wsdd
 [java] Done processing
 [echo] Done...

...But it does not show up as deployed on axis "View the list of deployed Web
services" link and this link does not complain about anything. Why is this?
thought it would throw an error if not deployed and one tried to undeploy it.

Here's deploy.wsdd









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

  

  
  http://ie/tcd/taylorjw/flightbooking/wsdl"/>
  
  
  
  
  http://ie.tcd/taylorjw/flightbooking"; returnType="rtns:anyType"
xmlns:rtns="http://www.w3.org/2001/XMLSchema"; soapAction="bookFlights" >
http://ie.tcd/taylorjw/flightbooking"; type="tns:anyType"
xmlns:tns="http://www.w3.org/2001/XMLSchema"/>
  
  
  

  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Flight"
type="java: flightCompany.bookFlights.rpcservice.Flight"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Passenger"
type="java: flightCompany.bookFlights.rpcservice.Passenger"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Booking"
type="java: flightCompany.bookFlights.rpcservice.Booking"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />

  



deploy trouble

2005-06-06 Thread James Taylor
Hi there,
 I'm trying to deploy a service to axis using the admin client and is
not listed in axis/server-config.wsdd. It seems to deploy and undeploy ok:
axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\deploy.wsdd
 [java] Done processing
 [echo] Done...

axisDeploy:
 [echo] doing deploy task...
 [java] Processing file E:\taylorjwDocs\JavaProjects\Development\WorkingJAX-
RPCmodel\src\flightCompany\bookFlights\rpcservice\undeploy.wsdd
 [java] Done processing
 [echo] Done...

...But it does not show up as deployed on axis "View the list of deployed Web
services" link and this link does not complain about anything. Why is this?
thought it would throw an error if not deployed and one tried to undeploy it.

Here's deploy.wsdd









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

  

  
  http://ie/tcd/taylorjw/flightbooking/wsdl"/>
  
  
  
  
  http://ie.tcd/taylorjw/flightbooking"; returnType="rtns:anyType"
xmlns:rtns="http://www.w3.org/2001/XMLSchema"; soapAction="bookFlights" >
http://ie.tcd/taylorjw/flightbooking"; type="tns:anyType"
xmlns:tns="http://www.w3.org/2001/XMLSchema"/>
  
  
  

  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Flight"
type="java: flightCompany.bookFlights.rpcservice.Flight"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Passenger"
type="java: flightCompany.bookFlights.rpcservice.Passenger"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />
  http://ie.tcd/taylorjw/flightbooking";
qname="ns:Booking"
type="java: flightCompany.bookFlights.rpcservice.Booking"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle=""
  />

  



--
Between the question and the answer lies free will


my woes with doc/lit wrapped and String[] return types

2005-06-06 Thread Nathaniel A. Johnson
hi all,

with the help of numerous people here (especially anne) and lots of
stepping through code and docs, i have finally gotten my client to
accept String[] return types with the doc/lit wrapped style.

for some reason, axis is creating an ArrayList rather than a String[]
for the return type of my methods, even though i never mention ArrayList
in my code.  maybe the serializer for arrays just creates an ArrayList
for arrays and i missed the documentation for that some where.  anyway,
here is the code i finally ended up using (note: getMembers() returns
String[]).

Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL(baseUrl +
  "/GroupsServiceService"));
call.setOperationName("getMembers");
call.setEncodingStyle("wrapped");
call.addParameter("group", XMLType.XSD_STRING, ParameterMode.IN);
call.setReturnType(XMLType.XSD_STRING);
List members = (ArrayList)call.invoke(new Object[] { group });

what seemed odd to me was that return type needed to be set to the type
of the array elements, not the return type of the method call.  i guess
this does make sense, but it's not something i would first think of.

feel free to comment on the code if anyone feels i am doing something
stupid.

thanks again to everyone that helped me through this!
nate



Fwd: Re: import schema to wsdl

2005-06-06 Thread James Taylor

So I should just chang change types:bookFlightsRequest to types:bookFlights and
reflect this in the external schema, will I have to change   also?

...heres the bit of the wsdl that would have to be changed...










http://www.w3.org/2001/XMLSchema";
elementFormDefault = "qualified"
targetNamespace = 
"http://ie.tcd/taylorjw/flightbooking";>
http://ie.tcd/taylorjw/flightbooking";
schemaLocation="BookFlights.xsd"/>
http://www.w3.org/2001/XMLSchema"; />




















Quoting Anne Thomas Manes <[EMAIL PROTECTED]>:

> James,
>
> If you want an interface that accepts parameters rather than an
> object, then you must define your WSDL so that it matches the
> "wrapped" convention. What that means is that your input message
> element name must be identical to your operation name. Currently your
> input message element name is bookFlightsRequest and your operation
> name is bookFlights. If you fix it so that they are the same, it
> should give you what you want.
>
> Anne
>
> On 6/6/05, Jeff <[EMAIL PROTECTED]> wrote:
> > In general, I wouldn't let Axis provide a WSDL file. Tell it to use your
> > WSDL file by adding a  element to the WSDD file before you deploy
> > so you wind up with something like:
> >
> >  > xmlns="http://xml.apache.org/axis/wsdd/";
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> >
> >   /MyService.wsdl
> >
> >   http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort
> >
> >
> > Jeff
> >
> >
> >
> > - Original Message -
> > From: "James Taylor" <[EMAIL PROTECTED]>
> > To: 
> > Sent: Monday, June 06, 2005 5:02 AM
> > Subject: Re: import schema to wsdl
> >
> >
> > Thanks for your help jeff. The main problem was the conflicting target
> > namespaces I was trying to import into my wsdl. I've gotten the wsdl2java
> > tool
> > to work fine now. Just a question on what will when the service gets
> > deployed
> > to axis. I presume axis will make a different wsdl then the one I gave to
> > the
> > tool as it has defined a method signature for the portType as
> >  public java.lang.Object bookFlights(java.lang.Object parameters) throws
> > java.rmi.RemoteException; would any one mind commenting on this as I
> defined
> > the method signature in the wsdl more specific then this... I know that I
> > defined a custom collection bean that is of type object - I presume I'll
> > cast
> > the parameters to get at it.
> > Regards,
> > James.
> >
> > My wsdl and external schema...
> >  >   targetNamespace="http://ie/tcd/taylorjw/flightbooking/wsdl";
> >   xmlns="http://schemas.xmlsoap.org/wsdl/";
> >   xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
> >   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> >   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >   xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >
> >
> > 
> >  > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
> > elementFormDefault = "qualified"
> > targetNamespace = "http://ie.tcd/taylorjw/flightbooking";>
> > http://ie.tcd/taylorjw/flightbooking";
> > schemaLocation="BookFlights.xsd"/>
> > http://www.w3.org/2001/XMLSchema"; />
> >
> > 
> > 
> >
> > 
> > 
> > 
> >
> > 
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> >  > transport="http://schemas.xmlsoap.org/soap/http"; />
> > 
> >  
> >  
> >   
> >  
> >  
> >   
> >  
> > 
> >   
> >
> >   
> > > binding="tns:BookFlightsSOAPBinding">
> >  > location="http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
> >
> >   
> >
> > 
> >
> >
> > 
> >
> > 
> > http://www.w3.org/2001/XMLSchema";
> > targetNamespace = "http://ie.tcd/taylorjw/flightbooking";
> > xmlns:fb="http://ie.tcd/taylorjw/flightbooking";>
> >
> > 
> > 
> > 
> >  > maxOccurs="unbounded"/>
> > 
> > 
> >
> > 
> > 
> >
> > 
> > 
> > 
> > 
> >
> > 
> > 
> >
> >
> >
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> >
> >
> > 
> > 
> > 
> > 
> > 
> >
> > 
> > 
> > 
> > 
> > 
> >
> >
> > 
> >
> >
>


--
Between the question and the answer lies free will
- End forwarded message -


--
Between the question and the answer lies free will


Re: wrapped style client

2005-06-06 Thread Ravi Krishnamurthy

I had to make the following changes in the addParameter:

_call.addParameter(new javax.xml.namespace.QName("http://tempuri.org/";, 
"A"),org.apache.axis.Constants.XSD_FLOAT,float.class,ParameterMode.IN);
_call.addParameter(new javax.xml.namespace.QName("http://tempuri.org/";, 
"B"),org.apache.axis.Constants.XSD_FLOAT,float.class,ParameterMode.IN);


instead of
_call.addParameter( 
"A",org.apache.axis.Constants.XSD_FLOAT,float.class,ParameterMode.IN);
_call.addParameter( 
"B",org.apache.axis.Constants.XSD_FLOAT,float.class,ParameterMode.IN);
  


Dont know why I did not get any exception if that is not right!!

Thanks,
Ravi

Ravi Krishnamurthy wrote:


Hello:
I'm trying to write a client to document/literal webservice as wrapped 
style to the following webservice:


http://chs.gotdotnet.com/quickstart/aspplus/samples/services/MathService/VB/MathService.asmx 



I have attached my client program. I'm trying to invoke the Add 
operation. There are 2 static methods in the program:


1. add_good - this gives the expected result (12 + 12 = 24)
2. add_bad  - returns 0 - Passing the same input.  Looks like I'm 
doing something wrong which is not very obvious to me. Could someone 
throw some pointers.


Thanks for your help and time.

Regards,
Ravi




import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.enum.Style;
import org.w3c.dom.Document;
import org.w3c.dom.Element;

import javax.xml.namespace.QName;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.ParameterMode;
import java.net.URL;


import java.util.Iterator;

public class MathClient
{
private static String endpoint = 
"http://chs.gotdotnet.com/quickstart/aspplus/samples/services/MathService/VB/MathService.asmx";;
private static String wsdlURL = endpoint + "?WSDL";
public static void main(String [] args) throws Exception {
 

//checkExists();

add_good();

add_bad();

//checkExists();
 
 
   
   }

   
   public static void add_good() throws Exception{
   
   Service  service = new Service(new URL(wsdlURL), new QName("http://tempuri.org/","MathService";));

   Call _call= (Call)(service.createCall(new 
QName("http://tempuri.org/","MathServiceSoap";),
   new QName("http://tempuri/org/","Add";)));
   _call.setSOAPActionURI("http://tempuri.org/Add";);
   _call.setOperationStyle(Style.WRAPPED);
   System.out.println(" Response from add_good is " + _call.invoke(new 
Object[] {new Float(12) , new Float(12)}));
   }
   
   public static void add_bad() throws Exception{
   
   Service  service = new Service();

   Call _call= (Call)(service.createCall());
   
   _call.setUseSOAPAction(true);

   _call.setSOAPActionURI("http://tempuri.org/Add";);
   
   _call.setTargetEndpointAddress( new java.net.URL(endpoint) );

   _call.setOperationStyle(Style.WRAPPED);
   
   _call.setOperationName(new QName("http://tempuri.org/","Add";));

   
_call.addParameter("A",org.apache.axis.Constants.XSD_FLOAT,Float.class,ParameterMode.IN);
   
_call.addParameter("B",org.apache.axis.Constants.XSD_FLOAT,Float.class,ParameterMode.IN);
   
   _call.setReturnClass(Float.class);
   
   System.out.println(" Response from add_bad is " + _call.invoke(new Object[] {new Float(12) , new Float(12)}));

   }
}






AW: Long time before Axis actually sends request

2005-06-06 Thread Ferruh Zamangoer
Sorry I have not see that you have solved the problem :=)

-Ursprüngliche Nachricht-
Von: Ferruh Zamangoer [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 20:03
An: axis-user@ws.apache.org
Betreff: AW: Long time before Axis actually sends request

I don't know why the request takes so long. But you can explicitly define
your own client-config.wsdd if your needed anything to configure, when you
have no own client-config.wsdd the default client-config.wsdd in the
axis.jar is used. My idea for you is to include log4j to see where the
startup hangs?

Regards
Ferruh 

-Ursprüngliche Nachricht-
Von: Marcus Andersson [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 18:25
An: axis-user@ws.apache.org
Betreff: Long time before Axis actually sends request

When I invoke a service method on a client, generated with WSDL2Java, it
takes about 5 seconds until Axis actually sends the request. I have checked
using a packet sniffer on the ports where the request goes.

Why is this? What have I done wrong? I have no client-config.wsdd. Is it
because of this?

I have tested Axis 1.1 with JDK1.4.2 and also tested with Axis 1.2 and Java5
(both times on WinXP Pro SP2). Same results. 

Please tell me if you need more information.

Regards,

/Marcus

-- 
Marcus Andersson
Dreampark AB 
Direct: +46 11 26 42 20
Mobile: +46 734 225 295




AW: One Way Method for Web Service Axis

2005-06-06 Thread Ferruh Zamangoer
If your client not need the document then write the method see below. Then
you have a one-way message.
 
public void echoDocument(Document doc) throws RemoteException {
System.out.println("EchoDocument");
return doc;
}

-Ursprüngliche Nachricht-
Von: Alberto De Stasi [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 18:34
An: axis-user@ws.apache.org
Betreff: One Way Method for Web Service Axis

Hi all, I have this problem;

I publishing a web server and a client that they use a call with OneWay 
operation (without return response to client).
So, my client is:

…
call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(endPointURLString));
call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});

(I use a call.invokeOneWay(…) method to call my service)

Then my web service is:

public Document echoDocument(Document doc) throws RemoteException {
System.out.println("EchoDocument");
return doc;
}

And I don’t sure this my service is right! How to make this service?
The wsdd file of axis is:
 provider="java:MSG" style="document" use="literal"

Then I use a TCP Monitor and I see both request and response, and I think 
that my problem is service (echoDocument).

The case without OneWay is work and I use a call.invoke (for client java) 
and a service is echoDocument

I want to use a OneWay and I see into TCP Monitor only request (client to 
service) without response (service to client)!

Thanks

_
250MB per la tua casella di posta http://www.msn.it/hotmail/minisite_10



Re: import schema to wsdl

2005-06-06 Thread Anne Thomas Manes
James,

If you want an interface that accepts parameters rather than an
object, then you must define your WSDL so that it matches the
"wrapped" convention. What that means is that your input message
element name must be identical to your operation name. Currently your
input message element name is bookFlightsRequest and your operation
name is bookFlights. If you fix it so that they are the same, it
should give you what you want.

Anne

On 6/6/05, Jeff <[EMAIL PROTECTED]> wrote:
> In general, I wouldn't let Axis provide a WSDL file. Tell it to use your
> WSDL file by adding a  element to the WSDD file before you deploy
> so you wind up with something like:
> 
>  xmlns="http://xml.apache.org/axis/wsdd/";
> xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> 
>   /MyService.wsdl
> 
>   http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort
> 
> 
> Jeff
> 
> 
> 
> - Original Message -
> From: "James Taylor" <[EMAIL PROTECTED]>
> To: 
> Sent: Monday, June 06, 2005 5:02 AM
> Subject: Re: import schema to wsdl
> 
> 
> Thanks for your help jeff. The main problem was the conflicting target
> namespaces I was trying to import into my wsdl. I've gotten the wsdl2java
> tool
> to work fine now. Just a question on what will when the service gets
> deployed
> to axis. I presume axis will make a different wsdl then the one I gave to
> the
> tool as it has defined a method signature for the portType as
>  public java.lang.Object bookFlights(java.lang.Object parameters) throws
> java.rmi.RemoteException; would any one mind commenting on this as I defined
> the method signature in the wsdl more specific then this... I know that I
> defined a custom collection bean that is of type object - I presume I'll
> cast
> the parameters to get at it.
> Regards,
> James.
> 
> My wsdl and external schema...
>targetNamespace="http://ie/tcd/taylorjw/flightbooking/wsdl";
>   xmlns="http://schemas.xmlsoap.org/wsdl/";
>   xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
>   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>   xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >
> 
> 
>  xmlns:xsd = "http://www.w3.org/2001/XMLSchema";
> elementFormDefault = "qualified"
> targetNamespace = "http://ie.tcd/taylorjw/flightbooking";>
> http://ie.tcd/taylorjw/flightbooking";
> schemaLocation="BookFlights.xsd"/>
> http://www.w3.org/2001/XMLSchema"; />
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  transport="http://schemas.xmlsoap.org/soap/http"; />
> 
>  
>  
>   
>  
>  
>   
>  
> 
>   
> 
>   
> binding="tns:BookFlightsSOAPBinding">
>  location="http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
>
>   
> 
> 
> 
> 
> 
> 
> 
> http://www.w3.org/2001/XMLSchema";
> targetNamespace = "http://ie.tcd/taylorjw/flightbooking";
> xmlns:fb="http://ie.tcd/taylorjw/flightbooking";>
> 
> 
> 
> 
>  maxOccurs="unbounded"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>


AW: Long time before Axis actually sends request

2005-06-06 Thread Ferruh Zamangoer
I don't know why the request takes so long. But you can explicitly define
your own client-config.wsdd if your needed anything to configure, when you
have no own client-config.wsdd the default client-config.wsdd in the
axis.jar is used. My idea for you is to include log4j to see where the
startup hangs?

Regards
Ferruh 

-Ursprüngliche Nachricht-
Von: Marcus Andersson [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 18:25
An: axis-user@ws.apache.org
Betreff: Long time before Axis actually sends request

When I invoke a service method on a client, generated with WSDL2Java, it
takes about 5 seconds until Axis actually sends the request. I have checked
using a packet sniffer on the ports where the request goes.

Why is this? What have I done wrong? I have no client-config.wsdd. Is it
because of this?

I have tested Axis 1.1 with JDK1.4.2 and also tested with Axis 1.2 and Java5
(both times on WinXP Pro SP2). Same results. 

Please tell me if you need more information.

Regards,

/Marcus

-- 
Marcus Andersson
Dreampark AB 
Direct: +46 11 26 42 20
Mobile: +46 734 225 295




Re: One Way Method for Web Service Axis

2005-06-06 Thread Anne Thomas Manes
But your service returns a Document. For a one-way message exchange,
the service should not produce a return value.

anne

On 6/6/05, Alberto De Stasi <[EMAIL PROTECTED]> wrote:
> Hi all, I have this problem;
> 
> I publishing a web server and a client that they use a call with OneWay
> operation (without return response to client).
> So, my client is:
> 
> …
> call = (Call) service.createCall();
> call.setTargetEndpointAddress(new URL(endPointURLString));
> call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});
> 
> (I use a call.invokeOneWay(…) method to call my service)
> 
> Then my web service is:
> 
> public Document echoDocument(Document doc) throws RemoteException {
> System.out.println("EchoDocument");
> return doc;
> }
> 
> And I don't sure this my service is right! How to make this service?
> The wsdd file of axis is:
>  provider="java:MSG" style="document" use="literal"
> 
> Then I use a TCP Monitor and I see both request and response, and I think
> that my problem is service (echoDocument).
> 
> The case without OneWay is work and I use a call.invoke (for client java)
> and a service is echoDocument
> 
> I want to use a OneWay and I see into TCP Monitor only request (client to
> service) without response (service to client)!
> 
> Thanks
> 
> _
> 250MB per la tua casella di posta http://www.msn.it/hotmail/minisite_10
> 
>


RE:[SOLVED] Long time before Axis actually sends request

2005-06-06 Thread Marcus Andersson
Okay, problem solved.

After some debugging I found that all time spent was in the creation of
network sockets. Sniffed the traffic some more and talked to the sys admin
and, voila, problem solved.

Sorry to have bothered you.

/Marcus 

-Original Message-
From: Marcus Andersson [mailto:[EMAIL PROTECTED] 
Sent: den 6 juni 2005 18:25
To: axis-user@ws.apache.org
Subject: Long time before Axis actually sends request

When I invoke a service method on a client, generated with WSDL2Java, it
takes about 5 seconds until Axis actually sends the request. I have checked
using a packet sniffer on the ports where the request goes.

Why is this? What have I done wrong? I have no client-config.wsdd. Is it
because of this?

I have tested Axis 1.1 with JDK1.4.2 and also tested with Axis 1.2 and Java5
(both times on WinXP Pro SP2). Same results. 

Please tell me if you need more information.

Regards,

/Marcus

--
Marcus Andersson
Dreampark AB 
Direct: +46 11 26 42 20
Mobile: +46 734 225 295






One Way Method for Web Service Axis

2005-06-06 Thread Alberto De Stasi

Hi all, I have this problem;

I publishing a web server and a client that they use a call with OneWay 
operation (without return response to client).

So, my client is:

…
call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(endPointURLString));
call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});

(I use a call.invokeOneWay(…) method to call my service)

Then my web service is:

public Document echoDocument(Document doc) throws RemoteException {
   System.out.println("EchoDocument");
   return doc;
}

And I don’t sure this my service is right! How to make this service?
The wsdd file of axis is:
provider="java:MSG" style="document" use="literal"

Then I use a TCP Monitor and I see both request and response, and I think 
that my problem is service (echoDocument).


The case without OneWay is work and I use a call.invoke (for client java) 
and a service is echoDocument


I want to use a OneWay and I see into TCP Monitor only request (client to 
service) without response (service to client)!


Thanks

_
250MB per la tua casella di posta http://www.msn.it/hotmail/minisite_10



RE: Calling Axis WebServices from C and .NET

2005-06-06 Thread John, Anil
Just to add to Anne's comment RE: .NET

If you are going to be exposing your web service for consumption by
varied clients, it may be worthwhile to consider the WSDL/Schema first
approach to implementing your web service and client piece.

In short:
- Define the messages that are going to be exchanged between the client
the service in a message schema (XSD file)
- Generate a WS-I compliant WSDL from the message Schema
- On the Service side use WSDL2Java to create your service stub and do
the implementation.
- On the client side, in addition to what Anne mentioned, another option
is to use the free WSCF tool that will generate the client proxies in
.NET from the schema and the WSDL.
You can find it @
http://www.thinktecture.com/Resources/Software/WSContractFirst/default.h
tml

One of the added benefits with this tool is that you have the ability to
automate the creation of the WSDL from the Message Schema using this
tool. The generated WSDL is WS-I BP 1.1 compliant.  Hand
creating/editing WSDL is not for the faint of heart :-)

A drawback is that the GUI version of the tool is a VS.NET add-in, which
means that it needs to be installed under Visual Studio.NET. But there
is also a command line version of the tool available.

This BTW, does NOT guarantee InterOp, it just improves your chance of
success! In particular, the things to watch out for would be the lack of
schema artifact support in the tools that are doing the Schema-to-Code
Mapping e.g. Lack of support for the  artifact under JAX-RPC or
Lack of support for Substitution groups under .NET.  You can maximize
your chance of a successful InterOp by focusing keeping things simple.

Regards,

- Anil


-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 04, 2005 5:56 PM
To: axis-user@ws.apache.org
Subject: Re: Calling Axis WebServices from C and .NET

When consuming a web service from .NET, you should use the .NET
WebReference client capability. (Simply add a WebReference to your
client application.) It's not good idea to use an unmanaged code
implementation, such as Axis C++.

For C/C++ applications on Linux, you can use Axis C++ or gSOAP
(http://www.cs.fsu.edu/~engelen/soap.html) or a commerical
implementation such as Systinet Server for C++
(http://www.systinet.com/products/ssc/overview).

For old ASP apps, if they are written in VB6, I suggest that you use
PocketSOAP (http://www.pocketsoap.com). If these apps are written in
C/C++ then you could use either PocketSOAP or any of the three C/C++
tools.

Anne

On 6/4/05, Leslie Tighe <[EMAIL PROTECTED]> wrote:
> Hello,
>   
> I have a set of java components in a J2EE app that I need to expose as

> a webservice.  I was planning on using Axis 1.2 for this. However, the

> client layer can be quite varied - C application on Linux, .NET 
> applications and old ASP apps.  Can any suggest how to best approach 
> the client part of this and what tools should I be using?  I am 
> assuming that for the .NET app, I can consume the J2EE services using 
> the C++ version of Axis, but I am not sure about the others.
>   
> Thanks in advance for your help. 
>   
> Regards
> Leslie
> 
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com


Long time before Axis actually sends request

2005-06-06 Thread Marcus Andersson
When I invoke a service method on a client, generated with WSDL2Java, it
takes about 5 seconds until Axis actually sends the request. I have checked
using a packet sniffer on the ports where the request goes.

Why is this? What have I done wrong? I have no client-config.wsdd. Is it
because of this?

I have tested Axis 1.1 with JDK1.4.2 and also tested with Axis 1.2 and Java5
(both times on WinXP Pro SP2). Same results. 

Please tell me if you need more information.

Regards,

/Marcus

-- 
Marcus Andersson
Dreampark AB 
Direct: +46 11 26 42 20
Mobile: +46 734 225 295




Simple type confusion

2005-06-06 Thread Kador, Daniel
This may not be suited for this list.  If this is the case, I apologize
for cluttering up your inboxes.

I'm having a problem getting Axis to deploy properly with a WSDL that
uses a schema in an external file.  Here is the type called "Purpose"'s
definition in the schema:



5.1.41










The problem lies in the "description" attribute.  It's of type
"descriptionType".  Here is "descriptionType"'s declaration:



5.1.5
restricted to
xs:string




When I use this, after I deploy my WSDL normally, I try to view the WSDL
through my web browser.  This is the error I get:

AXIS error

Sorry, something seems to have gone wrong... here are the details:

Fault - Bean attribute description is of type
org.apache.axis.types.NormalizedString, which is not a  simple type

AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
 faultSubcode: 
 faultString: Bean attribute description is of type
org.apache.axis.types.NormalizedString, which is
not a simple type
 faultActor: 
 faultNode: 
 faultDetail: 
{http://xml.apache.org/axis/}hostname:ORLIWG2H5Y61

This didn't make sense to me at first, because xs:normalizedString IS of
simpleType (at least according to the O'Reilly reference that I use).  I
can solve this problem in one of two ways.  I can change the attribute
type of "description" from "descriptionType" to "xs:normalizedString".
Or, I can change the restriction base of "descriptionType" from
"xs:normalizedString" to "xs:string".

The problem is, I don't want to have to change my schema, because it
corresponds to industry standards as it is.  Can anybody see a problem
that I'm missing?  I can provide the WSDL/schema if requested.

Thanks,
Dan Kador


AW: AW: One Way Method for Web Service Axis

2005-06-06 Thread Ferruh Zamangoer
Have you try the below code lines what happens? Is there any Exception?
What I have not understand is do you need the Document on the client side?



-Ursprüngliche Nachricht-
Von: Alberto De Stasi [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 17:56
An: axis-user@ws.apache.org
Betreff: RE: AW: One Way Method for Web Service Axis

Thanks for your time,
but I have this client java:

…
call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(endPointURLString));
call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});

while my web service is:

public Document echoDocument(Document doc) throws RemoteException {
System.out.println("EchoDocument");
return doc;
}

with your wsdd as

provider="java:MSG" style="document" use="literal"

I want use a method OneWay and I don’t understand if my method echoDocument 
must be void?
How must write my web service for type OneWay?

Thanks Pasquy

>From: "Ferruh Zamangoer" <[EMAIL PROTECTED]>
>Reply-To: axis-user@ws.apache.org
>To: 
>Subject: AW: One Way Method for Web Service Axis
>Date: Mon, 6 Jun 2005 17:35:08 +0200
>
>You can use void, what I have see is in the interface Call you can use the
>method
>
>void   invokeOneWay(java.lang.Object[] params)
>   Invokes a remote method using the one-way interaction mode.
>
>For example:
>
>Service service = new Service();
>Call call   = (Call)service.createCall();
>call.invokeOneWay()
>
>Hope it helps.
>
>Regards
>Ferruh
>
>
>
>-Ursprüngliche Nachricht-
>Von: Alberto De Stasi [mailto:[EMAIL PROTECTED]
>Gesendet: Montag, 6. Juni 2005 17:27
>An: axis-user@ws.apache.org
>Betreff: One Way Method for Web Service Axis
>
>Hi all,
>I want for my web service a method that use a one way operation. How must 
>be
>
>this method? Method must be void?
>
>Can you help me?
>
>Thanks Pasquy.
>
>_
>Scarica gratuitamente MSN Toolbar! http://toolbar.msn.it/
>

_
Blocca le pop-up pubblicitarie con MSN Toolbar! http://toolbar.msn.it/



I want use a OneWay method with Axis

2005-06-06 Thread Alberto De Stasi

Hi all,

I have this client java:

…
call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(endPointURLString));
call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});

while my web service is:

public Document echoDocument(Document doc) throws RemoteException {
   System.out.println("EchoDocument");
   return doc;
}

with your wsdd as
provider="java:MSG" style="document" use="literal"

I want use a method OneWay and I don’t understand if my method echoDocument 
must be void?

How must write my web service for type OneWay?

Thanks Pasquy

_
Scopri il nuovo MSN Htomail - 10MB di allegati 
http://www.msn.it/hotmail/minisite_10




RE: AW: One Way Method for Web Service Axis

2005-06-06 Thread Alberto De Stasi

Thanks for your time,
but I have this client java:

…
call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(endPointURLString));
call.invokeOneWay(new SOAPBodyElement[] {new SOAPBodyElement(body)});

while my web service is:

public Document echoDocument(Document doc) throws RemoteException {
   System.out.println("EchoDocument");
   return doc;
}

with your wsdd as

provider="java:MSG" style="document" use="literal"

I want use a method OneWay and I don’t understand if my method echoDocument 
must be void?

How must write my web service for type OneWay?

Thanks Pasquy


From: "Ferruh Zamangoer" <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: 
Subject: AW: One Way Method for Web Service Axis
Date: Mon, 6 Jun 2005 17:35:08 +0200

You can use void, what I have see is in the interface Call you can use the
method

voidinvokeOneWay(java.lang.Object[] params)
  Invokes a remote method using the one-way interaction mode.

For example:

Service service = new Service();
Call call   = (Call)service.createCall();
call.invokeOneWay()

Hope it helps.

Regards
Ferruh



-Ursprüngliche Nachricht-
Von: Alberto De Stasi [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 6. Juni 2005 17:27
An: axis-user@ws.apache.org
Betreff: One Way Method for Web Service Axis

Hi all,
I want for my web service a method that use a one way operation. How must 
be


this method? Method must be void?

Can you help me?

Thanks Pasquy.

_
Scarica gratuitamente MSN Toolbar! http://toolbar.msn.it/



_
Blocca le pop-up pubblicitarie con MSN Toolbar! http://toolbar.msn.it/



AW: One Way Method for Web Service Axis

2005-06-06 Thread Ferruh Zamangoer
You can use void, what I have see is in the interface Call you can use the
method 

voidinvokeOneWay(java.lang.Object[] params)
  Invokes a remote method using the one-way interaction mode.

For example:

Service service = new Service();
Call call   = (Call)service.createCall();
call.invokeOneWay()

Hope it helps.

Regards
Ferruh

 

-Ursprüngliche Nachricht-
Von: Alberto De Stasi [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 17:27
An: axis-user@ws.apache.org
Betreff: One Way Method for Web Service Axis

Hi all,
I want for my web service a method that use a one way operation. How must be

this method? Method must be void?

Can you help me?

Thanks Pasquy.

_
Scarica gratuitamente MSN Toolbar! http://toolbar.msn.it/



Re: Response Header deserialization?

2005-06-06 Thread Silvester Pozarnik
Let me answer my own question. In order to deserialize the explicit
response headers which are defined in the WSDL of the service you grab
first the SOAP header element


  GepirParty value = binding.getOwnerOfGLN( go );
  SOAPHeaderElement she = binding.getResponseHeader(ns,
"gepirResponseHeader");

And then deserialize it with:

GepirResponseHeader grh = (GepirResponseHeader)
she.getObjectValue(GepirResponseHeader.class);

The GepirResponseHeader class is emitted by WSDL2Java.

I found the answer in
http://wiki.apache.org/ws/FrontPage/Axis/WSDLJavaHeaderServer . This
should be anyway better documented.

BR
Silvester


AW: Attachments

2005-06-06 Thread Ferruh Zamangoer
Hi,

the problem was that I have run the server, the client on the same machine.
My Laptop had not enough memory and I have tested with client and server on
different machines. We have successfully send over 1GB :=) it works. 

Here are the test code if anybody are interested.


Thanks for any help
Ferruh


 



-Ursprüngliche Nachricht-
Von: Mike Haller [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005 15:58
An: axis-user@ws.apache.org
Betreff: Re: Attachments

Afaik default heap size for Java applications is 64MB. If you need more 
memory, use "-Xmx256M" as arguments to the JVM to give the client 
application more memory.

Althouhg this does not solve the problem that the whole request is held 
in memory. Why?

Ferruh Zamangoer schrieb:
> I’am trying to send large attachement files with generated classes with 
> WSDL2Java. When I try to send a file with 4-6 MB it works. When I try to 
> send a file with 80MB I become on the client side a Exception in thread 
> "main" java.lang.OutOfMemoryError: Java heap space.


FileUploadServiceClient.java
Description: Binary data


FileUploadService.java
Description: Binary data


deploy_upload.wsdd
Description: Binary data


undeploy_upload.wsdd
Description: Binary data


One Way Method for Web Service Axis

2005-06-06 Thread Alberto De Stasi

Hi all,
I want for my web service a method that use a one way operation. How must be 
this method? Method must be void?


Can you help me?

Thanks Pasquy.

_
Scarica gratuitamente MSN Toolbar! http://toolbar.msn.it/



AW: Attachments

2005-06-06 Thread Ferruh Zamangoer








Hi,

 

the problem was
that I have run the server, the client on the same machine. My Laptop had not
enough memory and I have tested with client and server on different machines. We
have successfully send over 1GB :=) it works. Here are the test code if anybody
are interested.

 

 

Thanks

Ferruh

 

 

 

 









Von: Falk Sippach
[mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005
15:22
An: axis-user@ws.apache.org
Betreff: AW: Attachments



 

Hi,

 

Java limits the maximum heap size to 64
MByte. You have to call java with the argument -Xmx512m to extend heap size to
512 MByte for example.

 

Falk.

 







Von: Ferruh
Zamangoer [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 6. Juni 2005
15:14
An: axis-user@ws.apache.org
Betreff: Attachments

Hi,

 

I’am trying to send large attachement files with
generated classes with WSDL2Java. When I try to send a file
with 4-6 MB it works. When I try to send a file with 80MB I become on the
client side a Exception in thread
"main" java.lang.OutOfMemoryError: Java heap space. 

 

On the server side the following error occurs:

 

238363 [http-8080-Processor4] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  -
type:"application/octet-stream"

 238363 [http-8080-Processor4] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  -
recordlength:"1048576"

 255177 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 255318 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(empty00)

 255318 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 255368 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(empty00)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(toAxisFault00)

 255888 [http-8080-Processor4] DEBUG
org.apache.axis.enterprise  - Mapping Exception to AxisFault

 java.lang.RuntimeException:
java.net.SocketException: Connection resetAxisFault

 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString:
java.net.SocketException: Connection reset

 faultActor: 

 faultNode: 

 faultDetail: 

   
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Connection
reset

   
at java.net.SocketInputStream.read(SocketInputStream.java:168)

   
at
org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:747)

   
at
org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:777)

   
at
org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:225)

   
at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:248)

   
at
org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:129)

   
at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:712)

   
at org.apache.coyote.Request.doRead(Request.java:429)

   
at
org.apache.coyote.tomcat4.CoyoteInputStream.readBytes(CoyoteInputStream.java:153)

   
at org.apache.coyote.tomcat4.CoyoteInputStream.read(CoyoteInputStream.java:110)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:152)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:139)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readHeader(DimeDelimitedInputStream.java:318)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:243)

   
at org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)

   
at org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)

   
at
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)

   
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentByReference(AttachmentsImpl.java:315)

   
at
org.apache.axis.encoding.DeserializationContext.getObjectByRef(Dese

Re: Attachments

2005-06-06 Thread Mike Haller
Afaik default heap size for Java applications is 64MB. If you need more 
memory, use "-Xmx256M" as arguments to the JVM to give the client 
application more memory.


Althouhg this does not solve the problem that the whole request is held 
in memory. Why?


Ferruh Zamangoer schrieb:
I’am trying to send large attachement files with generated classes with 
WSDL2Java. When I try to send a file with 4-6 MB it works. When I try to 
send a file with 80MB I become on the client side a Exception in thread 
"main" java.lang.OutOfMemoryError: Java heap space.


Response Header deserialization?

2005-06-06 Thread Silvester Pozarnik








Is there any
magic in handling the response headers when using the WSDL2Java tool (axis
1.2)? 

 

Given the WSDL
definition (fragment):

...

 

 


   

    

    

   

 


 

 

 


   

    

    

    

   

  

 

...

  
     ...



 

  Get owner of a
GLN

  

  

 

...

 


 

 


  

   

   

  

  

   

   

  

 

...

 

The WSDL2Java
tool generates the client side RouterSoap_BindingStub as it should and there
are also gepirRequestHeader and gepirResponseHeader classes available. Great!
But my problem is that I can not find a way to automagically deserialize the
response header (gepirResponseHeader):

 

  RouterLocator
rl = new RouterLocator();

  rl.setEndpointAddress(
"routerSoap", setup.getSoapEndPointAddress() ); //
RouterSoap_BindingStub is generated by WSDL2Java

  RouterSoap_BindingStub
binding = (RouterSoap_BindingStub) rl.getrouterSoap();   

// initialize the
header

  GepirRequestHeader
hdrs = new GepirRequestHeader();

  hdrs.setCascade(
new Integer( 8 ) );

  hdrs.setRequesterGln(
setup.getLocalGLN() );

  binding.setHeader(
ns, "gepirRequestHeader", hdrs ); // pass the header

 

// create and
populate the input parameter

  GetOwnerOfGLN
go = new GetOwnerOfGLN();

  go.setVersion(
new BigDecimal( setup.getVersion() ) );

  go.setRequestedGln(
msgin.getVal() );

  try {

   GepirParty
value = binding.getOwnerOfGLN( go ); // invoke

 

  // is this
only way to access the headers?

   SOAPHeaderElement[]
hel = binding.getResponseHeaders();

   SOAPHeaderElement
she = binding.getResponseHeader(ns, "gepirResponseHeader");

 

// 

    gepirResponseHeader
grh = ???

 

 

What I’ve
got is the SOAPHeaderElement (a DOM Node object) containing the
 element,
but what I want is a deserialized java class gepirResponseHeader that WSDL2Java
has generated for me. The odd thing is that the input and output parameters as
well as request headers are automatically serialized/deserialized by generated
client stub, but with response header you have to write code that deal with XML
and DOM. Am I missing something?  

 

 

BTW., the content
of the response message is as follows:

 

 





   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance

   xmlns:xsd="http://www.w3.org/2001/XMLSchema">

 

 


   761000141

  
1

   0

  

 

 

  

   

   
708718177

   
MEANTIME RECORDS 

    NOBELSG
35

   
0268

    OSLO

   
NO

    


Karin Krog

 +4722446509


+4722436015

    

  


 


 



 

BR

Silvester Pozarnik

 

 

 

 








AW: Attachments

2005-06-06 Thread Falk Sippach



Hi,
 
Java limits the maximum heap size to 64 MByte. You have to 
call java with the argument -Xmx512m to extend heap size to 512 MByte for 
example.
 
Falk.


Von: Ferruh Zamangoer 
[mailto:[EMAIL PROTECTED] Gesendet: Montag, 6. Juni 2005 
15:14An: axis-user@ws.apache.orgBetreff: 
Attachments


Hi,
 
I’am trying to send large 
attachement files with generated classes with WSDL2Java. When I try to send a file with 4-6 
MB it works. When I try to send a file with 80MB I become on the client side a 
Exception in thread "main" 
java.lang.OutOfMemoryError: Java heap space. 

 
On the server side the following 
error occurs:
 
238363 [http-8080-Processor4] DEBUG 
org.apache.axis.attachments.DimeDelimitedInputStream  - 
type:"application/octet-stream"
 238363 [http-8080-Processor4] 
DEBUG org.apache.axis.attachments.DimeDelimitedInputStream  - 
recordlength:"1048576"
 255177 [http-8080-Processor4] 
DEBUG org.apache.axis.utils.NSStack  - NSPush 
(32)
 255318 [http-8080-Processor4] 
DEBUG org.apache.axis.i18n.ProjectResourceBundle  - 
org.apache.axis.i18n.resource::handleGetObject(empty00)
 255318 [http-8080-Processor4] 
DEBUG org.apache.axis.utils.NSStack  - NSPop 
(empty)
 255368 [http-8080-Processor4] 
DEBUG org.apache.axis.utils.NSStack  - NSPush 
(32)
 255838 [http-8080-Processor4] 
DEBUG org.apache.axis.i18n.ProjectResourceBundle  - 
org.apache.axis.i18n.resource::handleGetObject(empty00)
 255838 [http-8080-Processor4] 
DEBUG org.apache.axis.utils.NSStack  - NSPop 
(empty)
 255838 [http-8080-Processor4] 
DEBUG org.apache.axis.i18n.ProjectResourceBundle  - 
org.apache.axis.i18n.resource::handleGetObject(toAxisFault00)
 255888 [http-8080-Processor4] 
DEBUG org.apache.axis.enterprise  - Mapping Exception to 
AxisFault
 java.lang.RuntimeException: 
java.net.SocketException: Connection resetAxisFault
 faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 

 faultString: 
java.net.SocketException: Connection reset
 faultActor: 

 faultNode: 

 faultDetail: 

    
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Connection 
reset
    
at 
java.net.SocketInputStream.read(SocketInputStream.java:168)
    
at 
org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:747)
    
at 
org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:777)
    
at 
org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:225)
    
at 
org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:248)
    
at 
org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:129)
    
at 
org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:712)
    
at 
org.apache.coyote.Request.doRead(Request.java:429)
    
at 
org.apache.coyote.tomcat4.CoyoteInputStream.readBytes(CoyoteInputStream.java:153)
    
at 
org.apache.coyote.tomcat4.CoyoteInputStream.read(CoyoteInputStream.java:110)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:152)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:139)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream.readHeader(DimeDelimitedInputStream.java:318)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:243)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
    
at 
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
    
at 
org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)
    
at 
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
    
at 
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)
    
at 
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)
    
at 
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)
    
at 
org.apache.axis.attachments.AttachmentsImpl.getAttachmentByReference(AttachmentsImpl.java:315)
    
at 
org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:617)
    
at 
org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
    
at 
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
    
at 
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
    
at 
org.apache.axis.message.MessageElement.publishToHandler(MessageEleme

Re: document/literal wrapped... getting closer

2005-06-06 Thread Nathaniel A. Johnson
thanks anne!  i had a typo in my ant task and it must have defaulted
back to something i wasnt expecting.  its sending the right xml back as
a response now.  i'm getting a class cast without much to go on:

java.lang.ClassCastException
at $Proxy0.getMembers(Unknown Source)
at
edu.iu.uis.osg.client.GroupsClientImpl.getMembers(GroupsClientImpl.java:43)
at edu.iu.uis.osg.TestGroupsClient.main(TestGroupsClient.java:48)

i can call the rest of the methods (the ones with int return values)

also, when trying to use wsdl2java, i get this error:
[axis-wsdl2java] org.xml.sax.SAXException: Fatal Error:
URI=http://localhost:8080/osg-dev/services Line=2: Illegal character at
end of document, <.

i thought i saw a message about this earlier and i even tried the axix
1.2.1 code and get the same thing.  not sure if this is related to my
earlier problems, but will look into it

thanks for you help
nate

Anne Thomas Manes wrote:
> I see the problem. Your response is supposed to look like this:
> 
>  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="id-2183019">
> http://services.osg.uis.iu.edu/GroupsService";>
> 
> jhopf
> thrclark
> jitrue
> bmcgough
> xqi
> songupta
> rkirkend
> pmckown
> temay
> natjohns
> jthomas
> 
> 
> 
> but instead you have an extra  wrapper around your array:
> 
>  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="id-2183019">
> http://services.osg.uis.iu.edu/GroupsService";>
>  
> jhopf
> thrclark
> jitrue
> bmcgough
> xqi
> songupta
> rkirkend
> pmckown
> temay
> natjohns
> jthomas
> 
> 
> 
> 
> Please log a bug report.
> 
> Anne
> 
> On 6/5/05, Nathaniel A. Johnson <[EMAIL PROTECTED]> wrote:
> 
>>hello everyone,
>>
>>this is a follow-up on the doc/literal posting/conversation with anne.
>>my client is now sending requests, and receiving responses from the
>>server.  the soap messages look good, but the client can't seem to
>>deserialize the responses from the server.  i also regenerated the wsdl
>>with pretty parameter names (to do that with the ant task, you just have
>>to supply the optional parameter implClass).  i have attached a file
>>that has a request, one with a response, and my pretty wsdl.
>>
>>if anyone has any idea for me, as to why doc/literal wrapped gives
>>deserialization errors at the client (not server), and rpc/encoded works
>>perfectly, i'd love to be enlightened.
>>
>>thanks!
>>nate
>>
>>here is the exception:
>>
>>(core.CollectionFactory  59  ) Using JDK 1.4 collections
>>(crypto.CryptoFactory113 ) Using Crypto Engine
>>[org.apache.ws.security.components.crypto.Merlin]
>>(crypto.CryptoFactory113 ) Using Crypto Engine
>>[org.apache.ws.security.components.crypto.Merlin]
>>(signature.Reference ?   ) Verification successful for
>>URI "#id-2183019"
>>(client.Call 2450) Exception:
>>org.xml.sax.SAXException: SimpleDeserializer encountered a child
>>element, which is NOT expected, in something it was trying to deserialize.
>>at
>>org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)
>>at
>>org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
>>at
>>org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
>>at
>>org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)
>>at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
>>at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
>>at org.apache.axis.client.Call.invoke(Call.java:2448)
>>at org.apache.axis.client.Call.invoke(Call.java:2347)
>>at org.apache.axis.client.Call.invoke(Call.java:1804)
>>at
>>org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.performJaxRpcCall(JaxRpcPortClientInterceptor.java:492)
>>at
>>org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.invoke(JaxRpcPortClientInterceptor.java:451)
>>at
>>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
>>at
>>org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:174)
>>at $Proxy0.getMembers(Unknown Source)
>>at
>>edu.iu.uis.osg.client.GroupsClientImpl.getMembers(GroupsClientImpl.java:43)
>>at edu.iu.uis.osg.TestGroupsClient.main(TestGroupsClient.java:46)
>>org.springframework.remoting.RemoteAccessException: Cannot access remote
>>service
>>[{http://services.osg.uis.iu.edu/GroupsService}GroupsServiceService];
>>nested exception is org.apache.axis.AxisFault: ; nested exception is:
>>org.xml.sax.SAXException: SimpleDeserializer encountered a child
>>element, which is NOT expected, in something it was trying to deserialize.
>>AxisFault
>> faultCode: {http://schema

Attachments

2005-06-06 Thread Ferruh Zamangoer








Hi,

 

I’am trying to send large attachement files with
generated classes with WSDL2Java. When I try to send a file
with 4-6 MB it works. When I try to send a file with 80MB I become on the
client side a Exception in thread
"main" java.lang.OutOfMemoryError: Java heap space. 

 

On the server side the following error occurs:

 

238363 [http-8080-Processor4] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  -
type:"application/octet-stream"

 238363 [http-8080-Processor4] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  - recordlength:"1048576"

 255177 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 255318 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(empty00)

 255318 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 255368 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(empty00)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 255838 [http-8080-Processor4] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(toAxisFault00)

 255888 [http-8080-Processor4] DEBUG
org.apache.axis.enterprise  - Mapping Exception to AxisFault

 java.lang.RuntimeException:
java.net.SocketException: Connection resetAxisFault

 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString:
java.net.SocketException: Connection reset

 faultActor: 

 faultNode: 

 faultDetail: 

    {http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connection reset

    at
java.net.SocketInputStream.read(SocketInputStream.java:168)

    at
org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:747)

    at
org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:777)

    at
org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:225)

    at
org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:248)

    at
org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:129)

    at
org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:712)

    at
org.apache.coyote.Request.doRead(Request.java:429)

    at
org.apache.coyote.tomcat4.CoyoteInputStream.readBytes(CoyoteInputStream.java:153)

    at
org.apache.coyote.tomcat4.CoyoteInputStream.read(CoyoteInputStream.java:110)

    at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:152)

    at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:139)

    at
org.apache.axis.attachments.DimeDelimitedInputStream.readHeader(DimeDelimitedInputStream.java:318)

    at
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:243)

    at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)

    at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)

    at
org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)

    at
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)

    at
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)

    at
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)

    at
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)

    at
org.apache.axis.attachments.AttachmentsImpl.getAttachmentByReference(AttachmentsImpl.java:315)

    at
org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:617)

    at
org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)

    at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)

    at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)

    at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140)

    at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)

    at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)

    at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)

    at
org.apache.axis.providers.java.JavaProv

AW: Connection reset?

2005-06-06 Thread Ferruh Zamangoer








Hi,

 

I have see in my locator
class that the endpointadress port was changed by the TCPMon. That was the
problem :=) sorry.

 

Regards

Ferruh

 









Von:
Ferruh Zamangoer [mailto:[EMAIL PROTECTED]de] 
Gesendet: Montag, 6. Juni 2005
13:29
An: axis-user@ws.apache.org
Betreff: Connection reset?



 

Hi,

 

I used a service to upload large files and it works
fine. Then I used the TCPMonitor to see what which messages are sent between
server and client. After using TCPMonitor my example does not work? But
I’am not sure if the TCPMon was the problem. I see in the exception a
Connection reset. Can anybody tell me what is happens and why the connection is
reset? Is it possible that a timeout was exceeded?

 

 

98142 [http-8080-Processor5] DEBUG org.apache.axis.attachments.DimeDelimitedInputStream 
- id:"527CE885C4ECF75832DF6F4203867040"

 98142 [http-8080-Processor5] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  -
type:"application/octet-stream"

 98142 [http-8080-Processor5] DEBUG
org.apache.axis.attachments.DimeDelimitedInputStream  -
recordlength:"1048576"

 109458 [http-8080-Processor5] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 109458 [http-8080-Processor5] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  - org.apache.axis.i18n.resource::handleGetObject(empty00)

 109468 [http-8080-Processor5] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 109468 [http-8080-Processor5] DEBUG
org.apache.axis.utils.NSStack  - NSPush (32)

 109478 [http-8080-Processor5] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  -
org.apache.axis.i18n.resource::handleGetObject(empty00)

 109488 [http-8080-Processor5] DEBUG
org.apache.axis.utils.NSStack  - NSPop (empty)

 109498 [http-8080-Processor5] DEBUG
org.apache.axis.i18n.ProjectResourceBundle  - org.apache.axis.i18n.resource::handleGetObject(toAxisFault00)

 109508 [http-8080-Processor5] DEBUG
org.apache.axis.enterprise  - Mapping Exception to AxisFault

 java.lang.RuntimeException:
java.net.SocketException: Connection resetAxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString:
java.net.SocketException: Connection reset

 faultActor: 

 faultNode: 

 faultDetail: 

   
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Connection reset

   
at java.net.SocketInputStream.read(SocketInputStream.java:168)

   
at
org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:747)

   
at org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(InternalInputBuffer.java:777)

   
at
org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:225)

   
at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:248)

   
at
org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:129)

   
at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:712)

   
at org.apache.coyote.Request.doRead(Request.java:429)

   
at
org.apache.coyote.tomcat4.CoyoteInputStream.readBytes(CoyoteInputStream.java:153)

   
at org.apache.coyote.tomcat4.CoyoteInputStream.read(CoyoteInputStream.java:110)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:152)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readFromStream(DimeDelimitedInputStream.java:139)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.readHeader(DimeDelimitedInputStream.java:318)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:243)

   
at org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)

   
at
org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)

   
at org.apache.axis.attachments.ManagedMemoryDataSource.(ManagedMemoryDataSource.java:146)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.readAll(MultiPartDimeInputStream.java:100)

   
at
org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(MultiPartDimeInputStream.java:108)

   
at
org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(AttachmentsImpl.java:156)

   
at org.apache.axis.attachments.AttachmentsImpl.getAttachmentByReference(AttachmentsImpl.java:315)

   
at
org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:617)

   
at org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)

   
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationConte

Re: Cannot install Axis - Pls. help.

2005-06-06 Thread Jeff



I didn't precisely say "global problem with the class path" and I 
sort of guessed that you would be a Java developer. I was simply bringing your 
attention to the fact that countless developer-years have been lost due to 
people dealing with class path problems. Your current problem seems to be such a 
problem.
 
By moving JAR files from  C:\Apache\Tomcat4\webapps\axis\WEB-INF\lib 
to  C:\Apache\Tomcat4\common\lib you should be giving them greater exposure 
so more things should work. In reality you might get versioning problems between 
different web applications but not under a simple 
configuration.
 
Did you overwrite any JAR files when you moved to 
JAR files to C:\Apache\Tomcat4\webapps\axis\WEB-INF\lib ?
 
 
Jeff
 
 

  - Original Message - 
  From: 
  Gila 
  Cohen 
  To: axis-user@ws.apache.org 
  Sent: Monday, June 06, 2005 5:54 AM
  Subject: Re: Cannot install Axis - Pls. 
  help.
  Jeff, Thanks for your reply. What do you mean by 
  saying there is a global problem with the class path? I am a java programmer, 
  can you please give me some more information? looks like I have to know this 
  stuffI tried your advice - and it got worse: now I cannot run any 
  other web application! Could that be the logging jars from axis are disturbing 
  the logging jars of my existing applications? Here is what I get when 
  I try to open an existing web app: 
  Bad GatewayThe proxy server received an invalid response from an 
  upstream server.
  
  Apache/2.0.48 (Win32) mod_jk2/2.0.4 Server at gulistan.bot.huji.ac.il Port 80 
  And in the error log of tomcat:Created catalinaLoader in: 
  C:\Apache\Tomcat4\server\libjava.lang.reflect.InvocationTargetExceptionat 
  sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
  Method)at 
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)at 
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at 
  java.lang.reflect.Method.invoke(Method.java:324)at 
  org.apache.catalina.startup.BootstrapService.init(BootstrapService.java:231)at 
  org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:297)Caused 
  by: java.lang.NoClassDefFoundError: 
  org/apache/log4j/Layoutat 
  org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:153)at 
  org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285)at 
  org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)at 
  org.apache.commons.digester.Digester.(Digester.java:346)at 
  org.apache.catalina.startup.Catalina.createStartDigester(Catalina.java:280)at 
  org.apache.catalina.startup.CatalinaService.load(CatalinaService.java:183)at 
  org.apache.catalina.startup.CatalinaService.load(CatalinaService.java:258)... 
  6 moreThat is - nothing else in the logsThanks again 
  for your help,GCAt 20:28 05/06/2005, you wrote:
  Java is broken! The fact of the 
matter is that the one and only show-stopperproblem with Java can be 
summed up in one term: 'class path'. It's somethingthat some Java 
developers pretend doesn't exist and novices think they 
havelicked...until they start to write more code! Unfortunately, the Sun 
folksthink that trivia like for-each is more important than fixing the 
class pathproblem. Admittedly, it is a big problem and I suspect that 
the solution isgoing to come from someone outside of Sun setting aside a 
good deal of timeto figure it out but until that happens, we will have 
to put up with thissort of insane solution...Stop Tomcat. 
Move  log4j-1.2.8.jar  to  /common/lib  
Start Tomcatand test. If you still have a problem, then repeat for 
commons-discovery.jarand commons-logging.jar, together. If you still 
have a problem, then repeatfor other JARs in  
/webapps/axis/WEB-INF/libJeff- 
Original Message - From: "Gila Cohen" 
<[EMAIL PROTECTED]>To: Sent: 
Sunday, June 05, 2005 7:02 AMSubject: Re: Cannot install Axis - Pls. 
help.>>> Hi,>> OK, I am sending 
the directory structure, and as you can see, it has all> the files. I 
tried to install axis on another machine just the way I do it> on my 
machine, and it works there! I am trying to find what is the> 
difference between the 2 machines. Following some of the emails in 
the> site, I thought the mcaffe antivirus might be disturbing - so 
I> un-installed on the failing machine it and tried to validate the 
axis> installation without it - with no success.> Other 
reasons I can think of:> 1) different versions of Java:  on the 
successful machine I have java 1.5> installed, including java web 
service developer pack 1.5. On the failing> machine I have java 
1.4.0> 2) some other sw is disturbing.>> well, these 
options are more difficult to check... but I'll get to them in> a

Complex type with array

2005-06-06 Thread Falk Sippach
Hi,

I'm using Axis 1.2 RC2. My webservice return a complex type with an
array inside.

The complex type looks like this:

object
{
int id;
String name;
String uuid;
Attribute [] attributes;
ObjectType objtype;
}

Attribute and ObjectType are complex types (Java beans)as well.

My client (C++) is using Axis C++ 1.5 final, so I had to turn off the
multref support on server side. The service response looks like this:


  
  ..[10 times ]
  
  1
  name
  ..
  124353-1234-...


Axis C++ can't deserialize the return message. First it's looking for
the id-Element, but it finds only -elements. Is this
Return-message correct? Shouldn't be there something like a wrapper
around the ten attributes-elements, which also describes the number of
attributes fields (of the array)?

I attach the wsdl-file and the response message to this mail.

Thanks for your help.

Falk.


Service.wsdl
Description: Service.wsdl
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/";>11http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp1http://schemas.xmlsoap.org/soap/encoding/"/>1http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp1http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 111http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp2http://schemas.xmlsoap.org/soap/encoding/"/>2http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp2http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 211http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp3http://schemas.xmlsoap.org/soap/encoding/"/>3http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp3http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 311http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp4http://schemas.xmlsoap.org/soap/encoding/"/>4http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp4http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 411http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp5http://schemas.xmlsoap.org/soap/encoding/"/>5http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp5http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 511http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp6http://schemas.xmlsoap.org/soap/encoding/"/>6http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp6http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 611http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp7http://schemas.xmlsoap.org/soap/encoding/"/>7http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp7http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 711http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp8http://schemas.xmlsoap.org/soap/encoding/"/>8http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp8http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 811http://schemas.xmlsoap.org/soap/encoding/";>Beschreibung zu Attributtyp9http://schemas.xmlsoap.org/soap/encoding/"/>9http://schemas.xmlsoap.org/soap/encoding/";>Attributtyp9http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/"/>http://schemas.xmlsoap.org/soap/encoding/";>uuid-123123-123123-123http://schemas.xmlsoap.org/soap/encoding/";>Wert 911http://schemas.xmlsoap.org/soap/encoding/";>Beschrei

Re: Cannot install Axis - Pls. help.

2005-06-06 Thread Gila Cohen



Jeff, 
Thanks for your reply. What do you mean by saying there is a global
problem with the class path? I am a java programmer, can you please give
me some more information? looks like I have to know this stuff
I tried your advice - and it got worse: now I cannot run any other web
application! Could that be the logging jars from axis are disturbing the
logging jars of my existing applications? 
Here is what I get when I try to open an existing web app: 
Bad GatewayThe proxy server received an invalid response from an
upstream server.

Apache/2.0.48 (Win32) mod_jk2/2.0.4 Server at gulistan.bot.huji.ac.il
Port 80 
And in the error log of tomcat:

Created catalinaLoader in: C:\Apache\Tomcat4\server\lib
java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.catalina.startup.BootstrapService.init(BootstrapService.java:231)
at
org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:297)
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Layout
at
org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:153)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:285)
at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at
org.apache.commons.digester.Digester.(Digester.java:346)
at
org.apache.catalina.startup.Catalina.createStartDigester(Catalina.java:280)
at
org.apache.catalina.startup.CatalinaService.load(CatalinaService.java:183)
at
org.apache.catalina.startup.CatalinaService.load(CatalinaService.java:258)
... 6
more

That is - nothing else in the logs
Thanks again for your help,
GC

At 20:28 05/06/2005, you wrote:
Java is broken! The fact of the
matter is that the one and only show-stopper
problem with Java can be summed up in one term: 'class path'. It's
something
that some Java developers pretend doesn't exist and novices think they
have
licked...until they start to write more code! Unfortunately, the Sun
folks
think that trivia like for-each is more important than fixing the class
path
problem. Admittedly, it is a big problem and I suspect that the solution
is
going to come from someone outside of Sun setting aside a good deal of
time
to figure it out but until that happens, we will have to put up with
this
sort of insane solution...
Stop Tomcat. Move  log4j-1.2.8.jar  to 
/common/lib  Start Tomcat
and test. If you still have a problem, then repeat for
commons-discovery.jar
and commons-logging.jar, together. If you still have a problem, then
repeat
for other JARs in  /webapps/axis/WEB-INF/lib

Jeff

- Original Message - 
From: "Gila Cohen" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, June 05, 2005 7:02 AM
Subject: Re: Cannot install Axis - Pls. help.

>
>
> Hi,
>
> OK, I am sending the directory structure, and as you can see, it has
all
> the files. I tried to install axis on another machine just the way I
do it
> on my machine, and it works there! I am trying to find what is
the
> difference between the 2 machines. Following some of the emails in
the
> site, I thought the mcaffe antivirus might be disturbing - so 
I
> un-installed on the failing machine it and tried to validate the
axis
> installation without it - with no success.
> Other reasons I can think of:
> 1) different versions of Java:  on the successful machine I
have java 1.5
> installed, including java web service developer pack 1.5. On the
failing
> machine I have java 1.4.0
> 2) some other sw is disturbing.
>
> well, these options are more difficult to check... but I'll get to
them in
> a while.
>
> BTW, I get an error while I start tomcat - I am also sending the
error
from
> tomcat's log.
>
> Many thanks,
> GC
>
> Directory of C:\Apache\Tomcat4\webapps\axis\WEB-INF\lib
> 
>
> 06/05/2005  01:49p 
  .
> 06/05/2005  01:49p 
  
..
> 05/07/2005 
09:14p 
55,147 activation.jar
> 06/13/2003 
10:28a
385,010 axis-ant.jar
> 06/13/2003 
10:28a  
1,235,721 axis.jar
> 06/13/2003 
10:28a 
71,442 commons-discovery.jar
> 06/13/2003 
10:28a 
31,605 commons-logging.jar
> 06/05/2005 
01:49p  
0 dir.txt
> 06/13/2003 
10:28a 
35,759 jaxrpc.jar
> 06/13/2003 
10:28a
352,668 log4j-1.2.8.jar
> 06/13/2003 
10:28a 
18,501 saaj.jar
> 06/13/2003 
10:28a
113,853 wsdl4j.jar
>   
10 File(s)  2,299,706 bytes
>
2 Dir(s)  16,764,686,336 bytes free
>
>
> Error from tomcat log:
> =
>
>
> 2005-06-05 08:58:07 WebappLoader[/axis]: Deploying class
repositories t

"org.apache.axis.ConfigurationException" and everything works

2005-06-06 Thread gvl

Hello all,

Can someone help me out with this "problem"? 

I used WSDL2JAVA to generate classes to consume a web service. 

Allthough everything works fine, in the log following exception is thrown:
"org.apache.axis.ConfigurationException: No service named
SendReceiveSoapPort is available".
 

I tried to use the "search" function on the mailing list but with no
success...


Best regards / Vriendelijke groeten / Cordialement, 

 

Geert Van Landeghem

Java & iSeries400 consultant

 

foundation.be 

Mobile: 0477/75.95.33

Tel: 052/42.73.70

  www.foundation.be




Getting Errors during compilation of current CVS

2005-06-06 Thread Andreas Bohnert

hi,
I just get the current cvs and I'm not able to compile it.
What I'm doing wrong?

regards,
andreas


 [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/NodeImpl.java:45: 
org.apache.axis.message.NodeImpl is not abstract and does not override 
abstract method getUserData(java.lang.String) in org.w3c.dom.Node
   [javac] public class NodeImpl implements org.w3c.dom.Node, 
javax.xml.soap.Node,

   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/MessageElement.java:73: 
org.apache.axis.message.MessageElement is not abstract and does not 
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node
   [javac] public class MessageElement extends NodeImpl implements 
SOAPElement,

   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java:40: 
org.apache.axis.message.SOAPHeaderElement is not abstract and does not 
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node

   [javac] public class SOAPHeaderElement extends MessageElement
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/SOAPPart.java:89: 
org.apache.axis.SOAPPart is not abstract and does not override abstract 
method renameNode(org.w3c.dom.Node,java.lang.String,java.lang.String) in 
org.w3c.dom.Document
   [javac] public class SOAPPart extends javax.xml.soap.SOAPPart 
implements Part

   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPEnvelope.java:50: 
org.apache.axis.message.SOAPEnvelope is not abstract and does not 
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node

   [javac] public class SOAPEnvelope extends MessageElement
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPHeader.java:50: 
org.apache.axis.message.SOAPHeader is not abstract and does not override 
abstract method getUserData(java.lang.String) in org.w3c.dom.Node

   [javac] public class SOAPHeader extends MessageElement
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBody.java:46: 
org.apache.axis.message.SOAPBody is not abstract and does not override 
abstract method getUserData(java.lang.String) in org.w3c.dom.Node

   [javac] public class SOAPBody extends MessageElement
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/message/SOAPBodyElement.java:37: 
org.apache.axis.message.SOAPBodyElement is not abstract and does not 
override abstract method getUserData(java.lang.String) in org.w3c.dom.Node

   [javac] public class SOAPBodyElement extends MessageElement
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:82: 
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has 
been deprecated

   [javac] SSLContext context = getContext();
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:101: 
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has 
been deprecated

   [javac] SSLContext context =
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:102: 
warning: [deprecation] com.sun.net.ssl.SSLContext in com.sun.net.ssl has 
been deprecated

   [javac] com.sun.net.ssl.SSLContext.getInstance("SSL");// SSL
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:150: 
warning: [deprecation] com.sun.net.ssl.KeyManagerFactory in 
com.sun.net.ssl has been deprecated

   [javac] com.sun.net.ssl.KeyManagerFactory kmf =
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:151: 
warning: [deprecation] com.sun.net.ssl.KeyManagerFactory in 
com.sun.net.ssl has been deprecated

   [javac] com.sun.net.ssl.KeyManagerFactory.getInstance(algorithm);
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:156: 
warning: [deprecation] com.sun.net.ssl.TrustManager in com.sun.net.ssl 
has been deprecated

   [javac] com.sun.net.ssl.TrustManager[] tm = null;
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:159: 
warning: [deprecation] com.sun.net.ssl.TrustManagerFactory in 
com.sun.net.ssl has been deprecated

   [javac] com.sun.net.ssl.TrustManagerFactory tmf =
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:160: 
warning: [deprecation] com.sun.net.ssl.TrustManagerFactory in 
com.sun.net.ssl has been deprecated

   [javac] com.sun.net.ssl.TrustManagerFactory.getInstance("SunX509");
   [javac] ^
   [javac] 
/home/abo/workspace/ws-axis/java/src/org/apache/axis/components/net/SunJSSESocketFactory.java:168: 

Re: import schema to wsdl

2005-06-06 Thread Jeff
In general, I wouldn't let Axis provide a WSDL file. Tell it to use your
WSDL file by adding a  element to the WSDD file before you deploy
so you wind up with something like:

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

  /MyService.wsdl

  http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort


Jeff



- Original Message - 
From: "James Taylor" <[EMAIL PROTECTED]>
To: 
Sent: Monday, June 06, 2005 5:02 AM
Subject: Re: import schema to wsdl


Thanks for your help jeff. The main problem was the conflicting target
namespaces I was trying to import into my wsdl. I've gotten the wsdl2java
tool
to work fine now. Just a question on what will when the service gets
deployed
to axis. I presume axis will make a different wsdl then the one I gave to
the
tool as it has defined a method signature for the portType as
 public java.lang.Object bookFlights(java.lang.Object parameters) throws
java.rmi.RemoteException; would any one mind commenting on this as I defined
the method signature in the wsdl more specific then this... I know that I
defined a custom collection bean that is of type object - I presume I'll
cast
the parameters to get at it.
Regards,
James.

My wsdl and external schema...
http://ie/tcd/taylorjw/flightbooking/wsdl";
  xmlns="http://schemas.xmlsoap.org/wsdl/";
  xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
  xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >


http://www.w3.org/2001/XMLSchema";
elementFormDefault = "qualified"
targetNamespace = "http://ie.tcd/taylorjw/flightbooking";>
http://ie.tcd/taylorjw/flightbooking";
schemaLocation="BookFlights.xsd"/>
http://www.w3.org/2001/XMLSchema"; />




















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

 
 
  
 
 
  
 

  

  
   
http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
   
  







http://www.w3.org/2001/XMLSchema";
targetNamespace = "http://ie.tcd/taylorjw/flightbooking";
xmlns:fb="http://ie.tcd/taylorjw/flightbooking";>























































Re: import schema to wsdl

2005-06-06 Thread James Taylor
Thanks for your help jeff. The main problem was the conflicting target
namespaces I was trying to import into my wsdl. I've gotten the wsdl2java tool
to work fine now. Just a question on what will when the service gets deployed
to axis. I presume axis will make a different wsdl then the one I gave to the
tool as it has defined a method signature for the portType as
 public java.lang.Object bookFlights(java.lang.Object parameters) throws
java.rmi.RemoteException; would any one mind commenting on this as I defined
the method signature in the wsdl more specific then this... I know that I
defined a custom collection bean that is of type object - I presume I'll cast
the parameters to get at it.
Regards,
James.

My wsdl and external schema...
http://ie/tcd/taylorjw/flightbooking/wsdl";
  xmlns="http://schemas.xmlsoap.org/wsdl/";
  xmlns:tns="http://ie/tcd/taylorjw/flightbooking/wsdl";
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
  xmlns:types="http://ie.tcd/taylorjw/flightbooking"; >


http://www.w3.org/2001/XMLSchema";
elementFormDefault = "qualified"
targetNamespace = 
"http://ie.tcd/taylorjw/flightbooking";>
http://ie.tcd/taylorjw/flightbooking";
schemaLocation="BookFlights.xsd"/>
http://www.w3.org/2001/XMLSchema"; />




















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

 
 
  
 
 
  
 

  

  
   
http://localhost:9081/AxisWeb/services/BookFlightsSOAPPort"; />
   
  







http://www.w3.org/2001/XMLSchema";
targetNamespace = "http://ie.tcd/taylorjw/flightbooking";
xmlns:fb="http://ie.tcd/taylorjw/flightbooking";>






















































Re: Bug 1.2RC3->1.2: Using CommonsHttpClient fails

2005-06-06 Thread Andreas Bohnert

Hey Mike,

could you have a look at http://issues.apache.org/jira/browse/AXIS-2033.
Maybe you know how to do it?

regards,
andreas


Mike Moran wrote:

Andreas Bohnert wrote:


Yepp, I just did it.
But maybe it would be helpful to post your fix to the database as well?!
what do you think?


I've updated http://issues.apache.org/jira/browse/AXIS-2033 with the 
code which worked for me (just in case you missed a notification)