soa

I have to send a byte array (encoded photo) from my PHP client to the WCF host. when I do a var_dump() on my array in PHP I get an array[2839] which is ok but on the server side when I debug I see that received array is only byte[5]... Any idea how I can fix it? I used code like this $file = file_get_contents($_FILES['Filedata']['tmp_name']); $byteArr = str_split($file); foreach ($byteArr as $key=>$val) { $byteArr[$key] = ord($val); } $client = new SoapClient('http://localhost:8000/MgrService?wsdl', array( 'location' => 'http://localhost:8000/MgrService/SOAP11', 'trace' => true, 'soap_version'

In a RESTful SOA, suppose I issue a POST request via AJAX but I don't get a response before the request times out. Further suppose a re-submission of the request would be harmful. POST is not idempotent. For example, maybe I am posting a bank transfer of money. If I don't get a response, I don't know if the server processed the request. What is the best practice to deal with this, assuming I have control over the client-side and the services side? My initial thought is to include a nonce (i.e. a pseudo-id; some sort of unique identifier) with each POST request; e.g. perhaps a value in the If

I have to create a Java EE application which converts large documents into different formats. Each conversion takes between 10 seconds and 2 minutes. The SOAP requests will be made from a client application which I also have to create. What's the best way to handle these long running requests? Clearly the process takes to much time to run without any feedback to the user. I can think of the following ways to provide some kind of feedback, but I'm not sure if there isn't a better way, perhaps something standardized. The client performs the request from a thread and the server sends the document

I would like to incorporate SOA pattern in my 3 tier structure. I created a Service layer (WCF Host) between the BLL and the UI. My structure setup is now looks like this UI <> WCF <> BLL <> DAL <---[Entities] ---> The problem is, I have my entities in separate DLL (ANd it was visible in ALL Layers except on the UI) Now, I need to expose it so that the consumer of my service can use it.In this case, the UI. How can I possibly do that? Entities.DLL namespace Entities { public class Account { public string AcctID { get; set; } public string AcctName { get; set; } } } now, Im planning to use it

I'm an architect in a large scale financial company and we are in the beginning of implementing a new business oriented infosystem across our different countries. From the very early on the core idea has been to follow microservice oriented principles as much as possible (and making sure engineers have read Building Microservices book by Sam Newman) . By now I've come to crossroads. Our services are primarily JSON REST services using Swagger for automated documentation, but in order to use these services in our business processes and making sure not to write business logic into services

开始，先说一句，还是用maven的好 1、由于没用maven，和对dubbo不是很了解的原因，这次，总因为jar包不对，而导致：dubbo客户端程序，启动不起来 所以决定：将原来用过的所有jar包全部去，将dubbo-demo-provider-2.5.4-SNAPSHOT/lib下的所有jar包全部导入项目中 一切就OK了 2、服务消费者代码 import java.util.Set; import javax.validation.ConstraintViolation; import javax.validation.ConstraintViolationException; import org.springframework.context.support.ClassPathXmlApplicationContext; import com.alibaba.dubbo.demo.ValidationParameter; import com.alibaba.dubbo.demo.ValidationService; import com.alibaba.dubbo.rpc.RpcException; public class Consumer { /** * @param args * @throws Exception */ public static void

I've got a requirement to pass parameters as Xml to my stored procedures. I have a WCF service in the middle tier that makes calls to my data layer which in turn forwards the request to the appropriate stored procedure. The design is that the WCF service is responsible for building the Xml to pass to the Repository. I'm just wondering whether to keep control of what parameters are contained within the Xml in the middle tier or use a Dictionary built up by the client which I then convert to Xml in the middle tier? At the moment I've gone for the latter - for example: public

What is the path of least evil when dealing with polymorphism and inheritance of entity types in a service-oriented architecture? A principle of SOA (as I understand it) is to have entity classes as mere data constructs, lacking in any business logic. All business logic is contained in narrow-scoped, loosely-coupled services. This means service implementations are as small as possible furthering the loose coupling, and means the entities avoid having to know about every behaviour the system may perform on them. Due to Java's quite baffling decision to use the declared type when deciding which