Error 404--Not Found" while starting an app by Weblogic

Solution:-

The failure to load the client runtime will cause the 'loading' status you are seeing. You've narrowed the search area !
you are seeing paths that, for a project named "Project" on a server listening on port 7001, look correct.
You'll need to figure out why WL isn't serving those files. You've confirmed they are in the WAR file, so why is it not serving them. For faster testing, simply try to load on the urls, e.g.

http://localhost:7001/Project/config.js

in a browser tab. If it 404's, there's no point in trying to load the app. I would re-validate that Weblogic is not throwing any errors however. In web.xml, there are servlet mappings for several paths, e.g:

   <servlet-mapping>
        <servlet-name>springapp</servlet-name>
        <url-pattern>/lib/runtimeLoader.js</url-pattern>
    </servlet-mapping>

<servlet-mapping>
        <servlet-name>springapp</servlet-name>
<url-pattern>/config.js</url-pattern>
    </servlet-mapping>

If weblogic if failing to honor those mappings for whatever reason, this can prevent those file from being served. These errors are likely to occur when you first deploy the WAR, not when you try to load the project. I would re-deploy my WAR with the WL console open and in verbose mode.

                                                            OR

A 404 simply means that the URL is invalid or that the resource actually isn't there where you think it is. First test its availablility independently with an absolute URL. Such as http://example.com/context/page.jsp. If that doesn't work, then verify if the resource is actually there in your webapp where you expect it to be. If that does work, then you likely used a relative URL in the redirect such as: <meta http-equiv="refresh" content="3;url=/page.jsp">   You need to be aware that any relative URL's in the page are relative to the absolute URL of the current request. Thus, if the page was requested with for example http://example.com/context/wait.jsp, then the above relative URL will resolve to http://example.com/page.jsp. This is thus not going to work if the page is actually located at http://example.com/context/page.jsp. You should then replace the URL by the right relative URL: <meta http-equiv="refresh" content="3;url=page.jsp">   or just an absolute URL: <meta http-equiv="refresh" content="3;url=http://example.com/context/page.jsp">