[JBoss Seam] - seam-gen error (generate-entities did not work)
by grdzeli_kaci
hi all,
seam version : 1.1.6 GA (i got it from CVS few days ago)
jboss version : 4.0.5 GA
ant version : 1.7.0
os version : SUSE LINUX 10.1 (i586)
java version : 5.0
i tryed to use seam gen template,
fierst i did seam setup, then seam new-project, all works fine now i want generate entities but i got an error:
| paatal@paatal:~/InstalledPrograms/jboss-seam-1.1.6.GA> ./seam generate-entities
| Buildfile: build.xml
|
| validate-workspace:
|
| validate-project:
|
| generate-entities:
| [hibernate] Executing Hibernate Tool with a JDBC Configuration (for reverse engineering)
| [hibernate] 1. task: hbm2java (Generates a set of .java files)
| [hibernate] 23-Feb-07 1:48:19 AM org.hibernate.cfg.Environment <clinit>
| [hibernate] INFO: Hibernate 3.2 cr4
| [hibernate] 23-Feb-07 1:48:19 AM org.hibernate.cfg.Environment <clinit>
| [hibernate] INFO: hibernate.properties not found
| [hibernate] 23-Feb-07 1:48:19 AM org.hibernate.cfg.Environment buildBytecodeProvider
| [hibernate] INFO: Bytecode provider name : cglib
|
| BUILD FAILED
| java.lang.NoClassDefFoundError: org.hibernate.bytecode.cglib.BytecodeProviderImpl
|
| Total time: 3 seconds
|
|
any idea ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020472#4020472
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020472
19Â years, 2Â months
[JBoss jBPM] - Re: jpdl-3.2.Beta2: how to access variable from task form in
by avbentem
"cdart_rrr" wrote : looks to be a bug in org.jbpm.jpdl.xml.JpdlXmlReader in resolveTransitionDestination() (l 805 of my version of 3.2beta2). It tries to get the expression from the text of element - if null it then goes to try to get it from the expression attribute. Only trouble is the text is returned from getTextTrim() as "" rather than null so you never get to look at the attribute.
Ok, it's even a bit more sophisticated. In the current version 1.7 (committed February 7th) yet another attribute is taken into account: attribute decision on the element transition. I did not know that! In fact, this has been like this since earlier versions. Your bug is now at line 745; http://fisheye.jboss.com/browse/JBPM/jbpm.3In /jpdl/jar/src/main/java/org/jbpm/jpdl/xml/JpdlXmlReader.java?r=1.7
739 String condition = transitionElement.attributeValue("condition");
| 740 if (condition==null) {
| 741 Element conditionElement = transitionElement.element("condition");
| 742 if (conditionElement!=null) {
| 743 condition = conditionElement.getTextTrim();
| 744 // for backwards compatibility
| 745 if (condition==null) {
| 746 condition = conditionElement.attributeValue("expression");
| 747 }
| 748 }
| 749 }
Note that fixing this (or when using the element text rather than an attribute) will get the expression into the database, but then one still needs the additional check for isEmpty(), as explained in my earlier post, to actually evaluate the expression at runtime.
"cdart_rrr" wrote : Is cvs still there? (I noted your comment above about wrong cvs details).Right now, while writing this, I'm having no trouble connecting to :pserver:anonymous:@anoncvs.forge.jboss.com:/cvsroot/jbpm
Arjan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020465#4020465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020465
19Â years, 2Â months
[JBoss Seam] - Conversation @Begin
by quilleashm
Hi there,
I have a question about the implementation of @Begin. At the moment the @Begin is only done AFTER a bean method has completed it's invocation. Is there any reason why it is done like this rather than beginning the conversation before the method invocation. The only thing I could think of was if an exception occurs the conversation state would need to be rolled back.
If I do a manual Redirect.execute() in methods which have @Begin(nested = true) then the nested conversation id is not correctly propogated on the redirect as the nested conversation is not begun until after the method completes, by which point the redirect has happened.
Would it be possible to change this behaviour (this also seems more natural to me to begin the conversation before the method), or would this have too many breaking side-effects?
Cheers.
Mike.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020464#4020464
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020464
19Â years, 2Â months
[Messaging, JMS & JBossMQ] - EJB3 Cluster application JMS Error-JBoss 4.0.5GATrailBlazer
by mp123
Hello JBoss Folks,
While I'm trying to deploy the clusterstore(EJB3TrailBlazer POJO Clustering demo)application, getting the following Error.
I'm using JBoss 4.0.5.GA - EJB3 Cluster configuration in HP-UX system.
09:54:12,228 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@871dcc(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)769d7a destination=queue/clusterstore isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
| javax.jms.JMSSecurityException: User: null is NOT authenticated
| at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230)
| at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66)
| at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613)
| at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172)
| at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:165)
| at org.jboss.mq.Connection.authenticate(Connection.java:1065)
| at org.jboss.mq.Connection.<init>(Connection.java:252)
| at org.jboss.mq.Connection.<init>(Connection.java:323)
| at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116)
| at org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137)
| at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:108)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
| at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:359)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:305)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:589)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
|
|
Please help where I did wrong??
Thanks in advance,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020463#4020463
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020463
19Â years, 2Â months