3 Replies Latest reply on Dec 19, 2006 10:03 AM by Gavin King

    Why "embeddedEjb true" in component.properties?

    eekboom Newbie

      It's quite confusing: The ant build never uses this setting at all, but has the values hardcoded in the targets.

      When I use my IDE to build (so that ant filter tokens are not replaced in component.xml), then the resulting ear is not deployable to JBoss because it wants to use an embedded ejb3 container.

      I think JBoss deployment should be the default so the value should be "false".

        • 1. Re: Why
          Gavin King Master

          Here is a quote from the ant build:

          <target name="war" depends="compile">
           <copy todir="${build.dir}/resources/WEB-INF">
           <fileset refid="example.war.webinf"/>
           <filter token="jndiPattern" value="${example.name}/#{ejbName}/local"/>
           <filter token="embeddedEjb" value="false"/>
           <filter token="microcontainer" value="false"/>

          • 2. Re: Why
            eekboom Newbie

            Huh? That's exactly what I meant: The value of "embeddedEjb" is jardcoded to "false" in this snippet":

            "gavin.king@jboss.com" wrote:
            Here is a quote from the ant build:

            <filter token="embeddedEjb" value="false"/>

            In another place in the build file it's hardcoded to "true".

            So the value defined in component.properties is never used at all.

            When I build with my IDE the ant filter tokens in component.xml are not replaced, but Seam is clever enough to dynamically retrieve the values from component.properties, which makes seam want to use the embedded ejb container, which fails in JBoss.

            Not a big deal, but quite confusing.

            • 3. Re: Why
              Gavin King Master

              components.properties is ONLY used when running tests from within the IDE. Notice that this is what is hinted at in the documentation.