Deploying EJB under JBOSS-Tomcat bundle

Hi
I am trying to perform a proof of concept using a simple EJB. I have downloaded and installed the jboss-3.2.0RC1_tomcat-4.1.18 co-bundle. Now, can anyone tell me how I deploy my simple EJB under this? Is there any documentation or tutorial anywhere?
Currently I have copied the following directory structure into %JBOSS_HOME%\server\default\deploy
Login.war
    {jsp files}
    au
        com
            keytrust
                {class files}
    META-INF
        ejb-jar.xmlThis deploys without error, but gives me an exception "javax.naming.NameNotFoundException: ejb not bound" when I try to access the ejb.
Can anyone help me, or direct me to an appropriate reference?
Thanks
John

Hi.
Here is the session portion from one of my working ejb-jar.xml descriptors:
    <session>
      <display-name>ConferenceController</display-name>
      <ejb-name>ConferenceControllerEJB</ejb-name>
      <home>com.gumbtech.conf.ejb.ConferenceControllerHome</home>
      <remote>com.gumbtech.conf.ejb.ConferenceController</remote>
      <ejb-class>com.gumbtech.conf.ejb.ConferenceControllerBean</ejb-class>
      <session-type>Stateful</session-type>
      <transaction-type>Bean</transaction-type>
      <ejb-ref>
        <ejb-ref-name>ejb/ConferenceHome</ejb-ref-name>
        <ejb-ref-type>Entity</ejb-ref-type>
        <home>com.gumbtech.conf.ejb.ConferenceHome</home>
        <remote>com.gumbtech.conf.ejb.Conference</remote>
        <ejb-link>ConferenceEJB</ejb-link>
      </ejb-ref>
      <security-identity>
        <description></description>
        <run-as>
          <description></description>
          <role-name>admin</role-name>
        </run-as>
      </security-identity>
    </session>And the matching portion from it's sister jboss.xml descriptor:
  <session>
    <ejb-name>ConferenceControllerEJB</ejb-name>
    <jndi-name>ConferenceControllerHome</jndi-name>
    <ejb-ref>
      <ejb-ref-name>ejb/ConferenceHome</ejb-ref-name>
      <jndi-name>ejb.ConferenceHome</jndi-name>
    </ejb-ref>
    <ejb-ref>
      <ejb-ref-name>ejb/StatelessConferenceHome</ejb-ref-name>
      <jndi-name>ejb.StatelessConferenceHome</jndi-name>
    </ejb-ref>
    <resource-ref>
      <jndi-name>java:/OracleDS</jndi-name>
    </resource-ref>
  </session>After losing an entire head of hair over this, the only thing that worked for me, thanks to no documentation anywhere, was to ensure that the EJB portion of my ejb-name that you see below was present on the end of each and every bean I declared in my descriptors ...
<ejb-name>ConferenceControllerEJB</ejb-name>...and that this name was identical in both jboss.xml and ejb-jar.xml.
Notice too that the newer jboss uses dots instead of slashes in the jndi-name of another ejb I am referencing from my bean:
<jndi-name>ejb.ConferenceHome</jndi-name>You don't reference another bean yet, but if you do ...this will hang you for weeks as well until you get that dot in there.
Furthermore, I found was so paranoid by this point that I never again wavered from keeping the following naming convention for my class names (??):
The remote interface: MyThing
The bean implementation: MyThingBean
The home interface: MyThingHome
Then, finally ...the darn thing worked.
They use reflection maybe ?
Hope this might help.

