[JBoss jBPM] - jPDL Designer 3.1.0SP1 and Eclipse 3.3: ClassCastException o
by Bish
I've recently downloaded the jPDL suite for 3.2.2, but I have a problem running the designer in Eclipse.
Specifically, I downloaded jbpm-jpdl-suite-3.2.2.zip and extracted to c:\jbpm-jpdl-3.2.2
If the directory names are to be believed, then the designer version in the 3.2.2 suite is 3.1.0SP1. (C:\jbpm-jpdl-3.2.2\designer\eclipse\plugins\org.jbpm.gd.jpdl_3.1.0.SP1)
Then I followed the instructions in c:\jbpm-jpdl-3.2.2\designer\readme.html and downloaded eclipse-SDK-3.3-win32.zip then ran the "ant install" target. Then I started going through the steps in the getting started doc on the wiki.
Where the getting started guide says "double click on gpd.xml" I find the file opens in the default XML browser rather than the jBPM Process Designer. If I tell it to open with the Process Designer then I get a ClassCastException as shown in the stack-trace below (from Eclipse .log file).
I _can_ open the processdefinition.xml file with the Process Designer, but if I right click on the nodes I don't get the correct context menu.
I noticed someone on the Getting Started Documentation thread had the same issue but no solution was posted. Anyone else seen it or solved it?
Cheers,
Ian.
!ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685
!MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
!STACK 0
java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095562#4095562
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095562
18Â years, 9Â months
[JCA/JBoss] - Merge xa and no-xa Connections - CMT problem
by grdzeli_kaci
hi all,
i have two database
1. Oracle 10g
2. Oracle Timesten In Memory Database
i tried to use xa transactions with them and i had not any problem with distributed transactions.
problem appears after i have configured replications on timesten database.
anonymous wrote :
| Use of distributed (XA) transactions in the presence of replication is highly problematic. It is impossible for the database to guarantee consistency and recoverability since it only sees part of the 'big picture'. This is true for all databases and vendors. Different vendors approach this issue in different ways. Some document the (many, serious) potential issues but allow you to mix XA and replication. Some ignore the issues and permit you to use them (usually leading to subtle and serious problems after a system has been live for months or years). TimesTen takes a more defensive approach and forbids you to mix replication and XA thereby avoiding all the nasty problems that will inevitably arise.
|
| Note that XA transactions are at best very slow and more typically are really, really slow so if you are using any significant amount of XA transactions then there is probably no value in using TimesTen. If you only use XA for a very small part of the application then there are often better, and faster, approaches that can be used.
|
and i got an error like this :
| WorkerThread#0[192.168.9.151:40657]*JdbcOdbc.createSQLException:Reason = [TimesTen][TimesTen 7.0.2.0.0 ODBC Driver][TimesTen]TT11036: XA transactions may not be started while replication is configured -- file "xaStart.c", lineno 219, procedure "sbXAStart"; SQLstate = S1000; VendorCode = 11036
| java.sql.SQLException: [TimesTen][TimesTen 7.0.2.0.0 ODBC Driver][TimesTen]TT11036: XA transactions may not be started while replication is configured -- file "xaStart.c", lineno 219, procedure "sbXAStart"
| at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:9337)
| at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:9471)
| at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:9436)
|
i remove xa for timesten and try to use non-xa datasource, but now i can't merge these two connections.
of course i use container managed transaction.
how i can manage two database connections ?
also i could not use bean managed transactions for some reason.
any idea will be appreciated.
_________________
Regards,
Paata
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095561#4095561
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095561
18Â years, 9Â months
[JBoss/Spring Integration] - NotSerializableException: AbstractEntityManagerFactoryBean$M
by alpheratz-jb
Question: has anyone seen the following before?
[This is with 'All' config JBoss 4.2.1GA. and Spring 2.1M4 and Toplink Essentials JPA 2.0-b58g]
| 14:36:08,158 ERROR
| [org.jboss.web.tomcat.service.session.JBossCacheService]
| externalizeSession(): exception occurred externalizing session
| SessionBasedClusteredSession[id:ZhOYIR+Pdkv7GkUG3bjcsg** lastAccessedTime: 1192509366298 version: 3 lastOutdated: 0]
| java.io.NotSerializableException:
| org.springframework.orm.jpa.AbstractEntityManagerFactoryBean$ManagedEntityManagerFactoryInvocationHandler
| at
| java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
| at
| java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
| at
| java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream
|
Why should the EntityManager stuff be serialized into the session anyway...doesn't make any sense to me!
As always, enlightenment very gratefully accepted.
Cheers,
Alph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095560#4095560
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095560
18Â years, 9Â months