Re: Problem with Wrapped Literal style in .NET client
Dear Anne,
Thanks for your kind response.Following is the service class
definition. With this service class I provided two sets of service
definitions in the wsdd file which are enclosed below along with their
corresponding generated wsdl.Scenario 1 is with
the wrapped/literal encoding which gives the problem mentioned in my
previous mail.And Scenario 2 is the default
encoding scheme(which I believe is rpc/literal).With scenaio 2
everything is working nice and smooth(offcourse I have small amount
payload until now).
Service class definition ::
/*
* Copyright (C) 2004 Sikraft Solutions Ltd. All Rights Reserved.
*
* This software is the confidential and proprietary information
* of Sikraft Solutions Ltd.
* You shall not disclose such Confidential Information and shall use
* it only in accordance with the terms of the license agreement
* you entered into with Sikraft.
*/
package com.sikraft.ihis.inpatient.roomtype;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import com.sikraft.welkin.business.Result;
import com.sikraft.welkin.business.ServiceFacade;
import com.sikraft.welkin.exception.GenericException;
import com.sikraft.welkin.service.BaseJaxRPCService;
import java.util.List;
/**
* Exposes the Inpatient RoomType related service to the external world
* @author Ahad
* @version 1.0
*/
public class JaxRpcIRTypeService
extends BaseJaxRPCService
{
private static Log theLogger = LogFactory.getLog(JaxRpcIRTypeService.class);
public static final String SERVICE_NAME = "irtypeService";
/**
* creates a room type in the system
*
* @param theData PersistantCapableDTO
*/
public Result add(IRTypeDTO theData) throws GenericException
{
return provideService(theData, SERVICE_NAME, ServiceFacade.SERVICE_ADD);
}
/**
* update a room type info existing in the system
*
* @param theData PersistantCapableDTO
*/
public Result modify(IRTypeDTO theData) throws GenericException
{
return provideService(theData, SERVICE_NAME, ServiceFacade.SERVICE_MODIFY);
}
/**
* provides all room type of the system
*
* @return allIRType List
*/
public IRTypeDTO[] getAllIRType() throws GenericException
{
List allIRType = ( (IIRTypeService)
getService(SERVICE_NAME)).getIrtypeDAO().getAllIRType();
IRTypeDTO allIRTypeArray[] = (IRTypeDTO[]) allIRType.toArray(new
IRTypeDTO[allIRType.size()]);
return allIRTypeArray;
}
public IRTypeDTO findById(Long id)throws GenericException
{
theLogger.trace("findById() :: " + id);
Object obj = findDTOById(IRTypeDTO.class,id);
theLogger.trace("findById() :: " + obj);
return (IRTypeDTO)obj;
}
public IRTypeDTO[] findIRTypes(String hqlQueryCondition,Object
params[])throws GenericException//Specific field Search
{
List searchedDepartments =
findPersistantCapableDTOs(IRTypeDTO.class.getName(),hqlQueryCondition,params);
return (IRTypeDTO[])searchedDepartments.toArray(new
IRTypeDTO[searchedDepartments.size()]);
}
public Object[][] findSpecificDataWithFullValue(String
fieldNames[],String fieldValues[],String returnFieldNames[])
{
return
super.findSpecificData(fieldNames,fieldValues,returnFieldNames,IRTypeDTO.class);
}
public Object[][] findSpecificDataWithPatialValue(String
fieldName,String partialOrFullFieldValue,String returnFieldNames[])
{
return
super.findSpecificData(fieldName,partialOrFullFieldValue,returnFieldNames,IRTypeDTO.class);
}
}
With a above code base followings are two scenarios:
Scenario 01. (wrapped/literal)
01.a.
Service Element defined in wsdd ::
urn:ihis
01.b. WSDL with the above service element definition
- http://xml.apache.org/xml-soap";
xmlns:impl="urn:ihis" xmlns:intf="urn:ihis"
xmlns:tns1="http://lang.java";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
-
-
- http://www.w3.org/2001/XMLSchema";>
http://lang.java"; />
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
http://schemas.xmlsoap.org/soap/http"; />
-
-
-
-
-
Re: Problem with Wrapped Literal style in .NET client
If you convert your WSDL from rpc/literal to wrapped/literal, you shouldn't need to make any changes to your code base. If you supply the before and after WSDL file, perhaps we can help you diagnose the problem. Anne On Mon, 28 Feb 2005 12:34:00 +0600, Murad <[EMAIL PROTECTED]> wrote: > 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 with Wrapped Literal style in .NET client
Please help me out as the problem remains the same. On Mon, 28 Feb 2005 15:45:53 +0600, Murad <[EMAIL PROTECTED]> wrote: > Thanks.. You showed two ways to track the problem. With number 2 I > found no errors in deserializing my classes associated with the proxy. > For number 1.I also provide all possible priviledges to the temp > directory. > > > On Mon, 28 Feb 2005 09:58:02 +0100, Gilles Devaux <[EMAIL PROTECTED]> wrote: > > 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 > > > > -- > Best regards, > > Murad > -- Best regards, Murad
Re: Problem with Wrapped Literal style in .NET client
Thanks.. You showed two ways to track the problem. With number 2 I found no errors in deserializing my classes associated with the proxy. For number 1.I also provide all possible priviledges to the temp directory. On Mon, 28 Feb 2005 09:58:02 +0100, Gilles Devaux <[EMAIL PROTECTED]> wrote: > 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 > -- Best regards, Murad
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
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
