I hava a GWT project running on port 3000, and i have a Java project running on port8080. Now i just want to send a string from port 3000 to 8080. Would it be possible by using GWT request builder? or how to make this process happen by using other technology?
I also need data to be sent from port 8080 to port 3000....
Yes it is possible.
I'm assuming your java project should be a service/webapp, since you have mentioned the port in which your java project is running is 8080(default tomcat port).
Your access from GWT project running on port 3000 to java project running on port 8080 is a Cross Site Request.
References on Cross site request:
http://www.gwtproject.org/doc/latest/tutorial/Xsite.html
(Please read section : Access Restrictions: Same Origin Policy)
GWT RequestBuilder - Cross Site Requests
Related
I have a semantic web/RDF application which runs on Tomcat and is backended with MySQL. Apache HTTPD is in front as a reverse proxy and the OS is Red Hat Linux 6. I am seeing a lot of Connections to port 80 per IP. What I want to know is what determines whether the include for a css or .js file is served over the existing TCP socket, or a new one is created for each GET that occurs while the web page is "built". Is that exclusively the application itself, or is it the Apache web server, or the Linux kernel as well?
I am using:
WAMP
PHP 5.3
XDebug
NetBeans
I want to debug and have the debug port in Netbeans set as 9000 (after following various tutorials, including this one --> Xdebug And Netbeans Problem ). The problem is, I'm unsure as to the purpose of the port 9000.
Does debug port 9000 mean that I must run Wamp on port 9000?
You don't run Wamp on port 9000: it's NetBeans that runs on port 9000!
Your debug client (NetBeans, in this case) needs to listen for incoming connections so Xdebug is able to establish a connection and send the apporpriate info. Please note that there're two requests involved:
Someone (possibly NetBeans) connects to the web server to request the HTML document and start a debug session.
Xdebug connects to whoever requested the debug session (NetBeans) and sends some XML with variables and other debug info.
Details can vary depending on your settings but this is the general idea.
The port you choose is irrelevant as far as:
It's available (no other app is using it) at this moment.
It's reachable from the web server (no firewall / router issues).
I have a swing client which connects to my ejb2 application deployed in JBoss 5.1. There is a particular requirement from Customer to make it available on internet.
The deployment architecture is as follows,
swing_client --> extranet_ip |firewall | --> iis7_machine --> jboss5.1_machine.
jndi properties in client is as follows
Context.PROVIDER_URL=http://extranet_ip:9180/invoker/JNDIFactory
Context.INITIAL_CONTEXT_FACTORY=org.jboss.naming.HttpNamingContextFactory
This configuration works fine when the client is inside intranet. But it does not work in internet (extranet).
When I tried initially I got the error 'Connection refused'
After seeing some posts in various forums, I changed the file server\deploy\http-invoker.sar\META-INF\jboss-service.xml, to reflect the extranet_ip in invokerURL.
Aftet this I am getting the following error.
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://10.200.1.193:4546/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
Where 10.200.1.193 is the intranet IP address of JBoss Server machine.
I tried changing the trasport parameter in remoting-jboss-beans.xml to http, but at that time client is not working in both intranet and extranet.
Please anybody suggest a way forward for this issue. Or is there any other way to implement RMI over Http in JBoss?
Update: As a solution, I had to change my deployment architecture as follows.
swing_client --> extranet_ip |firewall | --> jboss5.1_machine
where the JBoss Application Server will be directly exposed through firewall. Then update clientConnectAddress in the remoting-jboss-beans.xml to the extranet IP. Also open the ports 8080 & 4446 in the firewall for this address.
This way the swing client is working if I use the jnid properties as follows.
Context.PROVIDER_URL : http://extranet_ip:8080/invoker/JNDIFactory
Context.INITIAL_CONTEXT_FACTORY : org.jboss.naming.HttpNamingContextFactory
But still looking for a solution where there is no need to open any non-standard ports and no need to expose the Application Server directly.
After a long struggle I found a solution for my issue. The solution was to change EJB container's invoker type to http in standardjboss.xml. When the invoker is http, it will use the settings in http-invoker.sar for remote binding.
I have build a web project in Symfony 1.4 and ORM as Propel. we have a VPS to host our web site, I have created my project on web server and configured it with the IP on port no 8080,
like http://s.o.m.e.i.p:8080. it works fine, but we bought a Domainname as "mysite.com" and it is pointing towards the web server ip i.e http://s.o.m.e.i.p. How can i configure my Symfony Project to http://s.o.m.e.i.p so that it will point the domain name.
This is not doable only in Symfony - you have to alter your apache configuration to use port 80.
I have used Eclipse 3.4 to create a Dynamic Web Project. I have also configured my server to use port 8443 with ssl. If I start my server I can access my test.jsp by going to it's address
https://localhost:8443/TestContext/test.jsp
In eclipse, I have installed this server and added my project to the server. If I Run test.jsp it always launches as
http://localhost:8080/TestContext/test.jsp
My question is: How can I set up eclipse to run this on https://localhost:8443/ rather than the default 8080? Thanks in advance.
You should have a project called "Servers". There your tomcat should have its folder - for example "Tomcat 6.0.20 at localhost-config". There is server.xml there, in which you can enable SSL.
When you enable the SSL, the server accepts requests on port 8443 as well as on 8080. The server is not run on a port - it accepts connections on multiple ports. So just type https://localhost:8443/