Similar Messages

  • Jsp debugging under jboss/tomcat

    empty

    When you stop at a breakpoint you should be able the see the JSP page
    with a marker pointing to the current JSP line. In your case that should
    be maintenance/ad/adEdit.jsp
    Can you debug the demo application from NitroX on your server?
    What version (build number) of NitroX are you using?
    M7 Support
    [email protected] wrote:
    I am using jboss 3.2.5 with embedded tomcat 5.0.26I am able to set up a web project, set a breakpoint on my jsp page, and
    NitroX will stop at the breakpoint. However, it says it can't find the
    source for my jsp page (i.e. "The source of the type
    'org.apache.jsp.maintenance.ad.adEdit_jsp' could not be shown as the
    type was not found.")
    What do I need to do to get that to show up? Jboss/Tomcat makes a new
    temp folder each time the project is deployed, do I have to change it
    every time? I can't even get it to work by pointing the source folder
    to that temp folder.
    Thanks!

  • Deploying ejb in jboss

    I have a jboss 3 that deploys two entity beans and two session beans. the problem is that it keeps trying to deploy an old jar file that doesn't even exist. it's really weird. even though i delete from /tmp/deploy directory and default/deploy directory, it keeps trying to deploying an old file.. i don't even know where the heck this file is... i can't even find it
    but after i stop the server and restart the server, then it deploys the new jar file successfully... but it keeps deploying an old file when i try to redeploy it after i make a change on one of the files.
    does anybody know why?

    As far as I can remember there is a Cache setting somewhere....try looking up the Docs

  • Deploying  ejb in Jboss got error

    I have created the day05_signon.jar and META-INF directory and put it in default/deploy
    got error message day05_signon.jar
    status : null state fail
    watch day05_signon.jar
    am i doing anything wrong?pls advise

    I have created the day05_signon.jar and META-INF directory and put it in default/deploy
    got error message day05_signon.jar
    status : null state fail
    watch day05_signon.jar
    am i doing anything wrong?pls advise

  • Deploying BC4J as a session EJB in JBoss.Help while looking up

    Hello there,
    I have developed a simple bc4j component.I have deployed the
    same in Weblogic server5.1.I have to deploy the same thing in
    JBoss Server.I am using JBoss-Tomcat bundle(Jboss-2.2.2_Tomcat-
    3.2.2).I have deployed the BC4J component as a session bean in
    JBoss server(No erros while deploying)
    But the problem is when to call this session bean.To lookup the
    application module as is done in Weblogic the value for
    JboContext.DEPLOY_PLATFORM is given as JboContext.PLATFORM_WLS.
    This is taken to be specific to weblogic server.What is the
    value for this property for a JBossServer.
    Any help would be appreciated.Thanks a lot

    Hello there,
    I have developed a simple bc4j component.I have deployed the
    same in Weblogic server5.1.I have to deploy the same thing in
    JBoss Server.I am using JBoss-Tomcat bundle(Jboss-2.2.2_Tomcat-
    3.2.2).I have deployed the BC4J component as a session bean in
    JBoss server(No erros while deploying)
    But the problem is when to call this session bean.To lookup the
    application module as is done in Weblogic the value for
    JboContext.DEPLOY_PLATFORM is given as JboContext.PLATFORM_WLS.
    This is taken to be specific to weblogic server.What is the
    value for this property for a JBossServer.
    Any help would be appreciated.Thanks a lot

  • Is it possible to deploy EJBs onto Tomcat server

    Hi all,
    Please advice me if it is possible to deploy EJBs on the Tomcat Server.
    If so how to go about it?
    Thanks
    Ranjan

    No , it is not possible.Tomcat does not have a
    Ejb container.It only has a web container.
    Try using free servers like Sun One application server for
    deploying your ejb's.
    Get back in case of any issues

  • Deploy ejb in netbeans using jboss

    I would like to know the steps to deploy ejb using jboss in netbeans..or please suggest a site which gives the detailed steps for deployment.
    Thank you

    Google

  • Unable to deploy EJB 3.0 on JBoss 4.0.4GA - no home interface

    I am stuck in that my EJB3.0 project (one entity bean, one session bean and one client test bean) builds OK but somehow Eclipse Europa is unable to deploy it to JBoss (4.0.4 GA and 5 Beta) -- something to do with JNDI error as it involves javax.naming exceptions.
    My Eclipse directory structure is :-
    Titan (project name)
    |
    ejb - com.titan (package name)
    | |
    | domain -> Cabin.java (my entity bean)
    | |
    | travelagent -> TravelAgentBean.java
    | -> TravelAgentRemote.java
    |
    META_INF -> ejb-jar.xml
    -> MANIFEST.MF
    -> persistence.xml
    My ejb-jar.xml is :
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
    <display-name>Titan</display-name>
    <enterprise-beans>
    <!-- Session Beans -->
    <session >
    <display-name>TravelAgentBean</display-name>
    <ejb-name>com/titan/travelagent/ejb/TravelAgentBean</ejb-name>
    <remote>com.titan.travelagent.ejb.TravelAgentRemote</remote>
    <ejb-class>com.titan.travelagent.ejb.TravelAgentBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    </ejb-jar>
    And my persistence.xml is :
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
    <persistence-unit name="Titan">
    <provider>org.hibernate.ejb.HibernatePersistence</provider>
    <class>com.titan.domain.Cabin</class>
    <properties>
    <property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver" />
    <property name="hibernate.connection.url"
    value="jdbc:oracle:thin:@localhost:1521:XE" />
    <property name="hibernate.connection.username" value="SYSTEM" />
    <property name="hibernate.connection.password" value="Swordfish1" />
    </properties>
    </persistence-unit>
    </persistence>
    I right-click on the Titan project name and choose Build Project. I get the following error message :-
    13:01:06,046 WARN [verifier] EJB spec violation:
    Bean : com/titan/travelagent/TravelAgentBean
    Section: 7.11.2
    Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
    13:01:06,046 WARN [verifier] EJB spec violation:
    Bean : com/titan/travelagent/TravelAgentBean
    Section: 7.11.3
    Warning: A Session bean must define at least one ejbCreate method.
    13:01:06,046 WARN [verifier] EJB spec violation:
    Bean : com/titan/travelagent/TravelAgentBean
    Section: 7.11.1
    Warning: The session bean must implement either a remote home and remote, or a local home and a local interface or a service endpoint interface.
    13:01:06,062 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/Titan.jar
    I don't understand, because as of EJB 3.0, you don't really need a home or local-home interface anymore...

    Using @SecurityDomain("exemplo1") in my EJB and NOT providing jboss.xml, it works.
    @SecurityDomain("exemplo1")
    @RolesAllowed("yyy")
    @Stateless(name="UserManagement")
    public class UserManagementBean implements UserManagement {
      public void add(User user) {
    }Damn! This is some serious shit... I don�t want to configure this in every single EJB.
    EJB 3.0 is nice, but some small trivial details like this and others, that was forgotten by Sun, piss me off!

  • Error at the time of Deploying EJB  jar on JBoss

    Hi:
    I am going to create web service using EJB3.0.
    But at the time deploying file on JBOss i am getting following error:
    12:22:51,856 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar state=PreReal mode=Manual requiredState=Real
    org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar
         at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175)
         at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
         at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
         at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
         at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
         at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:265)
         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:143)
         at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
         at org.jboss.Main.boot(Main.java:209)
         at org.jboss.Main$1.run(Main.java:544)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
         at java.lang.String.substring(String.java:1938)
         at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:533)
         at org.jboss.ws.metadata.wsdl.WSDLUtils.getTypeNamespace(WSDLUtils.java:700)
         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processWebService(JAXWSWebServiceMetaDataBuilder.java:313)
         at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:107)
         at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
         at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:76)
         at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:70)
         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.start(DeploymentAspectManagerImpl.java:144)
         at org.jboss.wsf.container.jboss50.BareWSFRuntime.start(BareWSFRuntime.java:66)
         at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:48)
         at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
         at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:115)
         at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
         ... 18 more
    12:22:51,897 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
    *** CONTEXTS IN ERROR: Name -> Error
    vfszip:/home/crayom/projects/tools/jboss-5.0.0.CR2/server/default/deploy/TempConvert.jar -> java.lang.StringIndexOutOfBoundsException: String index out of range: -1So, can any body tell me the solution of this problem?
    Thank You.

    AnupDesai wrote:
    Hi:
    After adding require packages also i am getting the same error.
    Well, if it's not a version problem with either the JDK (installing java 6 on top of a java 5 distribution) or the Jars (like JAXB) , then , as pointed out, you might have written your Web service using a packageless class:
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1
         at java.lang.String.substring(String.java:1938)
         at org.jboss.wsf.common.JavaUtils.getPackageName(JavaUtils.java:533)Restart a new project in your IDE with a packaged ws from the start, and see if it works.

  • Jboss/tomcat mapping configuration error

    I can't even get the combination to serve a .jsp file or .html file. Regardless of the URL that I attempt, I only get a No Context configured to process this request error from tomcat and INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI from JBoss. I've tried to access all of the various webapps under the catalina directory and can't get to any of them. I know that catalina is started because the log file shows
    <Service name="JBoss-Tomcat">
    <Engine name="MainEngine" defaultHost="localhost">
    <Logger className="org.jboss.web.catalina.Log4jLogger" verbosityLevel="trace" category="org.jboss.web.localhost.Engine" />
    <Host name="localhost">
    <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="localhost_access" suffix=".log" pattern="common" directory="../server/default/log" />
    <DefaultContext cookies="true" crossContext="true" override="true" />
    </Host>
    </Engine>
    <!-- A HTTP Connector on port 8080 -->
    <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8080" minProcessors="3" maxProcessors="10" enableLookups="true" acceptCount="10" debug="0" connectionTimeout="60000" />
    </Service>
    </Server> in jboss.web:service=EmbeddedCatalinaSX
    2002-06-12 23:29:44,760 INFO [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Creating
    2002-06-12 23:29:44,760 INFO [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Created
    2002-06-12 23:29:44,760 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying tomcat4-service.xml
    2002-06-12 23:29:44,760 DEBUG [org.jboss.deployment.MainDeployer] start step for deployment file:/D:/JBoss3.0/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/tomcat4-service.xml
    2002-06-12 23:29:44,760 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/D:/JBoss3.0/jboss-3.0.0_tomcat-4.0.3/server/default/deploy/tomcat4-service.xml
    2002-06-12 23:29:44,760 INFO [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Starting
    2002-06-12 23:29:44,760 INFO [org.jboss.deployment.MainDeployer] Adding deployer: org.jboss.web.catalina.EmbeddedCatalinaServiceSX@7dadcd
    2002-06-12 23:29:44,760 DEBUG [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Setting catalina debug level to: 0
    2002-06-12 23:29:44,760 DEBUG [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Setting catalina.home to: ../catalina
    2002-06-12 23:29:44,760 DEBUG [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] Setting catalina.base to: ../catalina
    with no errors. I'm confused because I was able to consistently work with previous versions of JBoss with no problem. The configuration seems to have changed radically, is this some recent change that I just can't find a reference to? Thanks for any help.

    Hi
    For Tomcat 3.x you need to use one of the following options:
    (Note: this is with JBoss/Tomcat OR JBoss/Jetty)
    Place you .war files in the following location:
    C:\jboss-3.0.3\server\default\deploy and the app is automatically available.
    If my app's name is DavidOnline.war, when deployed, I can access it at
    http://localhost:8080/DavidOnline..
    OR
    Copy your entire development directory to the deploy direction above, RENAME your
    directory from say C:\JspApps to C:\JspApps.war and you can work from that location and see your changes immeadiatly.
    There is a file called jboss-service.xml that has some config options, also for the Tomcat bundle there is a file named tomcat-service.xml that has the standard server.xml section.. I suggest you check out the JBoss website, free docs and forums.. http://www.jboss.org.
    Thanks, Hope this helps.

  • JBoss & Tomcat: Which one?

    Hi,
    I'd like to hear from you guys about what I am thinking. I have JBoss AS do I need to install Tomcat? Or it is bundled already? Because I don't have any idea where I will put my development files / programs in JBoss. And also can someone helped me where to start? A good tutorial link in J2EE / JBoss configuration.
    Thanks a lot! Hope to hear from you guys!

    Hi guys,
    Btw, I tried using it now (Netbeans 5.5 and JBoss 4) but when I compiled it. I ran into some problems. Here is the complete compiling info of my project.
    pre-init:
    init-private:
    init-userdir:
    init-user:
    init-project:
    do-init:
    post-init:
    init-check:
    init:
    deps-jar:
    deps-j2ee-archive:
    init:
    deps-jar:
    Created dir: C:\Applications\TBK-EA\TBK-EA-ejb\build\jar
    Created dir: C:\Applications\TBK-EA\TBK-EA-ejb\build\ear-module
    Copying 3 files to C:\Applications\TBK-EA\TBK-EA-ejb\build\ear-module\META-INF
    compile:
    library-inclusion-in-manifest:
    Created dir: C:\Applications\TBK-EA\TBK-EA-ejb\dist
    Building jar: C:\Applications\TBK-EA\TBK-EA-ejb\dist\TBK-EA-ejb.jar
    dist-ear:
    init:
    deps-module-jar:
    deps-ear-jar:
    init:
    deps-jar:
    compile:
    library-inclusion-in-manifest:
    dist-ear:
    deps-jar:
    Created dir: C:\Applications\TBK-EA\TBK-EA-war\build\ear-module\WEB-INF\classes
    Created dir: C:\Applications\TBK-EA\TBK-EA-war\build\ear-module\META-INF
    Copying 1 file to C:\Applications\TBK-EA\TBK-EA-war\build\ear-module\META-INF
    Copying 3 files to C:\Applications\TBK-EA\TBK-EA-war\build\ear-module
    library-inclusion-in-archive:
    library-inclusion-in-manifest:
    Copying 1 file to C:\Applications\TBK-EA\build
    compile:
    compile-jsps:
    do-ear-dist:
    Created dir: C:\Applications\TBK-EA\TBK-EA-war\dist
    Building jar: C:\Applications\TBK-EA\TBK-EA-war\dist\TBK-EA-war.war
    dist-ear:
    pre-pre-compile:
    Created dir: C:\Applications\TBK-EA\build\jar
    pre-compile:
    do-compile:
    Copying 3 files to C:\Applications\TBK-EA\build\META-INF
    Copying 1 file to C:\Applications\TBK-EA\build
    post-compile:
    compile:
    pre-dist:
    do-dist-without-manifest:
    do-dist-with-manifest:
    Created dir: C:\Applications\TBK-EA\dist
    Building jar: C:\Applications\TBK-EA\dist\TBK-EA.ear
    post-dist:
    dist:
    pre-run-deploy:
    Starting server JBoss Application Server 4
    Starting JBoss Application Server 4
    Starting JBoss Application Server 4
    JBoss Application Server 4 Started
    Distributing C:\Applications\TBK-EA\dist\TBK-EA.ear to [org.jboss.deployment.spi.LocalhostTarget@6f54e]
    Deploying C:\Applications\TBK-EA\dist\TBK-EA.ear
    Deploying C:\Applications\TBK-EA\dist\TBK-EA.ear
    Waiting for server to start the module http://localhost:7000/TBK-EA-war
    Applicaton Deployed
    Operation start started
    Operation start completed
    post-run-deploy:
    run-deploy:
    Browsing: http://localhost:7000/TBK-EA-war/
    run-display-browser:
    run-ac:
    run:
    BUILD SUCCESSFUL (total time: 5 minutes 26 seconds)
    Not after that my browser opened and I got:
    HTTP Status 404 - /TBK-EA-war/
    type Status report
    message /TBK-EA-war/
    description The requested resource (/TBK-EA-war/) is not available.
    Apache Tomcat/5.5.20
    What's the problem here? Pls. help me. Thanks!

  • How to deploy EAR file in Tomcat?

    Is we can deploy ear file in tomcat?
    Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
    But samethink I have tried EAR file. But it is not working.
    Is we can deploy EAR file or not?
    If not plz give reason.

    Hi
    Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
    The Tomcat Servlet/JSP Container      
    The Apache Tomcat 5.5 Servlet/JSP Container
         Apache Logo
    Links
    * Docs Home
    Contents
    * Contents
    * Introduction
    * Installation
    * Deployment
    * Source Code
    * Processes
    * Example App
    Application Developer's Guide
    Deployment
         Printer Friendly Version
    print-friendly
    version
    Background
    Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
    A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
    The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
    Standard Directory Layout
    To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
    * *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
    * /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
    * /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
    * /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
    When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
    Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
    Shared Library Files
    Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
    * $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
    * $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
    Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
    * The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
    * An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
    Web Application Deployment Descriptor
    The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
    As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
    The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
    NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
    Tomcat Context Descriptor
    The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
    A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
    Deployment With Tomcat 5
    In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
    * Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
    * Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
    * Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
    * Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
    * Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
    Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
    Copyright © 1999-2006, Apache Software Foundation

  • Delay in AJP Connector jBoss/TomCat Solaris 10

    I have:
    - IIS 6, Windows 2003 Server on dual PIII with jk 1.2.15 installed and working
    - Solaris 10 on Sun E420R with Quad Processors with jBoss / Tomcat version 4.0.3SP1
    There is a significant delay in page loading that occurs randomly (every 10-20 clicks) which lasts for 10-18 or so seconds.
    I've traced it to the read method in ChannelSocket.java. The delay always occurs while receive() is reading the header portion of the message. The length of the header that the read is trying to read is 4 bytes. The call to BufferedInputStream will block until it gets these 4 bytes of the header (10-18 seconds). I've modified the code and put a call in to available() before and after the read. The before returns 0 and the after returns 1138 or so.
    I've tried every imaginable combination of configs on the IIS side to get around the problem ... and then some kernel TCP/IP configs on the Solaris side ... too many to list here.
    The problem seems to be isolated to Solaris ... because Linux, XP, Windows 2003 server all work without this problem.
    My question is this ... is there any thing that I can configure to have this read return faster? Changes to the Solaris kernel ... some config parameter ... ?? Anyone experience this before?
    I'll gladly list the things I've tried to get some idea of how to solve this.
    I think ultimately this is my problem: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4479751
    Thanks in advance!

    Hi
    For Tomcat 3.x you need to use one of the following options:
    (Note: this is with JBoss/Tomcat OR JBoss/Jetty)
    Place you .war files in the following location:
    C:\jboss-3.0.3\server\default\deploy and the app is automatically available.
    If my app's name is DavidOnline.war, when deployed, I can access it at
    http://localhost:8080/DavidOnline..
    OR
    Copy your entire development directory to the deploy direction above, RENAME your
    directory from say C:\JspApps to C:\JspApps.war and you can work from that location and see your changes immeadiatly.
    There is a file called jboss-service.xml that has some config options, also for the Tomcat bundle there is a file named tomcat-service.xml that has the standard server.xml section.. I suggest you check out the JBoss website, free docs and forums.. http://www.jboss.org.
    Thanks, Hope this helps.

  • Deploying EJBs [b]not[/b] in an EAR

    Is it possible to deploy EJBs in 9.0.3 without the EJB jars belonging to an EAR? It looks like the deployment tools can handle deploying EARs and WARs only. The reason I ask is that I'm looking into porting a large component based EJB/web service application that currently runs in JBoss. Under JBoss, the EJBs are deployed in jars and the web services in WARs. Shared classes are deployed into the lib directory. I realize this is non-standard, but it facilitates development and administration since individual components (EJBs) can be added or redeployed without redeploying the whole EAR. Our business model is to build solutions (application) out of components and it would be somewhat painful to have to create and maintain very large EAR files for each solution.

    Hi Jeff,
    I believe the recommended way to do this in OC4J is to build a hierarchy of parent (and child) applications. Make an EAR (i.e. application) that only contains EJBs, and make it the parent application of your web services application. You can find more details in the documentation.
    Good Luck,
    Avi.

  • Application Deployment Issue on JBoss 4.2.3

    Hi,
    I am trying to deploy a Java Application on JBoss 4.2.3 AS. This application run seamlessly on JBoss 3.0.5. After deploying, I could see errors below.
    Could any one please suggest what could be the issue? Were there any changes in the deployment file structure? Please advice.
    Thanks,
    2009-09-29 15:43:41,112 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,128 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,165 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,177 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,198 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,208 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
    org.jboss.deployment.DeploymentException: expected one container-name tag
    2009-09-29 15:43:41,256 ERROR [org.jboss.system.server.Server] Root deployment has missing dependencies; continuing
    Incomplete Deployment listing:
    --- Incompletely deployed packages ---
    org.jboss.deployment.DeploymentInfo@cad26b26 { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar }
    deployer: org.jboss.ejb.EJBDeployer@ab835a
    status: Deployment FAILED reason: expected one container-name tag
    state: FAILED
    watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar
    altDD: null
    lastDeployed: 1254203021081
    lastModified: 1254203019961
    mbeans:
    org.jboss.deployment.DeploymentInfo@7888101a { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar }
    deployer: org.jboss.ejb.EJBDeployer@ab835a
    status: Deployment FAILED reason: expected one container-name tag
    state: FAILED
    watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar
    altDD: null
    lastDeployed: 1254203021154
    lastModified: 1254203020008
    mbeans:
    org.jboss.deployment.DeploymentInfo@8d818653 { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar }
    deployer: org.jboss.ejb.EJBDeployer@ab835a
    status: Deployment FAILED reason: expected one container-name tag
    state: FAILED
    watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar
    altDD: null
    lastDeployed: 1254203021190
    lastModified: 1254203020008
    mbeans:
    --- MBeans waiting for other MBeans ---
    ObjectName: jboss:service=invoker,type=jrmp
    State: FAILED
    Reason: java.lang.AbstractMethodError: org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(Ljava/lang/String;)V
    I Depend On:
    jboss:service=TransactionManager
    ObjectName: jboss:service=invoker,type=http
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss:service=invoker,type=httpHA
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss:service=invoker,type=http,target=Naming
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss:service=invoker,type=http,target=Naming,readonly=true
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss.jca:service=LocalTxCM,name=hsqldbDS
    State: CONFIGURED
    I Depend On:
    jboss.jca:service=LocalTxDS,name=hsqldbDS
    jboss.jca:service=LocalTxPool,name=hsqldbDS
    jboss.jca:service=CachedConnectionManager
    jboss.security:service=JaasSecurityManager
    jboss.jca:service=RARDeployer
    ObjectName: jboss.jca:service=LocalTxDS,name=hsqldbDS
    State: CONFIGURED
    I Depend On:
    jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
    jboss:service=Hypersonic
    Depends On Me:
    jboss.jca:service=LocalTxCM,name=hsqldbDS
    ObjectName: jboss.jca:service=XaTxCM,name=jmsra
    State: CONFIGURED
    I Depend On:
    jboss.jca:service=RARDeployer
    jboss.jca:service=XaTxDS,name=jmsra
    jboss.jca:service=XaTxPool,name=jmsra
    jboss.jca:service=CachedConnectionManager
    jboss.security:service=JaasSecurityManager
    ObjectName: jboss.jca:service=XaTxDS,name=jmsra
    State: CONFIGURED
    I Depend On:
    jboss.jca:service=RARDeployment,name=JMS Adapter
    Depends On Me:
    jboss.jca:service=XaTxCM,name=jmsra
    --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
    ObjectName: jboss.jca:service=RARDeployment,name=JMS Adapter
    State: NOTYETINSTALLED
    Depends On Me:
    jboss.jca:service=XaTxDS,name=jmsra
    ObjectName: jboss:service=invoker,type=http
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss:service=invoker,type=http,target=Naming,readonly=true
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss:service=invoker,type=jrmp
    State: FAILED
    Reason: java.lang.AbstractMethodError: org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(Ljava/lang/String;)V
    I Depend On:
    jboss:service=TransactionManager
    ObjectName: jboss:service=invoker,type=http,target=Naming
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
    ObjectName: jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
    State: NOTYETINSTALLED
    Depends On Me:
    jboss.jca:service=LocalTxDS,name=hsqldbDS
    ObjectName: jboss:service=invoker,type=httpHA
    State: FAILED
    Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;

    continued....
    <!-- ==================================================================== -->
      <!-- Security                                                             -->
      <!-- ==================================================================== -->
      <mbean code="org.jboss.security.plugins.SecurityConfig"
          name="jboss.security:name=SecurityConfig">
        <attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute>
      </mbean>
      <mbean code="org.jboss.security.auth.login.XMLLoginConfig"
          name="jboss.security:service=XMLLoginConfig">
        <attribute name="ConfigResource">login-config.xml</attribute>
      </mbean>
      <!-- JAAS security manager and realm mapping -->
      <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
          name="jboss.security:service=JaasSecurityManager">
        <attribute name="SecurityManagerClassName">
          org.jboss.security.plugins.JaasSecurityManager
        </attribute>
      </mbean>
      <!-- ==================================================================== -->
      <!-- Transactions                                                         -->
      <!-- ==================================================================== -->
      <mbean code="org.jboss.tm.XidFactory"
          name="jboss:service=XidFactory">
      </mbean>
      <mbean code="org.jboss.tm.TransactionManagerService"
          name="jboss:service=TransactionManager">
        <attribute name="TransactionTimeout">300</attribute>
        <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
      </mbean>
      <!--
         | Uncomment to use Tyrex (tyrex.exolab.org) transaction manager plugin
         | instead of the org.jboss.tm.TransactionManagerService and comment out
         | the TransactionManagerService above.
         | Make sure you have Xerces in lib/. At the moment JBoss does not
         | ship Xerces as part of distribution. Version 1.x seems to work fine,
         | though 2.x should as well, use whichever you like.
         |
      <mbean code="org.jboss.tm.plugins.tyrex.TransactionManagerService"
             name="jboss:service=TransactionManager">
            <attribute name="ConfigFileName">../conf/default/domain.xml</attribute>
      </mbean>
      -->
      <!--commented to run grmbs on JBoss 4.2.3, comment removed -->
      <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
          name="jboss:service=ClientUserTransaction">
      </mbean>
      <!-- The CachedConnectionManager is used partly to relay started UserTransactions to
        open connections so they may be enrolled in the new tx-->
      <mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager" name="jboss.jca:service=CachedConnectionManager">
      </mbean>
      <!-- ==================================================================== -->
      <!-- The deployers...                                                     -->
      <!-- ==================================================================== -->
      <!-- Main Deployer and SARDeployer are provided by main -->
      <!-- EJB deployer, remove to disable EJB behavior-->
      <mbean code="org.jboss.ejb.EJBDeployer" name="jboss.ejb:service=EJBDeployer">
        <attribute name="VerifyDeployments">true</attribute>
        <attribute name="ValidateDTDs">false</attribute>
        <attribute name="MetricsEnabled">false</attribute>
        <attribute name="VerifierVerbose">true</attribute>
        <!-- Add a dependency on the JMS provider(jms-service.xml) for MDBs. If
          you are not using MDBs and JMS remove these.
        -->
        <depends>jboss.mq:service=JMSProviderLoader,name=JBossMQProvider</depends>
        <depends>jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool</depends>
      </mbean>
      <!-- EAR deployer -->
      <mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer">
      </mbean>
      <!-- WAR Deployer is provided by tomcat or jetty -->
      <!-- RAR Deployer is provided by the rar.sar package -->
      <!-- Uncomment to activate the BeanShell script sub-deployer --> 
      <!--mbean code="org.jboss.varia.deployment.BeanShellSubDeployer"
               name="jboss.scripts:service=BSHDeployer">
      </mbean-->
      <!-- ==================================================================== -->
      <!-- JBoss Server Management                                              -->
      <!-- ==================================================================== -->
      <!-- ==================================================================== -->
      <!-- Monitoring and Management                                            -->
      <!-- ==================================================================== -->
      <!-- Uncomment to enable JMX monitoring of the entity bean locking
      <mbean code="org.jboss.monitor.EntityLockMonitor"
             name="jboss.monitor:name=EntityLockMonitor"/>
      -->
      <!-- ==================================================================== -->
      <!-- Invokers to the JMX node                                             -->
      <!-- ==================================================================== -->
      <!-- RMI/JRMP invoker -->
      <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
             name="jboss:service=invoker,type=jrmp">
        <attribute name="RMIObjectPort">4444</attribute>
        <attribute name="ServerAddress">${jboss.bind.address}</attribute>
        <attribute name="RMIClientSocketFactory">custom</attribute>
        <attribute name="RMIServerSocketFactory">custom</attribute>
        <attribute name="RMIServerSocketAddr">custom</attribute>
        <!-- Added as per JBoss 4.2.3 Server defaults, starts -->
         <depends>jboss:service=TransactionManager</depends>
        <!-- Added as per JBoss 4.2.3 Server defaults, ends -->
      </mbean>
      <mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
             name="jboss:service=invoker,type=pooled">
      </mbean>
      <mbean code="org.jboss.invocation.local.LocalInvoker"
             name="jboss:service=invoker,type=local">
      </mbean>
      <!-- ==================================================================== -->
      <!-- Deployment Scanning                                                  -->
      <!-- ==================================================================== -->
      <!-- Uncomment to enable caching of deployment units
      <mbean code="org.jboss.deployment.cache.FileDeploymentStore"
          name="jboss.deployment:type=DeploymentStore,flavor=File">
        <attribute name="DirectoryName">data/deployment-cache</attribute>
      </mbean>
      <mbean code="org.jboss.deployment.cache.DeploymentCache"
          name="jboss.deployment:type=DeploymentCache">
        <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
        <depends optional-attribute-name="Store">jboss.deployment:type=DeploymentStore,flavor=File</depends>
      </mbean>
      -->
      <!-- An mbean for hot deployment/undeployment of archives.
      -->
      <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
          name="jboss.deployment:type=DeploymentScanner,flavor=URL">
        <!-- Uncomment (and comment/remove version below) to enable usage of the
          DeploymentCache
        <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
        -->
        <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>

Maybe you are looking for

  • Paste in browse tab

    When I select one of the browse tabs for a piece of code and try to paste into the page (like in a text area), the paste may work depending on browser type (worked in IE tab, not firefox tab) but it also pastes in the source.

  • How to add an INK SIGNATURE

    Previous versions allowed the ability to add an INK SIGNATURE. In addition, the PLACE RECTANGLE box could be moved around and resized to fit the form. Have we gone backwards??

  • Emacs c-mode-hook no longer works?

    I just did a pacman -Syu and c-mode-hook doesn't seem to get triggered anymore in emacs.  I tried adding a hook with just a print statement and it never printed anything.  Did the same for text-mode-hook and it printed out just fine.  I'm using c-mod

  • Ram choice for K8T Neo FISR2 Motherboard

    Can anyone tell me if this particular model of ram is compatible with the k8t neo fisr2 motherboard? http://www.crucial.com/store/MPartspecs.Asp?mtbpoid=AC1B73A7A5CA7304&WSMD=MS%2D6702+%28K8T+Neo%2DFIS2R%29&WSPN=CT6464Z40B according to crucial it is

  • How to create a line in flash action script 3.0

    i am trying to create a line that can be draggable and  extedable from start and end points of line. some one help plzz