6 Replies Latest reply on Feb 5, 2008 10:14 AM by dimival

    Questions about deploying compressed WAR

    dimival Level 1
      I've been having issues when trying to deploy a compressed Flex application into my Weblogic Server. I read in the Installation Guide ( http://www.adobe.com/support/documentation/en/flex/2/install.html) that you need to some "hacking" to make it work but i have a big question:

      The guide says:
      Locate the servlet definition for MessageBrokerServlet, and update the flex.write.path init-param element to specify an existing, writeable, directory path:

      <init-param>
      <param-name>flex.write.path</param-name>
      <param-value>C:/bea/flex</param-value>
      </init-param>


      I have no clue about this, i mean what is supposed to be in the path C:/bea/flex??? Can anyone explain what the "flex.write.path" means or referrers to?


      Diego

        • 1. Re: Questions about deploying compressed WAR
          Mete Atamel Level 1
          Hi dimival,

          flex.write.path is basically the path to a writable folder. Flex/FDS will use this folder to save the stuff that it usually saves in your FDS installation directory. Since you're trying to run FDS compressed, there's no installation directory, therefore it needs to have access to a writable folder to write these files and that's why you need to define fkex.write.path.
          • 2. Questions about deploying compressed WAR
            dimival Level 1
            So basically is it any writable and empty folder??? Can i create a new one and use it as the write.path?
            • 4. Questions about deploying compressed WAR
              dimival Level 1
              I tried setting the write path to any folder like the example and i got this during the server startup:

              [Flex] [WARN] The watch-file, /WEB-INF/flex/services-config.xml, could not be resolved to a path and will be ignored.
              [Flex] [WARN] The watch-file, /WEB-INF/flex/proxy-config.xml, could not be resolved to a path and will be ignored.
              [Flex] [WARN] The watch-file, /WEB-INF/flex/remoting-config.xml, could not be resolved to a path and will be ignored.
              [Flex] [WARN] The watch-file, /WEB-INF/flex/messaging-config.xml, could not be resolved to a path and will be ignored.
              [Flex] [WARN] The watch-file, /WEB-INF/flex/data-management-config.xml, could not be resolved to a path and will be ignored.
              [Flex] [WARN] The touch-file, /WEB-INF/web.xml, could not be resolved to a path and will be ignored.

              And then when i tried to run the sample application CRM (which is included in the samples war when you install flex 2) i get this error:

              java.sql.SQLException: The url cannot be null

              so what's wrong?


              • 5. Re: Questions about deploying compressed WAR
                Mete Atamel Level 1
                "The url cannot be null" indicates that you're trying to access to the Database but the url you're using is null for some reason. I'd put a breakpoint where that SQLException is thrown and see if you can spot the problem from the stacktrace.
                • 6. Re: Questions about deploying compressed WAR
                  dimival Level 1
                  Any idea why i get this when deploying the compressed war?

                  [Flex] [WARN] The watch-file, /WEB-INF/flex/services-config.xml, could not be resolved to a path and will be ignored.
                  [Flex] [WARN] The watch-file, /WEB-INF/flex/proxy-config.xml, could not be resolved to a path and will be ignored.
                  [Flex] [WARN] The watch-file, /WEB-INF/flex/remoting-config.xml, could not be resolved to a path and will be ignored.
                  [Flex] [WARN] The watch-file, /WEB-INF/flex/messaging-config.xml, could not be resolved to a path and will be ignored.
                  [Flex] [WARN] The watch-file, /WEB-INF/flex/data-management-config.xml, could not be resolved to a path and will be ignored.
                  [Flex] [WARN] The touch-file, /WEB-INF/web.xml, could not be resolved to a path and will be ignored.