3 Replies Latest reply on Oct 21, 2003 3:35 PM by Viet

    Nukes rant: if it's this troublesome it's not going very far

    maladon Newbie

      We're building an intranet portal with no budget and no requirements (of course) and so I had to pick an open source portal solution. I looked at 13 different choices and am planning on using Nukes -- but -- it's been such a hassle that I might switch to something else.

      Here's my troubles so far:
      The tutorial doesn't work as described:
      1 - the build.sh scripts ignore ANT_HOME environement variable. SuSE installed ant in /opt/jakarata/ant, which the build script can't find. I had to hack the build script just to build Nukes.

      2 - When I deploy nukes core to JBoss it gives me exceptions trying to find the {path-to-JBoss}/deploy/nukes directory. I had to create that by hand. What's this directory for? Deploying to this directory yields nothing!

      3 - When I deploy my sar, per the instructions, I get exceptions on the JBoss console indicating that my MBean doesn't have the management extensions. However, I can deploy the exact same file to the integrated JBoss/Nukes alpha release it shows up in the portal.

      4 - I tried to install the news module, but that failed. The build deploy target expects to have that mysterious nukes directory defined (which it wasn't). Of course, copying the EAR file there doesn't actually deploy it, I had to manually copy it to the deploy directory where JBoss promptly puked out an exception and didn't deploy it. (java.lang.NoClassDefFoundError: de/nava/informa/core/ChannelIF)

      As a JBoss newbie debugging this crap is a royal pain. I've done lot's of J2EE on other app servers (WebSphere, Silverstream, Tomcat, etc.) and so I suspect that some of these issues are just deployment issues with JBoss. But, having to delve into the bowels of the overly-complicated Nukes build process is a waste of my time. I'm supposed to be spending my time building modules and blocks for my portal!

        • 1. Re: Nukes rant: if it's this troublesome it's not going very
          Viet Master

          > We're building an intranet portal with no budget and
          > no requirements (of course) and so I had to pick an
          > open source portal solution. I looked at 13
          > different choices and am planning on using Nukes --
          > but -- it's been such a hassle that I might switch to
          > something else.
          >
          > Here's my troubles so far:
          > The tutorial doesn't work as described:
          > 1 - the build.sh scripts ignore ANT_HOME environement
          > variable. SuSE installed ant in /opt/jakarata/ant,
          > which the build script can't find. I had to hack the
          > build script just to build Nukes.

          it is because we provider ANT with the build : use build.sh or build.bat to build the project.

          >
          > 2 - When I deploy nukes core to JBoss it gives me
          > exceptions trying to find the
          > {path-to-JBoss}/deploy/nukes directory. I had
          > to create that by hand. What's this directory for?
          > Deploying to this directory yields nothing!

          yes, this is recent and is not documented. nukes.ear should be deployed in deploy and all other modules should be deployed in nukes directory.

          >
          > 3 - When I deploy my sar, per the instructions, I get
          > exceptions on the JBoss console indicating that my
          > MBean doesn't have the management extensions.
          > However, I can deploy the exact same file to the
          > integrated JBoss/Nukes alpha release it shows up in
          > the portal.

          this is because we switched the components to use model mbeans now.

          >
          > 4 - I tried to install the news module, but that
          > failed. The build deploy target expects to have that
          > mysterious nukes directory defined (which it wasn't).
          > Of course, copying the EAR file there doesn't
          > actually deploy it, I had to manually copy it to the
          > deploy directory where JBoss promptly puked out an
          > exception and didn't deploy it.
          > (java.lang.NoClassDefFoundError:
          > de/nava/informa/core/ChannelIF)
          >

          have to see that.

          > As a JBoss newbie debugging this crap is a royal
          > pain. I've done lot's of J2EE on other app servers
          > (WebSphere, Silverstream, Tomcat, etc.) and so I
          > suspect that some of these issues are just deployment
          > issues with JBoss. But, having to delve into the
          > bowels of the overly-complicated Nukes build process
          > is a waste of my time. I'm supposed to be
          > spending my time building modules and blocks for my
          > portal!

          fact is that you should use the solution like the nukes alpha release and you are using the build that is targetting nukes developpers.

          Right now I am very busy working on the forum module. I will commit it this week and after I want to create a true 1.0 nukes for people like you.

          In the meanwhile I will updaye the nukes tutorial (tonight probably) so it will not stuck people because of out dates informations.

          julien

          • 2. Re: Nukes rant: if it's this troublesome it's not going very
            maladon Newbie

            Thanks for your prompt reply...

            >> SuSE installed ant in /opt/jakarata/ant,
            > > which the build script can't find. I had to hack
            > the
            > > build script just to build Nukes.
            >
            > it is because we provider ANT with the build : use
            > build.sh or build.bat to build the project.

            I am using build.sh -- that's what I had to hack. I have ANT_HOME set, why not just use it?

            > > 2 - When I deploy nukes core to JBoss it gives me exceptions trying to find the
            > > {path-to-JBoss}/deploy/nukes directory. I had to create that by hand. What's this directory for?
            > > Deploying to this directory yields nothing!
            >
            > yes, this is recent and is not documented. nukes.ear should be deployed in deploy and all other modules
            > should be deployed in nukes directory.

            That makes sense.

            > fact is that you should use the solution like the
            > nukes alpha release and you are using the build that
            > is targetting nukes developpers.

            Just following the install instructions.

            > Right now I am very busy working on the forum module.
            > I will commit it this week and after I want to create
            > a true 1.0 nukes for people like you.

            What would be helpful is two different bundles: one integrated with JBoss like the current alpha and one that isn't bundled with JBoss so people can deploy it to an already running version of JBoss. Since we're going to go with Nukes I might as well start using JBoss as my app server and so I want to be able to manage/administer Nukes and JBoss separately.

            > In the meanwhile I will update the nukes tutorial
            > (tonight probably) so it will not stuck people
            > because of out dates informations.

            Fantastic!
            A couple of points that would be helpful to have in the tutorial:

            -list of jar files needed to compile our own blocks, modules and templates
            -a slightly less trivial example -- don't use another login block
            -walk-through of doing some administration
            - add a new module
            - configuring the faq
            - configuring the news module
            - configuring the built-in CMS features (is this just the HTML module?)

            I like the architecture and structre of blocks and modules, and the fact that it's all J2EE. That's the reason we're trying Nukes. I should have paid more attention to the status of alpha. I had hoped that since it's running jboss.org it'd be a little more polished than it is.

            Thanks again for your quick repsonses. I'll stick with the alpha release for now! :-)

            • 3. Re: Nukes rant: if it's this troublesome it's not going very
              Viet Master

              > Thanks for your prompt reply...
              >
              > >> SuSE installed ant in /opt/jakarata/ant,
              > > > which the build script can't find. I had to
              > hack
              > > the
              > > > build script just to build Nukes.
              > >
              > > it is because we provider ANT with the build : use
              > > build.sh or build.bat to build the project.
              >
              > I am using build.sh -- that's what I had to hack. I
              > have ANT_HOME set, why not just use it?

              If we embed our ANT version we are sure of the build result.

              >
              > > > 2 - When I deploy nukes core to JBoss it gives me
              > exceptions trying to find the
              > > > {path-to-JBoss}/deploy/nukes directory. I
              > had to create that by hand. What's this directory
              > for?
              > > > Deploying to this directory yields nothing!
              > >
              > > yes, this is recent and is not documented.
              > nukes.ear should be deployed in deploy and all other
              > modules
              > > should be deployed in nukes directory.
              >
              > That makes sense.
              >
              > > fact is that you should use the solution like the
              > > nukes alpha release and you are using the build
              > that
              > > is targetting nukes developpers.
              >
              > Just following the install instructions.
              >
              > > Right now I am very busy working on the forum
              > module.
              > > I will commit it this week and after I want to
              > create
              > > a true 1.0 nukes for people like you.
              >
              > What would be helpful is two different bundles: one
              > integrated with JBoss like the current alpha and one
              > that isn't bundled with JBoss so people can deploy it
              > to an already running version of JBoss. Since we're
              > going to go with Nukes I might as well start using
              > JBoss as my app server and so I want to be able to
              > manage/administer Nukes and JBoss separately.

              ok

              >
              > > In the meanwhile I will update the nukes tutorial
              > > (tonight probably) so it will not stuck people
              > > because of out dates informations.
              >

              This is done, the HTML look was crappy, I made it more readable and the informations should be up-to-date.

              > Fantastic!
              > A couple of points that would be helpful to have in
              > the tutorial:
              >
              > -list of jar files needed to compile our own blocks,
              > modules and templates

              you can use the template module as starting point

              > -a slightly less trivial example -- don't use another
              > login block
              > -walk-through of doing some administration
              > - add a new module
              > - configuring the faq
              > - configuring the news module
              > - configuring the built-in CMS features (is this
              > is just the HTML module?)

              yes, yes, yes but... you know what ? I am lacking of time to do that.

              >
              > I like the architecture and structre of blocks and
              > modules, and the fact that it's all J2EE. That's the
              > reason we're trying Nukes. I should have paid more
              > attention to the status of alpha. I had hoped that
              > since it's running jboss.org it'd be a little more
              > polished than it is.

              good to hear that. stay tuned

              >
              > Thanks again for your quick repsonses. I'll stick
              > with the alpha release for now! :-)