RE: Is it possible to have references to the same classes if I use document/literal wrapped
No, it does not, I have a similar architecture that just works fine
-Message d'origine-
De : Soti, Dheeraj [mailto:[EMAIL PROTECTED]
Envoyé : mardi 29 mars 2005 01:54
À : 'axis-user@ws.apache.org'
Objet : Is it possible to have references to the same classes if I use
document/literal wrapped
I have following kind of structure where this structure can be very deep. Can
this cause some issues?
public class Person {
String name;
Person friend1, friend2;
}
Thanks
Dheeraj Soti
RE: Problem deserializing arrays of complex types
Hi, I have found the solution, I mail it to be in the archive. Apparently AXIS does not like the attributes in the LinkType type. Setting elements instead of attributes fixed the problem. Thanks for the help. -Message d'origine- De : Gilles Devaux [mailto:[EMAIL PROTECTED] Envoyé : lundi 21 février 2005 14:21 À : axis-user@ws.apache.org Objet : Problem deserializing arrays of complex types Hi, First of all sorry if this subject has already been treated before but I can't find my answer in the archives. I have a problem while deserializing arrays with AXIS 1.1. The serialized message (SOAP) is correct but the other way gives me the following exception: Could not convert LinkType to bean field routeManeuvers[1]', type ManeuverType (see WSDL for type definition) The thing is that I have list of lists with complex types elsewhere in the WSDL but this one is not working, here is the XSD (relevant part) contained in my WSDL file. The thing is that if I remove the ConnectedLinksType definition and reference it works, even with a list of 'PlaceType' inside a list of 'ManeuverType'. If I add the ConnectedLinksType, the serialization is fine but not the deserialization. I have already tried to create ArrayOfXXX for complex types for all lists without success. I have also externalized the definition of the string restriction (type attribute in 'ConnectedLinksType') without success. I have tried to remove the restriction on the 'type' attribute and just keep a simple string without success. Someone has any idea ? Thanks a lot Gilles DEVAUX.
RE: Problem with Wrapped Literal style in .NET client
I also had this problem: 2 things: 1) It is possible that your temporary directory is not accessible by the .NET accounts -> your program can't create the temporary assemblies. 2) .NET can't serialize an object and the assembly is not created -> use the XmlPreCompiler (http://weblogs.asp.net/mnolton/archive/2004/12/01/273027.aspx) program to check wich object can't be serialized and modify the WSDL definition accordingly -Message d'origine- De : Murad [mailto:[EMAIL PROTECTED] Envoyé : lundi 28 février 2005 07:34 À : axis-user@ws.apache.org Objet : Problem with Wrapped Literal style in .NET client Hello All, I am trying to convert rpc encoding style wrapped/literal style.With .NET wsdl tool I am able to generate the proxy classes and dependency quite well. But at the time of running .net application there is an exception(FileNotFoundException) ... What I observed each time .NET application is trying to create a dll dynamically and try to load it later in the temp directory.I provided all the neccessary previleges into this directory.But the same error is still there.What I see this exception dont occur with rpc encoded style. I have an existing code base using rpc literal style.I want to convert this into either document or wrapped style. Which one would be better? Which conversion will be easier? In my proxy class I have methods with complex signatures(which are working nice with existing rpc encoded scheme). Please suggest. Regards, Murad
RE: Problem deserializing arrays of complex types
Hi, Just an update to say that de deserialization works with the server implemented in Axis 1.1 and the client generated with the .NET framework (whereas the AXIS 1.1 and Axis 1.2RC2 clients don't) and so I still don't understand where the problem is. Thanks -Message d'origine----- De : Gilles Devaux [mailto:[EMAIL PROTECTED] Envoyé : lundi 21 février 2005 14:21 À : axis-user@ws.apache.org Objet : Problem deserializing arrays of complex types Hi, First of all sorry if this subject has already been treated before but I can't find my answer in the archives. I have a problem while deserializing arrays with AXIS 1.1. The serialized message (SOAP) is correct but the other way gives me the following exception: Could not convert LinkType to bean field routeManeuvers[1]', type ManeuverType (see WSDL for type definition) The thing is that I have list of lists with complex types elsewhere in the WSDL but this one is not working, here is the XSD (relevant part) contained in my WSDL file. The thing is that if I remove the ConnectedLinksType definition and reference it works, even with a list of 'PlaceType' inside a list of 'ManeuverType'. If I add the ConnectedLinksType, the serialization is fine but not the deserialization. I have already tried to create ArrayOfXXX for complex types for all lists without success. I have also externalized the definition of the string restriction (type attribute in 'ConnectedLinksType') without success. I have tried to remove the restriction on the 'type' attribute and just keep a simple string without success. Someone has any idea ? Thanks a lot Gilles DEVAUX.
RE: choice (and WSDL2Java)
The only workaround I found is to write a proper documentation :)
Try to use this definition:
mailto:[EMAIL PROTECTED]
Envoyé : mercredi 23 février 2005 02:33
À : axis-user@ws.apache.org
Objet : Re: choice (and WSDL2Java)
OK, thanks for the confirmation. Is there any workaround?
I thought about splitting the definition into two parts, like
... but I can't get that to work either. I think it's not proper XML schema.
Gilles Devaux wrote:
>Same thing here, it appears that AXIS interpret the element just
>like the element.
>
>-Message d'origine-
>De : Bill Keese [mailto:[EMAIL PROTECTED]
>Envoyé : mardi 22 février 2005 09:43
>À : Axis-User
>Objet : xsd:choice (and WSDL2Java)
>
>It looks like WSDL2Java doesn't support xsd:choice for Axis 1.2. Can anyone
>confirm/deny this?
>
>I had a declaration like this:
>
>
>
>
>
>
>
>
>I expected the generated java code to look like this:
>class FilterList {
>Filters[] filters;
>}
>
>But instead it's a strange class like below. The problem w/the class below is
>that you can't have a FilterList containing two or more "and"
>nodes.
>
>public class FilterList implements java.io.Serializable { private
>jp.co.beacon_it.inicio.client.soap.schema.query.AndFilter and; private
>jp.co.beacon_it.inicio.client.soap.schema.query.OrFilter or; private
>jp.co.beacon_it.inicio.client.soap.schema.query.NotFilter not; ...
>}
>
>
>
>
>
RE: choice (and WSDL2Java)
Same thing here, it appears that AXIS interpret the element just
like the element.
-Message d'origine-
De : Bill Keese [mailto:[EMAIL PROTECTED]
Envoyé : mardi 22 février 2005 09:43
À : Axis-User
Objet : xsd:choice (and WSDL2Java)
It looks like WSDL2Java doesn't support xsd:choice for Axis 1.2. Can anyone
confirm/deny this?
I had a declaration like this:
I expected the generated java code to look like this:
class FilterList {
Filters[] filters;
}
But instead it's a strange class like below. The problem w/the class below is
that you can't have a FilterList containing two or more "and"
nodes.
public class FilterList implements java.io.Serializable { private
jp.co.beacon_it.inicio.client.soap.schema.query.AndFilter and; private
jp.co.beacon_it.inicio.client.soap.schema.query.OrFilter or; private
jp.co.beacon_it.inicio.client.soap.schema.query.NotFilter not; ...
}
Problem deserializing arrays of complex types
Hi, First of all sorry if this subject has already been treated before but I can't find my answer in the archives. I have a problem while deserializing arrays with AXIS 1.1. The serialized message (SOAP) is correct but the other way gives me the following exception: Could not convert LinkType to bean field routeManeuvers[1]', type ManeuverType (see WSDL for type definition) The thing is that I have list of lists with complex types elsewhere in the WSDL but this one is not working, here is the XSD (relevant part) contained in my WSDL file. The thing is that if I remove the ConnectedLinksType definition and reference it works, even with a list of 'PlaceType' inside a list of 'ManeuverType'. If I add the ConnectedLinksType, the serialization is fine but not the deserialization. I have already tried to create ArrayOfXXX for complex types for all lists without success. I have also externalized the definition of the string restriction (type attribute in 'ConnectedLinksType') without success. I have tried to remove the restriction on the 'type' attribute and just keep a simple string without success. Someone has any idea ? Thanks a lot Gilles DEVAUX.
