It is a URL. There is a major difference. For one thing, no such file as "outside.jsf" exists anywhere and no file explorer or command-line directory tool can find it. If you pass that URL to the appserver at "ip", the appserver will analyze the URL, send it to a webapp, the webapp will analyze it further, and generate output based on the analysis.
The consequences of this critical difference are as follows:
1. Because the appserver at "ip" is not serving a file, but instead resolving a URL, what comes back from "ip" won't be xhtml source, it will be an actual webpage in HTML.
2. Because http://ip:7001/outside.jsf is a URL and not a file path, any function that attempts to open and read files (such as the "include" directive) will fail
What you are really looking to do is embed one bit of generated HTML inside another bit of HTML. There are several ways to do that. Portal servers do so using Portlets, but Portlets are specialized objects and we have a forum just for them. Another way is to use a construct such as HTML frames or IFRAMEs. That has to be done carefully, however, as JSF doesn't really like frames very much.
Customer surveys are for companies who didn't pay proper attention to begin with.