2 Replies Latest reply on Jan 5, 2011 2:30 PM by shawnwevans

    Issue with jboss-as-distribution-6.0.0.20101110-CR1.zip and jbossws-cxf-3.4.0.GA

    shawnwevans

      Unzip both, updated the ant.properties file and ran:

       

        ant -Djboss.server.instance=standard -Dspring=true deploy-jboss600

      and

        ant -Djboss.server.instance=standard -Dspring=true deploy-jboss601

      and

        ant -Dspring=true deploy-jboss600

      and

        ant -Dspring=true deploy-jboss601

       

      And got the following error with each:

       

      BUILD FAILED
      C:\jboss\jbossws-cxf-bin-dist\build\build-deploy.xml:137: The following error occurred while executing this line:
      C:\jboss\jbossws-cxf-bin-dist\build\jbossws-deploy-macros.xml:411: Unable to delete file C:\jboss\jboss-6.0.0.20101110-CR1\lib\endorsed\jboss-jaxb-api_2.2_spec.jar

       

      The file is not read-only and I am able to delete it via the command line without issue.

       

      Ideas?

       

      I would have thought that since CXF is the the standard since M4 that we wouldn't have to still run ant -Djboss.server.instance=standard -Dspring=true deploy-jboss600

       

      Thanks,

      Shawn

        • 1. Re: Issue with jboss-as-distribution-6.0.0.20101110-CR1.zip and jbossws-cxf-3.4.0.GA
          asoldano

          Sorry for the late reply.

          Regarding the "Unable to delete file...", assuming the file is actually there, I'm not a windows expert... might be something related to the file being locked by another process or what?

           

          Regarding the need for the installation, yes, JBossWS-CXF is the default, however Spring is not installed and shipped by default in JBoss AS 6 in order for not forcing users to have a given Spring implementation version in their server classpath. So, if you really need Spring (please note current JBossWS-CXF works fine without Spring except for some advanced features that are really built on top of it in Apache CXF), either you manually install it in JBoss AS, or you leverage the -Dspring=true option of JBossWS installation for doing that while updating/overwriting the jbossws stack. That's btw how we install jbossws-cxf w/ spring for test purposes.

          • 2. Re: Issue with jboss-as-distribution-6.0.0.20101110-CR1.zip and jbossws-cxf-3.4.0.GA
            shawnwevans

            With M4 it worked and with CR1 it wouldn't work. The permissions on the .\lib\endorsed\ directory is the same for both directories.

             

            But to make it work, I just deleted all of the files in .\lib\endorsed\ before I run ant -Dspring=true deploy-jboss600 and it works fine... shrug...

             

            Also when I unzip, I right click on the zip file in file explorer and select WinZip -> Extract to here

             

            Thanks