-
1. Re: Fibo-tutorial -- I cannot run it???
babaxter1 Jan 30, 2006 6:43 AM (in response to jdidboss)Make sure the following configuration files
- application.xml
- ejb-jar.xml
- jboss.xml
- jboss-web.xml
- web.xml
have appropriate settings.
---------- application.xml -----------<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd"> <application> <display-name>Sum Application</display-name> <module> <ejb>FiboEJB.jar</ejb> </module> <module> <web> <web-uri>FiboWeb.war</web-uri> <context-root>/fibo</context-root> </web> </module> </application>
---------- ejb-jar.xml -----------<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> <ejb-jar > <description><![CDATA[No Description.]]></description> <display-name>Generated by XDoclet</display-name> <enterprise-beans> <!-- Session Beans --> <session > <description><![CDATA[Description for Fibo]]></description> <display-name>Name for Fibo</display-name> <ejb-name>Fibo</ejb-name> <home>tutorial.interfaces.FiboHome</home> <remote>tutorial.interfaces.Fibo</remote> <ejb-class>tutorial.ejb.FiboBean</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> <!-- To add session beans that you have deployment descriptor info for, add a file to your XDoclet merge directory called session-beans.xml that contains the <session></session> markup for those beans. --> <!-- Entity Beans --> <!-- To add entity beans that you have deployment descriptor info for, add a file to your XDoclet merge directory called entity-beans.xml that contains the <entity></entity> markup for those beans. --> <!-- Message Driven Beans --> <!-- To add message driven beans that you have deployment descriptor info for, add a file to your XDoclet merge directory called message-driven-beans.xml that contains the <message-driven></message-driven> markup for those beans. --> </enterprise-beans> <!-- Relationships --> <!-- Assembly Descriptor --> <!-- To specify your own assembly descriptor info here, add a file to your XDoclet merge directory called assembly-descriptor.xml that contains the <assembly-descriptor></assembly-descriptor> markup. --> <assembly-descriptor > <!-- To specify additional security-role elements, add a file in the merge directory called ejb-security-roles.xml that contains them. --> <!-- method permissions --> <!-- To specify additional method-permission elements, add a file in the merge directory called ejb-method-permissions.ent that contains them. --> <!-- transactions --> <!-- To specify additional container-transaction elements, add a file in the merge directory called ejb-container-transactions.ent that contains them. --> <!-- finder transactions --> <!-- message destinations --> <!-- To specify additional message-destination elements, add a file in the merge directory called ejb-message-destinations.ent that contains them. --> <!-- exclude list --> <!-- To specify an exclude-list element, add a file in the merge directory called ejb-exclude-list.xml that contains it. --> </assembly-descriptor> </ejb-jar>
---------- jboss.xml -----------<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd"> <jboss> <enterprise-beans> <!-- To add beans that you have deployment descriptor info for, add a file to your XDoclet merge directory called jboss-beans.xml that contains the <session></session>, <entity></entity> and <message-driven></message-driven> markup for those beans. --> <session> <ejb-name>Fibo</ejb-name> <jndi-name>ejb/Fibo</jndi-name> </session> <!-- write a merge file jboss-webservices.ent for webservice-description --> </enterprise-beans> <resource-managers> </resource-managers> <!-- | for container settings, you can merge in jboss-container.xml | this can contain <invoker-proxy-bindings/> and <container-configurations/> --> </jboss>
---------- jboss-web.xml -----------<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.3//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_3_0.dtd"> <jboss-web> <!-- Resource Environment References --> <!-- For additional resouce-env-ref tags add a merge file called jbossweb-resource-env-ref.xml --> <!-- Resource references --> <!-- For additional resouce-ref tags add a merge file called jbossweb-resource-ref.xml --> <!-- EJB References --> <!-- For additional ejb-ref tags add a merge file called jbossweb-ejb-ref.xml --> <ejb-ref> <ejb-ref-name>ejb/Fibo</ejb-ref-name> <jndi-name>ejb/Fibo</jndi-name> </ejb-ref> <!-- EJB Local References --> </jboss-web>
---------- web.xml -----------<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app > <distributable/> <!-- To use non XDoclet filters, create a filters.xml file that contains the additional filters (eg Sitemesh) and place it in your project's merge dir. Don't include filter-mappings in this file, include them in a file called filter-mappings.xml and put that in the same directory. --> <!-- To use non XDoclet filter-mappings, create a filter-mappings.xml file that contains the additional filter-mappings and place it in your project's merge dir. --> <!-- To use non XDoclet listeners, create a listeners.xml file that contains the additional listeners and place it in your project's merge dir. --> <servlet> <servlet-name>Compute</servlet-name> <display-name>Computation Servlet</display-name> <description><![CDATA[Servlet that compute Fibonacci suite]]></description> <servlet-class>tutorial.web.ComputeServlet</servlet-class> </servlet> <!-- To use non XDoclet servlets, create a servlets.xml file that contains the additional servlets (eg Struts) and place it in your project's merge dir. Don't include servlet-mappings in this file, include them in a file called servlet-mappings.xml and put that in the same directory. --> <servlet-mapping> <servlet-name>Compute</servlet-name> <url-pattern>/Compute</url-pattern> </servlet-mapping> <!-- To specify mime mappings, create a file named mime-mappings.xml, put it in your project's mergedir. Organize mime-mappings.xml following this DTD slice: <!ELEMENT mime-mapping (extension, mime-type)> --> <!-- To specify error pages, create a file named error-pages.xml, put it in your project's mergedir. Organize error-pages.xml following this DTD slice: <!ELEMENT error-page ((error-code | exception-type), location)> --> <!-- To add taglibs by xml, create a file called taglibs.xml and place it in your merge dir. --> <!-- To set up security settings for your web app, create a file named web-security.xml, put it in your project's mergedir. Organize web-security.xml following this DTD slice: <!ELEMENT security-constraint (display-name?, web-resource-collection+, auth-constraint?, user-data-constraint?)> <!ELEMENT web-resource-collection (web-resource-name, description?, url-pattern*, http-method*)> <!ELEMENT web-resource-name (#PCDATA)> <!ELEMENT url-pattern (#PCDATA)> <!ELEMENT http-method (#PCDATA)> <!ELEMENT user-data-constraint (description?, transport-guarantee)> <!ELEMENT transport-guarantee (#PCDATA)> <!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)> <!ELEMENT auth-method (#PCDATA)> <!ELEMENT realm-name (#PCDATA)> <!ELEMENT form-login-config (form-login-page, form-error-page)> <!ELEMENT form-login-page (#PCDATA)> <!ELEMENT form-error-page (#PCDATA)> --> <ejb-ref > <description><![CDATA[Reference to the Fibo EJB]]></description> <ejb-ref-name>ejb/Fibo</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <home>tutorial.interfaces.FiboHome</home> <remote>tutorial.interfaces.Fibo</remote> </ejb-ref> </web-app>
Hope this helps you to fix your problem. -
2. Re: Fibo-tutorial -- I cannot run it???
jdidboss Jan 30, 2006 7:01 PM (in response to jdidboss)baxter -- I still cannot run the Fibo-tutorial app.
I checked (as well as I can) that the values appear as in the code you sent to me (seeing that most of the text are "comment-to-do"). I did find some small differences in values for ejb-jar.xml for "description" and "display-name" but I changed them anyway as per the CODE. I found and fixed the text-values and performed a RUN-XDoclet. I re-ran the RUN-Packaging and deployed the FiboApp.ear entered the localhost url and receive the same 404-message as indicated in my original email.
Here is my question...how does the localhost url get resolved to find "fibo" in the JBoss Appsrvr since localhost will resolve to ROOT.war.
Is it possible that the deployment places FiboApp.ear in the "wrong" place?
I know I am missing a detail or kernel of knowledge -- but which detail am I missing.
Please RSVP -- thanks...John -
3. Re: Fibo-tutorial -- I cannot run it???
jdidboss Jan 31, 2006 9:31 AM (in response to jdidboss)I think I found the "problem" but need some help here...
Upon EAR deployment from the IDE, we get this error...
08:57:13,593 ERROR [MainDeployer] Could not initialise deployment:
file:/C:/J2EE/JBoss/jboss-4.0.3SP1/server/default/deploy/FiboApp.ear
org.jboss.deployment.DeploymentException: Failed to find module file: FiboEBJ.jar
However, the FiboEBJ.jar is packed within the FiboApp.ear
and the EAR was sent to the jboss-server-deploy folder.
Is there some differences with v1.3 and v1.4 of the J2EE libraries?
I am using v1.4 J2EE BUT the tutorial indicates that
we should be selecting v1.3 EAR Deployment Descriptor
(I am using v1.3 EAR-DeplDescr).
Thanks in advance. -
4. SOLVED Re: Fibo-tutorial -- I cannot run it???
jdidboss Jan 31, 2006 11:31 AM (in response to jdidboss)OK -- I made a typing error and entered FiboEBJ.jar by mistake.
Should have been FiboEJB.jar in the application.xml.
I apologize for clogging up the forum.
Thanks, anyway. -
5. Re: Fibo-tutorial -- I cannot run it???
carl.patterson Jan 31, 2006 3:44 PM (in response to jdidboss)I ran into the same symptom - but found that my FiboApp.ear file had only application.xml. When I manually added the ejb and war archives, it worked fine.
I've gone over the relevant pieces - the application.xml is fine and I double checked what I did throughout the chapter on packaging. It really looks like the non-existence FiboEJB.jar and FiboWeb.war cause a problem.
Even when I delete the (mostly empty) .ear file and re-run packaging, however, I still see the same problem.
Here's a copy of the packaging-build.xml file, which I suspect from the above has to indicate the problem
<?xml version="1.0" encoding="UTF-8"?>
I'm using JBoss-4.0.3SP1 and eclipse 3.1.1 with JBossIDE 1.5 - updated either 28 or 29-Jan,
I'd appreciate any help,
carl -
6. Re: Fibo-tutorial -- I cannot run it???
carl.patterson Jan 31, 2006 3:54 PM (in response to jdidboss)All,
my apologies about that last post having an empty xml file
It's[list=]<?xml version="1.0" encoding="UTF-8"?> <project name="Packaging Generator" default="_packaging_generation_"> <target name="_packaging_generation_" depends="N65540,N65573,N65616"/> <target name="N65540" description="FiboEJB.jar"> <jar destfile="FiboEJB.jar"> <zipfileset dir="src/META-INF" prefix="META-INF"> <include name="ejb-jar.xml"/> </zipfileset> <zipfileset dir="src/META-INF" prefix="META-INF"> <include name="jboss.xml"/> </zipfileset> <zipfileset dir="bin" includes="tutorial/ejb/*.class,tutorial/interfaces/*.class"/> </jar> </target> <target name="N65573" description="FiboWeb.war"> <jar destfile="FiboWeb.war"> <zipfileset dir="src/WEB-INF" prefix="WEB-INF"> <include name="web.xml"/> </zipfileset> <zipfileset dir="src/WEB-INF" prefix="WEB-INF"> <include name="jboss-web.xml"/> </zipfileset> <zipfileset dir="bin" prefix="WEB-INF/classes" includes="tutorial/web/*.class"/> <zipfileset dir="src/docroot"/> </jar> </target> <target name="N65616" description="FiboApp.ear" > <jar destfile="FiboApp.ear"> <zipfileset dir="src/META-INF" prefix="META-INF"> <include name="application.xml"/> </zipfileset> <zipfileset dir="." prefix="/Tutorial/FiboEJB.jar"> <include name=""/> </zipfileset> <zipfileset dir="." prefix="/Tutorial/FiboWeb.war"> <include name=""/> </zipfileset> </jar> </target> </project>
thanks,
carl -
7. Re: Fibo-tutorial -- I cannot run it???
esgargs Aug 8, 2006 4:17 AM (in response to jdidboss)I, too, cannot run the tutorial, and have checked all the files.
My config is Eclipse 3.2 with the IDE 2.0a1 bundled download.
when I goto /fibo, I get a "directory listing for /", but nothing in it, even after running the server in debug mode and setting breakpoints.
Also, when I deploy the EAR file, I get the following exceptions:03:13:41,359 INFO [EARDeployer] Init J2EE application: file:/C:/Jboss/jboss-4.0.4.GA-ejb3/server/default/deploy/FiboApp.ear 03:13:41,687 INFO [EjbModule] Deploying Fibo 03:13:42,593 INFO [ProxyFactory] Bound EJB Home 'Fibo' to jndi 'ejb/Fibo' 03:13:42,625 INFO [EJBDeployer] Deployed: file:/C:/Jboss/jboss-4.0.4.GA-ejb3/server/default/tmp/deploy/tmp49434FiboApp.ear-contents/FiboEJB.jar 03:13:42,671 INFO [TomcatDeployer] deploy, ctxPath=/fibo, warUrl=.../tmp/deploy/tmp49434FiboApp.ear-contents/FiboWeb-exp.war/ 03:13:43,406 INFO [JBossCacheManager] init(): replicationGranularity_ is 0 and invaldateSessionPolicy is 2 03:13:43,421 ERROR [JBossCacheManager] JBossCacheService to Tomcat clustering not found java.lang.NoClassDefFoundError: org/jboss/cache/CacheException at org.jboss.web.tomcat.tc5.session.JBossCacheManager.init(JBossCacheManager.java:144) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy84.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.server.WebServiceDeployer.start(WebServiceDeployer.java:117) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy85.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:997) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) 03:13:43,421 ERROR [TomcatDeployer] Failed to setup clustering, clustering disabled. Exception: org.jboss.web.tomcat.tc5.session.ClusteringNotSupportedException: JBossCacheService to Tomcat clustering not found at org.jboss.web.tomcat.tc5.session.JBossCacheManager.init(JBossCacheManager.java:150) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:332) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy84.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.server.WebServiceDeployer.start(WebServiceDeployer.java:117) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy85.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:997) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) 03:13:43,500 INFO [EARDeployer] Started J2EE application: file:/C:/Jboss/jboss-4.0.4.GA-ejb3/server/default/deploy/FiboApp.ear
Someone suggest something!
Thanks -
8. Re: Fibo-tutorial -- I cannot run it???
ashishjain Aug 15, 2006 8:35 AM (in response to jdidboss)I am facing the similar problem while deploying the FiboBean.
I am using JBOSS SERVER 4.0.4 and JBOSS ID 1.5
I build FiboBean under J2EE 1.4 project with EJB specification as 2.0 and rest everything as per article.
When I right click on "FiboApp.ear" file and select
Deployment > Deploy To...
I get the exception that17:59:46,481 INFO [TomcatDeployer] deploy, ctxPath=/test, warUrl=.../tmp/deploy/tmp25737test-exp.war/ 17:59:46,731 INFO [EARDeployer] Init J2EE application: file:/D:/setups/jboss/jboss-4.0.4.GA/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear 17:59:46,731 ERROR [MainDeployer] Could not initialise deployment: file:/D:/setups/jboss/jboss-4.0.4.GA/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear org.jboss.deployment.DeploymentException: No META-INF/application.xml found at org.jboss.deployment.EARDeployer.init(EARDeployer.java:133) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:861) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:464) at java.lang.Thread.run(Thread.java:595) 17:59:46,751 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@597ba83f { url=file:/D:/setups/jboss/jboss-4.0.4.GA/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear } deployer: org.jboss.deployment.EARDeployer@3c9616 status: null state: FAILED watch: file:/D:/setups/jboss/jboss-4.0.4.GA/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear altDD: null lastDeployed: 1155644986731 lastModified: 1155644988000 mbeans:
However application.xml file is there. -
9. Re: Fibo-tutorial -- I cannot run it???
oshima Aug 15, 2006 8:46 AM (in response to jdidboss)Hey !!!
By the look of things,the server cannot find your application.xml file that describes all the components of the ear file to the server. At the root of your ear file there must be a META-INF directory that contains the application.xml file.
Remember JBoss uses application.xml to deploy ur ear. -
10. Re: Fibo-tutorial -- I cannot run it???
ashishjain Aug 15, 2006 9:43 AM (in response to jdidboss)The structure of FiboApp.ear is :
It contains one META-INF folder and 2 files: FiboEJB.jar and FiboWeb.jar
Further META-INF contains application.xml.
Since I am using JBOSS IDE 1.5 and JBOSS Server 4.0 and it was written in the article,
I didnt build FiboEJB-client.jar and since I didn't build FiboEJB-cliet.jar I didn't include it in FiboWeb.jar
So, application.xml is there under META-INF inside FiboApp.ear
Also,
Under Descriptors, I choose "EAR 1.3 Deployment Descriptor" but I am using J2EE 1.4. Is this thing fine.
While XDoclet Configuration I choose EJB specification as 2.0 and servlet specification as 2.3
For jobswebxml subtask (while configuring XDoclet), I change specification to 4.0 from 3.0 as written in the article since I am using JBOSS server 4.0.
Please clarify the problem. -
11. Re: Fibo-tutorial -- I cannot run it???
oshima Aug 15, 2006 9:48 AM (in response to jdidboss)FiboWeb.jar ? Isnt this suppose to be a war file (FiboWeb.war) since its a web app not jar file?
-
12. Re: Fibo-tutorial -- I cannot run it???
ashishjain Aug 15, 2006 11:52 AM (in response to jdidboss)Ya its war file..
Typed wrongly in my previous message
So it is FiboWeb.war and not FiboWeb.jar. -
13. Re: Fibo-tutorial -- I cannot run it???
kayoumt Aug 15, 2006 2:46 PM (in response to jdidboss)I'm having exactly the same problem. I followed line-by-line Laurent Etiemble's tutorial.
I'm working with two machines : Windows XP (for the Eclispse-Jboss IDE), RHEL4 linux for the Jboss server (deployment).
Any idea ??? -
14. Re: Fibo-tutorial -- I cannot run it???
kovacjo Aug 27, 2006 2:00 AM (in response to jdidboss)Hi All,
I found the solution for the problem that was the initiator of this topic. In the application.xml the context root must be without leading slash ('/').
At least it worked for me.
Best regards to all of you.