7 Replies Latest reply on Mar 13, 2006 1:57 PM by sgv

    FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in JBos

    twojenski

      I'm trying to execute (or not execute) these 2 steps as instructed by the tutorial. If we are to skip these steps (9.2 and 9.3) how is the FiboApp.ear ever going to know about the FiboEJB-client.jar and FiboWeb.war files?

      If we skip these steps then how will these (FiboEJB-client.jar and FiboWeb.war) ever be created?

      Does anyone have any additional steps on how to package and deploy this application on JBoss 4.0.3?

      Tek

        • 1. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in

          Hi, sorry if the tutorial is a little confusing, but you're only supposed to skip step 9.2, and a specific sub-step of 9.3... the tutorial reads:


          If you are running JBoss 4.0 or above, You will receive a ClassLoaderException if you attempt to package your EJB interfaces in both the WAR and EJB-JAR because of the new Tomcat scoped classloading. To avoid this issue, you should skip this section, and also skip adding FiboEJB-client.jar to FiboWeb.war below.


          So, as it says we just need to skip the part in 9.3 where we add FiboEJB-client.jar to FiboWeb.war, which is also marked :


          If you are running JBoss 4.0 or above, you should skip this step (see explanation above).


          So, in summary.. you want to do ALL of step 9.3 EXCEPT for adding FiboEJB-client.jar to FiboWeb.war

          • 2. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in
            twojenski

            Thanks.

            I was confused after quickly reading the tutorial.... The JBoss requirement was 4.0.3 so I did not really understand why the was not specifically targeting 4.0.3.

            Marshall, thanks for putting me back on the right path.

            Another, question if I may. If I have a project that already generates a WAR file, is there any easy way to define that in Packaging Configurations of the Tutorial project. Assuming that this new web project correctly defines references to the FiboEJB in the web.xml and jboss-web.xml descriptors. My intention is to add another web project to the FiboApp.ear and have that new web project access the FiboEJB.

            Thanks

            Tek

            • 3. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in

              No problem =)

              Yes, this is pretty easy to do... go into your project's packaging configuration, and for your EAR configuration, just click "Add File", and instead of using "Project File" use "External File" which will let you add any other war/jar/whatever from other projects by selecting them on the filesystem.

              • 4. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in
                sgv

                Hello,

                Sorry for the dumb question - but I had the same confusion, but even after I fixed it I see, the directory listing instead of the fibo page. It looks as if the .html page is missing from a directory. Does it not get deployed ??

                Any help really appreciated.

                • 5. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in
                  sgv

                   

                  "sgv" wrote:
                  Hello,

                  I had the same confusion, but even after I fixed it I see, the directory listing instead of the fibo page. It looks as if the .html page is missing from a directory. Does it not get deployed ??

                  Any help really appreciated.


                  • 6. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in
                    sgv

                    Hello,

                    Here is the page that is displayed.

                    http://www.geocities.com/sahengala/ErrorPage.GIF

                    Any help appreciated.

                    Regards,
                    sgv

                    • 7. Re: FiboEJB-client.jar and FiboWeb.war steps 9.2 and 9.3 in
                      sgv


                      I have fixed it - XDoclet configurations. Had an extra / in the **/*Servlet . .

                      Regard,
                      sgv