[JBoss Seam] - Re: [OT] Seam and Tomahawk - lost property?
by gavin.king@jboss.com
anonymous wrote : Even if you had this experience in the past didn't mean that they are still true.
Fair enough, I'm willing to give you guys a chance.
anonymous wrote : And - what gives you the right to judge in such a drastic way.
What gives me the right is I'm the one people are asking for advice. If users ask you for advice, I believe it is your responsibility to tell them your honest opinion, ie, what you believe will help them have the most success on their project.
anonymous wrote : A search about "tomahawk" (using the search box in the right upper corner) brought up 6 hits, not *that* much, is it?
Ahem, the search is quite bad, there have of course been many more threads than that (probably more like 100).
anonymous wrote : Once in the past I expressed my personal feeling that Seam is too feature overloaded, immediately one of you guys campaign against me to stop saying such things. And I stopped.
I have no idea who "one of you guys" refers to, but it certainly wasn't me, and I have not heard of any such "campaign" or anything else about this episode.
anonymous wrote : I learned its your decision what you put into Seam.
Sure. And its your perfect right to critique my decisions.
anonymous wrote : So instead of forcing people not to use tomahawk redirect them to our user form
OK, I'll try that, but if we keep seeing the large number of problems we were seeing before, I'm going to have to reinstate the previous policy.
You see, in light of the bugs we've seen in the past, *someone* is going to have to test Seam+Tomahawk. I'm not going to do it because, frankly, the components offered in Tomahawk are not interesting to me and because I believe there are better alternatives. Are *you* guys going to take responsibility for this testing? If the answer is "no", then what's going to happen is that users will find the problems, and they will get frustrated with us because we don't want to take responsibility for them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993809#3993809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993809
19 years, 4 months
[JBoss jBPM] - Re: SuperState DB tests - the fix throws Exception when one
by gmournos
I applied the above fix but then undeploying a process definion throws Excpetions.
The test case broken is:
public void testUndeploy() {
| ProcessDefinition procDef = new ProcessDefinition("testUndeploy");
| State s = new State("testnode");
| procDef.addNode(s);
| jbpmContext.deployProcessDefinition(procDef);
| newTransaction();
| ProcessDefinition pd = jbpmContext.getGraphSession().findLatestProcessDefinition("testUndeploy");
| jbpmContext.getGraphSession().deleteProcessDefinition(pd);
| newTransaction();
| }
|
The hibernate query that creates the problem is:
Hibernate:
| update
| JBPM_NODE
| set
| PROCESSDEFINITION_=null,
| NODECOLLECTIONINDEX_=null
| where
| PROCESSDEFINITION_=?
| and (
| nodes0_.SUPERSTATE_ is null
| )
|
Finally the exception thrown is:
12:55:04,534 [main] WARN JDBCExceptionReporter - SQL Error: 904, SQLState: 42000
| 12:55:04,534 [main] ERROR JDBCExceptionReporter - ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| 12:55:04,534 [main] WARN JDBCExceptionReporter - SQL Error: 904, SQLState: 42000
| 12:55:04,550 [main] ERROR JDBCExceptionReporter - ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| 12:55:04,550 [main] ERROR AbstractFlushingEventListener - Could not synchronize database state with session
| org.hibernate.exception.SQLGrammarException: Could not execute JDBC batch update
| at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
| at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249)
| at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:92)
| at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)
| at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:218)
| at org.hibernate.persister.collection.AbstractCollectionPersister.remove(AbstractCollectionPersister.java:1030)
| at org.hibernate.action.CollectionRemoveAction.execute(CollectionRemoveAction.java:28)
| at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
| at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
| at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
| at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
| at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
| at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:162)
| at org.jbpm.svc.Services.close(Services.java:211)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
| ....
| Caused by: java.sql.BatchUpdateException: ORA-00904: "NODES0_"."SUPERSTATE_": invalid identifier
|
| at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
| at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8739)
| at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)
| at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
| at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993807#3993807
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993807
19 years, 4 months