web-services

问题 I am using Eclipse Juno and WildFly 8.2 and try to deploy soap web services with ws-security. This is my ref site. https://docs.jboss.org/author/display/JBWS/WS-Security#WS-Security-Authenticationandauthorization Deployment is ok! But the problem seems to be the client of Eclipse. I made some jsp codes with eclipse ide <%@ page import="javax.xml.ws.BindingProvider"%> <%@ page import="javax.xml.namespace.QName"%> <%@ page import="java.net.URL"%> <%@ page import="javax.xml.ws.Service"%> <%@

问题 I am using Eclipse Juno and WildFly 8.2 and try to deploy soap web services with ws-security. This is my ref site. https://docs.jboss.org/author/display/JBWS/WS-Security#WS-Security-Authenticationandauthorization Deployment is ok! But the problem seems to be the client of Eclipse. I made some jsp codes with eclipse ide <%@ page import="javax.xml.ws.BindingProvider"%> <%@ page import="javax.xml.namespace.QName"%> <%@ page import="java.net.URL"%> <%@ page import="javax.xml.ws.Service"%> <%@

问题 I've been trying to resolve this issue for a while and haven't been successful yet. I've got a basic ASP.NET WebService which I'm trying to call from javascript as such. using System; using System.Web; using System.Web.Services.Protocols; using System.Web.Services; using System.Web.Script.Services; namespace RandomWebServices { /// <summary> /// Summary description for WebServices1 /// </summary> [WebService(Namespace = "http://localhost:2900/")] [WebServiceBinding(ConformsTo = WsiProfiles

问题 Within an application, I've got Secret Keys uses to calculate a hash for an API call. In a .NET application it's fairly easy to use a program like Reflector to pull out information from the assembly to include these keys. Is obfuscating the assembly a good way of securing these keys? 回答1: Probably not. Look into cryptography and Windows' built-in information-hiding mechanisms (DPAPI and storing the keys in an ACL-restricted registry key, for example). That's as good as you're going to get for

问题 Within an application, I've got Secret Keys uses to calculate a hash for an API call. In a .NET application it's fairly easy to use a program like Reflector to pull out information from the assembly to include these keys. Is obfuscating the assembly a good way of securing these keys? 回答1: Probably not. Look into cryptography and Windows' built-in information-hiding mechanisms (DPAPI and storing the keys in an ACL-restricted registry key, for example). That's as good as you're going to get for

问题 If host my WCF services in IIS7 or WPAS, is it possible to load up two or more services into the same AppDomain so that they can share static variables? 回答1: Sure you can expose as many Endpoints within a Web Application as you want (even of different WCF Services). This should not be limited to either IIS or WPAS. Doing so will enable you to access any kind of shared data . Even though I would normally advise against using static variables to share information (But of course I don't know

问题 If host my WCF services in IIS7 or WPAS, is it possible to load up two or more services into the same AppDomain so that they can share static variables? 回答1: Sure you can expose as many Endpoints within a Web Application as you want (even of different WCF Services). This should not be limited to either IIS or WPAS. Doing so will enable you to access any kind of shared data . Even though I would normally advise against using static variables to share information (But of course I don't know

问题 I'm asking your sugegstions about an "architectural" scenario: I'd looking for a simplest publish/subscribe architecture to let talk two decoupled servers over on internet, sharing "sparse" but "real-time" messages/events. Let me explain: The PUBLISHER: Is a server (http://www.server.com) that generate some sort of events (by example events==ORDERS data on a e-commerce website). SUBSCRIBERS (one or more): Are "clients" that can subscribe to receive ORDERS events (http://www.client.com). In

问题 I am trying to devise a strategy for Web Services versioning and how to handle versions from a SCM point of view. We are doing bottom-up (JAX-WS) services, and therefore have less control over the schema and can't follow some schema versioning of the best practices. My current thoughts are: 1) Major changes (non-backwards compatible): Transmitted to the API client via new service URL (URL versioning). E.g.: http://com.example/v1/MyService http://com.example/v2/MyService This causes in my

问题 I created a pool of ports (webservice clients) because creating on the fly on each request the client lead to a bottleneck Now I noticed that the webservice clients hold references to the request and response... Is that normal... ? Unfortunately the payload is quite big for this websevice and like this even if not used for a while the pool holds references to some not anymore used responses...increasing heap .. Is there a way to clean those references after receiving the response ? Update: