-
1. Re: JBoss Seam, a great product that doesn't work :(
ericjava Jan 25, 2008 4:25 PM (in response to lazar.mihai)I must say, Seam is not easy to get started with. I have been using it for a year and I'm still figuring things out. It's great when you get it going, but until you have some experience with it it can be very frustrating to figure out, "why is this not working."
When I'm stuck with debugging something like what you have, what I do is I take a known-working application, and I incrementally transform the known-working app into the app you are trying to get working. That is tedious but it will find the problem. -
2. Re: JBoss Seam, a great product that doesn't work :(
nickarls Jan 25, 2008 4:37 PM (in response to lazar.mihai)Start with Eclipse Europa J2EE version and add JBoss Tools 2, it has wizards for a simple project you can then start fiddling around with.
Seam is an evolution along a long line of web development frameworks and ideas. If you are new to this stuff it can probably feel like trying to drink from a fire hose but that doesn't mean that the product itself "doesn't work". -
3. Re: JBoss Seam, a great product that doesn't work :(
oberiko Jan 25, 2008 4:51 PM (in response to lazar.mihai)Agreed with above.
For those of us coming from a more simple model (i.e. basic Struts, or even just plain Java development), having to deal with all the things Seam pulls together is a pretty tough start.
I've been playing with it for a week and am just now starting to get the hang of what's going... or at least so I think.
Still, when you look at what you're saving by not having to use each component individually, and all the "plumbing code" you are spared, it's tough to go back.
Big bonus in that, being an application stack instead of a web framework, it's not as likely to go obsolete any time soon. -
4. Re: JBoss Seam, a great product that doesn't work :(
jbalunas Jan 25, 2008 5:10 PM (in response to lazar.mihai)I'll see what I can help you with.
Could you post some more details on the issues you are seeing?
Did you get the basic seam-gen app working - but just adding on failed?
Is it a WAR deployment or an EAR deployment?
Have you tried a diff with the registration example - some times you might be missing a attribute or a simple typo?
-Jay -
5. Re: JBoss Seam, a great product that doesn't work :(
lazar.mihai Jan 25, 2008 6:40 PM (in response to lazar.mihai)Wow, thanks a lot for the prompt reply :).
I had RHDS RC1 and eclipse jee with jboss tools.. What I'm doing is this. I'm making a Seam Web Project with JBoss Seam 2.0.0.GA on JBoss AS 4.2.0.GA
The template works fine. When I access Generate Entities from the tool i get a n error saying something about ejb3deployer not beeing initialized.
Because of the errors I tried going back to the command line. The template worked fine.
Anyway.. I'm now doing JBoss AS 4.2.0.GA with JBoss Seam 1.2.1.GA looks like it works now. :-??
Also, what is that about Seam 2.0 being a technology preview ? Could that be the cause of the errors I get with deployment?
I'm pretty sure that when I was writting by hand I left out some configurations.
In conclusion it seems to be working for now. With Jboss Seam 1.2.1
Compared with Stripes, Seam still takes to much out of me, although if the facts on paper are right it will be worth it, at least that I'm hoping for.
Also found http://in.relation.to/Bloggers/Everyone/Tag/Seam, and it provided with some help.
If you know why I get that ejb3deployer error, or the most recent one
ERROR [SeamLoginModule] Error invoking login method
javax.el.PropertyNotFoundException: Target Unreachable, identifier 'authenticator' resolved to null
In the meanwhile I'll be playing with what works, don't think there is much more I can do right now :). -
6. Re: JBoss Seam, a great product that doesn't work :(
jbalunas Jan 25, 2008 7:04 PM (in response to lazar.mihai)I'm just trying to figure out exactly what went wrong.
You created a web project - so it is deploying as a WAR - right?
Then you ran generate-entities and got the error?
I'll have to look into the code a bit - but I believe the generate-entities will not work with a WAR deployment because you are generating entiy beans.
Try generating an EAR application, and then running generate-entities.
Also what does your Authenticator class look like, and your components.xml. The error is saying that it can't find your Authenticator class/component. -
7. Re: JBoss Seam, a great product that doesn't work :(
ericjava Jan 25, 2008 7:26 PM (in response to lazar.mihai)It's definitely better to do an EAR, not a WAR. Seam + EJB3 can be embedded in a WAR but the whole thing is not designed for that usage. It's designed to live in a container. JBoss AS in particular.
-
8. Re: JBoss Seam, a great product that doesn't work :(
lazar.mihai Jan 26, 2008 5:37 AM (in response to lazar.mihai)
You created a web project - so it is deploying as a WAR - right?
Yes it's a war.
Also what does your Authenticator class look like, and your components.xml. The error is saying that it can't find your Authenticator class/component.package org.domain.Simple.session; import org.jboss.seam.annotations.In; import org.jboss.seam.annotations.Logger; import org.jboss.seam.annotations.Name; import org.jboss.seam.log.Log; import org.jboss.seam.security.Identity; @Name("authenticator") public class Authenticator { @Logger Log log; @In Identity identity; public boolean authenticate() { log.info("authenticating #0", identity.getUsername()); //write your authentication logic here, //return true if the authentication was //successful, false otherwise identity.addRole("admin"); return true; } }
<?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:persistence="http://jboss.com/products/seam/persistence" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:bpm="http://jboss.com/products/seam/bpm" xmlns:security="http://jboss.com/products/seam/security" xmlns:mail="http://jboss.com/products/seam/mail" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.0.xsd http://jboss.com/products/seam/persistence http://jboss.com/products/seam/persistence-2.0.xsd http://jboss.com/products/seam/drools http://jboss.com/products/seam/drools-2.0.xsd http://jboss.com/products/seam/bpm http://jboss.com/products/seam/bpm-2.0.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-2.0.xsd http://jboss.com/products/seam/mail http://jboss.com/products/seam/mail-2.0.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.0.xsd"> <core:init debug="true" jndi-pattern="@jndiPattern@"/> <core:manager concurrent-request-timeout="500" conversation-timeout="120000" conversation-id-parameter="cid"/> <persistence:managed-persistence-context name="entityManager" auto-create="true" entity-manager-factory="#{SimpleEntityManagerFactory}"/> <persistence:entity-manager-factory name="SimpleEntityManagerFactory" persistence-unit-name="Simple"/> <drools:rule-base name="securityRules"> <drools:rule-files><value>/security.drl</value></drools:rule-files> </drools:rule-base> <security:identity authenticate-method="#{authenticator.authenticate}" security-rules="#{securityRules}" remember-me="true"/> <event type="org.jboss.seam.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.postAuthenticate"> <action execute="#{redirect.returnToCapturedView}"/> </event> <mail:mail-session host="localhost" port="2525" username="test" password="test" /> <!-- For use with jBPM pageflow or process management --> <!-- <bpm:jbpm> <bpm:process-definitions></bpm:process-definitions> <bpm:pageflow-definitions></bpm:pageflow-definitions> </bpm:jbpm> --> </components>
OK this is it. I'll head out and generate an EAR.
Also do I make of this ?--- Packages waiting for a deployer --- org.jboss.deployment.DeploymentInfo@86b0359d { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/as-ear.ear/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/as-ear.ear/ altDD: null lastDeployed: 1201379415187 lastModified: 1201249808750 mbeans: org.jboss.deployment.DeploymentInfo@4f36fae6 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/jboss-seam-dvd.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/jboss-seam-dvd.ear altDD: null lastDeployed: 1201379415281 lastModified: 1201379415281 mbeans: org.jboss.deployment.DeploymentInfo@5a00c1c7 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/numberguess.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/numberguess.ear altDD: null lastDeployed: 1201379415546 lastModified: 1201379415546 mbeans: org.jboss.deployment.DeploymentInfo@8aeb7948 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/build.xml } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/build.xml altDD: null lastDeployed: 1201379415562 lastModified: 1201379415562 mbeans: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@9fa5ed2b { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/diff-prod-ds.xml } deployer: org.jboss.deployment.XSLSubDeployer@6c08b2 status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=diffDatasource state: FAILED watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/diff-prod-ds.xml altDD: null lastDeployed: 1201379381421 lastModified: 1201379381406 mbeans: org.jboss.deployment.DeploymentInfo@dfc49f49 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Damm.war/ } deployer: MBeanProxyExt[jboss.web:service=WebServer] status: Deployment FAILED reason: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Damm.war/ deployment failed state: FAILED watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Damm.war/WEB-INF/web.xml altDD: null lastDeployed: 1201379383296 lastModified: 1201336427593 mbeans: org.jboss.deployment.DeploymentInfo@4930c95a { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Simple2.war/ } deployer: MBeanProxyExt[jboss.web:service=WebServer] status: Deployment FAILED reason: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Simple2.war/ deployment failed state: FAILED watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Simple2.war/WEB-INF/web.xml altDD: null lastDeployed: 1201379402093 lastModified: 1201379351796 mbeans: org.jboss.deployment.DeploymentInfo@b2abf990 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/tomcattest.war/ } deployer: MBeanProxyExt[jboss.web:service=WebServer] status: Deployment FAILED reason: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/tomcattest.war/ deployment failed state: FAILED watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/tomcattest.war/WEB-INF/web.xml altDD: null lastDeployed: 1201379409671 lastModified: 1201342432734 mbeans: org.jboss.deployment.DeploymentInfo@86b0359d { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/as-ear.ear/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/as-ear.ear/ altDD: null lastDeployed: 1201379415187 lastModified: 1201249808750 mbeans: org.jboss.deployment.DeploymentInfo@4f36fae6 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/jboss-seam-dvd.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/jboss-seam-dvd.ear altDD: null lastDeployed: 1201379415281 lastModified: 1201379415281 mbeans: org.jboss.deployment.DeploymentInfo@5a00c1c7 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/numberguess.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/numberguess.ear altDD: null lastDeployed: 1201379415546 lastModified: 1201379415546 mbeans: org.jboss.deployment.DeploymentInfo@8aeb7948 { url=file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/build.xml } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/build.xml altDD: null lastDeployed: 1201379415562 lastModified: 1201379415562 mbeans: --- MBeans waiting for other MBeans --- ObjectName: jboss.ws:service=DeployerInterceptorEJB21 State: CONFIGURED I Depend On: jboss.ejb:service=EJBDeployer ObjectName: jboss.ws:service=DeployerInterceptorEJB3 State: CONFIGURED I Depend On: jboss.ejb3:service=EJB3Deployer ObjectName: jboss.web.deployment:war=Damm.war,id=-540762295 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Damm.war/ deployment failed ObjectName: jboss.web.deployment:war=Simple2.war,id=1227934042 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Simple2.war/ deployment failed ObjectName: jboss.web.deployment:war=tomcattest.war,id=-1297352304 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/tomcattest.war/ deployment failed --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.web.deployment:war=tomcattest.war,id=-1297352304 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/tomcattest.war/ deployment failed ObjectName: jboss.web.deployment:war=Simple2.war,id=1227934042 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Simple2.war/ deployment failed ObjectName: jboss.ejb3:service=EJB3Deployer State: NOTYETINSTALLED Depends On Me: jboss.ws:service=DeployerInterceptorEJB3 ObjectName: jboss.ejb:service=EJBDeployer State: NOTYETINSTALLED Depends On Me: jboss.ws:service=DeployerInterceptorEJB21 ObjectName: jboss.web.deployment:war=Damm.war,id=-540762295 State: FAILED Reason: org.jboss.deployment.DeploymentException: URL file:/D:/rhdevstudiorc1/jboss-eap/jboss-as/server/default/deploy/Damm.war/ deployment failed
-
9. Re: JBoss Seam, a great product that doesn't work :(
lazar.mihai Jan 26, 2008 6:10 AM (in response to lazar.mihai)EAR deployment failed :( with something like the message I wrote saying EJBDeployer NotYETINSTALLED
-
10. Re: JBoss Seam, a great product that doesn't work :(
jbalunas Jan 26, 2008 5:03 PM (in response to lazar.mihai)From my quick look at it - something is up with your JBoss install. It looks like some of the errors that you posted do not have anything to do with the Seam apps.
I can't really look into that more right now - if I get a chance I'll look on Monday.
Do other applications, or the Jboss console work with your install?
Also try a clean install of JBoss. Because the install of JBoss is so easy (just unzip) it is sometimes easier to just do a quick install and try the changes.
-Jay -
11. Re: JBoss Seam, a great product that doesn't work :(
lazar.mihai Jan 26, 2008 6:30 PM (in response to lazar.mihai)Thanks allot Jay. I did do a clean install of JBoss AS, and it finally started to work :).
I was using RHDS RC1, and it had a JBoss 4.2.0_CP1. And I was deploying to it. EAR deployment still doesn't work for some reason. War works just fine. Already did some cool things and it all took so little time.. I can hardly believe it.
I'm now using Seam 2.0.0.GA, Eclipse JEE + JBoss Tools and JBoss AS 4.2.2.GA.
When deploying an EAR this is what it says :01:28:04,687 ERROR [MainDeployer] Could not initialise deployment: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asdwe-ear.ear/ org.jboss.deployment.DeploymentException: No META-INF/application.xml found at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.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 $Proxy9.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.GeneratedMethodAccessor3.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 $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.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:508) at java.lang.Thread.run(Unknown Source) 01:28:04,687 INFO [EARDeployer] Init J2EE application: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asqe-ear.ear/ 01:28:04,687 ERROR [MainDeployer] Could not initialise deployment: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asqe-ear.ear/ org.jboss.deployment.DeploymentException: No META-INF/application.xml found at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.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 $Proxy9.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.GeneratedMethodAccessor3.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 $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.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:508) at java.lang.Thread.run(Unknown Source) 01:28:04,687 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@caf559ae { url=file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/SOS-ear.ear/ } deployer: org.jboss.deployment.EARDeployer@97e3a5 status: null state: FAILED watch: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/SOS-ear.ear/ altDD: null lastDeployed: 1201426076687 lastModified: 1201418577031 mbeans: org.jboss.deployment.DeploymentInfo@d985dd85 { url=file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asdwe-ear.ear/ } deployer: org.jboss.deployment.EARDeployer@97e3a5 status: null state: FAILED watch: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asdwe-ear.ear/ altDD: null lastDeployed: 1201426084687 lastModified: 1201418588015 mbeans: org.jboss.deployment.DeploymentInfo@af60f8e7 { url=file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asqe-ear.ear/ } deployer: org.jboss.deployment.EARDeployer@97e3a5 status: null state: FAILED watch: file:/D:/ajboss/jboss-4.2.2.GA/server/default/deploy/asqe-ear.ear/ altDD: null lastDeployed: 1201426084687 lastModified: 1201418580203 mbeans: --- MBeans waiting for other MBeans --- ObjectName: persistence.units:ear=Simple3-ear.ear,unitName=Simple3 State: NOTYETINSTALLED I Depend On: jboss.jca:name=Simple3Datasource,service=DataSourceBinding --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.jca:name=Simple3Datasource,service=DataSourceBinding State: NOTYETINSTALLED Depends On Me: persistence.units:ear=Simple3-ear.ear,unitName=Simple3 01:28:04,781 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 01:28:04,812 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 01:28:04,828 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 42s:485ms
Maybe U can figure this out. Thanks again. -
12. Re: JBoss Seam, a great product that doesn't work :(
lazar.mihai Jan 26, 2008 6:35 PM (in response to lazar.mihai):-?? How do I say this. The funny thing is .. after I do a post on the forum everything starts working as it should.
Must be the air or something, or maybe the late hour..
Although I get those weird Error messages this time around the application started nicely. Did the Seam Generate Entities and worked again. To be honest I think we can close this topic since you helped me got started.
A milion thanks and enjoy the rest of the weeked :-h -
13. Re: JBoss Seam, a great product that doesn't work :(
ericjava Jan 26, 2008 6:36 PM (in response to lazar.mihai)Well, it says "No META-INF/application.xml found". Is there an application.xml file? There needs to be one.